One official assessment journey

One clear journey from SEC brief to final report.

SEC creates and releases the assessment. Schools assign and monitor it. Students research, write and submit—all in one clear, traceable workflow.

SEC creates & releasesSchools assign & trackStudents write & submit

AAC journey

Four steps. One shared record.

Traceable

  1. SEC releases the official brief

    01

    One approved assessment version

  2. Schools assign it

    02

    The right classes and candidates receive it

  3. Students complete their report

    03

    Research, writing and progress stay connected

  4. Schools submit with evidence

    04

    Final work and process records remain traceable

Each role sees only the work and actions it needs

The operational aha moment

One approved version. Every school. Every action traceable.

AAC turns a fragmented annual process into one controlled operational chain—from policy and official documents to school action, coursework evidence and reconciliation.

Management does not have to choose between national visibility and strict school-level control.

The same workflow provides both—through explicit capacities, immutable version evidence and scoped portal access.

Version certainty

Every school receives the exact approved AAC version.

Official documents, rules and release snapshots stay tied to one traceable version.

National oversight

See progress and exceptions without crossing school boundaries.

SEC operations can coordinate the national process while each school remains securely scoped.

Explainable evidence

Reconstruct who did what, when and under which capacity.

Sensitive reads and operational commands retain actor, reason and correlation evidence.

Exact AAC snapshotsReasoned sensitive accessExplicit exception states

One end-to-end workflow

See the whole operating cycle—not another disconnected portal.

Each hand-off carries the approved version, the responsible capacity and the evidence needed for the next decision.

  1. 01

    Author

    Create the AAC and official document set

  2. 02

    Verify

    Independent review and document verification

  3. 03

    Activate

    Lock an approved, versioned release basis

  4. 04

    Distribute

    Issue exact snapshots to eligible schools

  5. 05

    Collect

    Manage upload, nil and extension outcomes

  6. 06

    Authenticate

    Teacher decisions and principal summaries

  7. 07

    Reconcile

    Track transfer state, differences and audit

Management view

Exceptions become visible before they become crises.

Campaign status, school progress, validation concerns, nil outcomes, extensions and transfer differences remain connected to the same operating context.

AAC release

Exact version basis

School progress

Scoped operational state

Reconciliation

Explainable differences

Human process evidence

Make the student's working process visible—not guessed from the final file.

AAC can retain the research, drafting, interaction and submission trail that helps an authorised reviewer assess whether work developed through sustained human activity.

Evidence supports the human decision

The system does not claim that a black-box score can prove authorship or make an automatic cheating decision.

Research path

Source and search activity builds context around how the work developed.

Revision trail

Draft, save, restore and submission events show progression over time.

Interaction history

Authenticated activity and guidance interactions remain attributable.

Submission chain

The final artefact stays linked to its version and submission history.

Illustrative evidence view

Candidate working record

Process evidence available

  1. Research source opened

    Source activity

  2. Draft revision saved

    Revision 12

  3. Student editing session

    Authenticated

  4. Guidance reviewed

    Learning interaction

  5. Final submission recorded

    Version frozen

5

Recorded stages

12

Draft revisions

1

Submitted artefact

Human

Decision owner

Two portals, one controlled process

National coordination without weakening school-level boundaries.

SEC teams and schools work from the same approved operating context, while routes, permissions and data scope stay explicitly separated.

SEC

Command centre

Coordinate policy, operations and exceptions.

  • AAC authoring and version activation
  • School eligibility and controlled distribution
  • Coursework campaign and exception oversight
  • Authentication outcome coordination
  • Transfer, reconciliation, reports and audit

Fixed operating capacities

Business Staff
Schools

School-scoped portal

Act with clarity on exactly what is assigned.

  • Receive the exact AAC version assigned to the school
  • Upload, validate and replace coursework securely
  • Record nil submissions and request extensions
  • Complete teacher authentication and principal summary

Scope is derived on the server

A school cannot select another school's identifier to cross the boundary.

Same annual process strict permission boundaries

Governance by design

Control is built into the operating model—not added after the event.

The platform keeps authority, evidence and exception states explicit throughout the AAC lifecycle.

No false green states

Disconnected, reference-only and sent-but-unconfirmed outcomes remain visible as such. External success requires authoritative evidence.

Explicit capacity

SEC Business Staff is the simple business entry point; independent verification, final case decisions, technical operations and access administration remain enforced as server-side capacities.

No silent privilege

Platform administration does not silently bypass SEC membership and permission checks.

Maker-checker gates

Independent verification and approval controls are part of the workflow, not a manual reminder.

Authoritative outcomes

Reference-only, unconfirmed and disconnected states are never presented as external success.

Capacity model

The right authority at each decision point

No wildcard SEC access

Curator

Create and prepare AAC evidence

Explicit

Verifier

Independently verify official material

Explicit

Operations

Distribute and coordinate campaigns

Explicit

Technical

Operate transfers and bounded retries

Explicit

Auditor

Read-only evidence and audit access

Explicit

Procurement-ready traceability

Every visible capability has an operational reason to exist.

Phase 1 is organised around the actual access, audit, portal, upload and authentication requirements—not a collection of disconnected product features.

Evidence follows the requirement

Page routes, API operations, permissions and test evidence are maintained as one traceable implementation matrix.

R9

Access & Rights

Capacity-based access and maker-checker controls

R17

Audit Trail

Actor, reason and correlation evidence

R23

Portal Features

Versioned AAC, rules and deadlines

R31

Upload Data

Private uploads, validation and recovery

R39

Coursework Upload

Candidate, nil, extension and transfer flow

R40

Authentication

Teacher, concern and principal outcomes

External integrations stay clearly labelled until an approved authoritative source or receipt is connected.

Honest operational state
A clearer operating model

See your AAC process as one traceable workflow.

Walk through the SEC and school journeys, the permission model and the evidence available at every decision point.

Sign in to AAC