One row per posting
Do not merge two locations, two departments, or two job IDs into one row even if the employer name matches.
HireTea Independent hiring research
Application evidence, status, and tracker guide
Track what happened after you applied.
Keep one row for each exact posting, attach the dated source that supports each important field, and give every active row one next action and date. Status labels stay separate from outcomes; pay and schedule notes stay attached to the role that disclosed them. Your private saved applications live in a separate browser workspace.
Browser-local workspace One posting per row Evidence before interpretation
1 row for each exact posting
1 action for each active row
1 source attached to every claim
Quick answer
What should an application tracker include?
A useful application tracker should include the company, role, location, job ID, posting URL, date saved, application status, next action, next action date, pay notes, schedule notes, source saved, contact route, and a short decision note. The tracker should not become a diary. Each row should answer three questions: what is this lead, what evidence supports it, and what is the next action? If a saved field cannot change a decision, support a follow-up, or reconstruct what you saw, it probably does not belong in the active tracker view.
One next action
Every active row needs one clear next action and one date so the tracker stays useful during a busy week.
Evidence before memory
Use posting links, portal messages, invite details, and planner notes instead of relying on what you remember.
Saved workspace
The local tracker has moved to its own page
Open the dedicated workspace to add, review, export, or delete postings saved in this browser. Existing local records use the same storage and remain available after the move.
Source routes
Use a company guide to find evidence, then track the exact posting
The guide can help locate an application account, employer boundary, pay source, or status route. Your tracker row should still use the posting URL, job ID, confirmation, and messages for the application you actually submitted.
Walmart How much does Walmart pay, and what does applying involve? Amazon What does Amazon pay, and which account do you apply through? McDonald's What does a McDonald's restaurant pay, and who hires you? FedEx What does FedEx pay, and which FedEx company is hiring? Target What does Target pay, and how do you apply? Kroger What does Kroger pay, and which banner is hiring? TJX Companies What do TJ Maxx, Marshalls, and HomeGoods pay? Lowe's What does Lowe's pay, and is the job still open? Starbucks What does Starbucks pay baristas and shift supervisors? Chick-fil-A What does a Chick-fil-A restaurant pay? Apple What does Apple pay retail and corporate roles? Taco Bell What does a Taco Bell restaurant pay? Dunkin' What does a Dunkin' restaurant pay?
Columns
Tracker columns and how to fill them
The local vault and downloadable CSV keep the fields intentionally plain. You can work in this browser, export CSV or JSON, use a spreadsheet, copy the structure into notes, or rebuild it in another tool. The important part is that each field supports a decision instead of just storing clutter.
| Column | How to fill it | Why it matters |
|---|---|---|
| Company, role, and location | Use the exact employer name, role title, site, department, and location from the current posting. | It prevents you from mixing two similar postings or applying local details to the wrong role. |
| Job ID and posting URL | Copy the job ID, posting URL, platform, and date saved before the listing changes. | These fields give you a source trail if a posting expires, redirects, or gets replaced. |
| Application status | Use plain labels such as saved, not applied, applied, waiting, invited, offer, declined, closed, or paused. | A small status vocabulary makes the tracker easy to scan and reduces duplicate applications. |
| Next action and next action date | Write one concrete action and one date, such as compare role, check portal, prepare questions, or follow up. | Every active row should tell you what to do next without rereading the entire posting. |
| Pay notes and schedule notes | Copy pay wording, hours, availability, commute concern, and first-week timing exactly when possible. | Pay and schedule details are often the reason a lead moves from promising to weak. |
| Source saved and contact | Point to the posting, portal message, invite, email thread, local contact, or company hub that supports the row. | Evidence makes follow-up, comparison, and final decisions less dependent on memory. |
Status workflow
Status workflow from saved posting to decision
Status labels should move the row forward. If a row stays active but never gets a next action, it becomes noise. Use the workflow below to decide when to apply, compare, follow up, prepare, accept, decline, or close the row.
| Status | When to use it | Next action to write |
|---|---|---|
| Saved | The posting is interesting but you have not decided whether to apply. | Verify role title, location, schedule wording, pay wording, and application platform. |
| Not applied | You are still comparing the role against another active lead. | Use the posting checklist, red flags guide, company research checklist, and comparison worksheet. |
| Applied | The application was submitted and the row now depends on employer response. | Save confirmation text, portal status, account email, message thread, and first follow-up date. |
| Invited | The employer moved the row into an interview, assessment, local conversation, or next-step task. | Record invite time, channel, contact, preparation topic, and the date you need to confirm details. |
| Offer or decision | The row needs written detail before you accept, decline, or keep negotiating priorities. | Compare pay, schedule, commute, first-week instructions, role scope, and the deadline for your answer. |
| Closed or paused | The posting is expired, weakly supported, duplicate, or no longer worth a next action. | Write the close reason so you do not reopen the same weak lead later. |
Follow-up dates
Follow-up dates to put in the tracker
The next action date is the field that keeps a tracker alive. It should be tied to a reason, not a random reminder. If the employer gives a clear instruction, use that instruction. If not, use the row status and the source you saved to choose a practical check-in date.
| Stage | Date rule | Tracker note |
|---|---|---|
| After saving a posting | Same day or next day | Decide whether to apply, compare, or close before the posting disappears from your short list. |
| After applying | Three to five business days unless the employer gives a different window | Check portal status first, then use the follow-up planner if no next-step instruction is visible. |
| After a fast-response signal | 24-48 hours | Use the original channel and keep the message short, specific, and tied to the role title. |
| After an interview invite | Before the scheduled time | Confirm time, format, location or link, interviewer name when known, and preparation focus. |
| After offer details arrive | Before the response deadline | Compare pay, schedule, commute, role scope, first-week instructions, and unanswered questions. |
Group definitions
How to choose the right tracker group
You do not need a separate tracker for every employer. Use one row format, then tag the row with the tracker group that explains what needs the closest attention. That tag makes weekly review faster because similar rows need similar next actions.
| Group | When it applies | Tracker move |
|---|---|---|
| Portal status tracking | The posting sends you through a candidate account or employer careers portal. | Record account email, platform, confirmation message, status text, date viewed, and next action. |
| Fast-response tracking | The employer language suggests a quick contact window or a short action deadline. | Set the next action date while applying, then check the message thread before sending another follow-up. |
| Local-site tracking | The role can vary by store, property, franchise, department, facility, or local manager. | Keep location, operator, department, local contact, and local instructions separate from broad brand notes. |
| Interview handoff tracking | The next useful signal is a phone, video, in-person, or manager handoff. | Save invite date, interviewer title, channel, preparation topic, and the status after the conversation. |
| Pay and schedule tracking | The main decision risk is unclear pay wording, hours, availability, commute, or first-week timing. | Copy pay and schedule wording exactly, then link it to the offer, compare, and availability pages. |
| Evidence-first tracking | The page or posting leaves a detail unresolved. | Write the open question, save the source used, and decide whether the lead should pause or continue. |
Mistakes
Application tracker mistakes to avoid
A tracker should reduce uncertainty. If it grows into a long list of vague leads, it will create more work than it saves. Keep the columns plain, close weak rows, and make each active row earn its place with evidence and a next action.
Tracking only company names
A company name alone is too thin. Add role, location, job ID, posting URL, platform, status, and next action so the row can guide a decision.
Using vague statuses
Labels like maybe, interesting, or later do not tell you what to do. Use a status that points to an action, a date, or a close reason.
Forgetting source dates
A posting can change, expire, or move to a different platform. Save the date viewed next to the URL and update the row when a message changes.
Mixing pay and schedule from another row
Keep each posting separate. Do not copy pay notes, shift language, or local instructions from one location into another application row.
Leaving rows active forever
A tracker should reduce clutter. Close rows that no longer have a clear next action, useful evidence, or realistic fit.
Status interpretation
Read a status label without inventing an outcome
Employer systems use different labels, and some employers send applicants to a local manager instead of a central dashboard. The safe interpretation is narrow: record exactly what the current system or message says, identify what it does not establish, and choose one next action. A live posting, quiet profile, or unchanged label is never enough by itself to predict selection.
| Status family | What the evidence supports | What it does not prove | Tracker action |
|---|---|---|---|
| Saved or draft | The lead or unfinished form exists in a browser, profile, or employer system. | It does not prove submission or employer receipt. | Finish or close it; save the job ID and check for a confirmation after submitting. |
| Submitted or received | The system recorded delivery of an application at the displayed time. | It does not prove a person reviewed it or that requirements were met. | Save confirmation and the employer's stated response window; set one evidence-based follow-up date. |
| Under review or consideration | The employer has not publicly closed the application in that system. | It is not an interview promise, ranking, or estimated decision date. | Record the exact wording and date; prepare only for the next step the employer actually requests. |
| Action required or assessment | A named task is assigned, often with a deadline or completion state. | Assignment or completion does not prove a passing score or advancement. | Save the task name, sender, due date, accommodation route, completion screen, and any restart rule. |
| Interview or scheduling | A conversation or scheduling handoff has been requested for the named role. | It does not establish the round count, interviewer authority, or an eventual offer. | Confirm time zone, format, location or link, contact, role, and what evidence to prepare. |
| Offer or conditional offer | Written terms or a contingent next step are available for review. | A conditional offer is not necessarily cleared for Day 1, and a verbal summary is not the full agreement. | Save deadline, employer, pay basis, schedule, contingencies, benefits eligibility, start date, and the controlling document. |
| Closed or no longer considered | That application is no longer active in the displayed system. | The label usually does not prove the reason or create a rule for another requisition. | Record the close date and reason only when stated; archive the row without rewriting the employer's explanation. |
Evidence record
Save evidence by strength and hiring stage
Evidence does not need to be complicated, but different records answer different questions. A current requisition can support pay and duties; it cannot prove submission. A portal confirmation can prove receipt; it cannot prove review. Save the strongest record available for the next decision, and keep weaker discovery signals as questions rather than conclusions.
| Evidence level | Examples | How to use it |
|---|---|---|
| 1 · Current transaction record | Submitted confirmation, assigned portal task, recruiter invite, written offer, or onboarding instruction for the exact job. | Use for the applicant's current status, deadline, required action, and written terms. Keep the date and message context. |
| 2 · Exact current requisition | Official job detail with job ID, employer, location, role, pay, schedule, duties, qualifications, and date viewed. | Use for role fit and pre-application comparison. A live posting does not prove submission, review, or selection. |
| 3 · Official durable policy | Employer hiring FAQ, benefits eligibility page, candidate privacy notice, government rule, or controlling plan language. | Use for the scope the source actually names. Do not transfer a national or corporate policy to a franchise or excluded worker group. |
| 4 · Official local or operator evidence | Property, store, franchisee, local Operator, union trust, or official vendor page tied to the selected employment path. | Use when the local entity is identified. Preserve the relationship to the brand and confirm the offer employer. |
| 5 · Discovery signal | Search card, cached result, archive, aggregator, forum, or old applicant comment. | Use only to form a verification question. Do not treat it as current status, open headcount, pay, or a universal rule. |
Fields to keep with the row
Posting URL, job ID, role title, location, department, platform, date viewed, and exact pay or schedule wording.
Application confirmation, portal status, account email, task label, message thread, and next-step deadline.
Company hub URL, published evidence guide, pay research page, or comparison worksheet that helped you decide what to verify.
Interview invite, contact name or title, format, preparation topic, time zone, location or link, and date confirmed.
Offer message, start-date note, first-week instruction, pay detail, schedule detail, and reason for accepting, declining, or pausing.
Reader check
Did this page help you decide your next step?
Your response stays in this browser. Analytics receives only the selected category.
Found a source problem? Email the editor.
What was still missing?