Practical guide
How to track job applications and follow-ups
Keep one row per application, record the exact resume you sent, and give every active row a next action with a due date. Update the tracker when something happens, then review due actions regularly. The free CSV below provides a starting point without requiring a tracker subscription.
Download the free job application tracker
The template is a plain CSV that you can import into a spreadsheet application. It includes a clearly labeled fictional row showing how to record a submitted application and a planned status check. Replace or delete that row before adding your own information. You do not need to sign up to download it.
Import the file using commas as the separator if your spreadsheet does not separate the columns automatically. Keep dates in YYYY-MM-DD format, freeze the header row, and turn on column filters if available. Save your working copy in the spreadsheet’s normal format; export another CSV when you need a portable copy.
1. Track enough detail to make the next decision
Use one row per employer requisition rather than one row per job-board listing. If the same job appears on several boards, keep the employer’s posting as the main link and note where you found it. Separate rows make sense for genuinely different vacancies at the same employer; distinguish them with the requisition ID.
A tracker should help you act, so avoid adding columns you never use. If you are evaluating location or schedule constraints, add those details. If you are tracking referrals, keep referral status separate from application status so a request does not look like an application submission.
| Fields | What to record |
|---|---|
| Company, role, requisition_id, job_url | The specific opening, including the employer’s identifier if available |
| location, date_saved, date_applied | Work location and when you saved and submitted the application |
| status, last_update_date | The latest confirmed stage and the date that information changed |
| next_action, next_action_due | One concrete task and the date you plan to do it |
| resume_version, confirmation_reference | The exact submitted file and application receipt or reference |
| contact, last_contact_date, notes | Relevant contact context, communication date, and unresolved questions |
2. Use statuses that describe evidence
Start with Saved, Preparing, Applied, Interviewing, Offer, Rejected, Withdrawn, and Closed. You can add a distinct Assessment stage if that is useful. Keep the vocabulary consistent so filters work. Change a status when you have evidence, not because enough time has passed or a tool inferred progress.
Applied means you submitted through the required channel and recorded whatever confirmation was available. Interviewing means an interview was arranged or explicitly requested. No response is a note about communication; it is not proof of rejection. If you stop pursuing an unanswered application, mark it Closed with a note explaining your own decision.
Cedar Learning — Operations Coordinator — CL-104 Applied: 2026-09-23 Status: Applied Resume: Sam-Rivera-Cedar-Operations-2026-09-23.pdf Confirmation: FICTIONAL-CL104-001 Next action: Review the posting’s timeline before deciding whether to follow up Due: 2026-09-30 Note: Fictional example; no employer response or follow-up promise is implied
3. Give each active application one next action
Write an action you can perform: tailor the resume, finish a requested assessment, prepare interview examples, or check the employer’s stated timeline. ‘Waiting’ describes a condition but does not tell you what to do next. If you are waiting, make the next action a review on a chosen date rather than an automatic message.
Set dates from actual deadlines and commitments first. A recruiter’s promised update date matters more than a generic follow-up schedule. The sample’s September 30 review date is an organizational example, not a recommendation to contact every employer seven days after applying.
For interviews, put the appointment in your calendar with its timezone and use the tracker for preparation and follow-through. A CSV does not send reminders by itself. If reminders are important, create them in your calendar or task app and check they point to the correct application.
4. Preserve what you actually submitted
Save each submitted resume under a stable filename and enter that filename or an accessible private file link in resume_version. Do not overwrite a submitted file when tailoring the next application. Keep the posting text or a saved copy nearby so you can reconstruct what the employer asked for before an interview.
Record a confirmation number, receipt location, or useful portal reference when available. If submission is uncertain, note that explicitly and check the portal or confirmation email before applying again. A populated form and a saved draft are not evidence of a completed application.
5. Review the tracker without turning it into another job
Keep notes concise and factual. Store only information needed for your search, and check sharing permissions before sending the tracker to a coach or friend. Application records can contain personal contact information and links to private documents.
If maintaining rows becomes the bottleneck, compare dedicated trackers on capture accuracy, reminders, resume history, and export. Try a few real entries before migrating everything. A tool is useful when it reduces missed actions and preserves your records; a larger feature list alone does not make it a better fit.
- Update a row immediately after submitting, receiving a message, or completing an interview.
- Filter active rows by next_action_due and handle approaching deadlines first.
- Review overdue actions and deliberately reschedule or close them.
- Check for duplicate openings and rows with no next action.
- Back up the working file and archive finished searches when useful.