A job application tracker should show where each opportunity stands and the next action you can take. It is most useful when it connects applications, interviews, preparation, and follow-up dates in one record.
The aim is not to collect the largest possible application count. A useful tracker helps you avoid losing an interview invitation, applying twice to the same role, or arriving unprepared because the details were spread across messages.
Keep one row per role. Two applications to the same company should have separate rows when their job IDs or processes differ.
| Company | Role / job ID | Source / role link | Applied | Stage | Next action | Follow-up / check date | Interview preparation | Documents / notes |
|---|---|---|---|---|---|---|---|---|
| [Company] | [Title, ID] | [Source and saved link] | [Date / not yet] | [Stage] | [Action with date] | [Date and reason] | [Questions, examples, logistics] | [CV version, contact, evidence] |
| [Company] | [Role] | [Link] | [Date] | [Stage] | [Action] | [Date] | [Preparation] | [Notes] |
If the table becomes unwieldy, keep the stage, next action, and date in the main view. Put longer preparation notes in a separate record named with the company and role.
Choose a small set and apply it consistently:
“Waiting” should say what you expect and when you will check. It should not become a permanent category that hides every unanswered application.
All companies, roles, dates, and recruiting situations below are invented.
| Company | Role / ID | Source | Applied | Stage | Next action | Follow-up / check | Preparation |
|---|---|---|---|---|---|---|---|
| Cedar Works | Operations assistant / OA-14 | Company careers page | Nov 5, 2026 | Applied; receipt saved | Review status after the stated application window | Nov 16; portal check | Identify two examples of organizing competing requests |
| Blue Finch Studio | Junior project coordinator / PC-08 | University board | Nov 2, 2026 | Screening booked | Confirm call link and local time on Nov 9 | Nov 12; after screening | Review role, prepare project example and questions |
| Harbor Lab | Customer support associate / CS-21 | Company careers page | Oct 29, 2026 | Waiting after interview | Send requested work example by Nov 9 | Nov 13; recruiter said update by Nov 12 | Review case example before sending |
| Elm Services | Administrative assistant / AD-06 | Referral | Not yet | Preparing | Tailor CV and check required documents on Nov 10 | Nov 11; internal application target | Check working pattern and essential criteria |
| North Lane | Research assistant / RA-03 | Company careers page | Oct 20, 2026 | Closed: rejection | Archive notes; no follow-up planned | None | Keep reusable interview reflection |
The check dates have different meanings. Cedar's date is a personal review point. Harbor's follows a recruiter-provided expectation. Neither is a universal rule for when an employer should respond.
Record enough to reconstruct the application later:
Company / role / job ID:
Application date and route:
CV filename or version:
Cover letter filename or version:
Portfolio / work sample version:
Confirmation reference, if provided:
Role description saved for personal reference:
Contact and stated next step:This is particularly helpful when role pages disappear or several applications have similar titles. Save material only where permitted, and keep it organized without copying unnecessary personal information about other people.
A tracker is a personal planning record. It is not an employer's applicant-tracking system, and its stage labels do not reveal what is happening inside the employer's process.
“Prepare for interview” is too broad for the evening before a call. Break it into a few concrete checks:
| Preparation area | Action |
|---|---|
| Role understanding | Identify the main responsibilities and unclear expectations |
| Relevant experience | Choose examples you can explain accurately, including your contribution |
| Employer context | Review the employer's official information relevant to the role |
| Questions | Write questions about the work, expectations, and process |
| Logistics | Confirm format, address or link, time zone, accessibility needs, and contact |
| Afterward | Record the stated next step and a short reflection while it is fresh |
For the fictional Blue Finch screening, the candidate might prepare an example of coordinating a group assignment and one of handling a changed deadline. They should describe their actual experience, including limits, rather than upgrading a small contribution into sole project ownership.
Keep preparation separate from the interview appointment. An event at 14:00 tells you when to attend; it does not allocate the time to prepare.
Use the employer's stated process first. If the role says not to contact recruiters directly, do not build a repeated email sequence that ignores that instruction. If a recruiter gives an update date, record it and use that context when deciding whether to follow up.
There is no single follow-up interval that fits every hiring process. A personal check date helps you make a decision without implying the employer has promised a response.
For a process where a follow-up is appropriate, adapt this short message:
Hello [Name],
Thank you for speaking with me about [role] on [date]. You mentioned
that the next update was expected around [date]. I am checking whether
there is any news about the next step.
I remain interested in [specific part of the role]. Please let me know
if you need anything further from me.
Best,
[Name]After sending, record the message date and choose a sensible next check. Avoid daily follow-ups simply because the row still says “Waiting.”
First handle actual deadlines and invitations. Then review open opportunities:
You can observe patterns in your own record, but a small set of applications rarely proves why an employer responded. Treat conclusions such as “this CV caused more interviews” cautiously when roles, timing, and application routes also differ.
SelfManager.ai can hold dated preparation tasks and notes. Keep the role record as your master tracker, and put “review role description,” “confirm interview link,” or “check stated update” on the relevant work date. This is a manual job-search workflow, not recruiting automation or an employer-facing applicant system.
Yes, when there is a genuine next decision or preparation step. Give them a “Considering” or “Preparing” stage so they are not counted as submitted applications.
Use your judgment based on the advertised process and elapsed time. You can move it out of the active view while preserving the record. Do not mark it rejected unless that is actually known; “No update; inactive in my plan” is more accurate.
A maintained table may be enough. Add software when reminders, access across devices, or the volume of work creates a specific need. The useful habit is keeping the next action current.

Plan smarter, execute faster, achieve more
Create tasks in seconds, generate AI-powered plans, and review progress with intelligent summaries. Perfect for individuals and teams who want to stay organized without complexity.
Get started with your preferred account