How to Track Job Applications: The System That Scales to 100+
Active job seekers usually have 30–100 applications in flight at once. Without a system you forget who you applied to, miss follow-ups, and burn out. Here is the lightweight tracking system that scales.
ApplyTOP · May 15, 2026
An active job search runs 30–100 applications in parallel. Without a system, by week three you can't remember which company you applied to last Tuesday, you've missed three follow-up windows, and you're about to apply to the same role twice because you forgot the first one didn't pan out. The tracking system you set up in week one is the difference between a focused search and a stressful blur.
This post walks through the schema, the stages, the rhythm, and a comparison of the three tools most people end up using.
What every tracking row needs
One row per application. Each row should have:
- Company: just the name.
- Role: full title from the JD.
- Date applied: YYYY-MM-DD so it sorts.
- Source: LinkedIn, ATS direct, referral, ApplyTOP, etc. Helps you learn which sources are converting later.
- Recruiter name: if known. Saves time when you follow up.
- Stage: one of five values (see below).
- Next action: one short phrase: "follow up", "prep onsite", "wait", "send referral note".
- Next-action date: when to next look at this row.
- Job URL: so you can re-read the JD before any call.
- Notes: freeform. Recruiter feedback, salary discussion, things to mention next call.
Don't over-engineer. Don't add columns for "applied via ATS yes/no", "remote ok yes/no", "salary band". Those should be implicit from the JD URL.
Stages, not statuses
Use a stage field with exactly five values:
- applied: submitted, no response yet
- screen: recruiter screening call scheduled or done
- technical: technical interview round (could be one or several rounds)
- onsite: final-round panel or onsite
- closed: either offer received, rejected, or you withdrew
That's it. Don't invent a sixth stage for "responded but no call yet" or "waiting on take-home". Track those in the next-action field instead. The point of stages is to filter your view (e.g. "show me everything in screen or later"). Granularity beyond five stops being useful.
The follow-up rhythm
Most recruiters take 5–10 business days to respond to an application. The right cadence:
- Day 0: Apply. Set next action = "follow up", next-action date = today + 7 business days.
- Day 7: If no response, send a short, specific follow-up. Not "checking in". Add new value. A relevant work sample, a question about the role, a recent company news item that makes you more interested.
- Day 14: If still no response, mark closed (rejected by silence) and move on.
The biggest mistake is the "checking in" follow-up that adds nothing. Recruiters delete those. A good follow-up note:
Hi Sarah,
Wanted to add one thing I forgot in the application: I noticed your team is using Temporal for the order workflows. I shipped a Temporal-backed reconciliation pipeline last quarter at [company] and could share the durable-execution gotchas we hit on the call if it's useful. Still very interested in the role.
Best,
. Alex
That gets responses. "Just following up to see if you've had a chance to review my application" doesn't.
Two daily blocks
Sustainable job searching is two 90-minute blocks per day, not 10 hours of tab-switching:
- Block 1 (morning): applying. Find new fresh roles, tailor CVs and cover letters, submit. Start with any role in your alerts that's less than 24 hours old.
- Block 2 (afternoon): follow-ups, prep, networking. Work through the next-action queue from your tracker.
Stop before you're tired. The job search is a marathon. Weeks 4–8 are when applications quality usually drops because of fatigue. Protect the quality of the first hour by capping the day's volume.
Which tool: spreadsheet vs Notion vs ApplyTOP
Three approaches dominate. None is wrong. They fit different scales of search.
| Tool | Best for | Setup time | Limits |
|---|---|---|---|
| Google Sheet | Lightweight searches (<30 active applications) | 5 minutes | No alerting, no auto-stage updates, breaks when you sort wrong |
| Notion table | Mid-size searches with prep notes per role | 30 minutes | Same as sheet plus a learning curve. Templates exist online if you don't want to build. |
| ApplyTOP | Active searches that combine alerting + tracking | 2 minutes | Subscription. Best when you also want hourly job alerts and AI match scoring. |
The honest comparison: a spreadsheet is fine for the first 20 roles. Around the 30–50 range, the manual cost of finding fresh roles AND keeping the spreadsheet in sync becomes the bottleneck. That's the moment most people switch to either Notion (still manual but better organized) or a dedicated tracker.
What ApplyTOP collapses: the find-and-track loop. Job alerts arrive in your dashboard already deduplicated and scored against your CV; when you apply via the direct link, the application gets added to your tracker automatically with the source pre-filled. You still own follow-ups and notes. The system handles the bookkeeping that's mechanical.
If you're at 30+ applications and burning out, that's the signal to move off a spreadsheet. Try ApplyTOP free.
The one thing that breaks every tracking system
Inconsistency. The system only works if you update it within 60 seconds of every state change. Right after you apply, right after a recruiter emails, right after the call ends. If you "batch" updates for the end of the day, you forget half of them and the tracker drifts. Within a week you stop trusting it; within two weeks you abandon it.
Build the 60-second habit. It's the only rule that matters.