Build a job application tracker you will actually keep using

Track decisions, not just application counts

When several applications are in progress, it becomes easy to confuse which CV you sent, when a role closes or whether an email needs a response. A tracker is a small record of those decisions. It can be a spreadsheet, a notebook or a document; the best version is one you can update immediately after taking action.

This guide offers an original workflow for organising your own search. It is not an employer database and does not provide verified vacancies. You remain responsible for checking each opportunity at its official source.

The National Careers Service recommends keeping a copy of submitted application answers. Add that habit to a tracker so your notes describe what you actually sent, rather than what you remember writing.

Employer | Role | Reference | Official URL | Date checked | Deadline + zone | Status | CV version | Submitted | Next action | Review date

Set up a practical tracking routine

Start with the minimum useful fields

Create one row per distinct vacancy. If the same opening appears on several job boards, keep the employer’s reference and official posting in a single row. Duplicate rows can make your progress look larger while hiding repeated applications to the same role.

Keep sensitive documents out of a shared tracker. You can record “identity check requested” without storing a passport number or uploading a scan into a sheet that other people can access.

Separate the deadline from your own target date

An employer’s closing date is an external constraint. Your target submission date is a planning choice. Record them separately so that a personal target does not accidentally become a claimed employer deadline.

For a role closing on Friday, you might plan to finish the draft on Tuesday, review it on Wednesday and submit on Thursday. That example is only a scheduling method. Some employers close roles early, and a deadline without a time zone needs clarification rather than an assumption.

Give every active row a next action

“In progress” is not a task. “Check whether the qualification is essential”, “rewrite the customer-service example” or “confirm interview time zone” tells you what to do when you reopen the tracker. Keep the next action small enough to complete in one sitting.

Use a short status list and define what each label means. “Submitted” should mean the application was sent through the requested route, ideally with a confirmation saved. A half-completed online form belongs under “preparing”. A role you decided not to pursue belongs under “withdrawn” or “not applying”, with a brief reason if that will help future decisions.

Record the version you actually sent

Save your CV, letter and application answers in a private folder with a consistent naming system. For example, role-reference-date is easier to recognise later than a sequence of files named “final”. Link the tracker to the saved copy, not to a working document you will continue changing for another employer.

After submission, save the acknowledgement or note the confirmation number if one is provided. If the site does not confirm receipt, record that uncertainty and check the employer’s stated support route. Do not submit the same application repeatedly simply because an automated email is slow.

Plan follow-ups around the employer’s instructions

If the vacancy or confirmation gives a timeline, use it. If it asks applicants not to contact the team, respect that instruction. When no timeline is stated, choose a reasonable review point in your own tracker rather than assuming that silence means rejection.

A useful follow-up is short and identifies the role and application date. It asks whether an update is available without demanding a decision. Record the date and response so that you do not send overlapping messages from different channels.

Run a weekly review with three questions

First, what is due soon? Sort active rows by deadline or next-action date. Second, what is blocked? Identify missing documents, unclear requirements or unanswered questions. Third, what have you learned? Look for repeated mismatches between the roles you choose and the evidence you can provide.

For example, if several suitable roles ask for the same software skill, that is a reason to plan genuine practice. It is not a reason to add the software to your CV before learning it. If your applications are concentrated in roles requiring a licence you lack, reconsider the search filters.

Measure progress without misleading yourself

Application count is only one measure. Also notice the number of suitable roles researched, complete tailored submissions and interviews that help you learn. Do not compare your rate with someone else’s without understanding the roles, locations and eligibility conditions involved.

Keep closed rows for your own reference, but remove private information you no longer need. Review sharing permissions if you use a cloud spreadsheet. A tracker should reduce confusion, not become an unnecessary store of other people’s contact details.

Your first session can be simple: add the opportunities you are currently considering, assign one next action to each and schedule your next review. Expand the tracker only when a new field solves a real problem.