Track OT Supplemental Essays Without Mixing Up Schools or Prompts
School-specific responses are easy to confuse when several prompts sound similar. A clear tracker should connect each response to one school, one prompt and one application cycle. That lets you reuse your preparation notes without accidentally treating two different requirements as identical.
Keep the shared statement and supplemental responses separate. Their destinations and purposes may differ even when they discuss related experiences.
Capture the exact requirement
For every response, record the school/pathway, cycle, prompt, published limit, file or text-entry format, deadline and destination. Add the source or portal location where you found the instructions.
USC Chan's admissions page illustrates why this matters: it identifies program-specific writing and explains which statement its admissions team focuses on. Do not assume that completing a general statement resolves every school's writing requirement.
Avoid storing only a label such as “why OT essay.” It may conceal important differences in what schools ask you to address.
Give each response a stable identity
A useful internal label might be ProgramB_2027_Response02. Keep that identifier attached to the prompt, working file, feedback and final submission. If you rename the document title, you can still tell which requirement it belongs to.
| Tracker field | Example of its purpose |
|---|---|
| School and pathway | Prevent mixing campuses or degree options |
| Prompt and source | Preserve the actual question |
| Limit and format | Distinguish words, characters, pages and file types |
| Working version | Point to the student's current draft |
| Status and next action | Make remaining work visible |
| Submitted version | Preserve what the application received |
Organize themes without merging assignments
You may keep personal notes about experiences, interests and questions that could help you think through multiple prompts. Keep those notes in a separate library. Each final response still needs its own review against the actual instructions.
For a fictional example, two programs might ask about teamwork, but one asks for a specific event while the other asks how you would contribute to a cohort. Labeling both simply “teamwork” can hide the different tasks. The tracker should preserve the complete prompt.
Schedule work by effort and dependencies
Group tasks into drafting your own response, reviewing instructions, requesting feedback, revising and finalizing. Estimate which responses need the most attention. A small word limit does not necessarily mean a quick task.
Use a weekly view showing the next action rather than only the ultimate deadline. “Review feedback on Response 2” is easier to act on than “School B application incomplete.”
Run a destination check before submission
Check the school name, pathway, prompt, length and file version. Search for references to other institutions. If you paste into a portal, reread the pasted text and verify formatting and any portal count rather than assuming the editor's display transferred exactly.
Save a copy of the final response and submission confirmation. If instructions change, preserve both the old and new prompt records so you can understand which version you followed.
Start by adding every supplemental prompt from your active shortlist to one tracker. Then link each to your overall checklist and keep the shared statement in its own document record.