OTCAS Application Timeline: Plan Backward From Each Deadline
An OT application timeline should begin with the exact deadline for each program and what that deadline requires. A date alone does not explain whether you need to submit, have all materials received, or reach a verified status. Those distinctions determine when you need to finish your part of the work.
Build your timeline around the earliest relevant requirement, then add room for tasks controlled by other people. Your target date is a planning tool; the official deadline remains the school's rule.
Capture the meaning of every date
For each school, record the cycle, start term, deadline type, date, stated time zone and source. Include separate dates for priority review, supplemental materials and scholarships where applicable. If wording is unclear, ask the school rather than assigning your own interpretation.
Liaison describes verification as a process that begins after the application reaches complete status and currently says it can take up to ten business days. That processing estimate is not a guarantee that submitting ten days before every school deadline is sufficient. OTCAS verification
Work backward through dependencies
List the tasks that cannot happen immediately: transcript delivery, evaluator completion, a course-equivalency answer, final grades or a required verification form. Put these on the calendar before polishing tasks you control yourself.
The following is a planning example, not an official OTCAS schedule:
| Planning stage | Main work |
|---|---|
| Early preparation | Confirm schools, requirements and unresolved eligibility questions |
| Before the busiest submission period | Request materials and agree on recommender target dates |
| Draft-completion target | Assemble student-authored documents and school-specific responses |
| Final review target | Check files, course records, destinations and missing materials |
| After submission | Monitor status, save receipts and respond to requests |
Choose actual dates based on your programs and the time each dependency requires. Liaison's quick-start guide is a useful process reference when building that schedule.
Use two calendars, or two clearly labeled date types
Keep official dates visually distinct from your own targets. A personal target can move when you revise your plan. A school deadline should change only when you have new authoritative information.
For a fictional program, you might record an official verified deadline of November 15 and a much earlier personal submission target. If a transcript is missing, the task is to resolve that dependency. Moving your personal target closer to November 15 does not remove the problem.
Monitor the application after you submit
Submission is a milestone, not the end of the workflow. Record the portal's actual status, the time you checked it and any missing materials. Keep supplemental portals visible even if the main application is progressing normally.
When a status seems delayed, identify the responsible party. A school can clarify its deadline policy; the application service can answer a processing question. Give each inquiry a follow-up date so it does not disappear into email.
Review your timeline every week
Look for approaching deadlines, tasks blocked by someone else and newly changed school instructions. Save the new source if a deadline changes. Do not overwrite the old record without noting why your plan changed.
Start by adding your earliest school's official deadline and its meaning. Then schedule the three dependencies most likely to take time. Use the recommendation tracker and application checklist to fill in the rest.