Skip to main content
Back to all 19 lessons

Lesson 11 of 19

Provide and review evidence

Explain what a specific file and version can support. Keep upload, review, independent verification and assessment selection separate.

This lesson concerns artificial intelligence (AI) governance: how your organisation assigns responsibility, checks AI use and records decisions and follow-up. AI Governance keeps these records; it does not operate the external AI tool for you.

At the end of this lesson

  • Identify the correct file/version and target.
  • Explain a traceable review entry.
  • Distinguish linking, reviewing, verification and assessment inclusion.

Before you begin

This lesson is for evidence providers and reviewers. You can read and complete the paper activity without an account.

For optional workplace practice, identify the claim and target record. Have current evidence-upload or review permission as appropriate. No real upload is needed to complete this lesson. If access is blocked, record your proposed response in your notes and ask the responsible administrator to check access.

Key ideas

A file can be available without being reviewed or selected. A hash identifies bytes; it does not prove the truth of a claim.

Follow these steps

1. Name the claim

Identify the statement needing support and the correct use case or activity. Evidence means information used to support or question that specific claim.

Check the result: You know why the file is relevant before adding it.

2. Check the file and version

Open Evidence on the intended record. Check for an existing file and version first. The supported file selector accepts PDF, Word, Excel, text and Markdown.

Check the result: You avoid a duplicate and can identify the exact version being discussed.

3. Wait for a usable file

An authorised editor may use Upload and link evidence. Files are scanned before they are made available. A pending, rejected, unreadable or failed scan is not successful review.

Check the result: The displayed scan and availability state tells you what can be opened. Use the current form’s limits rather than an example file’s size.

4. Read the relevant passage

Compare the passage with the claim. In your organisation’s review record, identify the file/version, passage, reviewer, finding and limits. The use-case evidence page lists files and information states; it does not provide a passage-by-passage review form.

Check the result: The finding says what the document supports without inventing an observed test.

5. Apply independent review rules

Distinguish the provider’s description from another person’s review. Arrange the review under your organisation’s responsibility and independence rules. Selecting an information state does not carry out an independent review. A file hash identifies bytes; it does not prove the contents true.

Check the result: The record describes who reviewed what, within their authority.

6. Check selection separately

Check the file version shown under Linked evidence. This use-case page shows the current version, not a full review-history form. Check the assessment’s selected version separately. Retain and reopen your substantive review through the organisation’s review record.

Check the result: Linked, reviewed and included remain distinct. An archived or unselected file is not assumed to have influenced the assessment.

Practise

Paper activity — fictional information

'A procedure document, version 2, tells staff to check drafts. It contains no observations of staff doing that work.' Write a two-sentence review entry stating what it supports and what remains unproved.

Write your response in your own notes before opening the answer. You do not need to sign in, change records or run an assessment.

Check your understanding

Does a reviewed procedure establish that staff reliably catch material errors?

Check your answer

No. It supports the existence of a documented instruction. It does not demonstrate performance. Example entry: 'Version 2 describes the required checking process. It provides no observed results showing whether reviewers detect material errors.' Reread steps 4–5 if document review is treated as a performance test.

Check your work

  • File/version and claim are traceable.
  • Reviewer finding and limits are explicit.
  • Assessment selection is checked separately.

Continue learning

Optional worked examples

Sources

These National AI Centre resources inform the lesson. This course does not imply Australian Government endorsement.