By Peter Miller · Published March 24, 2026 · Last updated: October 4, 2026
7 min read
The portal says under review. Your inbox is quiet. That gap makes it feel like nobody logged a decision at all, but the employer side usually has more detail than you'll ever see, and you can't read most of it from the outside.
You're not trying to become an admin. You're trying to avoid surprises on the next req at the same company. Check your resume for free on the PDF you'll reuse so parsed fields match what you think you already submitted.
Below is a side-by-side view of what you see versus what the ATS stores, plus what that means for your file, email, and follow-up choices.
Two views of the same decision
Your portal is a summary. The ATS is the system of record. Recruiters live in the second view. Job seekers live in the first. Comparing them stops you from reading too much or too little into a status chip.
How candidate decisions are logged: portal vs ATS
| What you see | What the ATS stores |
|---|---|
| Application received | Submit timestamp, source, file type, and parse success or failure flags |
| Under review | Stage change time, owner, sometimes rank relative to req, often no public note |
| Interview scheduled | Calendar event, interviewer names, feedback forms waiting after the meeting |
| Rejected | Disposition code, optional internal reason, email send log, profile retained |
| Generic email copy | Template used, send time, and whether a recruiter edited the body before send |
| Offer or hire | Comp approval chain, start date notes, background check status, requisition close time |
None of that internal layer is a moral judgment on you personally. It is workflow data. Still, it persists longer than the email you delete on your phone.
Automated dispositions may fire before a human opens your profile. The portal might jump from received to rejected without an interview. That log entry still ties to the req version you applied against, even when the public reason stays generic.
Before: You assume under review means a recruiter is debating your file daily.
After: You treat the label as a stage timestamp and focus on parse quality before you send another upload.
Before: You reapply with a new email to hide a rejection.
After: You keep one email, fix the PDF, and apply to a different req so records merge cleanly.
Copy-paste: what to log for yourself
Req ID / title applied
Date submitted
Portal status shown
Parse check: contact + latest title OK?
Follow-up sent? (date + channel)
Next action: fix file / wait / new req
What logged data means for your next apply
I've updated disposition in Workday while the candidate portal still showed in progress until the nightly sync, which is why you should not refresh obsessively for hidden meaning.
Reapply with the same email and a cleaner parse merges into one profile at many employers. That helps recruiters see history. It also means sloppy answers on screening questions stick around.
Internal notes about salary expectations or role level can carry to future reqs at large companies. Answer forms honestly and keep numbers aligned with what you'd repeat on a phone screen.
A rejection on one req does not erase positive notes from an earlier interview at the same employer. It also does not guarantee a second look if the logged reason was level or location mismatch.
Referral flags and source tags also log at submit time. If a friend forwarded your resume, that timestamp can explain faster movement you cannot see from the portal alone.
Background check and offer stages add more rows recruiters see after you think the process ended. Assume the profile stays active until you receive a written close from HR.
For the path your file takes before logging starts, read what happens to your resume after submission .
When to follow up versus when to fix the file
Follow up once after a reasonable window if the req is still open and you have a named contact. Logging a polite note becomes another timestamp on the profile.
If parse failed or your title field was blank, follow-up will not repair rank. Fix layout, then apply to a fresh req or wait until the team reopens the role.
Saved application drafts on employer sites can log partial answers before you finish. Submit once intentionally. Multiple half saves can timestamp conflicting data on the same profile.
Arguing in email about a rejection rarely changes a logged disposition. It can add a thread recruiters skim later. Keep follow-ups short and forward-looking when the req is still live.
Do not create duplicate profiles with slightly different emails to game the system. Merge rules vary, and recruiters notice when the same name appears twice with different phones.
Compare how recruiters filter applicants on job boards when you're deciding whether silence is timing or fit.
A simple rule before you reapply
If the portal rejected you, assume the profile stays. Send a stronger file next time, not an argument about the last note you cannot read.
If the portal still says received and the req closed externally, move on without spamming resubmits. Duplicate uploads can clutter the same req without moving stage.
If you interview and lose, a thank-you note is enough. Recruiters already logged feedback you will not see verbatim.
Treat every form answer as part of the log. Free-text fields about salary, start date, or sponsorship stick to the profile longer than the cover note you typed in a hurry.
When a company uses multiple ATS portals across brands, the same email might still merge profiles. Keep answers consistent so later recruiters do not see conflicting comp numbers from two subshells.
Make the logged profile match your best file
Before another apply at the same employer, upload once to a checker and confirm parsed employer, title, and email.
Score your job match on the new req so the record that gets stored aligns with posting language before you hit submit.
If you attach a note, keep the same title and contact strings in the cover letter generator output so the logged packet does not contradict your parsed resume.
Act on what you control
How candidate decisions are logged will stay asymmetric. You get labels; employers get history. Use that fact to keep contact lines clean, answers consistent, and proof bullets sharp on the next upload. That is the part of the log you can still rewrite.
Screenshot your portal status when you submit if you need a personal paper trail. The employer log will still be richer, but your own timestamp helps you choose follow-up timing without refreshing the page every hour.
When you move to a new req at the same company, open the posting fresh and re-read screening questions. Logged answers from an old req can auto-fill and send stale comp or location data if you click through too fast.
If you are unemployed and anxious, focus on the file you control tonight: parse, proof, and consistent email. You cannot edit recruiter notes. You can stop handing them a profile that fights itself on the next apply.
That is enough for one evening. Submit when the file is clean, then step away from the portal refresh button.
Frequently asked questions
Usually no. Candidate portals show coarse status labels and messages recruiters choose to send. Internal notes about fit, comp, or interview feedback stay on the employer side. Assume anything you typed in an application or email is visible; assume internal comments are not.
No. Most ATS platforms retain the profile, parsed resume, and decision history for compliance and future reqs. A rejection on one role does not always block you on another, but duplicate profiles can merge if you apply again with the same email.
The label often means no recruiter updated the stage yet, not that someone is actively debating your file daily. Batches fill, reqs pause, or owners forget to close loops. Silence is frustrating; it is not always a hidden fail score you could have seen.
Fix parse and proof on the PDF you will reuse. Use a consistent email so records merge cleanly. Tailor employer title and top bullets to the next req instead of chasing a secret logged reason you cannot read.