To understand how assessment systems must be reviewed, validated and confirmed as fit-for-purpose before they are implemented, and how this must be evidenced under Standard 1.3. 

Under Standard 1.3, RTOs must ensure that the assessment system:

  • Is consistent with the training product

  • Reflects unit requirements

  • Supports valid and reliable assessment outcomes

  • Is fit-for-purpose before use

Auditors assess whether assessment tools were reviewed prior to implementation — not whether issues were corrected later.

The emphasis is preventative control.

Practical Application

Assessment design is not limited to drafting tools.

It involves structured system controls such as:

  • Mapping tools to unit requirements

  • Confirming assessment methods are appropriate

  • Reviewing contextualisation

  • Confirming instructions are clear

  • Verifying evidence requirements

  • Confirming marking guides support consistent judgement

 Pre-use review must be documented.

  This may include:

  • Mapping matrices

  • Tool review checklists

  • Approval documentation

  • Version control records

  • Formal release authorisation

If tools are used before review, defensibility weakens. Purchased tools do not remove responsibility. All tools require internal review prior to use.

Common Risk Areas

  • High-level mapping without element-level coverage

  • Contextualisation altering unit intent

  • No documented approval before release

  • Version confusion or uncontrolled amendments

  • Marking guides lacking clear decision rules

  • Tools implemented before formal review

These weaknesses are governance gaps — not necessarily assessment failure — but they weaken defensibility.

                                                                                  What Defensible Assessment Design Looks Like

                 Strong systems demonstrate:

  • Element-level mapping to unit requirements

  • Structured pre-use review processes

  • Documented approval and release controls

  • Clear version history

  • Governance oversight of tool implementation

There should be a visible control chain linking:

                                                         Training Product → Tool Design → Mapping → Pre-Use Review → Approved Release

                                                            When that chain is documented, the assessment system becomes defensible.