This template combines the application date, submitted document versions, latest contact, and your own plan. Record what actually happened separately from what you intend to do next. The worked example uses a fixed fictional snapshot dated October 23, 2026.
Give each opportunity its own record
The original example contains three opportunities:
| ID and opportunity | Actual state in the fictional record | Materials and contact |
|---|---|---|
| A1: Cedar Exhibits, Program Assistant | Applied October 20, 2026. | Resume R3 and letter L2; acknowledgement received. |
| A2: North Archive, Visitor Coordinator | Saved prospect; no application sent. | Required writing sample still to check. |
| A3: River Studio, Operations Assistant | Applied October 18, 2026. | Resume R2 and letter L1; interview invitation received. |
The snapshot contains two submitted applications and one prospect. Saving A2 does not make it a third submission. A1's acknowledgement confirms a contact event in the example; it is not an interview invitation.
The Michigan work-search activity worksheet illustrates keeping contact dates, activities, employers, contact methods, and evidence records together. This template uses that general record-keeping idea for a personal application tracker, with original document-version and next-action fields.
Keep the submitted packet identifiable
Select A1 to inspect Resume R3 / Letter L2. Those labels refer to the materials sent with that application. A3 retains Resume R2 / Letter L1 even if you have since prepared newer versions.
In your own tracker, use version labels and document references you can find again. Record the packet after submission so you can review the same material before an interview. Keep a revised resume separate from the version already sent.
The example's packet references are text labels. They are not download links or proof that those fictional files exist.
Put your next action beside the latest contact
| Record | Latest known position | Self-planned next action |
|---|---|---|
| A1 | Acknowledgement received; no further contact supplied. | Follow up on October 27, subject to the employer's instructions. |
| A2 | Application not sent. | Check the writing-sample requirement on October 23. |
| A3 | Interview invitation for October 25 at 14:00 America/New_York; joining route absent. | Confirm the joining route on October 23. |
Choose Next actions for October 23 to show A2 and A3. A1's planned date is later. The filter uses the displayed snapshot date; it is not a live reminder service.
An unanswered application stays in its recorded state until you have new information. Silence alone does not establish rejection. Likewise, a follow-up date you choose is your plan, not a deadline the employer supplied.
Use fields that make the next review quick
The blank tracker includes employer, role, saved source or posting reference, application date, submitted material versions, latest actual contact, event date and time zone, evidence reference, status, next action, and self-planned action date.
Keep the contact record short and specific. “Acknowledgement email received” tells you more than “in progress.” If a message includes an instruction or date, keep its reference so you can check the original wording.
Use the prospect/submitted filters to review the correct group. When editing a local next-action note, refresh the review so the displayed selection reflects the updated entry. The browser example keeps temporary notes in the open page; maintain your actual tracker in the place you use for ongoing records.
Create a tracker with your own applications
Create one complete, self-contained HTML job search tracker.
Snapshot date: [FILL IN]
For each opportunity, supply:
- Employer, role, and saved posting/source reference
- Prospect or actually submitted status
- Application date, if submitted
- Submitted resume, letter, and other document version references
- Latest actual contact, source reference, and event date/time zone
- Next planned action and my chosen action date
- Missing details to check
[PASTE MY RECORDS]
Keep prospects separate from submitted applications. Count submissions
only where the record says an application was sent. Do not infer an
interview from an acknowledgement or rejection from silence. Keep my
planned dates separate from employer instructions.
Provide prospect/submitted filters, next actions for the stated snapshot
date, and record details showing the exact submitted packet. Do not
invent links to files or claim to connect to an employer's hiring system.
Include a blank opportunity scaffold with missing employer/role/status
feedback and temporary next-action notes. Keep views synchronized after
edits so an old filter result does not look current. Preserve notes when
switching records and ask before resetting typed work. No sending,
reminders, automatic status updates, storage, or claimed saved records.
Use text of at least 16px, labeled keyboard-accessible controls, and
a layout readable at 360px without horizontal scrolling. Put CSS and
JavaScript inline with no external dependencies. Return complete HTML.
Review the next action before starting another application
For this snapshot, A2 needs a requirement check and A3 needs the interview instructions. Complete those checks before treating either record as ready for its next step.
If you prepare an HTML overview in NOS, clarify the instruction above the record filters so it asks for a task you can finish. “Obtain the joining route” gives the next review a clearer starting point than “prepare interview.” Keep received messages and submitted documents with your actual application records.