OTSchoolPrereqs

OT School Recommendation Letters: Organize Requests and Receipts

Recommendation planning has two parts: choosing people who meet your schools' requirements and keeping the submission process visible. A person agreeing to help is an important first step, but it is not the same as an evaluation arriving in the application system.

Build a school-by-school requirement map before sending formal requests. Then maintain a separate tracker for each evaluator's progress.

Map the required roles

Record the number of recommendations, any required professional or academic relationships, the destination and the deadline. Keep optional additional recommendations separate from required ones.

Liaison advises applicants to check program requirements before selecting evaluators. Its current OTCAS instructions describe electronic submission by evaluators themselves and a request range of three to five evaluations. School requirements still need individual review. OTCAS evaluations

If a school's published requirement appears different from the platform's request rules, clarify how to proceed. Do not assume one instruction cancels the other.

Ask before sending the formal invitation

Discuss whether the person is willing and able to provide the requested evaluation by your target date. Confirm the appropriate email address and explain the submission route. This gives them a chance to decline before a time-sensitive request sits unanswered.

Prepare a concise reference packet if they want one: your current CV, program list, deadlines and a factual reminder of your work together. The evaluator should create and submit their own evaluation. Your organizer's role is to track the process.

Use clear statuses

Status Meaning
Considering You have not asked the person yet
Agreed They have agreed to participate
Request sent The formal invitation has been issued
In progress They have acknowledged or begun the evaluation
Received The destination shows completion
Follow-up needed A problem or unanswered question needs attention

Record the date and source of each status. A verbal assurance that a letter was submitted is useful, but check the portal if that is the official destination.

Plan respectful follow-ups

Agree on a personal target that leaves time before the school deadline. Keep a follow-up date and note any scheduling constraints the evaluator shares. A concise reminder can include the deadline and submission route without repeating your whole application story.

If an invitation was not received, verify the address and use the system's instructions for resending or correcting the request. Do not repeatedly create new requests without understanding what happens to the existing one.

Resolve optional-letter questions early

An extra evaluation can introduce a new dependency. Before requesting one close to a deadline, check whether the program wants it, how it should be submitted and whether a pending optional item affects review. Record the answer instead of relying on another applicant's experience.

Close the loop after receipt

Confirm that required evaluations reached the right destination and thank the people who helped. Keep the relationship and submission history for your own records, but do not assume a letter or permission carries automatically into a new cycle.

Add the most time-sensitive recommendation task to your application timeline today. Keep the supporting CV organized with the document version guide.

Review the linked sources for your intended school, pathway and application cycle.