> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crewpass.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Background-check status

> Read a crew member's standardised, provider-agnostic background-check status.

Each crew member on your fleet carries a **background-check status**. It appears on
the fleet roster alongside verification status, so you can see at a glance who has
cleared and who is still in progress.

<Info>**Requires** `crew:status:read` (included in your management plan). It's part of the [crew roster](/guides/crew) response. Authenticated with your API key as a Bearer token over TLS; reads are not signed.</Info>

## Where you see it

```json theme={null}
{
  "crew_unique_id": "crew_001",
  "verification_status": "verified",
  "background_check_status": "completed",
  "...": "..."
}
```

## The status values

CrewPass normalises every provider's vocabulary into one standard set:

| Status        | Meaning                                      |
| ------------- | -------------------------------------------- |
| `pending`     | A check exists but hasn't started.           |
| `awaiting`    | Waiting on information from the crew member. |
| `in-progress` | Being processed.                             |
| `completed`   | Cleared.                                     |
| `declined`    | Did not clear.                               |
| `expired`     | A previously completed check has lapsed.     |

`null` means there's no background check on record for that crew member.

<Note>
  You get the standardised status value and nothing more, with no invented ETA.
</Note>

## Next

* [Webhooks](/webhooks) — receive a `crew.status.changed` event when this moves.