Service Description

1. Service overview

Nova generates, hosts and maintains interactive formative learning content for vocational education and training. From nationally recognised training-package components (and comparable frameworks in other jurisdictions), the Service produces libraries of interactive practice activities mapped to the source component's elements, performance criteria and knowledge evidence, adapts them to a provider's industry context, delivers them to learners across web, LMS and classroom channels, and maintains them continuously through automated quality assurance, real-world currency checking and feedback-driven revision. The Service is provided as software-as-a-service: Supahuman hosts all components, and no customer-side installation is required.

2. Definitions

In this document:

• "Provider" or "Customer" — the training organisation (RTO, TAFE, PTE, enterprise trainer or equivalent) subscribing to the Service.
• "Learner" — a person accessing learning content served by the Service.
• "Unit" — a unit of competency or equivalent training component the Service builds content from.
• "Activity" or "artefact" — a single interactive learning experience generated by the Service (for example a simulation, scenario, quiz or game).
• "Learning space" — a hosted collection of activities scoped to a qualification, unit or custom program, served to learners through a link.
• "Workspace" or "portal" — the Provider's administration environment within the Service.
• "Contextualised variant" — a Provider-specific adaptation of a library activity into an industry or client context.

3. Content generation and the library

The Service maintains a shared library of Units imported from training.gov.au (and comparable registers), including their elements, performance criteria, knowledge evidence and packaging rules. For each Unit, an AI scan identifies learning opportunities and the Service generates interactive activities against them. All generated content is formative practice: activities teach through attempt and feedback, may be repeated without consequence, and do not conduct or record summative assessment unless a Provider explicitly enables assessment features on eligible non-accredited scopes.

• Activity forms include: interactive simulations and models, branching scenarios, process walkthroughs, hazard identification, sequencing and classification exercises, fault-finding, document tasks, calculation practice, voice role-plays with an AI counterpart, quizzes and knowledge checks, skills games (arcade, escape-room, time-trial and matching formats), daily micro-learning cycles, study notes, podcasts, explainer videos and whiteboard lessons.
• Every activity carries a mapping matrix recording which elements, performance criteria and knowledge-evidence items it practises.
• Whole qualifications can be onboarded in one operation, with core units imported automatically and electives selected by the Provider.
• Teaching resources (demonstrations, group activities, session materials) are generated alongside learner activities and delivered to teaching staff through a separate hub.

4. Contextualisation

Library activities can be adapted by the Service into a Provider's delivery context — industry setting, terminology, scenarios, client co-branding and cohort profile — producing contextualised variants owned by that Provider's workspace. Variants serve in place of the library original on that Provider's learning spaces. Whole-of-qualification contextualisation aligned to a training and assessment strategy is supported.

5. Learner access and delivery channels

The Service is designed for zero-friction learner access. Learners do not require accounts, passwords or app installation for standard access.

• Hosted links: each learning space is served at a stable link that runs in any modern browser on any device, installable as a progressive web app. Optional access codes, cohort labels, expiry and pause controls apply per link.
• LMS integration: spaces export as SCORM 1.2 packages that act as connectors to the hosted content, reporting completion, score, session time and per-unit progress objectives to the LMS gradebook. LTI launch is supported for identity-carrying access. Because the SCORM object connects rather than contains, content updates apply without re-export or re-upload.
• Offline/self-contained export: where enabled for a Provider, spaces can be exported as self-contained SCORM packages containing the content files, subject to a periodic licence verification to Supahuman confirming the Provider's subscription remains active.
• Classroom mode: an organisation-wide link that turns any browser-equipped classroom screen or tablet into a delivery surface — launching activities on the shared screen, handing them to learner phones by QR code, and hosting live class quiz games with named participation.
• Learner support features include an AI learning coach (where enabled), audio guides, accessibility controls, glossaries, and formative feedback on uploaded work.

6. The provider portal

Each Provider operates a branded workspace giving administrative control of its estate.

• Programs and scope: import qualifications and units, monitor registered-scope coverage against the library at unit level, and onboard gaps.
• Learning spaces: create, brand, curate (hide or add activities per space), sequence into modules, and mint learner links.
• Team management: role-based access (Owner, Designer, Trainer) with invitation, role change, pause/restore and removal, each notified by email.
• Insights: engagement and progress analytics across spaces, links and learners, with weekly email reporting to workspace owners.
• Delivery register: an automatically maintained record of what was taught and when, with trainer attestation and CSV export for audit evidence.
• Audit log: a searchable, exportable record of administrative actions and learner activity within the workspace.
• Quality feedback: staff can flag content issues; the Provider's own variants are corrected from that feedback through the Service's revision pipeline, and library issues are remediated centrally by Supahuman.

7. Quality assurance

Every generated or revised activity passes an automated quality audit before publication, reviewing: safety of instruction; factual correctness; grounding against the source Unit (no invented regulatory content); coverage of the mapped criteria; pedagogy; cultural respect, including organisation-provided acknowledgements; language and accessibility; interaction integrity; visual legibility; and currency of real-world references. Content failing the audit is automatically repaired and re-audited, or withheld for human review. Unresolved safety findings always hold content for human review. Learner-facing and staff-facing reporting channels feed residual defects back into the same repair pipeline.

8. Content currency

Published content is maintained against the changing real world as a standing service function.

• Regulatory and standards currency: content citing legislation, regulations, standards, codes of practice, statutory rates or regulators is re-verified against primary sources on a rolling schedule using live web research; material changes trigger an automatic correction republished through the quality gate, with every change recorded in the audit log.
• Training-package currency: unit supersessions on training.gov.au are tracked, with affected Providers notified.
• Evergreen refresh: selected content types receive scheduled refreshes (for example, daily micro-learning cycles extend over time), and provider-facing documentation — including this document — is rewritten automatically as the Service ships changes.

9. Records, evidence and reporting

The Service maintains records supporting a Provider's evidentiary and audit obligations.

• Learner activity: pseudonymous play, progress and completion events per link and space, surfaced in Insights and exportable.
• Delivery register: contemporaneous, append-only session records generated by classroom delivery, with named participation from live class games, optional trainer attestation (locked once given), manual entries for off-platform sessions, and CSV export.
• Audit logs: administrative actions (team, links, spaces, curation, billing configuration, content corrections) recorded append-only with actor, action, subject and time; searchable and exportable on both the Provider and Supahuman sides.
• Weekly reporting: workspace owners receive a weekly engagement report; Supahuman operates equivalent platform-level reporting.

10. Service management and updates

The Service is updated continuously. New capabilities, content types and corrections deploy without customer action, maintenance windows or version migrations. Content updates propagate immediately to all delivery channels, including LMS-connected content, without re-export. Material capability changes are reflected in this document through its automatic maintenance cycle. Supabase-hosted customer data and Stripe-processed billing are managed under those platforms' respective certifications alongside Supahuman's own controls.

11. Support

Support is provided in-product and by email.

• Learners: an in-activity help and problem-reporting channel, triaged AI-first with human escalation, plus the AI learning coach where the Provider enables it.
• Provider staff: in-portal support, content flagging, and email support at hello@supahuman.ai.
• Response and resolution targets, where committed, are set out in the applicable agreement or order.

12. Data, privacy and security

The Service is architected for minimal personal data and strict tenancy separation.

• Learner identity is pseudonymous by default: standard access requires no learner account, and a learner-supplied display name is the only identifier unless a Provider enables tracked-learner features or LTI identity.
• Usage analytics may include coarse, city-level location derived from network routing at the time of access; no street address, precise coordinates or raw IP address is stored against learner activity.
• Provider content, variants, learner records and configuration are isolated per workspace; no Provider can access another's data.
• Administrative access by Supahuman staff to a Provider's workspace is possible for support purposes, is visibly badged, and is recorded in the Provider's own audit log as Supahuman action.
• Data is hosted on enterprise cloud infrastructure; payment card data is handled exclusively by Stripe and never touches Supahuman systems.
• Provider data is exportable (content packages, CSV records) and is handled in accordance with the applicable agreement and Supahuman's privacy policy.

13. Customer responsibilities

The Service depends on the Provider for certain inputs and decisions.

• Confirming the fitness of generated content for the Provider's specific delivery and compliance context before relying on it — the Service provides formative practice and evidence tooling and does not certify competency or replace the Provider's assessment obligations.
• Maintaining the accuracy of workspace configuration: scope, team membership and roles, branding, and per-space settings.
• Managing distribution of learner links and access codes appropriate to the audience.
• Providing and maintaining LMS-side configuration where LMS delivery is used.

14. Exclusions and limitations

For clarity, the Service does not include:

• Student management system (SMS/AVETMISS) functions: enrolment, USI management, government reporting or certification issuance.
• Summative assessment services, assessment validation or competency decisions, except the optional practice-assessment features described above on eligible non-accredited scopes.
• Human instructional-design services, except where separately agreed.
• Bespoke development, integrations or content types not described in this document, except where separately agreed.

15. Commercial terms and document control

Pricing, committed volumes, billing cadence, payment terms and any service-level commitments are set out in the applicable agreement, order form or rate card, not in this document. This document is maintained automatically as the Service evolves and republished at this address; the date shown at the foot identifies the current version. Where a signed agreement references a dated copy of this document, that dated copy applies to the engagement, and this address always shows the current state of the Service.