Create the shared AI record — Harbour Lane Accounting

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

Harbour Lane Accounting needs a defensible next step.

Harbour Lane must distinguish the proposed external tool from its own intended use.

Follow Harbour Lane Accounting

See the work in context.

Record the system

Maya records the proposed client follow-up drafting tool once.

Record the use

She creates a separate use case for preparing reviewed client follow-up drafts.

Name responsibility

The record names Maya, the lifecycle stage and the next review gate.

What remains uncertain

Keep the limit visible.

The supplier remains unselected and the proposed system record is not an endorsement.

Recorded outcome: System facts and Harbour Lane’s intended use are visible as separate connected records.

Try it in the worked example

Open the matching read-only chapter.

Application record: Client follow-up drafting tool and AI-assisted client follow-up use case

You will be asked to sign in before the read-only Harbour Lane Accounting chapter opens.

Open create the shared ai record in Harbour Lane Accounting

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.
The supplier remains unselected and the proposed system record is not an endorsement.
System facts and Harbour Lane’s intended use are visible as separate connected records.