- What reaches them
- A confirmation that the form was accepted and a status that reads as under review. Nothing about which queue the record entered or who it is assigned to.
- What it means from there
- The application is in the process, and the word review implies a reader.
- What happens next
- Records the date and the wording, and keeps other processes running while the status stays unchanged.
Application Ingestion
The initial ingestion gate where candidate CV and structured application fields enter the talent acquisition database / ATS.
Barrier B-001 Stage: Intake Step in the funnel: #3 Evidence: established
On the canonical path
Applied, and told so — The application is submitted and acknowledged. The record holds what the candidate actually wrote, and the candidate can tell that it arrived.
This entry is one of the ways that commitment stops being kept.
What it looks like
Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.
- 18:22:04 POST /apply — 200 OK
- 18:22:04 Candidate record created · linked to req #4471
- 18:22:05 Required fields validated: 12 of 12
- 18:22:05 Status: Under review
What to notice: Passing this gate means a row exists and is attached to a live requisition. It says nothing about whether anyone will read it.
Barriers before this one
Barriers after this one
Mechanisms operating at this barrier (4)
- M-003 ATS Parser Extraction Failure candidate Multi-column formatting, graphics, custom fonts, or unsupported document layouts cause ATS parser to corrupt or omit critical work history.
- M-005 Pre-Selected Internal Candidate none Requisition was publicly advertised to satisfy corporate policy or legal compliance while an internal employee was already earmarked for the role.
- M-006 Stale or Orphaned Job Requisition none Job posting remains active on careers page and aggregator portals despite the team having ceased active hiring or closed headcount.
- M-020 Automated Application Expiration Timeout none ATS configuration automatically issues bulk rejections to all pending unreviewed applications after 45 or 60 days.
Interventions targeting this barrier
From each side
The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.
- What reaches them
- A request that validated against the schema and a record linked to a live requisition. The CV arrives here as fields, not as a reading.
- What it means from there
- The transaction succeeded. This is throughput, which is what the buyer of the platform evaluates.
- What happens next
- Creates the record, applies the default status, and starts the expiry clock that ships enabled.
- What reaches them
- A counter on a requisition rising against a screening capacity that does not rise with it.
- What it means from there
- Passing this gate carries no signal about the candidate. Until triage reaches the record, it is volume.
- What happens next
- Nothing at this gate. The queue is worked at the next one, in an order set there.
Employer policyNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Hiring managerNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Public policy and industry standardsNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
