A tracker should answer decisions, not merely count applications.
A list of company names and dates can tell you how busy the search has been. It cannot tell you which resume an employer received, whether the posting required a license, when the recruiter promised an update, or what you should do tomorrow. A useful tracker preserves the submitted record, the decision context, and one next action.
| Record layer | Fields to track | Why it matters |
|---|---|---|
| Identity | Employer, role, location, requisition/job ID, posting URL | Distinguishes similar roles and gives support a precise reference. |
| Submission | Application date, exact resume filename/version, cover letter version, submitted answers, confirmation or receipt | Shows what actually went to the employer—not what is in your current profile. |
| Decision context | Job-description snapshot, required qualifications, salary range, work arrangement, posting close date, source | Preserves the opportunity after the live posting changes or disappears. |
| Communication | Recruiter/contact, last contact date, stated timeline, interview dates | Keeps follow-up anchored to real events. |
| Action | Current stage, next action, follow-up date, owner, completed date | Turns the tracker into a decision system instead of an archive. |
| Outcome | Rejected, withdrawn, ghosted, offer, accepted/declined, reason when known | Makes funnel analysis possible without inventing explanations. |
Capture the record at five specific moments.
| Moment | What to record |
|---|---|
| Before applying | Save the URL, requisition ID, closing date, job-description text, salary/work arrangement, and intended resume version. |
| At submission | Record the date, exact attachment filenames, key screening answers, and confirmation/application ID. |
| After applying | Add the current stage and one concrete next action with a date. |
| After contact or interview | Update the last-contact date, people involved, stated timeline, interview evidence, and next commitment. |
| At disposition | Record the outcome and date. Add a reason only when the employer supplied it or clearly label your note as an inference. |
Do the smallest update while the evidence is still open. Copying the confirmation number immediately takes seconds; reconstructing it after the tab closes may be impossible. The submission confirmation checklist explains which signals prove receipt and which do not.
Remember exactly which resume you sent.
Store the filename or a version label with each application. A useful name contains your name, target role or resume family, and a version date—for example, Jordan-Lee-Product-Resume-2026-09.pdf. The label in the tracker must identify the actual uploaded file, not the document you intended to select.
Keep exported resumes in a stable folder rather than overwriting one generic resume.pdf. If you discover the wrong attachment later, the record lets you compare the difference before deciding whether to correct it. Use the wrong-resume recovery guide instead of withdrawing reflexively.
Save the job description before it changes or disappears.
Copy the role summary, essential requirements, responsibilities, location/work arrangement, salary range, closing date, and requisition ID into a private snapshot. Plain text is often more searchable and durable than a screenshot alone. Keep the original URL and capture date beside it.
The snapshot helps you prepare for interviews, interpret a screening question, compare an updated posting, and evaluate an eventual offer. It should not contain scripts, tracking pixels, or unnecessary page markup. If the posting includes personal recruiter details, retain only what you legitimately need for the application.
LinkedIn distinguishes applications completed on LinkedIn from applications redirected to an external employer site; off-platform applications may not be recorded in LinkedIn's own tracker. Read LinkedIn's application-flow explanation. Keep your own record regardless of the source.
Make “next action” a first-class field.
“Applied” is a state; “follow up with the listed recruiter one business day after the promised date” is an action. Every active application should have at most one next action and, when useful, a date. Examples include preparing for an interview, sending a thank-you, waiting until the posting closes, checking the portal, supplying a requested document, or closing the record.
Use the employer's timeline rather than a universal reminder. USAJOBS notes that agencies may wait until the announcement closes to review applications and may need up to two weeks after closing. See USAJOBS contact guidance. The follow-up date calculator turns the dates you actually know into a planning window.
Use metrics with clear denominators.
- Response rate: applications with a substantive employer response divided by submitted applications.
- Interview rate: applications that reached an interview divided by submitted applications.
- Offer rate: offers divided by submitted applications—or by final rounds when diagnosing the late funnel.
- Time to first response: days from submission to the first substantive response, not a portal view.
- Source performance: outcomes grouped by referral, company site, job board, recruiter, or another honest source label.
Do not treat an application view as an interview or a rejection. LinkedIn explicitly says a view or resume download does not guarantee a message, interview, or offer. Read the official explanation. Small samples can move dramatically after one outcome, so use the numbers to generate questions, not promises.
Keep the tracker private and portable.
Do not store passwords, security-question answers, Social Security or national ID numbers, copies of identity documents, bank information, or sensitive voluntary demographic answers in a general application tracker. Store only what helps manage the search. Export regularly to a format you control, and protect any file that contains private contact or application history.
The Jobsistant tracker below stores data in this browser and supports full-fidelity JSON plus CSV import and export. Clearing browser storage can erase the local copy, so export a backup before changing browsers or devices.
Common job application tracking questions.
At minimum, save the employer, role, requisition ID, application date, posting URL, exact resume version, current stage, and next action. Submission proof and a job-description snapshot make the record much more reliable.
Either can work if it preserves the same underlying record. A spreadsheet is flexible; a tracker can make reminders and stage changes easier. Exportability matters so you are not trapped in one tool.
Keep active records through the process and retain completed records long enough to learn from your search and answer later questions. Avoid storing passwords, government identifiers, or unnecessary sensitive information.