The Application Tracker Row Standard, Seven Fields Graded Pass or Fail

This guide sets out what one row in a job application tracker has to hold, and the test each field must pass. When a recruiter calls weeks later, or a follow-up comes due, you should be able to see what you sent and what to do next without guessing. It is for people applying to dozens of companies at once, in whatever tool they use to track. It is not another template. It gives you seven criteria with a pass test for each, entry rules for each status, a per-row procedure, and a checklist for auditing the whole tracker in one sitting.

What makes a job application tracker row complete?

A row is complete when all seven criteria below pass and no cell is blank. If any one criterion fails, the row is incomplete, however many columns it has.

Arguing about column counts gets you nowhere. The template pages that rank for "job application tracker columns" can't agree on a number: one lists 5 must-haves, another 8 essentials, and others suggest 10 or 12. None of them says when a row is finished. A standard needs a pass test for every field, written so that two people grading the same row reach the same verdict.

A row has to do four jobs:

• Interview prep: show what the job said, and what you claimed, on the day you applied.
• Duplicate and agency checks: show whether you, or someone acting for you, already submitted you to this employer.
• Follow-ups: show who to contact, and when.
• Close-outs: show when the row stops needing attention, and why.

These are the seven criteria:

1. Posting text. The full posting is stored as text you can open offline, with its URL and your own capture date.
2. Req ID and channel. The requisition ID is recorded exactly. That is the reference number the employer's system gives the opening. The row also records the channel you applied through, any agency by name, and the email address on the application.
3. Resume file. The row names one exact filename, and that file is a frozen, dated copy stored locally.
4. Pay figure and answers. The pay number you entered is recorded exactly as typed. A copy of your screening answers and cover letter sits with the resume.
5. Contact. The field holds a named person and their role, or the literal text "none found".
6. Next action. One verb and one date in ISO format (YYYY-MM-DD). Only one action.
7. Close-out. Either the row is open and its next action falls before your close-out threshold, or it is closed with a reason and a date.

Status entry rules

A status is only useful if it has an entry rule. A row moves into a status when the condition is true, and from then on it must pass the criteria listed.

Closed rows still have to pass criteria 1 to 4. A recruiter sometimes calls about a role you closed weeks ago, and the record of what you sent is exactly what you need on that call.

Why save the job description as text before you apply?

Because the posting is usually gone by the time a slow employer calls. The median US posting stays live about 23 days, but 36% of candidates have still heard nothing one to two months after applying.

Studies of different markets, using different methods, land in a narrow band:

The tail is long. A quarter of postings stay up more than 90 days and a tenth more than 180, and the LinkUp research attributes most of that spread to differences between employers. You cannot tell at apply time which postings will survive, so you capture every one.

The silence is common, not an edge case. Indeed's report found 35% of applications were never acknowledged at all. Criteria Corp, as reported by Fortune, found the share of applicants ignored by employers rose from 38% to 48% in one year. No survey I have found gives a median number of days to first response, so you cannot plan around a typical callback date. Plan for the posting to be gone.

The posted date on job boards understates a posting's age

Job boards date a posting from when they found it, and the date resets every time the role reaches a new board. Measured by the employer's own date, the median live posting is already 28 days old. Record your capture date as a separate field and never copy the board's date into it. This also settles the timing question: the capture date tells you how old your information is, not how old the job is.

Capture methods compared

The standard is a pasted text file plus a screenshot. The text gives you search, and the screenshot keeps the layout and any published pay band. Together they take 2 to 3 minutes. If you print to PDF instead, open the PDF and check that the full description, the headings and the application instructions are all readable.

Pass test for criterion 1: you can open the stored text with no network connection and read the posting through to its last section. The URL and capture date are on the row. A URL alone fails.

What it proves: you can prepare for the interview against the job as advertised, not the job as you remember it.

When it lies: the file exists but stops partway through, because a "Show more" section was never expanded.

Sources disagree on when to capture. Some say before you submit, others treat it as part of logging afterwards. I side with before. You need the req ID and any posted pay band in front of you while you fill in the form, and capturing after submission is exactly when people skip it. One source suggests keeping only a lightweight record (company, role, date, status, source) for applications that get no response. That fails because you can't know at apply time which applications will get one. Once a response arrives, the posting may already be gone.

Which resume version did I send? Only a local frozen copy can say

The applicant portal cannot reliably tell you, so the row has to point to a file you stored yourself when you submitted. Workday locks a submitted application and documents no way to download your resume. Greenhouse keeps one resume and replaces it with your latest upload.

Here is what is publicly established about each portal:

• Workday: university candidate guides say you cannot change an application after submission. One guide lists a "View submitted materials" option, but no download action for your own resume is documented.
• Greenhouse: the MyGreenhouse candidate FAQ says it does not support multiple resumes, and your most recently uploaded resume is used by default. You cannot change the email on a submitted application. Companies can choose whether to share status and emails with you at all.
• Lever and iCIMS: what a candidate can see again is not established publicly. If you need to rely on it, test it with one application and write down what the portal shows.
• Screening answers and salary fields: no vendor documentation says whether a candidate can see these again on any of the portals above.

So the only safe assumption is that the portal won't give you back what you typed.

Which portal you will meet most often

In Refolk's index of professional profiles, Workday is the ATS skill most often tagged on US recruiter-titled profiles, by a wide margin.

The most common employers among these profiles are Takeda, Boeing, Siemens and Lenovo for Workday. For iCIMS they are Amazon Web Services, then Plaid and Lenovo, and for Greenhouse, Meta, then Snowflake and Datavant. Treat these counts carefully: they are self-declared skills, so they are only a proxy for which systems employers run. They do point one way, though. The portal you are most likely to meet is the one that locks your application, so the frozen copy is not optional.

Pass tests for criteria 3 and 4

Criterion 3 passes when the row names a filename that matches a stored file with a date in its name. A pattern such as Company_Role_ReqID_YYYY-MM-DD.pdf works. "v3", "latest", "final" and "tailored" all fail, because none of them identifies one file.

Criterion 4 passes when the pay figure is recorded exactly as entered, and a copy of the cover letter and screening answers is stored next to the resume. If you entered a range, record the range. If the form had no pay field, write "n/a: no pay field on form".

What they prove: on a screening call you can repeat the numbers and claims you made, word for word.

When they lie: the filename on the row points to a file you later edited in place. Freeze means a copy you never open for editing again.

If you tailor in Refolk, each posting gets its own tailored resume and cover letter in a per-posting log. The version you sent then already sits against the posting it was written for, and the row only needs to name it.

How should the req ID and channel be recorded?

Record the req ID exactly as the employer shows it, the channel you applied through, any agency that submitted you by name, and the email address on the application. Together these let you catch a duplicate before it turns into an ownership dispute.

The reason is agency ownership. Agency protection windows vary by contract and commonly run 6 to 12 months after you are introduced. Some examples from public terms:

• Paraform: ownership is company-scoped, not role-scoped. If an agency submits you for Role A at Company X, its claim covers all of Company X's roles.
• RecruitiFi: ownership lasts 180 days per JobCast. Duplicates are detected on name and email, and only one submission is accepted.
• A KellyOCG clause: the candidate remains the property of the supplier for 12 months after submission.
• Employer side: if the client can show you were already in their ATS before the agency submitted you, no fee is owed.

The reviewer can see all of this. Greenhouse shows reviewers "Source", "Credited to" and an overview of other jobs you have applied to. If you apply directly to one role at a company where an agency has already put you forward for another, the recruiter has to sort out a conflict you could have flagged. Recording the channel protects you as much as it protects the agency.

Pass test for criterion 2: the row has the req ID (or "none shown"), a channel, an agency name or "no agency", and the application email. "LinkedIn" alone fails if an agency was also involved.

What it proves: you can answer "have you applied here before, and through whom?" in one search.

When it lies: you applied to one req ID and the agency submitted you to another at the same company, so the req ID search comes back clean. Always search by company name as well as req ID.

Before applying at any company where you have worked with an agency, ask directly:

Hi [Name],

Before I apply to [Company] for [Role, req ID if shown], can you confirm whether you or anyone at [Agency] has submitted my profile to [Company] for any role, and if so, which role and on what date?

I want to avoid a duplicate submission on either side. If you have not submitted me there, I plan to apply directly.

Thanks,
[Your name]

Record the answer on the row, with its date, before you submit.

What must the contact, next action, and close-out fields say?

The contact field holds a named person or the literal "none found". The next action is one verb and one ISO date. A row closes only when it reaches a threshold you wrote down in advance, with a reason and a date.

Contact

Passes: a name and role, such as "Priya N., talent acquisition partner", or the text "none found".

What it proves: the follow-up has somewhere to go, or you looked and found nothing.

When it lies: a blank field. The grader can't tell whether nobody was found or nobody looked. Spend 0 to 10 minutes looking, then write the result either way.

Next action

Passes: one verb and one date, such as "email recruiter 2025-03-04" with your own date in place of that one. Use exactly one action. If two things are due, the earlier one goes on the row and the other goes in notes.

What it proves: the tracker can be sorted by date into a to-do list.

When it lies: "follow up", "chase" or "waiting". None of these has a date, and "waiting" has no verb.

Close-out

Sources disagree on the threshold. One says to close if you hear nothing within 10 to 14 business days. Another says to close only once roughly six to eight weeks have passed with no response to either of two messages. The response data settles it for me: with 36% of candidates still waiting at one to two months, closing at two weeks throws away live applications.

My default policy:

1. First follow-up at 10 to 14 business days after applying, if a contact exists.
2. Second message two to three weeks after the first.
3. Close-out at eight weeks after applying if neither message got a reply. Reason: "no response". Date: the day you close it.

You can choose different numbers. Whatever you choose, write it down once and apply it to every row. The standard grades consistency, not your particular threshold.

The per-row procedure, from capture to close-out

Follow these seven steps for every application. Steps 1 to 5 take roughly 6 to 16 minutes per row, depending on how long the contact search takes. The weekly audit takes 15 to 30 minutes for the whole tracker.

Step 3 is the one people compress, and it is the one the portal can't undo. If you only have time for part of the procedure, do steps 1 and 3 at submission and fill in the rest the same day.

How tracker rows fail: false passes and what to check

Most failing rows look complete. Every cell has something in it, but what's in the cell can't answer the question it exists for. These are the eight false passes I see most, each with a check you can run in seconds.

1. Posting saved as a URL only.
   • Looks like: a link in the posting column.
   • Fails because: the link is dead when the recruiter calls.
   • Check: open the stored text with no network connection.
2. Screenshot taken without expanding "Show more".
   • Looks like: a saved image of the posting.
   • Fails because: the pay band and location in collapsed sections are missing.
   • Check: the saved text ends with the closing section or the equal opportunity statement. As noted above, this check is unverified, so expanding by hand is the real safeguard.
3. Resume recorded as "v3" or "latest".
   • Looks like: a version label.
   • Fails because: Greenhouse uses your most recently uploaded resume, so your profile doesn't prove what was sent, and Workday offers no documented download.
   • Check: the filename matches a frozen file with a date in its name.
4. Board date recorded as the posting date.
   • Looks like: a date in the right column.
   • Fails because: boards reset the date when a role reaches a new board, so the row understates the posting's age.
   • Check: a capture date is recorded separately, and the column is labelled as such.
5. Channel recorded as "LinkedIn" when an agency also submitted you.
   • Looks like: a filled channel field.
   • Fails because: ownership can be company-scoped, so applying to another role at the same company triggers a conflict.
   • Check: the channel and the agency name (or "no agency") are both on the row.
6. Contact field left blank.
   • Looks like: nothing, which graders tend to skip past.
   • Fails because: nobody can tell whether no one was found or no one looked.
   • Check: the field reads a name or the literal "none found".
7. Next action recorded as "follow up".
   • Looks like: a plan.
   • Fails because: it has no date and no specific verb, so the row never shows up when it's due.
   • Check: one verb plus an ISO date.
8. Close-out applied at 10 business days.
   • Looks like: a tidy closed row.
   • Fails because: it's premature when 36% of candidates are still waiting at one to two months.
   • Check: the close-out date is at or past your written threshold.

A full cell is not a passing cell. The test is whether it answers the question a recruiter will ask.

Two of these failures don't show up until the moment they cost you: the dead link and the version label. Both get found during a live call. That is why the procedure puts capture and freezing at submission, not at the weekly audit.

Auditing the tracker and keeping the standard current

Audit once a week, in one sitting of 15 to 30 minutes. Grade every open row against the checklist below and fix or flag each failure. A row that can't be fixed, such as a posting you never captured, gets a note saying so. That way nobody mistakes it for a passing row later.

The same row satisfies a state work-search log

If you are claiming unemployment benefits, some states require a work-search log, and a passing row already holds most of what they ask for.

Massachusetts Form 1750 asks for pay rate and Job ID, two fields most templates leave out. A row that passes this standard can be copied into that form. The only extra you need is the employer's address, which the form also asks for. Maine requires claimants who apply online to record the internet address, and to keep work-search logs for one year. That is one more reason the URL stays on the row even after the link dies. Rules differ by state, so check your own state's work-search page for the fields required and how long you must keep the log.

A row record you can paste into any tool

Company: [name]
Role: [title as posted]
Req ID: [exact ID or "none shown"]
Posting URL: [link]
Posting text file: [filename, opens offline]
Capture date: [YYYY-MM-DD, your date, not the board's]
Channel: [company site / board name / referral]
Agency: [agency and recruiter name, or "no agency"]
Application email: [address used]
Applied date: [YYYY-MM-DD]
Resume sent: [Company_Role_ReqID_YYYY-MM-DD.pdf]
Cover letter sent: [filename or "none"]
Pay figure entered: [exact figure or range, or "n/a: no pay field on form"]
Screening answers: [filename of saved copy, or "n/a: none asked"]
Contact: [name, role] or "none found"
Status: [Saved / Applied / In contact / Interviewing / Closed]
Next action: [verb] [YYYY-MM-DD]
Close-out threshold: [YYYY-MM-DD]
Closed: [reason, YYYY-MM-DD] or "open"

Refolk's per-posting tailoring log already holds the posting, the tailored resume and the cover letter for each application. If you use it, the "Resume sent" and "Cover letter sent" lines point at that version, and the fit score is there when you prepare for the call.

Keeping the standard current

Portal behaviour can change, and these mechanisms decide the standard's rules, so re-check them now and then rather than trusting this page forever:

• Resume storage: read the candidate FAQ for the ATS you meet most. If a portal starts letting you download what you submitted, criterion 3 still stands, because your local copy is the record you control.
• Lever and iCIMS: what candidates can see again is not established publicly. Test it with one real application and note what the portal shows you.
• Close-out threshold: if your own data shows replies arriving later than your threshold, move the threshold and re-date the open rows in one pass.
• Retention: keep closed rows and their files for at least as long as your state's work-search rule requires. Maine's is one year.

Adopt the seven criteria as written, choose your one threshold, and run the first audit this week. In a tracker that has never been graded, expect most early failures in criteria 1 and 3, the two that can't be fixed after the fact.