Cool Easy

← All articles

The minimum viable job-application tracker — what you actually need to record

A job-application tracker should take less time to maintain than the applications themselves. Most people's systems fail because they're designed for completeness, not for use.

13 May 2026 · 4 min read

Why most trackers fail

The instinct when starting a job search is to build infrastructure. You open a spreadsheet, design columns, maybe add colour-coded status rows. It looks like control.

The problem is that a well-designed tracker is optimised for completeness, and completeness is expensive to maintain. Every column you add is a column you have to fill for every application. By application twenty, you're either skipping fields (so the tracker is incomplete and therefore untrustworthy) or spending fifteen minutes per application on admin.

The more common failure: you build the system, use it for two weeks, then stop updating it. A tracker you stopped updating two weeks ago is worse than no tracker — it's a false record that misleads you about where things stand.

The fix isn't a better spreadsheet design. It's a different philosophy: track less, consistently, rather than track everything, sporadically.

The five fields that are actually enough

1. Company and role

One line. "Acme Corp — Senior Product Manager" or however you'd describe it to a friend. This is for recognition, not completeness.

The URL of the job posting. You'll need this when a recruiter calls and you've forgotten which Acme Corp role you applied to, or when you want to re-read the job description before an interview.

Don't skip this field. Job listings disappear frequently — save the URL early.

3. Status

Four values cover almost every job search: Interested (found it, haven't applied), Applied (submitted), Interviewing (in process), Closed (rejected, withdrew, or the role disappeared).

Resist the urge to add sub-statuses like "phone screen" or "second round" — that detail belongs in the note.

4. One note

Not notes — one note. The single most important thing future-you needs to remember about this application right now. Usually one of: what the next action is ("follow up 2 June"), a deadline ("closes Friday"), something to ask ("ask about remote policy"), or a gut-feel flag ("salary low, role interesting").

The note changes as you progress. Update it each time you interact with the role. It's a current-state summary, not a log.

5. Date applied

Useful for two things: knowing when a follow-up is overdue, and trimming applications you applied to months ago with no response.

That's the system. No salary column. No recruiter name column. No "how did I find this" column. Add those only if you identify a specific gap they'd fill.

The workflow

Capture at browse-time. The moment you're looking at a job and thinking "I might apply to this," pin it. Don't wait until you've decided — you'll either forget the listing or have to re-find it. Job Pin Board saves the URL and title automatically from the current tab; you add a one-sentence note and set status to "Interested." Twenty seconds.

Update status immediately when something changes. Don't save it for a Sunday admin session. When you submit an application, open the side panel and flip the status. When you get an email, update the note. Immediate updates take five seconds; reconstructing history takes fifteen minutes and introduces errors.

Weekly scan, not weekly update. Once a week, scan your "Interested" and "Applied" items. Anything where the note says follow up and the date has passed: follow up or close it. Anything you've lost energy for: close it. This session should take under ten minutes because your running updates mean nothing has drifted far.

Common mistakes

Adding fields you'll never actually use. "Recruiter LinkedIn," "salary estimate," "company size" — these look useful in week one. By week three you have fifty rows where three quarters of those fields are blank. Blank fields make a tracker feel broken.

Keeping "Interested" items indefinitely. If a role has been in "Interested" for three weeks and you haven't applied, you're probably not going to. Close it. Clearing old items is not giving up — it's keeping the tracker trustworthy.

Using multiple systems. LinkedIn saved jobs, an email folder, and a spreadsheet. The moment you split your tracking across systems you guarantee at least one of them is wrong. Pick one place.

Treating the tracker as a log. A log tries to capture everything that happened. A tracker only needs to capture what's currently true. You don't need to know that a recruiter called on May 4th — you need to know what happens next.

FAQ

What's the minimum number of fields I actually need per job application?

Five. Company and role (so you recognise it at a glance), a link to the listing (so you can reopen it when you get a call), a status (interested / applied / interviewing / closed), one note with the next action, and date applied. Everything else — salary range, recruiter name, interview notes — can be added to that one note field as needed.

Should I track salary ranges upfront?

Only if the salary is listed and meaningfully affects whether you'll apply. Don't add a salary field to every application speculatively — you'll end up with mostly blank fields that make the tracker look incomplete. Add salary to the note field for roles where it matters.

When should I expand beyond the minimum?

When you notice a concrete gap — for example, you keep forgetting recruiter names when they call, so you add that. Let the failure drive the addition, not anticipation of a failure that may never happen.

Does Job Pin Board work on niche job boards and company careers pages?

Yes. It's site-agnostic — pin from any URL. The extension captures the page title and URL automatically, so you don't need to copy-paste the link.