Track what actually happened to each application

A useful application tracker tells you what you know and what to do next. It should not turn a saved draft into a submitted application or an unanswered message into a rejection. Record the employer's actual wording alongside your own next action.

You can use a spreadsheet, a private document or a notebook. The format matters less than keeping each role identifiable and updating the record when something happens. Avoid collecting information you will not use, especially confidential clinical material or other people's personal details.

Start with one application record

Include the employer, exact role title, campus or unit if specified, requisition identifier and source link. Two vacancies with similar titles may be separate applications. A general residency page may be background information rather than the application destination.

Add the date you last checked the source, the status you can establish, where the supporting record is stored and one next action. Keep a personal reminder date distinct from an employer deadline. The application calendar guide explains that distinction in more detail.

Do not store passwords, access codes or identity documents in a general tracking sheet. Keep any submitted files in your own private storage and refer to a recognizable filename or location.

A fictional sequence of events

The example below follows one invented application. Its dates and portal labels are illustrative, not a real employer's process.

On a narrow screen, scroll the table sideways to read each column.

The fourth event does not replace the interview event with “offer pending.” Nothing in the fictional evidence supports that conclusion. Keep a short event history rather than overwriting the record in ways that erase what actually happened.

Preserve unfamiliar status wording

If the portal says “in process,” save that wording and the date. Do not translate it into “shortlisted” unless the employer explains that meaning. If a posting disappears, record that observation without deciding that every applicant has been rejected.

When a message and portal seem inconsistent, keep both with their dates. Check the employer's guidance or ask the appropriate contact about the specific discrepancy. Repeatedly refreshing a page does not necessarily resolve what its label means.

For a clear rejection or withdrawal, record the event and close the next-action loop for that application. Do not delete the submitted version if it will help you understand what you sent or avoid duplicating work later.

Give the next action an owner and a reason

“Follow up” is easy to postpone because it is vague. “Check the portal after the employer's stated update point” is more concrete. So is “Ask the scheduling contact to confirm the time zone.” If there is no action to take now, say that; an active application does not always need another message.

Before contacting someone, check your event history. Have you already asked? Was a reply received elsewhere? Did the employer specify a route or waiting period? Use the interview follow-up guide to keep a status question concise.

Review the tracker without turning it into a score

Look for unfinished tasks, missing submission evidence and approaching confirmed dates. Avoid ranking yourself by the number of applications or interpreting a small set of outcomes as proof of what employers think about you.

Use the application desk for one requirement, evidence note and next action. It is a preparation tool, not a connection to employer portals or an automatic multi-application tracker. The free preview of The Residency Application Workshop shows the broader packet-planning process.