> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/menu-areas/people-and-settings/personnel-screening.md).

# Personnel Screening

**Open this area:** In the CORTEX menu, select **People & settings → Personnel screening**.

Record actual externally verified BPSS or clearance metadata, review deadlines and personnel-owner revocation.

**Who uses this:** Administrator. **Open in CORTEX:** `/administration/screening`. **In-app guide:** `/help?topic=personnel-screening`.

**Expected result:** Authorised personnel reviewers can reconstruct verification and recheck history without uploading raw screening files or changing access grants.

## Before you start

* Use the correct workspace and explicit personnel screening read plus verify or revoke capability. Professional evidence or analyst access is insufficient.
* Obtain actual external verification, issuer, permitted purpose, personnel owner, next recheck and expiry dates, and a current approved UK profile. No example, role name or technical permission certifies screening.

## What to do

{% stepper %}
{% step %}

## Record a verified attestation

Open Administration, Personnel screening, Record verified attestation.

The page shows workspace/read/verify authority, actual external verification and approved UK profile prerequisites. Complete its validated Person and scheme, Verification dates, and Review attestation steps.

Select the person through exact-email lookup, private handling, explicit BPSS or security-clearance type and actual scheme.

A person cannot verify their own attestation; missing inputs block Continue and final save.
{% endstep %}

{% step %}

## Retain necessary references

Record the issuer, external verification reference, permitted purpose and accountable personnel owner.

Keep identity documents, raw screening files and sensitive identifiers in the authorised personnel system; there is no file upload here.
{% endstep %}

{% step %}

## Set evidence-based deadlines

Record a completed external verification date and future UTC recheck and expiry dates.

Recheck cannot fall after expiry. Adopt the current approved UK profile and explain the decision.
{% endstep %}

{% step %}

## Record an external recheck

Open the attestation and choose Record external recheck.

Supply fresh reference and dates; the new verification must be later than the previous one. Type and scheme remain fixed, and every earlier revision is retained.
{% endstep %}

{% step %}

## Record owner revocation

The named personnel owner with revoke capability records the actual reason.

Revocation is terminal for this attestation and remains possible after expiry or profile change. A newly verified replacement uses a separate record.
{% endstep %}
{% endstepper %}

## Check the result

* Is BPSS recorded separately from any clearance scheme?
* Are issuer, purpose and external reference actual and necessary?
* Are recheck and expiry dates still current before reliance?

## If you get stuck

<details>

<summary>What happens when a deadline passes?</summary>

The retained verification remains visible to authorised personnel reviewers, with recheck or renewal required. Obtain fresh external verification before relying on it; history is not silently changed or erased.

</details>

<details>

<summary>Why did my recheck conflict?</summary>

Another decision changed the record. Refresh the retained attestation, compare the new decision and keep your proposal. An unchanged retry recovers its recorded event; changed reuse is rejected. A revoked record cannot be reactivated.

</details>

<details>

<summary>Why was the page cleared?</summary>

Your current personnel access, organisation, workspace or handling changed. Private records and entered notes are cleared. Ask the personnel owner or access manager to review the legitimate scope.

</details>

## Responsibility and limits

* Screening records grant no technical access, formal appointment or automatic eligibility. Separate approved policy governs any later decision gate.
* Ordinary analysts cannot read attestations. Organisational, workspace, handling and explicit personnel capabilities apply before records are searched or paged.
* History is bounded to 32 revisions and one MiB. Preserve old records and use the approved replacement and retention process; revocation is not deletion.

**Reference and scope:** F21-R04: BPSS and security clearance remain distinct. Actual personnel-owner policy and acceptable external evidence must be supplied.

**Related workflows:** [Review professional competence and development](broken://pages/6df735255f56e27da202d1bb6b5d4080b857dd2a); [Manage accounts, grants and workspace membership](broken://pages/99c8701bc497eefb32769b668198b1f9f5fc6a93); [Preserve an exact revision and manage holds](broken://pages/0185ca5a2331760fb4c59665b8dde7f4d80e0fc6).
