Skip to content
Login
Application Tracker

A spreadsheet records what you typed.This records what happened.

Three statuses update automatically as you apply. Every change is recorded with a date and time, and each entry shows its source. Six weeks later, your application history is still accurate.

Open your applicationsSee how a row moves
  • Three statusesclicked, in progress, applied
  • Full audit trailevery change, with date and time
  • The document you sentthe exact version, and its score
01
The board

Forty open applications and no idea which ones have gone quiet.

See the screen
02
The receipt

They called back about a role you applied for in March.

See the screen
03
The trail

"I am fairly sure I applied to this one." Fairly sure is not a record.

See the screen
How a record updates

You do not maintain this.It updates itself while you apply.

Most trackers stop getting updated within two weeks. Not because you are careless, but because the application form has already taken twenty minutes and re-entering the same details is the last thing you want to do. So the first two steps happen on their own. The third one asks you, because only you know the answer.

  1. 01
    CLICKED_APPLY

    You opened the company's form

    The record is created the moment you leave for the portal, so an application you started is saved even if the form logs you out.

    Automatic
  2. 02
    APPLICATION_IN_PROGRESS

    You are partway through

    Kept separate from applied, on purpose. A half-finished application is the easiest one to forget, and the one most worth going back to.

    Automatic
  3. 03
    APPLIED

    You confirmed you sent it

    This one step stays with you. Nothing is marked applied unless you say so, so the record is always yours and never a guess.

    One tap from you

How each row knows

Verification only ever moves up. A row that has been confirmed cannot silently fall back to a guess.

  • UnverifiedStarted, awaiting your confirmation. Honest about being a maybe.
  • You confirmed itYou told us it went. The strongest thing available today.
  • Confirmed from your inboxReading the employer’s acknowledgement. Not built yet.

Every one of those transitions is written to an event log, so the history of a row is a record rather than its current state overwritten in place.

What it holds

The status, the document,and the proof behind both.

A tracker is only useful if it can answer questions weeks later. Where does this application stand, which document did I send them, and what proof do I have.

01

The board

Forty open applications and no idea which ones have gone quiet.

Every application in one place, whether you found it here or applied from the jobs list. Four counts sit across the top: today, this week, the total, and how many separate companies that actually represents.

What you get: A single table containing every application, its current stage, and the next step you can take. Interview practice uses the document already attached, so there is nothing to upload again. Before an interview, you can go through exactly what the interviewer is holding.

  • Four counts, no vanity metricsToday, this week, total, and distinct companies
  • Companies counted separatelyEleven applications at three companies is a different week
  • Started rows are keptThe ones you did not finish are the ones worth finding again
  • A link back to the postingThe original apply link stays on the row
Open the board
02

The receipt

They called back about a role you applied for in March.

Each row keeps the version of the resume and cover letter that went with it, the score each had at the time, and the details filled into the form, so preparing for the call does not start with guessing which draft they read.

  • The version, not just the fileResume v4 and letter v2, as they were the day you sent them
  • The score it had thenBoth documents keep the ATS score they carried at the time
  • What was in the formThe contact details and answers submitted alongside them
  • The reference numberWhere the portal gave one, it is on the row
See an application
03

The trail

"I am fairly sure I applied to this one." Fairly sure is not a record.

Every state change is written to an event log rather than overwriting the last one, and each row carries how it knows, so the board can tell you the difference between an application you sent and one you meant to send.

  • Transitions are appendedThe history survives, so the row is not just its latest value
  • Confidence is on the rowUnverified and confirmed are shown as different things
  • Verification only ratchets upA confirmed application cannot quietly become a maybe again
  • Failures say whyA row that did not go through keeps the reason it did not
Open your applications
What it will not pretend

A tracker earns its keepby being honest about what it knows.

The failure mode of every application tracker is quiet confidence, a tidy board that turns out to be a list of things you meant to do. These are the three choices that stop this one becoming that.

Unverified is a state, not a gap

A row you started but never confirmed is shown as exactly that. It would be easy to display it as applied and let the board look busier; the number you would then be reporting to yourself is the one that matters least.

The history is appended, not overwritten

Each transition is written to an event table, so the row is a record of what happened rather than a single field showing where it ended up. That is what makes the timestamps trustworthy later.

It tracks what you send from anywhere

Applications you make on your own, straight from a job posting, are first-class rows. A tracker that only counts what went through its own buttons is measuring itself, not your search.

Inbox confirmation, which would read the employer’s acknowledgement email, is not built yet. The board does not pretend otherwise.

Before you move off the spreadsheet

The questions worth asking

Do I have to update it myself?
Only once per application, and only for the step nobody else can see. Opening the employer’s form and starting the application both register on their own; confirming you actually sent it is the single tap you owe it.
Does it track applications I made on my own?
Yes. Applying straight from a posting creates a normal row, with the same states and the same detail panel. A tracker that only counted what went through our own buttons would be measuring the wrong thing.
Can it read my inbox to confirm applications?
Not today. Confirming from the employer’s acknowledgement email is designed and not built. The strongest confirmation available right now is your own, and the board labels it as exactly that.
What does it keep about each application?
The role, the company, the state and when it changed, the version of the resume and cover letter that went with it and the score each had, the details submitted in the form, and the portal’s reference number where there was one.
What happens to a row that fails?
It keeps the reason. A failed application that vanishes teaches you nothing; one that says what went wrong is the difference between a repeat and a fix.
Does the tracker cost anything?
There is a free tier and no card is required to start. Tracking is where the rest of the platform’s work ends up, so it is worth having on from the first application rather than the fiftieth.

The application you cannot remember sendingis the one they are calling about.

Start your next application from here and the record is created for you. What you sent, when you sent it, and which version — ready before the call comes, not after it.

Open your applications
  • Free tier, no card required
  • Your applications stay private