Upload up to 3 sources — a syllabus, timetable, plan, or schedule as a PDF, Word doc, slides, spreadsheet, text file, Google Drive file, or URL — pick the Calendar tile, and Scholarly generates an .ics file with one event per dated item, saved to your library and ready to import into Google Calendar, Outlook, or Apple Calendar. The Free plan includes one lifetime AI creation and one upload (8MB or 32 PDF pages). Premium ($30/mo or $144/yr) allows 10 AI creations per week and Laureate ($99/mo) allows 80.
Most schedules arrive as a PDF table or a paragraph of dates, and the usual fix is an evening of retyping them into a calendar one by one. Retyping is slow, and it is where deadlines get mistyped or skipped. The Calendar tile reads the document once and writes every dated item into a standard iCalendar file.
Because the generator is source-grounded, it only creates events for dates the document actually gives. A syllabus that lists a final exam date but no time produces an event without a time; a project plan that says "week of 3 March" does not get a fake 9am slot. Gaps stay visible so you can fill them from the real source, not from a guess.
The finished .ics is a real file in your Scholarly library, next to the syllabus or plan it came from. Import it into your own calendar, or share the file so a class, cohort, or project team all see the same dates.
The Calendar tile is deliberately strict. These are the boundaries to plan around.
Professionals use the Calendar tile for training schedules, certification roadmaps, project milestones, compliance deadlines, and onboarding plans — any document where the dates are the point. Generate once from the source document and everyone imports the same .ics instead of copying dates by hand.
Teams plans add shared libraries, so a training lead or project manager can keep the source plan, the calendar file, and the related SOPs together where the whole team can reach them.