What a Job Application Tracker Should Actually Track
A job application tracker is your own record of every role, interview, contact, and outcome. What to put in it, what to leave out, and how to read it.
By Alexander Hoff · Founder
A job application tracker is the record you keep of your own search. Three weeks after you apply somewhere, it should be able to tell you which version of the posting you were measured against, how much of it your resume covered, who you talked to, and what you promised them. Most trackers store a company name, a date, and a status, which answers none of that.
The name is half the problem. Search for "application tracker" and most of what you'll find is employer software. Greenhouse, Lever, Ashby, and Workday Recruiting are applicant tracking systems, the databases companies use to store applicants, run screening questions, schedule interviews, and record who got hired. Those systems track you, and you never get to see inside them. Some of them give candidates a status page, Greenhouse has one, but all that shows is whichever label the employer decided to publish. When we say tracker, we mean the opposite: your own record of every role you applied to, every interview, every person you met, and how each one ended.
What is the difference between a job application tracker and an applicant tracking system?
Who owns it and what it covers. An applicant tracking system belongs to one employer and covers one opening, and you're one of a few hundred entries in it. Your tracker belongs to you and covers the entire search, every company, with notes nobody else has.
The status page is the thing people mistake for a tracker, because it looks like one. In practice the labels sit there unchanged for weeks, and a lot of them never change at all. You can refresh that page for a month and not learn one thing you can act on.
What should a job application tracker actually track?
Five things, and each one is tied to a decision you'll actually have to make. If a field doesn't change what you do, you'll stop filling it in by the third week, and you should.
Paste the whole posting somewhere you can find it again. Save the URL and the date you submitted, and pull the hard requirements out into their own columns so you can scan them.
- Years of experience, worded the way the posting words it
- Location, and whether onsite is negotiable
- Any clearance, certification, or license they require
- Posted pay, if there is any
Postings get taken down, and some get edited while you're still in the process. Three weeks from now your interviewer will still be working from that document, and you may not be able to open it anymore.
The hard requirements are also worth reading across your whole list now and then. If every posting that went quiet had the same years-of-experience line on it, that's the thing to look at before you start rewriting bullets.
For each requirement, mark whether your resume covers it with a specific line, covers it partly, or doesn't address it. Keep the count, and keep the list of what you didn't address.
Across the kits we've analyzed, the typical posting writes down about eighteen requirements, and researching the company turns up another eight or so the posting never mentions but the team still screens for, like the specific systems they run or the migration they're in the middle of. The typical resume leaves eight of the full set unaddressed.
Counting by hand, you'll only get the written ones. The rest come from researching the company, or from Telosi's Requirements Analysis, which extracts both kinds and hands you the list. Either way, pay attention to any requirement that shows up unaddressed three weeks in a row. It's either something you did and never wrote down, or something you've never done, and those need completely different fixes. The first case is covered in tailoring a resume without sounding generic.
The date, the round, the format, and who was in the room. Before the interview, write down what you read and the questions you plan to ask, working from what to research about a company. After the interview, write the debrief within the hour, while you can still remember the exact wording of the question that threw you.
Keep a separate list of people, rather than burying names inside the interview rows.
- Name, title, and where they sit relative to the role
- How they came into your search: recruiter, panel, hiring manager, referral
- What you promised to send them, and the date you sent it
One hiring manager, who runs a team at a media company, explained why he picked the person he hired: "He emailed me before my first interview to introduce himself... showed me a sample of what he would build for us if he got hired." And: "We had a lot of candidates, and he was the only one who proactively reached out to me." That only works if you know who you're about to meet, and if you save that lookup you're not redoing it every round.
There are five outcomes worth telling apart: an offer, a rejection after interviewing, a rejection at the screen, no response by your own cutoff date, and the role closing with no hire at all. Give each one a date. If anyone gave you a reason, write down what they actually said, not a softer version of it.
If you make your kits through an account at Telosi, it keeps this same record for each one: when you applied, each interview with its prep notes, debrief, and the people involved, and how it ended.
How do I know whether my applications are failing or I just haven't sent enough?
Six applications and no interviews feels like a verdict. Do the arithmetic before you treat it as one. If your interview rate is somewhere around one in ten, the chance that six applications produce zero interviews comes out to roughly 53 percent, which is just 0.9 multiplied by itself six times. Zero out of six is the normal result. There's not much to diagnose until you're closer to thirty, and if you don't know your own rate yet, that's the first thing the tracker will give you.
One operations director, mid-search after a layoff, came to us for a review. The nine applications she had built through Telosi had produced no interviews, and she assumed her employment gap was the reason. Her own rows told a different story: just six of the nine had been out long enough for anyone to respond. Six rows can't tell you whether the applications were any good.
A stage column is what makes a real slowdown visible. One stage per application, with the date of each change. For a single row that feels like busywork. Counted across thirty days it tells you whether the search is actually working, and no job board is going to do that math for you.
| Stage | Recorded when | What a low number here usually means |
|---|---|---|
| Applied | You submit | Your target list is too scattered |
| Screen | A recruiter or hiring manager books time | The top of your resume, or a hard requirement |
| Interview | You meet the hiring manager or a panel | Not enough evidence behind the requirements |
| Offer | Terms arrive in writing | Closing, references, pay expectations |
Before you blame your resume, look at the rows. How many applications are old enough to have answered, and how widely does the list scatter across job titles?
How do I set one up this week?
Open a spreadsheet. One row per application, a second tab for people, a third for interviews, and a link from each row to the saved posting. These eleven columns cover it.
| Column | What goes in it | The decision it serves |
|---|---|---|
| Company and role | Company, team if you know it, the title as posted, the URL | Finding the posting after it comes down |
| Applied date | The date you submitted | When to follow up, and the base-rate math |
| Source | Referral, job board, recruiter reached out, applied directly | Which channel actually produces screens |
| Posting saved | Link to the pasted text, plus the date you saved it | Interview prep three weeks later |
| Hard requirements | Years required, location, clearance, posted pay | Whether to apply at all |
| Coverage | Covered, partial, or unaddressed for each requirement, plus the list of what's unaddressed | What to fix before you submit |
| Why you applied | One sentence, written before you submit | Your answer to the first interview question |
| Stage | Applied, screen, interview, offer, closed | Reading the funnel |
| Next action and date | The next thing you owe someone | Keeping things moving |
| People | Names, linked to the contact rows | Follow-up, and the next opening at that company |
| Outcome and date | Offer, rejection, no response, no hire | The rate you compute from |
One rule I use to keep the applied-date column honest: if a referral hasn't come through in 24 to 48 hours, I apply anyway and mark the referral as pending. Waiting on a warm intro is how a week goes by with nothing written down.
Then there's the weekly half hour, which matters more than the columns do.
- Anything still sitting at "applied" past your cutoff gets a decision: message a contact, or close it as no response. Twenty-one days is a reasonable cutoff. Rows left open forever make your rate look worse than it is.
- Applications, screens, interviews, offers. Four numbers, written next to last month's four so you can see the change.
- Find the requirement that came up unaddressed more than once. If you've done that work and left it off the resume, fix it this week. If you'd have to go get that experience, the thing to change is your target list. Then write down next week's companies before you close the file.
A few fields that look responsible to track and aren't worth the time:
- The employer's status label. Copying it into your tracker records a decision you didn't make and can't influence. Record what you did, and when.
- A keyword-match percentage from a scanner tool. It measures how much two documents overlap. It doesn't measure whether you can do the job.
- Every role you might apply to someday. Keep your shortlist in a different file. The tracker starts at the moment you submit, or the funnel numbers stop meaning anything.
What else should I know before I start tracking?
Do I need a dedicated tool, or is a spreadsheet enough?
A spreadsheet is enough for most people. Tools like Teal and Huntr add convenience: a browser button that captures the posting, an activity timeline, a cleaner view of the pipeline. Whatever you use, ask it the same question: does it hold the posting text, the per-requirement coverage, the interview debriefs, and the named contacts? If it only tracks company, title, date, and status, it's a nicer-looking version of the thing that wasn't working.
How long should I keep an application after I've been rejected?
At least through your next search. Roles reopen, hiring freezes end, and the person you met in round two moves to another company. The debrief notes from a process you lost are the best free interview prep you'll ever get for a similar role.
What do I record when I never hear back at all?
Pick a cutoff, mark it closed with no response, and date it. Going silent is the most common outcome in any search. If you leave those rows open, your funnel numbers stop meaning anything.