---
id: B-001
type: barrier
title: "Application Ingestion"
lang: en
registry: 2026.08.2
canonical: https://hoba.work/barriers/B-001
json: https://hoba.work/api/v1/barriers/B-001.json
---

# Application Ingestion

The initial ingestion gate where candidate CV and structured application fields enter the talent acquisition database / ATS.

> **On the canonical path** — [Applied, and told so](https://hoba.work/process#WF-003-applied)
>
> 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.

## At a glance

- Stage: Intake
- Step in the funnel: #3
- Evidence: established

## Passing condition

Application record is successfully received, validated for minimum schema, and linked to the active job requisition.

## What it looks like

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

**What the gate wrote** · the whole of it — *reconstruction*

```
  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.

## 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.

### Candidate

- **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.

### ATS vendor

- **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.

### Recruiter

- **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.

## Related entries

- precedes — [B-002](https://hoba.work/barriers/B-002) — Automated Filter & Parser Threshold

---

hoba — a public, versioned atlas of hiring obstacles. Content CC BY-SA 4.0. This document is generated from the registry; the canonical page is linked above.