Editorially revised on 9 October 2026.
A personal job application tracking system records what you applied for, what you submitted and what needs attention next. A notebook or spreadsheet can do this. You do not need a paid tool to begin, and keeping a tracker does not guarantee an interview.
This guide builds an original applicant-side record with fictional examples. It is separate from an employer's applicant tracking system: your spreadsheet cannot reveal a recruiter's internal status, change screening decisions or establish why you were rejected.
Yale's job search tracking resource supports keeping application and company records in ordinary tables. The worksheet, evidence labels and reconciliation cases below are original; they are not a copied Yale template or a claim that Yale endorses this particular system.
Start with one application per record
An employer can advertise several similar vacancies. Record the role title and vacancy identifier, not just the company name. Two applications to the same organisation may have different locations, deadlines, qualifications and document requirements.
Keep the official vacancy URL with the record. If you first discover a role on a job board, verify its employer application route before entering personal information. Save the date you checked it. A copied advertisement may remain online after the employer closes recruitment, so an old bookmark alone is insufficient evidence that applications are open.
Use your own short record identifier, such as APP-014. This is an organising label, not the employer's application number. Store a received application number separately and do not invent one when the portal provides none.
Keep preparing
Continue with Sarkari Resume Templates₹299 — coaching के एक महीने से काफ़ी सस्ता / far cheaper than a month of coachingBuild a compact worksheet
Start with these fields. Add columns only when they answer a recurring question; an elaborate tracker that is difficult to maintain can obscure the next action.
| Field | What to record |
|---|---|
| Vacancy | Role, employer and official identifier |
| Source | Official URL and date checked |
| Deadline | Published date, time and time zone |
| Submission | Actual date and acknowledgement |
| Documents | Names of the exact files sent |
| Evidence | Portal status or dated message |
| Next action | Task, owner and intended date |
| Closure | Confirmed outcome or your withdrawal |
For an interview invitation, add its date, time zone, location or meeting method and any requested preparation. For a government application, preserve the relevant notice and amendments, qualification information and permitted correction instructions. Follow the recruiting body's rules rather than treating your worksheet as authoritative.
Separate a private notes sheet from a summary you might share with a mentor. A mentor normally does not need identity document numbers, application passwords, private recruiter messages or another person's contact details to help you prioritise work.
Use statuses that describe evidence
Choose labels with clear meanings. “Saved” means you found the role; it does not mean you applied. “Prepared” means the materials are ready. “Submitted” means you have submission evidence. “Interview invited” requires an actual invitation. “No response as of date” records uncertainty without converting it into rejection.
If a portal displays “under review,” quote that status with the observation date. Do not turn it into “shortlisted” unless the employer actually says so. An automated acknowledgement may confirm receipt while leaving eligibility and screening unresolved.
You may close a record for your own planning because you withdrew or stopped pursuing it. Label that decision as yours. Keep employer-confirmed rejection distinct from an application you simply archived after silence.
Preserve the submitted version
Suppose you revise your resume after applying. The latest file on your laptop may no longer match the one the employer received. Keep a dated copy of the submitted resume and cover letter, using a private folder and an understandable filename.
A record could say “APP-014 resume submitted 9 October; project section emphasised spreadsheet cleaning.” It should not say “resume optimised” without identifying the version. When invited to interview, read the submitted copy so that your explanations match its dates, skills and contributions.
Harvard's resume guidance supports clear, factual descriptions tailored to the intended role. The version-control worksheet here is our original organisational exercise. For writing the document itself, use the resume mistakes guide.
Fictional case: two similar vacancies
Meera, a fictional graduate, saves two analyst vacancies at a fictional employer: one asks for spreadsheet reporting and another for SQL project evidence. She makes separate records, checks each official identifier and prepares distinct truthful project summaries.
She submits only the reporting application initially. Her tracker leaves the SQL vacancy at “prepared,” with a next action to review its qualification requirements. Counting both as submitted would create a false picture of her activity and could cause her to miss the second deadline.
When a message arrives without a vacancy identifier, she checks the sender against the employer's published recruitment route and asks which application it concerns through the verified channel. She does not assume it applies to both records or upload documents to an unfamiliar link merely because its subject mentions the company.
Fictional case: an unconfirmed submission
Arjun fills a portal form and clicks submit, but the browser displays an error. There is no acknowledgement and the portal still shows a draft. His record says “submission uncertain,” with the time and error observed.
He checks the portal's instructions and status before attempting again. If payment or a duplicate-application rule is involved, he uses the published support route instead of repeatedly submitting. He records the eventual acknowledgement only after receiving it.
This case illustrates the value of separating intention from evidence. It does not establish that every error means failure or that every employer permits duplicate submissions. A tracker helps document the question that needs resolution; the relevant portal determines the answer.
Plan follow-ups around instructions
Record any promised update date or stated contact policy. If an employer says not to contact individual staff or to use a specific portal, follow that instruction. There is no universal number of messages that will produce an interview.
A short original follow-up might read: “I submitted my application for vacancy X on date Y. The published process suggested an update after date Z. Could you advise whether an update is available or whether I should continue checking the portal?” Send it only through an appropriate verified channel.
After sending, record the date and purpose. A reminder is a prompt to reconsider whether contact is appropriate, not an instruction to send repeatedly. Silence should remain recorded as silence. Avoid inventing urgency or implying an offer you do not have.
Review the tracker without misleading yourself
At a weekly review, ask which deadlines need checking, which records lack submission evidence and which invitations require preparation. Check whether a vacancy has changed or closed and whether a new amendment affects your application.
If you count outcomes, define the denominator and period. “Two invitations among eight acknowledged applications submitted in this period” is more transparent than “my success rate doubled.” Some applications are still pending, roles differ and small totals cannot establish which change caused a result.
Track issues you can act on: missing documents, outdated links, inconsistent dates and late preparation. Keep a separate learning note for recurring skill gaps. Do not attribute every rejection to a resume format or algorithm when the employer has not provided that explanation.
Keep the record usable and private
Use access controls appropriate to your chosen tool. Check sharing settings before sending a link; a public spreadsheet can expose more than the intended row. Store credentials separately and avoid putting full government identifiers or payment details in a general-purpose tracker.
Maintain a backup you can retrieve. Periodically remove redundant copies and review who still needs access, following your own retention needs and any applicable instructions. Do not delete the only evidence of a submission you still need to establish.
Questions applicants ask
Can I use paper? Yes. Leave space for updates and keep supporting records in an organised private folder. The fields matter more than the tool.
Should I track every vacancy I see? You can keep a separate saved-opportunities list. Move a vacancy into the active tracker when you intend to evaluate or apply for it, so casual browsing does not inflate application counts.
Is a tracker an ATS workaround? No. It helps you manage your own records. It does not certify compatibility or alter an employer's selection process.
What should I do today? Reconstruct one recent application from its official notice, submitted files and acknowledgement. Identify the next action and verify any deadline before expanding the system. For the wider search, see job search strategies and interview mistakes.