10 min read
You track applications without losing your mind when each row holds the req ID, portal link, recruiter contact, resume file name, and follow-up date in one place. Company name alone won't tell you which PDF you sent, which Workday req is still open, or when you're allowed to nudge again.
Before you add another row, check your resume for free against the posting on your screen. You'll know whether the file you're about to log is parse-clean or whether you're tracking a broken upload.
Job searching is exhausting when every portal hides history behind a login. A single master tracker turns silence into patterns instead of personal failure. We're not building a second job here. One sheet, one habit, one row per submit.
If you've been juggling sticky notes and starred emails, that's why a recruiter email sends you into five tabs. Fix the row once and you won't reopen half your browser every Tuesday.
Quick Wins
- Create the tracker row before you click submit on the portal.
- Log the exact PDF filename, not "resume final v2 really final."
- Set follow-up date seven business days out the moment status hits Applied.
- Keep portal URL and req ID in the same cell so one click reopens the posting.
Why logging company names alone breaks your tracker
Most trackers die on the first week because each row says "Northwind, applied Monday." Monday what? Which req? Which portal login? Which bullet swap? When a recruiter replies six days later, you're reconstructing the apply from memory. That's not tracking. That's hope with columns.
Company name is not a unique key. Large employers run parallel reqs with the same title. Staffing firms forward your file to clients you never saw. One company row can hide three different uploads if you're not logging req ID and file name separately.
Portals bury their own history. Workday, Greenhouse, Lever, Taleo, and iCIMS each store status behind separate accounts. Your tracker is the only cross-portal memory that survives when you clear cookies or switch devices mid-search.
Contacts live outside the portal. A hiring manager email in your sent folder does not attach itself to the apply row unless you paste it there. Follow-up without a named row is how people send polite notes to the wrong req.
Read how to apply smarter on US job boards when you need daily caps and tier files before the tracker fills up. This page is the row you create after you decide the role is worth a slot.
Edge case: you apply through an employee referral link that skips the public req number. Log the referrer name and the internal job code they gave you. Without that, you cannot tell whether silence is slow HR or a dead internal req.
Edge case: agency recruiters shop one resume to multiple clients. One row per client submission, not one row for the agency. Same PDF, different req IDs, different follow-up owners.
How to track applications without losing your mind in one row
One complete row should answer five questions without opening email: What did I send? Where did I send it? Who owns it? When can I nudge? Is the req still alive? Build the row first, submit second. Reverse that order and you'll always be one tab behind.
Field 1: Req ID and portal URL
Copy the requisition number from the posting footer when Workday or Taleo shows it. Paste the full careers URL in the same cell. When the posting vanishes, the req ID still lets you reference the role in a follow-up note without guessing titles.
Before: Northwind marketing role, applied on company site.
After: Northwind | Req 44218 | https://careers.northwind.com/job/44218 | Applied 2026-09-08
Field 2: Resume and cover letter file names
Log the exact attachment names you uploaded. Tier and version in the filename beat a Notes column that says "tailored." When a recruiter asks about your HubSpot bullet, you open Miller_Marketing_TierA_v4.pdf instead of scrolling Downloads.
Before: Sent resume.
After: Miller_Ops_Analyst_TierB_v3.pdf + Miller_Ops_CL_v3.docx
Field 3: Contact and channel
Record recruiter or hiring manager name, email, or LinkedIn thread URL if that's where the conversation lives. Mark channel: portal message, email, or referral intro. Follow-up tone differs by channel. Your row should tell you which one to use.
Field 4: Status and parse preview
Status is Applied, Screen, Interview, Offer, Closed, or Withdrawn. Add Parse YES or NO when the portal shows imported employers after upload. A week of silence with Parse NO means fix the template, not send a third identical file.
A mid-level analyst whose tracker says Applied but Parse NO on three rows has a formatting problem, not a market problem. Fix the master file once, then re-apply only to open reqs where you still meet knockouts.
Field 5: Follow-up date
Set follow-up seven business days after apply when status is Applied and the req still shows open. One nudge, one new status, mark FOLLOWED UP. If the req closes, move the row to Closed and stop refreshing the portal daily.
Copy-paste tracker header
Paste this into a sheet tonight. Fill one row per submit before you close the portal tab.
Company | Title | Req ID | Portal URL | Contact | File sent | Parse | Applied | Status | Follow-up
Northwind | Ops Analyst | 44218 | careers.northwind.com/44218 | [email protected] | Miller_Ops_TierB_v3.pdf | YES | 2026-09-08 | Applied | 2026-09-17
Brightline | CS Lead | GH-9912 | boards.greenhouse.io/brightline/9912 | referral: Sam T. | Miller_CS_TierA_v2.pdf | YES | 2026-09-09 | Applied | 2026-09-18Composite note upgrade: operations coordinator
Before: Applied to logistics company, waiting to hear.
After: Harbor Co | Logistics Coord | Req 8810 | Workday | Miller_Logistics_TierB_v2.pdf | Parse YES | Applied 2026-09-05 | Follow-up 2026-09-14 | Notes: mirrored Coupa in bullet one.
Composite note upgrade: customer support lead
Before: Zendesk job, applied Thursday.
After: Relay Inc | CS Lead | Lever 4421 | lever.co/relay/4421 | [email protected] | Miller_CS_TierA_v3.pdf | Parse YES | Applied 2026-09-07 | Follow-up 2026-09-16 | Knockouts: auth YES, remote YES.
Weekly ten-minute review
Every Friday, sort by follow-up date ascending. Send notes due that day. Move Closed rows out of the active filter. Count Parse NO rows. If you have more than two, rebuild the master file before Monday's applies. Color the follow-up column on rows where the req still shows open but you have no contact. Those get portal messages instead of cold email guesses.
Add a Notes column for knockout answers you cannot afford to forget: sponsorship, clearance, salary band, remote rule. When a recruiter calls, you answer from the row instead of opening the application form again under pressure.
Read why mass applying hurts your job search when your tracker passes fifty Applied rows with zero Screen status. Volume without rows is noise you cannot fix.
I've screened Workday queues where the candidate applied twice to the same req because their tracker never recorded the first upload date. One honest row prevents duplicate noise on my side and embarrassment on yours.
Exceptions that still need a row
Rules bend. These cases still belong in the master tracker so follow-ups stay disciplined.
Referral with no public req. Log referrer, internal code, and date of intro email. Status starts at Intro sent, not Applied. Follow-up goes through the referrer first unless they told you to use the portal.
Repost with a new req ID. Same title, new number, new row. Do not overwrite last month's silence. Fresh post date plus new req ID is a new odds stack.
Withdrawn after better offer. Mark Withdrawn and add one line: accepted other offer. Keeps your active list honest when you run weekly follow-ups.
Interview loop with multiple rounds. One row, update Status to Phone, Onsite, or Panel. Add interview dates in a Notes column instead of spawning four rows for the same employer.
Parser fail on a strong fit. Pause new applies. Fix single-column export. Re-test in Notepad. Re-apply once with Parse YES logged. Do not stack five NO rows and call it persistence.
Edge case: contract role with rolling start dates. Log the contract end date in Notes so you know when to refresh the file without treating silence as rejection.
Edge case: internal transfer at your current employer. Still one row with internal req ID. HR portals hide external history fast when you juggle two processes.
Check the file before it earns a row
A tracker full of Parse NO rows is a diary of broken uploads. Run your tier PDF through HireFlow's free ATS checker before you log the filename. Confirm employers and dates import as plain text, not sidebar icons.
When parsing is clean but the posting language does not match bullet one, score your job match and decide whether the role earns today's cap. Weak match rows belong on a watch list, not in Applied with a follow-up date you already know will stall.
Save checker output in Notes beside the row. After two weeks you'll see whether silence came from stale reqs, weak match, or files that never imported. That beats adding ten more company-name-only rows.
When a portal asks for optional cover letter text, log the letter filename beside the resume in the same row. Plain-text fields strip formatting, so keep headers out of the paste. You can generate a cover letter from posting language, save it as Miller_Role_CL_v3.docx, and paste the body only. One filename pair per row means you never send the Northwind letter to Brightline by accident.
Sort your sheet by follow-up date every morning before you open job boards. Three due notes take less time than one panicked half hour reconstructing who you already emailed. That rhythm is what turns a tracker from guilt storage into a schedule you can trust.
What to do in the next ten minutes
Open a blank sheet, paste the tracker header, and rebuild rows for every open req you still remember. Set follow-up dates on anything in Applied status. Rename your resume files with tier and version before the next upload.
Going forward, create the row before submit every time. One row with req ID, portal, contact, file name, and follow-up date is how you track applications without losing your mind when recruiters finally reply.
When a row hits silence after a clean parse on a fresh req, follow up once on schedule instead of re-uploading the same PDF. When preview fails, fix the template before you touch tomorrow's apply.
Tracking is boring on purpose. Boring rows beat brilliant memory when you're managing more than five open reqs.
- Row first, submit second, every time.
- Filename and req ID in the same row as the portal link.
- One follow-up per open req, logged as FOLLOWED UP.
Read more
Frequently asked questions
Log company, role title, requisition ID when visible, portal URL, resume file name, contact name or email if listed, apply date, status, and follow-up date. That row should let you follow up, re-open the posting, and attach the same PDF without hunting email or browser history.
Either works if you use one master list. Spreadsheets win when you want custom columns for parse preview and knockout answers. Apps win when you need mobile reminders. Splitting data across a notes app, email flags, and a board creates the chaos this page is trying to prevent.
Schedule one follow-up seven to ten business days after apply when the req still shows open and you have a contact or portal message option. One polite note beats three anxious pings. Mark the row FOLLOWED UP so you do not duplicate outreach on the same req.
Name files with role tier and version, such as Miller_Ops_Analyst_TierB_v3.pdf. Log that exact filename in the tracker row. When a recruiter replies, you open the same file in ten seconds instead of guessing which export you uploaded.
Rebuild from sent-mail search and browser history for the last thirty days. Create rows for anything still open. Accept that closed reqs without notes are gone. Going forward, create the row before you hit submit so the gap does not reopen.