THE FACTORY¶
UCCA RTOpacks — Product Vision¶
18 March 2026 · Internal Document¶
"The people who know the most about the job are rarely the people writing the training materials. RTOpacks closes that gap."
The Problem¶
Australia has 15,000+ registered training organisations. Every one of them is legally required to deliver training against nationally endorsed units of competency. Every one of them is required to continuously improve their training and assessment. Every one of them needs to prove it to ASQA.
The content they use to do this is almost universally terrible.
Not because RTOs are incompetent. Because the process of turning expert knowledge into compliant training materials is broken. The spark plug technician knows exactly how to change a spark plug. The aged care worker knows exactly how to assist with personal hygiene with dignity. The chef knows exactly how to prepare meat safely. But getting that knowledge out of their heads, mapped to a unit of competency, formatted for delivery, assessed against performance evidence, and packaged for an LMS — that process is a nightmare.
So RTOs buy generic content from content farms. Decontextualised. Unmapped. Produced in bulk by people who've never held a torque wrench. And they hope ASQA doesn't look too closely.
RTOpacks ends this.
The Position¶
RTOpacks is a content engine. Not an LMS. Not a student portal. Not an enrolment system.
We build it. We sign it. We deliver it. What happens inside the LMS is not our problem.
Our customer is the RTO — specifically the people inside RTOs who create and manage training content. Trainers. Course writers. Compliance managers. Subject matter experts. The people who know the job.
Our product puts professional content production capability in their pocket. Literally.
The Product Stack¶
Tier 1 — Generic Pack¶
What everyone else sells. But faster, cheaper, and properly mapped.
Buy a unit or qualification. Get a standard assessment and training resource pack. No contextualisation. Instant delivery. SCORM-ready, xAPI-ready, print-ready.
Pricing: - Per unit: flat fee - Per qualification: core + minimum electives bundled - Extra electives: per unit add-on - Delivery: immediate — no human in the loop
This is the foot in the door. "We give you what the market gives you. But it actually maps to the unit."
Tier 2 — Contextualised Pack¶
The UCCA difference. No one else can do this.
Log in. Tell us about your learners. Your industry. Your workplace context. Your organisation's tone. Upload your logo. Select your AI model — Sonnet for speed, Opus for depth, or Mavis for human-in-the-loop production.
The engine runs against your context. Output is a fully contextualised pack — your language, your industry examples, your workplace scenarios — that you read, edit, and approve before it's packed.
The editor is inside the wall. You can read and annotate freely. You cannot export until you approve and pay. The content is yours the moment you tap Pack.
Tier 3 — Rich Media¶
Static images, graphs, diagrams. AI generated or uploaded.
Every content anchor can carry a static image. AI generated against your context. Or upload your own. Or pull from our licensed image library.
Graphs and diagrams generated from data you provide. Infographics built from unit content automatically.
Billed per asset or included at subscription tier.
Tier 4 — AI Video¶
Agentic video production. Billed per minute of finished content.
Select your video agent. Set the tone. The engine produces. You approve. Billed per minute of finished product time.
For when no one in the team can get to the workshop floor this week.
Tier 5 — Bring Your Own Video¶
Film it. Tag it. It goes in. $0 AI cost. Infinite authenticity.
The most powerful tier. $0 for the video production itself.
The trainer films the spark plug procedure on their phone via the RTOpacks app. Tags the insertion point. Uploads. The engine integrates it at the exact anchor point in the content. Their face. Their workshop. Their equipment. Their voice.
No AI can replicate this. And ASQA loves it — real workplace evidence, embedded in the training material, cryptographically timestamped.
The Compliance Checker — The Engine Inside the Engine¶
After Mavis dictates and hits Process, the engine does three things simultaneously:
1. Maps her content against the unit Every sentence tagged against performance evidence (PE), knowledge evidence (KE), and assessment conditions from the TGA unit. The engine knows the unit — it's in rtopacks-db.
2. Surfaces the gaps
📋 Compliance Check — AURTTA2014
─────────────────────────────────
✅ PE 1.1 — Addressed (section 2, para 3)
⚠️ PE 1.2 — Not addressed
✅ PE 1.3 — Addressed (section 4, para 1)
⚠️ KE 1 — Partially addressed
✅ KE 2 — Addressed (section 3, para 2)
─────────────────────────────────
2 gaps found. Pack cannot be signed until resolved.
3. Suggests content for each gap
⚠️ PE 1.2 — Remove and refit spark plugs to
manufacturer specifications
You haven't addressed this directly. Based on
what you've dictated, we suggest:
"When refitting spark plugs, torque to
manufacturer specification — typically
25-30Nm for aluminium heads. Over-tightening
risks thread damage. Under-tightening risks
blowout under compression."
[ Accept ] [ Modify ] [ I'll do it manually ]
Accept → drops into content at the right point, tagged to PE 1.2. Modify → inline editor opens, she rewrites, accepts. Manual → she dictates again for that section, engine reruns on that element only.
The process is iterative. Rerun compliance check as many times as needed. Green across the board = ready for peer review. The panel never receives a pack with gaps. The engine is reviewer one. Mavis is reviewer two. The panel is reviewer three. ASQA is reviewer four — and by then it's airtight.
Every accepted or modified suggestion is anchored to the PE/KE it addresses. The provenance record says: "PE 1.2 addressed via author-modified engine suggestion, accepted 15 March 2:47pm." Not just content approved. Evidence of what was addressed, how, and when.
The Running Bill¶
Top corner of the app. Live. Every asset, every engine interaction adds to the total.
📋 Current pack — AURTTA2014
─────────────────────────────────────────
Contextualisation run (Opus) $29.00
Compliance check $4.00
2 × engine suggestions accepted $6.00
1 × suggestion modified $3.00
3 × AI image generation $6.00
Video processing (2 clips) $12.00
─────────────────────────────────────────
Current total $60.00
[ Rerun compliance check ] [ Pack it ]
Mavis doesn't resent the bill. Each line item represents something she didn't have to think about. The engine found the gap. The engine suggested the fix. She tapped accept. Four dollars. Done. The alternative was an ASQA finding worth thousands.
The till isn't a cost. It's a value display.
Tap to pack. Tap to pay. Done.
The App — A Creator Tool, Not a Learner Tool¶
The RTOpacks app is for trainers, course writers, subject matter experts, and compliance managers. Students never touch it.
What the app does:
For the course writer (Mavis): - Dictate content via Whisper — lying on the couch, staring at the ceiling, Saturday morning - Drop anchor keywords naturally — "anchor video here," "anchor pic," "inline quiz, three questions" - Engine structures the dictation, parses anchor tags, builds the framework - Review assembled content inline - Assign shoot requests to team members - Review, annotate, approve or request revisions - Submit for peer review - Tap to pack when approved
For the filmmaker (Dave, Sarah, the workshop tech): - Receive a shoot list notification - See the brief — what to film, where, how, in what orientation, with what audio - No login to a content system. No reading a document. Just a list of shots and a camera button. - Tap. Point. Shoot. Upload. Done. - Engine processes and drops it at the anchor point automatically
For the compliance reviewer (Jenny): - Receive a review notification scoped to their sections - Read, watch, annotate inline - Reply to author notes - Approve or flag - All recorded, all timestamped
The Shoot List¶
The filmmaker never sees the document. They get a job list.
📋 SHOOT LIST — Certificate III Automotive
Assigned by: Mavis W.
1. Spark plug removal procedure
┌─────────────────────────────┐
│ 📐 Landscape │
│ 🎙 Live audio on │
│ 📍 TAFE auto garage │
│ 🚗 6 cylinder car │
└─────────────────────────────┘
[ Shoot now ] [ Mark done ]
2. Torque wrench calibration — wheel nuts
┌─────────────────────────────┐
│ 📐 Landscape │
│ 🎙 No audio — music bed │
│ 📍 Workshop floor │
│ 🔧 Show torque reading │
└─────────────────────────────┘
[ Shoot now ] [ Mark done ]
Production notes written by the course writer during dictation. Parsed by the engine. Delivered as a professional brief. The filmmaker executes without context-switching.
The Review Thread — One Blob, No Channels¶
Inline. Contextual. Threaded to the section. Visible to everyone on the pack. The filter is the reader.
No Slack channels. No email routing. No compliance matrix. A Post-it note on the page that everyone can see and anyone can reply to.
─── Section 4.2 — Preparation of Meat ──────────────────
│ [VIDEO: Dave's kitchen reference, 2:34] ▶ │
│ │
│ 💬 Mavis W. · 14 March · 9:47pm │
│ "This sits right visually but does it align │
│ to our policy on religious considerations? │
│ Jenny can you check for compliance. │
│ Dave — can we reshoot in uniform? I did │
│ this in my kitchen as a visual guide only. │
│ [Reference video attached ▶]" │
│ │
│ 💬 Jenny K. · 15 March · 8:23am │
│ "Checked. Halal prep covered in policy │
│ addendum. Need a disclaimer line before │
│ this section. I've drafted it below." │
│ │
│ 💬 Dave M. · 15 March · 11:04am │
│ "Reshoot done. Kids in uniform. │
│ Uploaded. Let me know if angle is ok." │
│ [New video uploaded ▶] │
│ │
│ 💬 Mavis W. · 15 March · 11:31am │
│ "Perfect. Approved. Jenny's disclaimer │
│ added. Section locked." │
│ │
│ ✅ Section approved · 15 March · 11:31am │
─────────────────────────────────────────────────────────
Jenny sees her compliance question and reply. Dave sees his reshoot request and result. Mavis sees everything. No one is overwhelmed. Everyone is in context.
Every message recorded. Every approval timestamped. Every revision documented. The blob is the audit trail.
The Peer Review Panel¶
Before a pack ships, it goes to the Ed Panel.
Mavis taps "Submit for Review." Notification goes to panel members. Each reviewer opens the course in their app — full content, all threads visible, all videos playable. They annotate. They flag. They approve section by section.
When all sections are approved by the required panel members — the pack is ready.
This isn't a formality. It's a quality gate with teeth.
What the approval record shows:
Pack: Certificate III Automotive — Unit AURTTA2014
Author: Mavis W.
Submitted for review: 15 March 2026 · 11:35am
Panel: 3 members required
Reviewer 1: Jenny K. (Compliance) · Approved · 15 March · 2:14pm
Reviewer 2: Robert S. (Industry) · Approved · 15 March · 4:07pm
Reviewer 3: Tim R. (Academic) · Approved · 16 March · 9:22am
Revisions: 2 requested · 2 resolved
Cryptographic signature: issued
UCCA Ledger entry: keys.ucca.online/verify/a3f9...
Pack status: APPROVED AND SIGNED
TAFE's procurement team sees this and thinks: "We can put this in front of ASQA without flinching."
The Compliance Lifecycle — The King Hit¶
This is the product that locks them in forever.
Every piece of content produced through RTOpacks is: - Timestamped at creation - Versioned on every edit - Signed on approval - Chained on the UCCA ledger
One year after approval, RTOpacks pings the author:
"Your content for AURTTA2014 was approved 52 weeks ago. Standards Clause 2.2 requires continuous improvement. Review your content now. Still current? One tap to approve and we'll issue your Continuous Improvement Certificate."
They open the app. Watch their own video. Read the content. Still current — tap approve. Updated — make changes, resubmit for panel review.
The Continuous Improvement Certificate: - Cryptographically signed by UCCA - Dated and versioned - Goes into Apple Wallet - Linked to the UCCA ledger entry - ASQA audit: "Show me your continuous improvement evidence." Hand them a URL.
keys.ucca.online/verify/a3f9...
Live verification page. Full chain. Every version. Every review. Every approval. Immutable.
This isn't a nice-to-have. This is what RTOs pay a compliance consultant $300/hour for. RTOpacks gives it to them automatically as part of the production process.
The LMS Integration Play¶
RTOpacks is not an LMS. We certify integrations.
We publish an API. Major RTO LMS providers — CloudAssess, aXcelerate, Wisenet, Moodle — write to our endpoint. Pack purchased, content pushed via API to their LMS automatically.
"RTOpacks Verified Integration" — a badge LMS providers want because it means their customers can buy packs and have them appear in the LMS without lifting a finger.
If their code is good: seamless. If their code is bad: that's their problem.
We don't touch students. We don't manage enrolments. We don't run a gradebook. We build content, sign it, and push it. The LMS handles the rest.
The Credential — Phone In, Phone Out¶
In: Trainer films on phone. Tags insertion point. Uploads via RTOpacks app. Engine integrates at the anchor. Content built around real workplace evidence.
Out: Learner completes assessment. Statement of attainment issued. Push notification to phone. Tap. It's in Apple Wallet. Cryptographically signed by UCCA. Scan the QR. Live verification page. Full provenance chain.
The phone is not a delivery mechanism. It's the interface between the physical world of work and the compliance record that proves competency was assessed against real workplace evidence.
The White Label Option¶
For RTOs who want their own branded experience:
- $150/month — we provision, we upload, your branding, your domain
- iOS app: additional monthly fee (Apple dev account + margin)
- Android: additional monthly fee
- Both: bundled discount
- Annual: 30% off, no refund
We own the app always. If the RTO wants custom builds, we're the builder. They don't go elsewhere. The app is UCCA infrastructure — we just skin it.
The Mavis Model — The Factory¶
Saturday morning. Coffee. App open. Shoot list ready.
Framework built Friday night on the couch — dictated, structured by the engine, anchors tagged. Saturday is execution. Shot by shot. Brief by brief. No context switching. No re-reading. No "wait which unit is this for again." The app holds all of that.
By midday: done. Tap review. Course assembled. Read through once. Approve. Tap pack.
Bill: $340. Time: four hours including breakfast.
One person. One morning. One complete, cryptographically signed, ASQA-ready, LMS-ready, Apple-Wallet-credentialed course.
Scale that. Ten Mavises. A hundred. Each a specialist. Aged care Mavis. Construction Mavis. Hospitality Mavis. All running the same app. All feeding the same engine. All getting paid per pack approved.
That's not freelance. That's a factory.
Revenue Architecture¶
| Product | Model | Price point |
|---|---|---|
| Generic pack — per unit | One-off | $X |
| Generic pack — per qualification | One-off | $Y (bundled) |
| Contextualisation run | Per run | $29 |
| AI image generation | Per asset | $2 |
| AI video | Per minute finished | $X |
| Bring your own video processing | Per clip | $X |
| White label LMS | Monthly subscription | $150/month |
| iOS app | Monthly | $X |
| Android app | Monthly | $X |
| Annual (any tier) | Annual | 30% discount |
| Compliance lifecycle | Included in subscription | — |
| Continuous Improvement Certificate | Included | — |
| API access | Per integration or per call | TBD |
| Credential issuance | Per certificate or subscription | TBD |
What This Is Not¶
- Not an LMS
- Not a student portal
- Not an enrolment system
- Not a gradebook
- Not a compliance consultant
- Not a content farm
What this is:
A factory. A studio. A compliance engine. A credential issuer. A production tool that turns expert knowledge into auditable, signed, market-ready training content — in a Saturday morning.
THE FACTORY · UCCA RTOpacks Product Vision Internal document — not for distribution 18 March 2026
"Well done Mavis."