Working session

Use the current session while you work and save a fresh file whenever you want a checkpoint.

Download empty template
Operating guide

How the job hunter should use the Job Hunter tool.

This tool replaces day-to-day spreadsheet tracking. The goal is to keep the application record truthful, current, and easy to hand off after every real action.

Shortest useful workflow

Do these every time.

  1. Open a job from Jobs or move it in Pipeline.
  2. Pick or generate the tailored resume version.
  3. Submit the application.
  4. Immediately record the status, resume used, and application date.
  5. Add a follow-up date if the job should come back into the queue.
  6. Export the session file before you stop or hand off work.

Field guide

What matters most.

StatusThe current workflow stage for the job.
Resume versionThe exact tailored resume used or prepared for this job.
Resume URLThe link to the version that was actually submitted.
Application dateThe date the submission was actually completed.
Follow-up dateThe date this job should return to the top of the queue.
NotesOnly keep notes that future-you will care about.
Backend file workflow
  • Load backend file when you start with an exported handoff.
  • Current session keeps the working copy moving while you work.
  • Save session file downloads the current state so another person or another machine can continue later.
  • Reset session rebuilds the current working copy from the empty starter file.

Session safety

Use files for checkpoints and resets.

Empty backend fileUse this when you want a clean starting point.
Demo fileUse this when you want an example session structure.
Reset sessionReplace the current session with the clean starter file in this browser.