Boston Work RoutesPUBLIC SERVICE / CAREER RESEARCH
Independent editorial publication. Not affiliated with the City of Boston. No sign-in, HR case service or official employee support.

Application Workshop

Track Applications Without Guessing What the Status Means

Keep a private, evidence-based application log that separates your actions, employer messages, and unresolved questions.

In this guide
  1. Use one record per position
  2. Separate three kinds of information
  3. Handle ambiguous labels carefully
  4. Plan a bounded follow-up
  5. Protect the log and close records accurately
  6. Sources and scope

A job-search log should reduce uncertainty, not conceal it behind optimistic labels. Saving a draft, sending an application, receiving a message, and being invited to an interview are different events. Record what actually happened so you can choose an appropriate next action without guessing.

Boston’s posting guidance, checked October 2, 2026, identifies the requisition ID as a useful reference. Keep the identifier shown on the current posting. This article describes a private tracking method, not the meaning of any particular employer’s status labels.

Use one record per position

Start with the exact title, employer, department if shown, posting identifier, official link, and date reviewed. Add any deadline exactly as stated, including time zone when available. If the source provides no deadline, write not stated. Do not convert that absence into a promise that the opportunity will remain open.

Store the materials you actually used in a private folder and link to that folder from your log. A version name should make sense later: role, document type, and date are usually enough. Keep different applications separate even when they use similar resumes.

Separate three kinds of information

  • My action: what you did and when.
  • Observed evidence: what a confirmation or employer message actually establishes.
  • Next step: what you intend to check, prepare, or ask.

A sent email supports a record that you sent something. It does not by itself prove that a recipient reviewed the attachment. A confirmation can support receipt while saying nothing about selection. Preserve the original message rather than replacing it with an interpretation that sounds more definite.

Hypothetical example: an applicant finishes a document and saves it locally on Tuesday, then submits materials on Wednesday and receives a receipt message. The log should preserve those events separately. Marking the application complete on Tuesday would have hidden the remaining submission step.

Handle ambiguous labels carefully

If an employer uses an unfamiliar status, record the label and observation date without translating it into a hiring prediction. Look for an official explanation or a direct message that clarifies it. A changed label can be worth noting, but it does not automatically establish whether someone has reviewed the application or how many candidates remain.

Similarly, a listing disappearing from a public page does not tell you why it disappeared or what happened to your application. Record the observation and keep the outcome unknown until there is evidence. This restraint makes the log more reliable when several searches overlap.

Plan a bounded follow-up

Follow any timing or contact instructions the employer provides. If no timeline is given, choose a reasonable review point for your own planning rather than inventing an employer response deadline. Before contacting someone, check existing messages and the posting so you do not ask for information already supplied.

A useful inquiry identifies the position and asks one concrete question. Avoid repeated messages to several staff members or assumptions that silence means a decision. Keep a dated note of the inquiry and any response. Never record speculation about individual staff members as an application fact.

Protect the log and close records accurately

The log may contain personal history and private communications. Use limited access, avoid public sharing links, and do not store passwords or identity documents in it. Remove unnecessary copies when they no longer serve a purpose, while retaining records you need for your own search.

  1. Check active records for a genuinely pending next step.
  2. Update outcomes only when supported by a message or your own decision.
  3. Distinguish a withdrawal you requested from one the employer confirmed.
  4. Archive closed records without rewriting their history.

Use the pre-submission quality check before adding a sent event, and compare roles systematically when deciding where to focus. The goal is a dependable account of your search, not a dashboard that claims certainty the available evidence cannot provide.

Related reading: Give Your Application Materials a Final Quality Check, Compare Two Municipal Roles Without Inventing a Winner.

Have a public source that changes this analysis? Suggest a correction. Please don’t send health records, financial information, employment records or account credentials.

Cookie settings