A portal status is an observation, not an outcome prediction
Status labels are useful when recorded with a date and source, but they rarely explain the employer's internal decision. A live posting, unchanged profile, chatbot message, or empty dashboard should not be converted into an interview promise or rejection without direct evidence.
What does the employer publicly document as the route back to this application?
Walmart documents a dashboard and a 60-day hourly application period. McDonald's directs restaurant candidates to the local restaurant for status. Target relies on Candidate Home and role-specific Workday detail pages. Apple exposes a profile but does not publish a universal status vocabulary or response deadline. UPS separates hourly and professional return paths. These patterns show why a single status glossary cannot safely describe every employer: the same-looking label can belong to a different system and stage.
Applicant rule
Store the exact label, date viewed, account or contact route, confirmation, last employer message, and one next action. If the employer does not define the label, describe only what the screen shows and avoid guessing what happens next.
Selected evidence cases
Five different ways an applicant is told to check status
These records compare a dashboard window, local restaurant contact, Candidate Home, a profile without a public glossary, and separate hourly and professional routes. The evidence date records what was publicly documented, not what an individual status label predicts.
01
Walmart
dashboard and hourly application window
Fixed-report state: Documented
Result cards exposed facility type, location, shift, and pay before a requisition was opened.
Evidence date:
Application system: Walmart Careers portal and Walmart Online Hiring Center for hourly roles
Known limit: Two current requisitions were retained; another role family would broaden the sample.
Restaurant cards identified location and franchise-owned status before the application handoff.
Evidence date:
Application system: Restaurant and hourly roles use McHire / Olivia; corporate roles use careers.mcdonalds.com / Sam; early-career candidates use the university process
Known limit: One restaurant card and one corporate requisition were retained; the restaurant detail endpoint was region-limited.
Four current retail, technical, corporate, and hardware records exposed role-specific pay and qualification evidence.
Evidence date:
Application system: Apple Jobs with Apple Account profile/sign-in, My Profile, Submit Resume, and a separate location picker for some nationwide retail requisitions
Known limit: The nationwide seasonal card showed a weekly-hours field that requires store-level confirmation.
Hourly candidates return through a unique message link while professional candidates use Workday.
Evidence date:
Application system: UPSjobs.com front door; sampled hourly warehouse cards route to Fountain while professional, supervisor, automotive, and maintenance cards route to Workday
Known limit: No stable current individual requisition was retained for the employer-level snapshot.
Create a dated status observation without guessing the outcome
Copy the exact label or message, connect it to the account or contact route, and pair it with the last direct employer communication. Then choose one follow-up action that does not depend on interpreting an undefined state.
Status routes document access, not hiring decisions
The comparison selects examples from the fixed research registers and does not create a new response-time sample. Public return instructions cannot reveal a private decision, recruiter queue, or interview probability.
The 25-employer/37-posting transparency report and the separate 16-company/58-record published-cohort
appendix remain distinct fixed outputs.
This brief documents public status-return evidence. It cannot interpret a private hiring decision, predict response time, or translate an undefined label into an outcome.