How to Track Job Applications Without Losing the Thread

Log every application the moment you send it, in one place, with seven fields: company, exact role title, date applied, where you applied, who the contact is, the current status, and the full text of the posting. Everything else is optional. A spreadsheet does this fine as long as you actually update it.

Tracking is not about tidiness

The reason to keep a record is not that a neat spreadsheet feels good. It is that a job search runs on details you cannot hold in your head past the second week.

You cannot follow up on what you cannot remember. A follow-up email needs a date, an exact role title, and a name, and those are the three things that blur first. Without them you send nothing, or you send something vague that reads like a mass mailing.

Then there is the phone call. Recruiters get to applications late. Someone rings on a Tuesday about a role you applied to five weeks ago, opens with the company name and nothing else, and expects you to know what they mean. That moment, more than any other, is what a tracker is for.

The quieter reasons add up. Without a record you apply twice to the same company through two boards, lose the posting before the interview, and have only a feeling to consult when you try to work out why nothing is landing.

A tracker is not a record of what you have done. It is a list of what you still owe a reply to.

The minimum set of fields worth recording

Track less than you think. Every extra column is another thing to fill in at the moment your motivation is lowest, and a half-filled tracker is worse than a short complete one. These fields change what you do next:

• Company. The name you applied under, not the parent brand, so a search finds it.
• Role title, exactly as posted. "Operations Coordinator II" and "Operations Coordinator" are different postings. Add the requisition ID if there is one; recruiters use it as a lookup key, so quoting it saves them a search.
• Date applied. The most useful field of all. It tells you when a follow-up is due and when silence has gone on long enough to close the row.
• Source. Careers page, a named board, a referral from a specific person, a recruiter who approached you. This is what later lets you notice that your replies all come from one channel.
• Documents sent. Filenames of the exact resume and letter. If you tailor per application, you will not remember which claims you made.
• Contact. A name and an email if you have one. Blank is fine, and common.
• Status and next action. Where it stands and what you owe it, with a date.
• The posting text. Saved in full. This is the field people skip and regret.

A filled-in record looks like this:

The notes line is not a diary entry. It is the two or three things you would want to be reminded of thirty seconds before a phone screen.

A status pipeline that matches how applications really move

Most people use three statuses: applied, interview, rejected. Almost everything then parks in "applied" forever, including the roles quietly filled back in March, and within a month the list stops meaning anything. Give each status a clear meaning and an implied next action, and give silence somewhere to go.

Two rules keep this honest. A row sits in one status only. And "no response" is a decision you make, not one they make for you: one follow-up sent, another week or two of silence, then archive. The cut-off is a judgement call; having any cut-off is what keeps the live list short enough to read. Archived rows stay in the file, because you will want them when the same company posts again in six months.

Save the posting text, because it will disappear

This is the part people learn the hard way. Postings come down. The role gets filled, the ad expires, the board rotates it out, the careers site is reorganised. The link you saved returns a 404 exactly when you need it, which is the evening before the interview.

You will want the original text for rereading what they asked for, checking which claims your letter made, writing a thank-you note that echoes their priorities, and checking the scope of the job if an offer describes something different.

Save the text, not a screenshot. Being able to search six weeks of postings for "night rota" or "SQL" beats a tidy capture. Paste the whole thing into a notes field or a text file with a predictable name.

Name the documents you sent the same way every time: Lastname-Resume-Company-Date.pdf. Six weeks later you can then find the exact resume a recruiter is holding without opening five files.

A saved posting also makes interview prep concrete: take the responsibilities they listed first and write out how you would handle each one. If you would rather start from a list, SwiftCover generates likely interview questions from a posting, which is a reasonable place to begin before you rewrite the answers in your own words.

Spreadsheet or dedicated tool, honestly

A spreadsheet is genuinely fine for most searches. If you are running a focused search in one field, with twenty or thirty applications open at a time, and you are the sort of person who updates a file, it will not let you down. It is free and it never changes its interface on you.

The last row is the real comparison. Neither option fails on features. Both fail on habit. A tool helps mainly by removing the gap between applying and recording, because that gap is where tracking dies. That is why tracking sits inside SwiftCover on the web next to the letter and resume it produced, rather than as a separate list to maintain by hand.

A tool earns its place if you apply from your phone, if your search is running long, or if you have tried the spreadsheet twice and abandoned it twice. Otherwise keep the spreadsheet and spend the saved effort on the applications themselves. How many to send is a separate question, worked through in how many jobs you should apply to.

The habit that keeps it current

One rule carries almost all the value: create the record before you close the tab. Not that evening, not on Sunday. While the posting is still open in front of you, because that is the only moment when copying the text costs you nothing.

Then a fifteen-minute weekly pass in the same slot each week. Read the live rows top to bottom and do three things: send the follow-ups that are due, archive the rows quiet past your cut-off, and delete anything in "to apply" you have decided against.

What the record actually buys you

Three moments make the habit pay for itself.

The unexpected call. Unknown number, a name you half recognise, a role you cannot place. With a searchable tracker you type the company name while they are still introducing themselves.

The follow-up. Specific beats polite. The tracker gives you the date, the exact title, and the requisition number, which together make the email easy for a recruiter to act on:

The wording and timing of those emails are their own topic, covered in the follow-up email after applying. The same record is what lets you write a fast, specific thank-you email after an interview.

The review. After a few weeks the archived rows start telling you something. Perhaps every reply came from a company site rather than a board, or every rejection arrived at the same stage. That is not a fact about hiring in general. It is a pattern in your own search, and it is the only evidence you get about what to change.

Common questions