Skip to content

Application workflow · All applicants

How to track applications and plan follow-ups

Keep the vacancy, the CV you sent and the next action together. Record when you submit, add the employer’s reply or portal update, and set a follow-up date when the process calls for one. A useful tracker should let you return to an application without reconstructing what happened.

What to take with you

  • Record submission only when it is confirmed.
  • Keep each employer's version and reference.
  • Follow the stated timeline and channel.

Choose states that describe observable events

Use a short set of states such as saved, preparing, ready, submitted, interview, closed and withdrawn. Keep a downloaded CV under preparation until you submit it. Then save the portal confirmation or sent application email with the record, along with any next step or uncertainty you want to return to.

Avoid too many states that you cannot consistently distinguish. The tracker is there to reduce repeated checking. For each active application, keep the employer, role, source, reference, submitted date and next action. If a detail is unknown, write that explicitly rather than filling it with an assumption to make the row look complete.

Preserve the exact packet

Save the CV, cover letter and relevant answers that the employer received. Store them under a role-specific name or link them to the record. When an interview arrives, revisit that version. Your latest general CV may contain different examples, and preparation is easier when you know what the interviewer has seen.

Keep confirmation emails or reference numbers where you can find them. A message saying a draft is ready is not a submission receipt. If submission was interrupted, check the employer's portal or confirmation channel before trying again. Record the uncertainty until you have evidence of the outcome.

Base reminders on the employer's timeline

If the employer gives a date for the next stage, record it with the source of that promise. If they ask applicants not to contact them, respect that instruction. If no timeline exists, choose a personal review date to check the application status; a review date does not automatically require sending a message.

After an interview, ask how the next stage will work and when you may expect an update. Harvard's interview guidance recommends clarifying next steps. Use that answer to plan a follow-up. Keep dates in the relevant time zone, especially when interviews or deadlines involve another country.

Source for the published guidance: Harvard MCS: Interviewing.

Worked example

An interviewer says the team expects an update by Thursday. The candidate records the date and waits through that period. On the next working day, they use the existing email thread for one concise status question. They do not send daily messages or contact unrelated employees.

Write a follow-up with a clear purpose

A useful follow-up identifies the role and reference, states the relevant event and asks one question. Check the addressee and use the channel the employer provided. Do not imply a personal connection you do not have. If you send from an existing thread, confirm the recipients still match the intended conversation.

Avoid adding urgency that is not real or repeating the entire CV. A genuine competing deadline can be stated accurately and politely. If there is no new information or unanswered practical question, another message may not be useful. Choose the next action from the situation rather than a fixed messaging quota.

Review the tracker once a week

Check active deadlines, unresolved submissions and interview preparation needs. Close roles that are explicitly no longer available or that you have chosen to withdraw from. Keep silence separate from rejection. You can archive inactive rows for your own organisation without claiming to know the employer's decision.

Jobvance can help keep preparation and next actions together; connected reply features depend on setup. You still review the status and send messages yourself. If you use a spreadsheet instead, the same event-based method works. Your next step is to correct one uncertain row and assign one real action, not to build a larger dashboard.

Sources and further reading

The links support the specific guidance cited above. Our checklists and worked examples show how to put the guidance into practice. Read current official requirements before acting.

About these guides and their sources

Jobvance Editorial · Source checks dated

These Jobvance guides bring together practical checklists, worked examples and published sources. They provide general application guidance, rather than individual career or legal advice.

We separate published source facts from our practical suggestions. Worked examples illustrate the advice; they are not customer case studies. Product instructions describe the available review workflow, and connected features depend on setup. You review documents and submit applications yourself.

Official requirements and product capabilities can change. Check the linked source and the employer's current instructions before acting. You can report an unclear passage or source.