Create the shared AI record — Brightpath Recruitment

In this lesson, you will learn to

Use the task with a clear purpose.

Record the AI system once.
Create a distinct use case.
Assign an accountable owner and review gate.

Why this matters

Brightpath Recruitment needs a defensible next step.

Brightpath must separate the supplier’s proposed aid from the recruitment use that could affect candidates.

Follow Brightpath Recruitment

See the work in context.

Record the system

Aisha records the proposed candidate shortlisting aid.

Record the use

The use case is limited to organising extracts from sample applications.

State prohibited uses

Ranking, rejection, recommendation and real recruitment decisions are outside the boundary.

What remains uncertain

Keep the limit visible.

Supplier validation is incomplete and the system is not approved for use.

Recorded outcome: The system and its high-impact organisational use are separately accountable.

Try it in the worked example

Open the matching read-only chapter.

Application record: Candidate shortlisting aid and candidate shortlisting review use case

You will be asked to sign in before the read-only Brightpath Recruitment chapter opens.

Open create the shared ai record in Brightpath Recruitment

Official guidance

Check the published source.

Sources checked 6 October 2026. zedhaque AI Governance is designed to support these National AI Centre resources. It is not approved, certified or endorsed by the Australian Government.

Three key points

What to remember.

Separate an AI system from each organisational use of it.
Supplier validation is incomplete and the system is not approved for use.
The system and its high-impact organisational use are separately accountable.