Why the spreadsheet dies in week two
The failure is structural, not a discipline problem. A tracking spreadsheet asks you to do data entry immediately after the least rewarding part of a job search, about a thing you have just finished thinking about, for a benefit that arrives weeks later. Week one it gets filled in. Week two it gets filled in on Sunday. Week three it is a list of company names with empty columns.
- The row is typed after the work, when the motivation for it is gone.
- The columns that matter most, the date you sent it and which version you sent, are the two most tedious to enter.
- Nothing reminds you, so the gap grows until catching up is its own project.
- By the time a recruiter calls, the sheet cannot tell you which version of your resume they are looking at.
A tracker that is a by-product
The row exists because the application does. Queue a posting and it appears as a record immediately, moves itself through the states the system knows about, and waits for you on the two transitions only you can confirm.
- Queued, then tailoring, then ready to send: those three happen without you.
- Submitted is one click, after you have sent it. That is the only routine bit of typing left, and it is a click rather than a row.
- Interviewing, offer, rejected, and withdrawn are yours to set as the outcome arrives.
- The exact resume and letter you sent are attached to the record, so a call six weeks later is not archaeology.
- The posting link, the company, and the fit score stay attached too, which is what the spreadsheet columns were for.
What the shape of your pipeline is telling you
The point of seeing all eight states as one bar rather than eight numbers is that the shape is diagnostic. Four counts tell you how much you have done. One proportional bar tells you what is wrong, and each of the three common shapes has a different fix.
- A wide ready-to-send band: the backlog is on your desk. The applications are written and you have not sent them, which is the cheapest problem on this list to fix.
- A wide submitted band with nothing past it: the search is waiting on other people. More applications is the answer, not better ones.
- Submitted moving to rejected with no interviews: the targeting is off, or the resume is not surviving the first screen. Look at the fit scores you sent at.
- Interviews that do not convert: the problem has moved past the application entirely, and no tracker fixes it.
- An empty bar: the search has not started, which is worth naming rather than working around.
The numbers actually worth watching
Most tracking advice produces columns nobody reads. Four figures carry almost all the signal in a job search, and each one has a specific action attached to it rather than a feeling.
- Reply rate. Under 5% across twenty-plus applications is a targeting problem, not a resume problem. Applying to better-matched roles beats rewriting.
- Median fit score of what you sent. If it is under 55, you are applying to jobs you were told you would not get.
- Days from submitted to first reply. Past about three weeks with no word, treat it as closed and stop counting it as live.
- Applications per week. Twenty to fifty over a search is the range that produces offers, and clustering them into one night is worse than spreading them.
Follow-ups, without a nagging schedule
Tracking exists so you can follow up at the right moment rather than at a random one. The timing is not complicated and the content matters more than the timing does.
- One follow-up, seven to ten working days after submitting, if the posting is still live and nobody has replied.
- Send it to a person if you can find one. A reply-all to a no-reply address is not a follow-up.
- Add something rather than repeating yourself: a relevant thing you shipped since, or a specific question about the role.
- After a second silence, mark it closed. A search where you are chasing the same five applications is a search that has stopped moving.