RTOpacks: The Closed Loop¶

Product Vision — Session 18 · 18 March 2026¶

"Invisible tools that make your work visible."

The Market Failure¶

ASQA has the intelligence but no commercial mandate. Their job is compliance, not capability growth. They will never tell an RTO what they could be delivering.

Training consultants give you verbals from across the room. You paid for ten hours, one of those is travel, and you get a Word doc with their logo on it. No mapping. No evidence. No course. No audit folder. Invoice to follow.

Everyone else — peak bodies, training package developers, software vendors — it's too hard. The moving parts are unmanageable. You need trainer data, scope data, corpus data, qual stream relationships, and ASQA standards all at once, all cross-referenced. Nobody has all of it.

The RTO's reality: Thin margins. Bums on seats at under $1,500 a throw. Government funding dependent. No time. No dedicated compliance staff. No budget.

RTOpacks has all of it. The answer is ready before they know to ask the question.

The Pipeline¶

Seven products. One closed loop. Every step either a natural off-ramp or a natural progression. Every step either free at entry or paid for depth. Every step building on the last.

Composer          →  design the architecture
Contextualiser    →  AI enrichment, one run, one observation
Auditor           →  map to unit outcomes and ASQA standards
Trainer Mapper    →  prove you can deliver it
Fill It           →  content production
Deliver           →  Moodle + SCORM + PassKit
Upscaler          →  expand what you can offer

Nothing forces you forward. Everything you've done is saved if you stop.

1. The Composer¶

The thought assembly tool for educational content.

Free at Level 0. Not a chat builder. Not an AI generator. A canvas where RTOs design the architecture of a course before a single word of content is written.

You get the unit in the context of your qual. That's the frame. Everything else is yours to design.

Level 0 — Free. The scratch pad. - Full canvas. All structural widgets. - Notes, flow arrows, video input boxes, formative and summative assessment placeholders. - Design the entire course architecture. Nothing locked. - What you can't do: generate educational content or assessment. You're assembling intent, not product. - Screen capture disabled. Photo of screen returns black. Rules are clear upfront. No anger. - Nothing lost. Persistent. Come back any time. - Print/export: no.

Level 1 — $10/month. The printer. - Everything in Level 0. - Print to PDF. Export to Word or Excel. - Up to 15 course designs per month. - Natural upgrade pull: they hit widgets they don't fully understand — video upload, formative assessment designer — and the next tier is right there.

Level 2 — $50/unit. Shell and fill. - AI generates the framework for a single unit. - Mapping assigned to content. Assessment outcomes mapped. - Three canvas modes: blank and build / shell and fill / shell, fill and edit.

Level 3 — $100/unit. The contextualiser entry point. - Full AI render with contextualisation. - 20 contextualiser runs per course, each saved. - The learning loop begins here.

2. The Contextualiser¶

One run. One observation. No chat.

Not a conversation thread. Not a bot. A single contextualiser run returns two things:

The shell — unit framework rendered in their specific context
One observation — something the engine noticed while it was working

"While we were running, we looked at the unit and where you're heading — have you considered touching on food safety here?"

Not a gate. Not a requirement. A single considered prompt from something that read the unit and read their brief. The RTO says yes or no. Either way it's logged. Move on.

The input quality signal:

Simple scorer before the run fires. Not a wall — a nudge.

Thin input: "We can run this but the output will be generic. Tell us more about your learners and setting."
Decent input: run it.
Rich input: run it and acknowledge it — "This is a strong brief."

The learning loop:

Run 1: "It's for inflight food service on domestic flights." → output

Run 2: "It's for inflight food service on domestic flights on Boeing 737-300 in Qantas fleet for trips between BNE-SYD and SYD-MEL. SYD is hub and where catering is located." → output deepens

Each run is saved. As their knowledge of how to describe their context builds, the output compounds. They're not just building a course — they're learning how to be a better instructional designer. The tool teaches them by showing them what better input produces.

The $100 isn't sunk cost psychology. By the time they hit the next step it's so far back in the rearview it's irrelevant. The anchor price in their head is $700. That's what they used to pay. For a generic course. No contextualisation. No mapping. No video. No SCORM. Delivered by someone who's never been in their industry.

The reference layer:

Optional toggle per course. Standard selector — AQF level descriptors, AQTF standards, training package frameworks, relevant legislation. Links included in output. Appears in course material as further reading, not mandatory content. Appears in the AQTF mapping document regardless — because that's where it counts.

This is the thread that pulls graduates up the AQTF ladder. The RTO's student won't care today. When they do care — RPL application, university credit recognition — the thread is already there. You didn't cost them anything by including it. You gave them a ladder they don't know they'll need yet.

The corporate pitch mechanic:

After a successful contextualised run:

"Want a version contextualised for a specific client? Name them, tell us their operation, and we'll produce a parallel version you can pitch."

Same unit. Different context layer. Fork, not rebuild.

The RTO walks into the pitch meeting with a live demo on the UCCA Moodle — not a proposal, not a slide deck. A working course, in the client's context, ready to run.

The client can't deliver it — they're not an RTO. The client can't certify it — they don't hold scope. The client can't steal it — it's contextualised to their operation, it has no value anywhere else. The IP belongs to the RTO.

The conversation flips. It's not "here's a course we sell." It's:

"We collaborated with you to build learning that describes your operation. It's yours. We certify it. Your people get a nationally recognised qualification that reflects exactly what they actually do."

3. The Auditor¶

Two modes. Both produce evidence.

Free — Self Audit:

You did the work. You drew the map.

Every block on the canvas has a drawer — pulls from the unit. Elements, performance criteria, required knowledge, required skills. All there, waiting. You draw arrows from the drawer points to the blocks you think address them. You decide when you're done.

Output: printout and Excel block-map. Your assertion. Your signature. Your responsibility. UCCA provided the unit data and the tool. You did the thinking.

Paid — AI Audit:

Two variants depending on whose canvas it is.

Your canvas (you built it): AI reads your flow, reads the unit, reads the standard. Identifies gaps — not gates, observations. Makes suggestions, you action or dismiss, all logged.

Our canvas (shell we generated): We built it so we validate it. No gap analysis needed — we narrate instead.

Every block gets a tooltip: "This introduction block addresses 1.2 of the unit outcome and 3.4 of ASQA's standards."

Tooltip turns down to show the exact words from the standard that this content answers. Dual audit: unit outcome AND regulatory standard. Both cited. Both linked.

We're not doing new work here. We already know the ASQA rules and the unit rules to generate the shell. We're just exposing them and highlighting them.

The sign-off moment:

At this point the RTO is $100 in. They can see exactly why it works. Every block justified. Every standard cited. A printed sheet they can take to the compliance officer for sign-off before a single piece of content is written.

That's never existed before. Sign-off on the architecture before you spend the content budget. No more building a course and finding out it doesn't map.

And then — and only then — does the fill-it meter start. Because now they know what they're buying. The "fill it" step isn't a leap of faith. It's an informed purchasing decision.

Everything into the audit folder.

4. The Trainer Mapper¶

"You've built the course. Now prove you can deliver it."

ASQA doesn't just audit the course. They audit the trainer. Vocational competency, industry currency, training and assessment credentials. RTOs fail audits not because the course is wrong but because they can't demonstrate the trainer is right.

Input — three paths: - Upload CV and credentials manually - LinkedIn pull — parse their profile - USI link — pull directly from the register

Three verdicts:

Green — "This person can train and assess this unit. Here's why." Evidence cited. Printable.

Amber — "They'll likely get over the line but you'd strengthen the case by adding: more recent industry experience in X / evidence of currency in Y / a referee from the workforce." Specific. Actionable. Not a rejection.

Red — "No suitable trainer exists in your current staff for this unit." - Option A: Here's what needs to be fixed and how long it realistically takes - Option B: "Want us to write the minimum specs for the role you need to advertise?"

The job ad generator:

Not a generic HR template. A minimum competency specification derived directly from the unit requirements, ASQA's trainer standards, and the specific contextualisation of the course. That's not a job ad. That's a compliance document that happens to attract the right person.

At CV stage — before interview:

Include the mapper link in the job ad. "Before applying, run your credentials against the unit requirements here." Self-selecting candidates. The RTO's inbox stops filling up with unqualifiable applicants.

At interview stage:

"Before we go further, run your credentials through our mapper against this unit." Result comes back in the room. Green means the conversation continues on salary. Amber means you both know exactly what needs to be addressed before the contract is signed. Red means you've saved everyone six months of awkward.

No more "I think we could get by." No more "you've got a few months to get your quals up before the audit."

The application — app only. No web interface.

Mapper runs green → app unlocks → record application video → submit.

The video brief is structured: - Why you want this role — 60 seconds - Your experience in this specific context — 60 seconds - Expected salary and availability for interview — 30 seconds

One take. Retake once. "Doesn't have to be perfect. We get nerves. But hit it."

A trainer who can't present to camera can't present to a classroom. The video isn't a hoop. It's the first evidence of competency.

Into the audit folder:

The application video is evidence. ASQA asks "why did you determine this person was suitable to deliver this unit?"

Credential mapping report ✓
Currency verified ✓
Competency benchmark met ✓
Statement of intent on record, in their own words, timestamped ✓

"Here's why we hired them. They told us. We checked. It stacked up."

ASQA can't argue with a person's own words cited back at them in their own voice.

The virus mechanic:

Every trainer who uses the mapper to apply for a job at an RTOpacks RTO now has the UCCA app on their phone. They're in the ecosystem. Their credentials are in the system. Their USI is linked. They deliver the course. Their students complete on the UCCA app. Students get certs in their wallets.

The product spreads through the workforce it certifies. Not ads. Not sales calls. The pipeline is the growth engine.

5. Fill It¶

Content production. The meter starts here.

They know what they're buying. The architecture is signed off. The trainer is validated. The mapping is done. Now they fill the shell.

Pricing flows from the L3 catalogue. Every line item traceable to a canvas decision. The docket is the invoice.

6. Deliver¶

Course → SCORM → Moodle → App → Wallet → Verification

SCORM package generated from canvas output
Delivered on UCCA Moodle (yourrto.rtopacks.com.au)
Completed on the UCCA app — no classroom needed
Certification issued to phone wallet via PassKit
Cabin manager asks for cert → crew taps phone → PassKit card → scan

No classroom. No paper. No LMS login. No PDF emailed to HR.

The cert is on the device that's already in their pocket at 35,000 feet.

The Preview Lab:

Tier	Duration	Price
Spot check	24 hours	$10
Review	7 days	$90
Monthly	30 days	$100/month

Front and back end access. Student view, assessor view, grade book. UCCA URL only — can't be passed off as production. "It works in ours. Call your vendor."

7. The Upscaler¶

The retention engine. The expansion engine. The business intelligence report they couldn't commission for under $10,000.

The system already knows: - Your trainers — credentials, currency, mapped competencies - Your existing scope — every qual you're approved to deliver - Your corpus — every course you've built in RTOpacks - Your learner cohort — who's completing, at what level, in what context

Nobody else has that picture. Not the RTO. Not ASQA. Not the training package developer. UCCA has it as a byproduct of the pipeline being used properly.

Vertical expansion — what you already have:

"Based on your current trainers and existing scope, you could add these quals with no additional operational cost. Your people are already qualified to teach them. Here's the gap between what you're approved for and what you could be approved for."

The king hit: "You only built to Cert III. Your trainers can deliver this all the way to Advanced Diploma. You're leaving three qualification levels on the table."

Not a sales pitch. A specific, evidence-based expansion opportunity derived from data they've already given us.

New stream addition — the full submission package:

Note: vertical expansion within an existing stream may not trigger an audit — confirm with ASQA standards before building. Where an audit is triggered, the Upscaler packages the submission.

The auditor arrives and finds: - Course built and mapped ✓ - Running live on the testbed — log in and see it ✓ - Trainer validation reports ✓ - Print delivery mapped ✓ - Online delivery mapped ✓ - Cross-mapped to learning outcomes and ASQA standards ✓ - Everything in the folder before they ask for it ✓

The audit isn't an inspection anymore. It's a presentation.

The compounding lock:

Every qual an RTO adds through the Upscaler increases the value of staying in RTOpacks. Their corpus grows. Their trainer profiles deepen. Their audit folder thickens. The cost of leaving isn't just switching cost — it's evidence destruction.

They don't leave. Not because they can't. Because why would you?

The Audit Folder¶

Everything in one place. Always current. Always complete.

Course architecture ✓
Contextualisation record ✓
Mapping to unit outcomes ✓
Mapping to ASQA standards ✓
Compliance sign-off sheet ✓
Trainer validation report ✓
Application video ✓
Hiring decision record ✓
Delivery evidence ✓
Learner certification record ✓

ASQA arrives. You open the folder. Discussion over before it starts.

That's not compliance management. That's compliance confidence. Completely different emotional state to walk into an audit with.

The Thesis — Fully Expressed¶

The corpus was always the moat. The Composer is the gate. The Contextualiser is the learning engine. The Auditor is the evidence machine. The Trainer Mapper is the hiring standard. The Upscaler is the retention and expansion engine. The App is the delivery vehicle. The Wallet is the credential. The Audit Folder is the confidence.

UCCA invisible throughout.

"The internet moved data without knowing who sent it. UCCO moves capability with full knowledge of who holds it, what they're certified to do, and what they actually did."

The Market Position¶

ASQA: has the intelligence, no commercial mandate Consultants: have the knowledge, too slow, too expensive, verbals from across the room Everyone else: too hard, moving parts unmanageable

RTOpacks: has the data, the pipeline, the delivery infrastructure, and the answer ready before they know to ask the question

For the first time RTOs can pitch to corporate clients — not just students off the street.

The client can't deliver it. The client can't certify it. The client can't steal it.

"We collaborated with you to build learning that describes your operation. It's yours. We certify it. Your people get a nationally recognised qualification that reflects exactly what they actually do."

That's not a training product. That's organisational knowledge capture with a qualification attached.

UCCA Inc · Product Vision · Session 18 · 18 March 2026

"Invisible tools that make your work visible."

"A schmoke and a pancake?" — Goldmember