OT School Application Checklist: Organize Every Requirement
An OT school application checklist works best when every item belongs to a particular program and application cycle. A general list can remind you to request transcripts. It cannot tell you whether one school needs a supplemental form, whether another accepts a course you are taking next spring, or which version of your resume you submitted.
Start with a school list, then give each school its own requirement checklist. Keep shared preparation—your coursework, experience history and document library—in one place so you can connect it to several applications without recreating it.
Create one record for each application
Record the institution, campus, degree, intended start term and application route. “University A” is too broad if it offers several entry pathways. Add the official admissions link and the date you reviewed it.
AOTA describes OTCAS as a shared application service for participating programs. Your planning system should also accommodate school portals and additional requirements. A task completed in one portal is not automatically complete everywhere.
Use a small set of understandable statuses: not started, in progress, waiting on someone else, ready to submit, submitted and confirmed received. Include “needs clarification” for requirements you cannot yet interpret.
Organize six groups of work
| Group | What to track | Evidence of completion |
|---|---|---|
| School research | Degree, format, location, cost, accreditation source | Saved comparison and official links |
| Coursework | Required subjects, labs, grades, recency, pending classes | Transcript entry or written course approval |
| Experiences | Observation, employment, volunteering, settings | Accurate log and required verification |
| Documents | CV/resume, statement, supplemental responses | Final file linked to its destination |
| Recommendations | Required roles, requests and due dates | Portal receipt/status |
| Submission and decisions | Deadlines, fees, interviews, offers | Receipt, invitation or decision letter |
The final column matters. “I asked my professor” and “the recommendation was received” are different milestones. Similarly, uploading a document into your organizer does not submit it to a school.
Turn missing items into next actions
Avoid vague tasks such as “finish prerequisites.” Write the next step you can actually take: “Send Program B the anatomy syllabus and ask whether the online lab is accepted.” Give that task an owner, a target date and a place to save the answer.
Here is a fictional example. You have completed statistics, but two schools describe the requirement differently. Mark the course completed in your academic record. In School A's checklist, link it to a confirmed requirement. In School B's checklist, leave the match awaiting approval. The same course can have different school-specific planning statuses.
Separate your target dates from official deadlines
Keep the published deadline and its meaning visible. Then choose an earlier personal target for finishing work. Record what must happen first: a final grade may be needed before a transcript request, while an official recommendation depends on another person's schedule.
Each week, review tasks due soon, unanswered questions and items waiting on someone else. A useful weekly review ends with a few specific actions. It should not require rereading every school website from scratch.
Make a final submission record
Before submitting, open each file from the actual upload location, compare it with the requirement and check the destination. After submitting, save the confirmation, date and exact file version. Continue monitoring outstanding materials and school communications.
Your first step today is small: choose one school and build its complete checklist. Once the structure works, add the others. For the two areas that usually need more detail, use the prerequisite matrix and deadline planning guide.