Tracking applications without building a bureaucracy

Everyone who has run a long search has built an elaborate tracker in week two and stopped updating it by week six. The failure is predictable: the tracker was designed while motivated, to be maintained while discouraged.

Design it for week nineteen instead. It needs to answer four questions in under a minute, and nothing else. For teams that need a structured record of working time after hiring, time tracking software provides a useful point of comparison.

The four questions

• What did I apply to, and when? — so that a call from an unknown number does not catch you blank.
• What needs a follow-up this week? — so that things do not lapse silently.
• What version of my documents went to this employer? — so that an interviewer's question about a bullet does not surprise you.
• Where is the pipeline leaking? — so that you fix the right stage.

A structure that survives

One spreadsheet. Nine columns, and resist the tenth.

• Employer.
• Role title, and a link to the posting — save a copy of the text, because postings disappear and you will want it before the interview.
• Date applied.
• Source: board, careers page, referral, agency. This column tells you later which channel actually works for you.
• Document version sent.
• Contact name, if you have one.
• Status: applied / screen / interview / final / offer / closed.
• Next action and date.
• Notes — salary discussed, who you met, anything said that you will want in three weeks.

The weekly review

Twenty minutes, same time each week. Three passes:

• Update statuses. Anything with no response after three weeks moves to closed — not because it definitely is, but because carrying dead applications as live ones distorts your sense of the pipeline and your mood with it.
• Set next actions. Every live row gets a date. Anything without one is not really live.
• Count. Applications sent, screens, interviews, finals, offers — cumulative, since the start.

Reading the counts

The counts are the point of the whole exercise, because they localise the problem. Rough diagnostics: For additional job-search tools, CareerOneStop offers a broader reference point.

• Under one screening call per ten applications: the documents or the targeting are wrong. Fix the résumé top third and the tailoring before sending anything else.
• Screens converting to interviews under a third of the time: the phone screen is the problem — usually the opening summary or the salary answer.
• Three or more interview processes with no final rounds: the interview answers need structural work.
• Two or more final rounds with no offer: usually a level mismatch, and worth asking directly for feedback.

Without counts, every rejection feels like the same rejection, and the instinctive response is to send more applications. Sometimes that is right. Usually it is not, and the counts are the only thing that tells you which.

Follow-up timing

A short, plain follow-up after a reasonable interval is normal and occasionally effective. Once, not twice. Roughly: seven to ten working days after an application if the posting gave no timeline; three to five working days after a stated decision date has passed; a week after an interview if you were told to expect an answer sooner.

Keep it to three sentences, restate the role and the date, and ask whether there is an updated timeline. Then let it go — the second follow-up almost never changes an outcome and is remembered.

What to keep after the search

When the search ends, keep the spreadsheet. It contains the conversion rates for your own profile in your own market, the names of everyone you spoke to, and the list of employers who nearly hired you — which is the single best starting point for the next search, whenever that comes.