Quick answer
A semester is two different schedules, and trying to build them as one calendar is why the attempt usually fails. Class meeting times repeat on a weekly pattern (MWF 9:00, TT 14:00) and run to a term end date. Assignment and exam deadlines repeat on nothing at all: they are a flat list of one-off dates scattered across sixteen weeks. Build them as two calendars from the same syllabus, subscribe once, and both live on the phone next to everything else.
Try it with a real schedule
Calfeed turns it into a calendar link people can subscribe to.
Every syllabus hands over the whole semester on day one, and almost nobody gets it onto a phone. The dates sit in a PDF in a downloads folder, and the first missed deadline is the reminder that they were there all along.
The reason the attempt usually fails is that a semester is not one schedule. It is two, and they do not go in the same calendar.
A semester is two schedules
Class meeting times repeat. ENG 150 on Monday, Wednesday, Friday at 9:00, every week, until the term ends. One weekly pattern with an end date covers four months.
Assignment and exam deadlines repeat on nothing at all. A reading due the 4th, a paper the 19th, an exam the 30th, then nothing for two weeks. A flat list of one-off dates.
A weekly rule cannot hold a flat list, so putting both in one calendar means either re-typing every deadline by hand or losing them. Two calendars off the same syllabus, and each one is simple.
Start with the syllabus
The syllabus converter takes the schedule table as text. Copy the rows out of the document and paste them in.
If the syllabus is a file rather than something you can select, upload it: a PDF converts directly, and a printed one works from a photo. Copyable text is still the fastest route when you have it, because you can paste only the rows you actually want and skip the trimming step later.
Course code, day, time, room. That is usually the whole row, and it is enough.
Build the class meeting times
Describe the pattern the way the syllabus writes it:
"ENG 150 MWF 9:00 to 9:50 in ACAD 303, Aug 25 through Dec 12. PSY 105 TT 14:00 to 15:15 in L136, same dates."
A weekly pattern plus a term end date builds the whole semester at once. Room numbers and instructor names carry through into the event, which matters more than it sounds like it does in week one of a schedule you have not memorized yet.
Build the deadlines separately
Paste the assignment and exam rows into a second calendar. These have no pattern, so there is nothing to describe: it is a list of dates and what is due.
Namespace the titles by course. "Psych: Chapter 16 Reading" and "Accounting: Exam I" read correctly in a week view, where "Chapter 16 Reading" on its own does not tell you which class it belongs to. A term of deadlines is usually seventy or eighty entries with almost no repetition, and the titles are the only thing making them scannable.
Trim before publishing
Most syllabi contain more than anyone wants on a phone. Say what to drop, in plain words, before you publish:
- "Ignore Wednesdays, Saturdays, and Sundays."
- "Only the lab sections, not the lectures."
- "Nothing after November 7."
This is the step worth knowing about, because the instinct when the result is too long is to upload the syllabus again and hope for a shorter answer. The extraction is usually correct. There is just more of it than you want, and saying so is faster than starting over.
Check the preview against the syllabus before publishing. Year is the thing to spot-check: a syllabus that lists "Aug 25" with no year can land in the wrong one.
Subscribe, and share it if it helps
Publishing gives back a calendar link. Add it once in Apple Calendar, Google Calendar, or Outlook and the term sits alongside everything else on the phone.
The link is stable, so it is worth sending to anyone else in the same section. One person turns the syllabus into a calendar and everybody else subscribes to it.
Edits reach subscribers on the calendar app's own schedule: Apple checks about hourly, Google every 12 to 24 hours. When a due date moves the night before, message the group as well rather than trusting the refresh to be quick enough.