Thirty Applications, One Sheet: Track a Job Search as a Pipeline

Disclosure: the writer sells spreadsheet packs, one of which contains the pipeline sheet this method is built on. The arithmetic works identically in a blank sheet, and the point of this page is the maths, not the file.

Thirty applications in and nothing back feels like a verdict on you. It is not a verdict; it is a missing measurement. A job search is a funnel with stages, and a funnel either converts at a stage or it does not. Once you write the stages down you can compute the one number that decides where to spend tomorrow: where the applications are actually leaking.

The nine columns, and what each one is for

A job-search pipeline needs the same nine fields a sales pipeline needs. This is the real header row of the sheet I ship, straight from Job-Pipeline.xlsx:

Date added | Prospect | Source | Service | Value $ | Stage | Next action | Next date | Won/Lost

Renamed for applications, nothing else changes:

Date added - when you sent it. Drives "how long has this been open".
Prospect -> Company.
Source - where you found it. This is the column that later tells you which channel converts, and it is the one people skip.
Service -> Role (the exact posted title; it is what you will be searched for).
Value $ - for a salaried role, put the posted salary band's midpoint, or leave it blank. It keeps the "open pipeline value" honest about what is actually live.
Stage - a dropdown, not free text.
Next action and Next date - the pair that stops the sheet becoming a graveyard.
Won/Lost - the outcome, filled in when the stage reaches a decision.

The stage list in the shipped file is Lead,Contacted,Replied,Call booked,Proposal sent,Follow-up,Won,Lost. Mapped one-for-one onto searching, all eight: Lead -> Applied, Contacted -> Reached out to them, Replied -> Recruiter replied, Call booked -> Screen call, Proposal sent -> Interview or assessment, Follow-up -> Chasing them, Won -> Offer, Lost -> Rejected or no response.

The win rate, and why the denominator matters more than the numerator

The formula in cell E107 of that sheet is the whole idea:

=IFERROR(COUNTIF(F4:F103,"Won")/(COUNTIF(F4:F103,"Won")+COUNTIF(F4:F103,"Lost")),0)

Read the denominator: Won plus Lost only. The other two summary cells sit above it and are the whole rest of the engine:

E105 =SUMIF(F4:F103,"Proposal sent",E4:E103)+SUMIF(F4:F103,"Call booked",E4:E103)+SUMIF(F4:F103,"Replied",E4:E103)+SUMIF(F4:F103,"Contacted",E4:E103)+SUMIF(F4:F103,"Lead",E4:E103)+SUMIF(F4:F103,"Follow-up",E4:E103)
E106 =SUMIF(F4:F103,"Won",E4:E103)

Read the denominator: Won plus Lost only. Open applications are deliberately excluded. That is what makes the number usable rather than decorative.

If you divide offers by everything you ever sent, your rate falls every single day for reasons outside your control - because applications you sent this morning are still sitting in the numerator-less pile. That version of the metric punishes you for starting a search, and by week three it is unfalsifiable: no result can improve it, so people abandon the sheet. Counting only decided outcomes fixes the horizon: 12 decisions with 1 win is 8%, and it stays 8% whether or not you have 30 more in flight.

The IFERROR wrapper exists because on day one the denominator is zero. Without it the sheet shows #DIV/0!, which is the moment a tracker dies.

Stage conversion: the number that tells you what to fix

Win rate alone is too coarse to act on. Break it into the transitions and each one points at a different artifact. These are ratios of counts, so they are all readable straight off the same column:

Applied -> screen call. This is your resume and your targeting. If 40 applications produce fewer than a couple of callbacks, more interviews will not fix it - you need the document to survive the first gate, or a different set of roles. See guide 07 for the five checks you can run on the file yourself.
Next: How to Price a Freelance Job When You Have No Idea What to Charge
Screen -> onsite/interview. This is how you talk about your work in three minutes, not the document.
Interview -> offer. This is the interview itself, or your rate at salary negotiation.
Source -> applied -> screen. Which channel actually converts. Two weeks of this column usually kills a platform habit that was never working.

Only compute these once a stage has double-digit counts. A 1-in-1 interview conversion rate is not a rate, and the fastest way to abandon this method is to read meaning into three data points. The failure mode of a personal pipeline is not the arithmetic - it is acting on noise.

Three rules that keep the sheet alive past week two

Every open row has a Next action and a Next date, or it is Closed. Blank next-date is the honest signal for "I am pretending this is still going". Mark it Lost and move on; your win rate gets more informative, not less.
Ten minutes a week, not daily. Daily updates make the numbers twitchy and teach you nothing new, because the stages move on the employer's clock. A fixed weekly sweep is the discipline that survives.
Enter rows inside the range the sheet is wired for: rows 4 to 103. The dropdown and all three formulas stop at row 3, so an application logged in row 2 or row 104 is invisible to the maths and nothing will warn you.
Log it at the moment you apply. A tracker reconstructed from sent folder history is a week behind by default and becomes decorative within a month.

What this arithmetic cannot tell you

It cannot tell you your odds. A personal win rate is descriptive of your search, not predictive of it, and it is computed from a sample of one market in one season. Anyone quoting you a universal application-to-offer percentage is guessing.
It cannot see the pipeline on the other side. Roles where you were silently dropped, requisitions frozen mid-process, or a hiring manager who decided in week one and never told you - none of it lands in your sheet. Low conversion is information about your materials and about luck you cannot measure, and the two look identical.
It will not make you apply more. A pipeline can absolutely be used as a productivity racket. Its useful purpose here is the opposite: to show you that one stage is the bottleneck, so you do fewer, better applications instead of more, worse ones.

The sheet this is built on, and its honest label

Say the awkward part plainly: Job-Pipeline.xlsx in the Habit + Budget Tracker Pack ($6) is documented as a freelance and sales pipeline, not a job-search product. What it ships is the header row above, a stage dropdown on rows 4-103, an open-pipeline total (SUMIF over the live stages), a won-this-period total, and the win-rate formula in E107. To use it for applications you change three labels - Prospect to Company, Service to Role, and the outcome column's header - and the arithmetic is the same arithmetic. One thing you must not rename is the eight values inside the Stage column: the summary formulas match those words as text (SUMIF(F4:F103,"Won",E4:E103)), and because the win rate is wrapped in IFERROR, renaming them makes it quietly read 0 instead of telling you it broke. The pack is six files: that pipeline, Monthly-Budget.xlsx, Habit-Tracker-2026.xlsx (note the year in the name), plus README, SUPPORT and LICENSE.

If you would rather build it yourself, do that - the three formulas in the sheet are the whole engine, and a blank workbook with a stage dropdown gives you identical output. The full catalog is at payhip.com/MonkeyRun, and the coupon LAUNCH20 takes 20% off any single order at checkout.

One honest note on the catalog: the ten products inside it total $61 bought separately and the Complete Bundle is $19. That is $42 off. Two files can never beat $19 (the two dearest are $18), the four cheapest already come to exactly $19, and from four items up the bundle ties or wins - so buy the single file you need today, and take the bundle the moment you want four.