How to Track Job Applications: Columns, Statuses and a Follow-Up Rhythm
After the twentieth application, it's hard to remember which company you emailed, who the recruiter was, and when you should follow up. A simple tracker fixes that. Here are the columns worth keeping, a status system, a follow-up rhythm, and how to keep your interview stories organised as well.
The columns worth tracking
Start small. You can always add more columns, but a tracker with 25 columns doesn't get updated. These cover most needs:
| Column | Why it's useful |
|---|---|
| Company · Role · Link | Postings disappear. Save the link, and paste the job description into a notes field or file. |
| Source | Job board, company site, referral, recruiter. Over time this shows which channels actually get replies. |
| Date applied | The start of your follow-up clock. |
| Status | One value per row (see below). This drives your daily to-do list. |
| Last contact | The date of your last email, call or message. Update it every time. |
| Next action / date | The one thing to do next, and when. |
| Contact | Recruiter or hiring manager name and how you reached them. |
| CV version | Which tailored version you sent, so you can tell what works. |
| Excitement (1–5) | Helps you decide where to spend prep time when interviews stack up. |
A status system that tells you what to do
Keep statuses few and mutually exclusive. One workable set:
- Saved: found it, haven't applied yet
- Applied: waiting for a reply
- Screening: recruiter call scheduled or done
- Interviewing: in the formal process
- Offer: decide and negotiate
- Rejected / Withdrawn / No response: closed. Keep these rows so your numbers stay honest.
Add a calculated "days since last contact" column if your tool supports formulas, and sort by it. The rows at the top are your follow-ups.
A follow-up rhythm
There's no universal rule for when to follow up. Some postings say "no follow-ups, please", and you should respect that. If they don't, many people use a rhythm like this:
- About a week after applying with no reply: one short, polite note to the recruiter or hiring manager, if you can find them.
- Within 24 hours after an interview: a thank-you note that mentions one specific thing you discussed.
- After the date they said they'd decide: one check-in asking about the timeline.
- Around three weeks of silence: send a final note or mark it "No response" and move on.
Treat these intervals as a starting point you can adjust, not a rule. What matters is that your tracker reminds you, so you neither chase daily nor forget a promising lead.
Subject: [Role] application — [Your name] Hi [Name], I applied for the [Role] position on [date] and wanted to say I'm still very interested. [One sentence on the most relevant thing you'd bring.] If it's useful, I'm happy to share more detail or a work sample. Thanks for your time. Best, [Your name]
The weekly review: read your own numbers
Once a week, spend 15–20 minutes on three questions:
- Volume: did you apply to as many roles as you planned? If not, was it a time problem or a shortage of good roles?
- Response rate by source: replies ÷ applications, per source. If one channel gets nothing after a fair number of tries, shift effort to the ones that work, often referrals and direct outreach.
- Where people drop out: no replies points to the CV or targeting. Screens but no interviews points to your short pitch. Interviews but no offers points to your stories and examples.
Your own numbers beat any general benchmark, because they reflect your field, level and market.
Keep a story bank for interviews
Behavioural questions ("Tell me about a time when…") come up again and again. Instead of improvising, keep 6–10 short stories in a structure such as STAR: Situation, Task, Action, Result.
- Keep the Situation and Task short, a sentence or two each.
- Make the Action the longest part, and say what you did ("I", not "we").
- End with a Result you can state plainly, with a number if you honestly have one, and what you learned.
- Tag each story with the skills it shows (leadership, conflict, failure, initiative…). One good story often answers several questions.
Next to each story, note which interviews you used it in so you don't tell the same company the same story twice.