commit 79589bf4d2b4b2f1fd75649b1fe5f5a3a480ef3f Author: Sandeep Sethi Date: Mon Jul 20 03:06:06 2026 +0000 Initial import of live site diff --git a/about.html b/about.html new file mode 100644 index 0000000..da7734b --- /dev/null +++ b/about.html @@ -0,0 +1,289 @@ + + + + + + + About RTOSure — RTOSure + + + + + + + + + + +
+
+
+ Our story +

Built by people who understand
the NVR Standards.

+

RTOSure is a product of RTO Software — the Australian company behind TEAMS, the student management system used by hundreds of RTOs and colleges across the country. We built RTOSure because we kept seeing the same problem: compliance managed in spreadsheets, institutional knowledge locked in one person, and audit preparation treated as a recurring emergency.

+
+
+
+ + +
+
+
+
+ +

Compliance software that actually knows your Standards.

+

[PLACEHOLDER — team origin story, connection to TEAMS, specific moment or client situation that triggered the product decision. Approx 100–150 words.]

+

The result is a system that knows the NVR Standards 2025, the ESOS framework, the National Code 2018, and the ELICOS Standards 2018 — not as configuration options, but as the architectural foundation of the product itself.

+

We're based in Australia, working exclusively in the VET and ELICOS sector. This isn't a generic compliance tool adapted for RTOs. It was built for RTOs from day one.

+
+
+
+
+
+
+
Australian companyBased in Australia. Built for Australian RTOs. Hosted on Australian servers.
+
+
+
+
Sector specialistsThe team behind TEAMS — used by hundreds of RTOs across Australia since [year].
+
+
+
+
Human expertiseThe RTOSure framework is maintained by people with deep VET sector and regulatory knowledge.
+
+
+
+
+
+
+
+ + +
+
+
+ +

Meet the people behind RTOSure

+

In the Australian VET sector, buyers research the people behind a product before signing. Here we are.

+
+
+
+
[PH]
+
[Name Placeholder]
+
Founder & CEO
+

[Bio placeholder — connect to specific regulatory expertise and VET sector background. Approx 50–70 words.]

+
+
+
[PH]
+
[Name Placeholder]
+
Head of Compliance
+

[Bio placeholder — RTO compliance specialist, ASQA audit experience, NVR Standards expertise. Approx 50–70 words.]

+
+
+
[PH]
+
[Name Placeholder]
+
Product Lead
+

[Bio placeholder — product development background, VET sector technology. Approx 50–70 words.]

+
+
+

Team bios and photos to be added before launch. Placeholder structure is final.

+
+
+ + +
+
+ +

The team behind TEAMS.

+

RTOSure is built by RTO Software — the same team that built and maintains TEAMS, Australia's purpose-built student management system for the VET sector. If your college already uses TEAMS, RTOSure integrates directly — no double entry, no data duplication.

+ See the TEAMS integration → +
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/compliance.html b/compliance.html new file mode 100644 index 0000000..6386ae8 --- /dev/null +++ b/compliance.html @@ -0,0 +1,288 @@ + + + + + + + Compliance Areas — RTOSure + + + + + + + + + + + +
+
+
+ Regulatory coverage +

Not configured. Not adapted.
Built in.

+

Every regulatory framework your college operates under — NVR Standards 2025, ESOS Act, National Code 2018, ELICOS Standards 2018 — is mapped into RTOSure from the legislative text up. Your obligations are already there. You just have to manage them.

+
+
+
+ + +
+
+
+ +

Which regulatory obligations
does your college carry?

+

Many Australian colleges operate under two or all three frameworks simultaneously. RTOSure covers them all in one system — with clean separation between each layer.

+
+ +
+
+ RTOSure +

NVR Standards 2025

+

Domestic RTOs / ASQA-regulated providers

+

The foundational compliance layer for every Australian RTO. 4 Quality Areas, 19 Standards, 3 Compliance Requirement Divisions, and FPPR obligations — all mapped to specific risk indicators and evidence requirements.

+ Explore NVR coverage → +
+ +
+ CRICOSSure +

ESOS Act & National Code 2018

+

CRICOS-registered providers

+

All 11 National Code 2018 Standards plus standalone ESOS Act obligations — covering international student admissions, CoE management, welfare obligations, PRISMS reporting, and student default provisions.

+ Explore CRICOS coverage → +
+ +
+ ELICOSSure +

ELICOS Standards 2018

+

ELICOS colleges and providers

+

Parts A–E of the ELICOS Standards 2018 — with course-type-specific compliance for General English, EAP, IELTS Preparation, EHSP, and under-18 student welfare obligations mapped in.

+ Explore ELICOS coverage → +
+
+
+
+ + +
+
+
+
+ +

Most Australian colleges operate
under two or three frameworks at once.

+

A CRICOS-registered RTO delivering both domestic and international students faces ASQA compliance under the NVR Standards AND ESOS/National Code obligations for its international cohort. Add ELICOS delivery and the compliance burden triples.

+

Generic compliance tools require you to configure each framework yourself. RTOSure maps them all in — because they were never configurable to begin with. They are regulatory obligations that exist whether your system knows about them or not.

+ See the multi-framework view → +
+
+
+
+
+ NVR Standards 2025 + 19 Standards +
+
+ National Code 2018 + 11 Standards +
+
+ ELICOS Standards 2018 + Parts A–E +
+
+
All mapped in one system
+
+
+
+
+
+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/contact.html b/contact.html new file mode 100644 index 0000000..7d0dafd --- /dev/null +++ b/contact.html @@ -0,0 +1,250 @@ + + + + + + + Contact Us — RTOSure + + + + + + + + + + +
+
+
+ Get in touch +

Talk to a real person
who understands RTOs.

+

We're based in Australia, operating in Australian business hours. Whether it's a support question, a pricing conversation, or a general enquiry — we're here.

+
+
+
+ + +
+
+
+
+

How to reach us

+
+
+ +
General enquirieshello@rtosure.com.au

We aim to respond within one business day.

+
+
+ +
Supportsupport@rtosure.com.au

For existing clients — product support and technical issues.

+
+
+ +
Business hours

Monday – Friday
9:00am – 5:30pm AEST / AEDT

Australian Eastern time. We do not operate on Australian public holidays.

+
+
+ Want a product demo instead? +

If you're evaluating RTOSure, a 30-minute demo is a better use of your time than a general enquiry.

+ Book a demo → +
+
+
+ +
+

Send us a message

+
+
+
+
+
+ +
+
+ +
+
+
+
+
+ + + + + + + \ No newline at end of file diff --git a/cricossure.html b/cricossure.html new file mode 100644 index 0000000..5fdfa90 --- /dev/null +++ b/cricossure.html @@ -0,0 +1,260 @@ + + + + + + + CRICOSSure — ESOS & National Code 2018 — RTOSure + + + + + + + + + + +
+
+
+ CRICOSSure — CRICOS Providers +

ESOS & National Code 2018.
Complete coverage.
Purpose-mapped.

+

All 11 National Code 2018 Standards plus standalone ESOS Act obligations — mapped into CRICOSSure from the legislative text. PRISMS workflows, CoE management, student welfare, agent obligations, and fee protection — all in one system.

+ +
+
+
+ +
+
+
+ +

All 11 National Code Standards
+ ESOS Act obligations

+
+
+

Standard 1 — Registered provider obligations

Provider registration, scope maintenance, regulatory reporting, and compliance with ESOS Act conditions.

+

Standard 2 — Recruitment & admissions

Accurate marketing, genuine student assessment, agent management, and admissions integrity.

+

Standard 3 — Fees, charges & refunds

Written agreements, fee schedules, refund obligations, and TPS requirements for pre-paid fees.

+

Standards 4–6 — CoE & enrolments

CoE management, enrolment conditions, course progress, attendance monitoring, and PRISMS reporting workflows.

+

Standards 7–9 — Welfare & support

Welfare obligations, accommodation, overseas student health cover, critical incidents, under-18 guardianship.

+

Standards 10–11 — Complaints & appeals

Internal complaints processes, external appeals pathways, record-keeping, and regulatory notifications.

+
+
+
+ +
+
+
+
+ +

Standalone ESOS obligations.
Also covered.

+

Beyond the National Code, the ESOS Act 2000 imposes direct obligations on registered providers — including student default provisions, record-keeping requirements, criminal offence provisions, and TPS reporting. CRICOSSure maps these separately from the National Code Standards so nothing is missed.

+
    +
  • Student default provisions and refund obligations
  • +
  • Record-keeping and document retention requirements
  • +
  • PRISMS reporting obligations and deadlines
  • +
  • Tuition Protection Service (TPS) obligations
  • +
+ Book a CRICOS demo → +
+
+
85+
Risk indicators
+
11
National Code Standards
+
1
ESOS Act section
+
100%
Framework coverage
+
+
+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/demo.html b/demo.html new file mode 100644 index 0000000..0c095e6 --- /dev/null +++ b/demo.html @@ -0,0 +1,276 @@ + + + + + + + Book a Demo — RTOSure + + + + + + + + + + +
+
+
+ Book a demo +

30 minutes.
Tailored to your framework.
No hard sell.

+

We'll show you RTOSure mapped to the compliance frameworks your college actually operates under — not a generic walkthrough. Bring your compliance manager. Or just come yourself.

+
+
+
+ + +
+
+
+ +
+ +

A real demo.
Built around your college.

+
+
+
1
+
We review your registration before the callWe'll look up your ASQA registration, CRICOS status, and any ELICOS delivery — so the demo is specific to your situation.
+
+
+
2
+
We show you your compliance, not oursThe demo is built around the frameworks your college is actually regulated by. You'll see how your obligations look inside RTOSure.
+
+
+
3
+
You ask the hard questionsWe leave 10 minutes at the end for your questions. Pricing, data security, onboarding, TEAMS integration — nothing is off limits.
+
+
+ +
+

Who should attend

+
    +
  • CEO / Principal / Director
  • +
  • Compliance Manager
  • +
  • Quality & Standards lead (if applicable)
  • +
+
+
+ + +
+

Book your demo

+
+
+
+
+
+ +
+
+ +
+
+ +
+
+ +

We'll confirm within one business day with a calendar link. Australian business hours.

+
+
+
+
+
+ + + + + + + \ No newline at end of file diff --git a/elicossure.html b/elicossure.html new file mode 100644 index 0000000..84fdd23 --- /dev/null +++ b/elicossure.html @@ -0,0 +1,235 @@ + + + + + + + ELICOSSure — ELICOS Standards 2018 — RTOSure + + + + + + + + + + +
+
+
+ ELICOSSure — ELICOS Colleges +

ELICOS Standards 2018.
Parts A to E.
All mapped in.

+

The ELICOS Standards 2018 cover five distinct parts — from provider management and marketing through to course delivery, teacher qualifications, and under-18 welfare. ELICOSSure maps all of them, with course-type-specific compliance built in for GE, EAP, EHSP, and IELTS Preparation programs.

+ +
+
+
+ +
+
+
+ +

ELICOS Standards 2018 — Parts A to E

+
+
+

Part A — Provider obligations

Registration requirements, governance arrangements, academic management, resources, and staff qualifications.

+

Part B — Marketing & recruitment

Marketing accuracy, agent management, admissions requirements, written agreements, and refund obligations.

+

Part C — Welfare & support

Student welfare obligations, accommodation, orientation, health and safety, critical incidents, and under-18 welfare.

+

Part D — Course delivery

Contact hours, class sizes, course materials, course progression, and attendance monitoring.

+

Part E — Teacher qualifications

TESOL qualifications, teacher registration, ongoing professional development, and CPD records.

+

Course-type specific

Additional requirements for General English, EAP, EHSP, and IELTS Preparation programs — mapped separately.

+
+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/features.html b/features.html new file mode 100644 index 0000000..065ab9f --- /dev/null +++ b/features.html @@ -0,0 +1,665 @@ + + + + + + + Features — RTOSure + + + + + + + + + + + +
+
+
+ Platform features +

Everything you need to manage compliance — nothing you don't.

+

Six purpose-built capabilities, each designed around a real compliance problem your team deals with every day. No feature bloat. No configuration burden. Built around your Standards from day one.

+ +
+
+
+ + +
+
+ + +
+
+ + +

Know your compliance status
without asking anyone.

+

A live dashboard maps every obligation across your registered frameworks. See what's compliant, what's due, and what's at risk — filtered by Standard, Quality Area, or staff member.

+
    +
  • Filter by NVR Standard, ESOS obligation, or National Code requirement
  • +
  • See open evidence gaps, upcoming deadlines, and overdue items
  • +
  • Drill down from summary to individual Standard-level detail
  • +
  • Export board-ready compliance reports in one click
  • +
+
+
+
+ +
+ RTOSure dashboard showing framework health, quality area risk and compliance activity +
+
+ + +
+
+ + +
+
+
+ +
+ RTOSure checklist and workflow guided compliance task +
+
+ + +
+
+ + +

Compliance tasks done correctly,
every time, by anyone.

+

Guided workflows walk your team through compliance tasks step by step — built around the specific Standards that apply to your college. No interpretation required. No steps skipped.

+
    +
  • Pre-built checklists for trainer PD, student monitoring, training package updates
  • +
  • Customisable checklists for organisation-specific workflows
  • +
  • Role-based task assignment with automated reminders
  • +
  • Task completion audit trail — who did what and when
  • +
+
+
+ + +
+
+ + +

Evidence captured at the point
it's created.

+

Built-in forms and quizzes capture evidence directly against the relevant Standard — at the moment the activity happens. External stakeholders (students, agents, employers) complete forms via a unique link. No login required.

+
    +
  • Forms auto-tagged to the Standard or obligation they satisfy
  • +
  • External stakeholder links — no login, no friction
  • +
  • Quizzes for compliance knowledge verification (trainers, staff)
  • +
  • Responses flow directly into the evidence register
  • +
+
+
+
+
📝
+ Forms screenshot
External stakeholder form with Standard tagging +
+
+
+ + +
+
+
+
🗂
+ Evidence register screenshot
Documents mapped to Standards with version history +
+
+
+ + +

Your audit response
starts here.

+

When the auditor asks for evidence of Standard 1.3, you don't search — you click. Every document, policy, and record is stored, mapped, and retrievable in the format auditors expect.

+
    +
  • Every document tagged to the Standard or requirement it addresses
  • +
  • Version control — always know which document is current
  • +
  • Activity log — who uploaded or updated each item, and when
  • +
  • Audit pack export — share a structured evidence bundle in one action
  • +
+
+
+ + +
+
+ + +

Stop things falling through
the cracks.

+

RTOSure doesn't just store your compliance data. It actively monitors it and alerts the right people when action is needed — before a gap becomes an audit finding.

+
    +
  • Automated reminders at 30, 14, and 7 days before deadlines
  • +
  • Alerts for expiring trainer credentials, WWCC records, and CPD logs
  • +
  • Escalation workflows if tasks remain incomplete
  • +
  • Email and in-app notifications to responsible staff
  • +
+
+
+
+ +
+ RTOSure notification and alerts dashboard +
+
+ + +
+
+ + +
+
+ + +

Know your risk
before ASQA does.

+

Purpose-built risk indicator frameworks — mapped to NVR, ESOS, National Code, and ELICOS — give you structured, evidence-based visibility into compliance exposure across every object type your college operates.

+
    +
  • 180+ NVR risk indicators across six object types
  • +
  • 85+ CRICOS / ESOS indicators across all 11 National Code Standards
  • +
  • 56+ ELICOS indicators across Parts A–E
  • +
  • Traffic-light risk scoring with priority weighting
  • +
+
+
+
+ +
+ RTOSure risk indicators dashboard +
+
+ + +
+
+ +
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + + \ No newline at end of file diff --git a/footer.html b/footer.html new file mode 100644 index 0000000..04a80e1 --- /dev/null +++ b/footer.html @@ -0,0 +1,248 @@ + + + + + + + diff --git a/header.html b/header.html new file mode 100644 index 0000000..92e26e4 --- /dev/null +++ b/header.html @@ -0,0 +1,250 @@ + + + + + + + + + diff --git a/images/CheckListDashboard.png b/images/CheckListDashboard.png new file mode 100644 index 0000000..9ead036 Binary files /dev/null and b/images/CheckListDashboard.png differ diff --git a/images/NVRDashboard.webp b/images/NVRDashboard.webp new file mode 100644 index 0000000..ffa3382 Binary files /dev/null and b/images/NVRDashboard.webp differ diff --git a/images/checklist.webp b/images/checklist.webp new file mode 100644 index 0000000..2da2124 Binary files /dev/null and b/images/checklist.webp differ diff --git a/images/compliance-dashboard.webp b/images/compliance-dashboard.webp new file mode 100644 index 0000000..223c0fd Binary files /dev/null and b/images/compliance-dashboard.webp differ diff --git a/images/notification.webp b/images/notification.webp new file mode 100644 index 0000000..3e8fabf Binary files /dev/null and b/images/notification.webp differ diff --git a/images/risk_indicator.webp b/images/risk_indicator.webp new file mode 100644 index 0000000..a81f514 Binary files /dev/null and b/images/risk_indicator.webp differ diff --git a/index.html b/index.html new file mode 100644 index 0000000..c8dc853 --- /dev/null +++ b/index.html @@ -0,0 +1,814 @@ + + + + + + + + + + + + RTOSure — Compliance Management for Australian RTOs + + + + + + + + + + + + +
+
+
+ +
+
+ + Purpose-built for Australian RTOs +
+

+ Compliance managed.
+ Audit ready.
+ Every framework covered. +

+

+ RTOSure maps your NVR Standards 2025, ESOS obligations, and National Code requirements into a single compliance management system — with dashboards, risk indicators, evidence registers, and guided workflows built around the frameworks your college is actually regulated by. +

+ +

+ 30 minutes. Tailored to your framework. No hard sell. +

+
+ + + +
+
+
+ + + +
+
+

Sound familiar?

+

+ The three problems every RTO
compliance manager knows too well. +

+ +
+ + +
+ +

ASQA audit risk

+

Your next audit notice gives you 30 days. Will your evidence be ready in time — or will you be pulling files from inboxes and shared drives?

+
+ + +
+ +

Compliance lives in one person

+

When your compliance manager is sick, on leave, or moves on — does your college's regulatory knowledge go with them?

+
+ + +
+ +

Spreadsheets and guesswork

+

Trainer currency records in email. Checklists in shared drives. Registers in someone's desktop folder. This is not compliance management. This is compliance risk.

+
+ +
+ +
+

RTOSure was built for exactly this problem.

+
+
+
+ + + +
+
+
+ +

+ Built around the frameworks you're
actually regulated by. +

+

Not configured. Not adapted. Built in — from the regulatory text up.

+
+ +
+
+
RTOSure
+
Domestic RTOs
+
NVR Standards 2025
+

Full coverage of all 4 Quality Areas, 19 Standards, and 3 Compliance Requirement Divisions — including FPPR obligations.

+
    +
  • All 19 NVR Standards mapped
  • +
  • Compliance Requirements Divisions 1–3
  • +
  • Fit and Proper Person Requirements
  • +
  • Risk indicators built to Standard level
  • +
  • AVETMISS reporting compliance
  • +
+ Explore NVR compliance → +
+ +
+
CRICOSSure
+
CRICOS Providers
+
ESOS Act & National Code 2018
+

Complete coverage of the ESOS framework and all 11 National Code 2018 Standards for CRICOS-registered providers.

+
    +
  • All 11 National Code Standards
  • +
  • ESOS Act obligations
  • +
  • PRISMS reporting workflows
  • +
  • CoE management
  • +
  • Student welfare & support obligations
  • +
+ Explore CRICOS compliance → +
+ +
+
ELICOSSure
+
ELICOS Colleges
+
ELICOS Standards 2018
+

Purpose-built for English Language Intensive Courses for Overseas Students — Parts A through E, with course-type-specific compliance built in.

+
    +
  • Parts A–E fully mapped
  • +
  • GE, EAP, EHSP and IELTS Prep compliance
  • +
  • Teacher qualification tracking
  • +
  • Contact hours and class size compliance
  • +
  • Under-18 welfare obligations
  • +
+ Explore ELICOS compliance → +
+
+
+
+ + + +
+
+
+ +

+ Everything a compliance-managed RTO needs.
Nothing it doesn't. +

+

Six capabilities, each built around a compliance problem your team deals with every day.

+
+ +
+
+
01
+ +

Compliance Dashboard

+

Know your compliance status without asking anyone. A live dashboard maps every obligation across your registered frameworks — filter by Standard, Quality Area, or staff member.

+
+ +
+
02
+ +

Checklists & Workflows

+

Compliance tasks done correctly, every time, by anyone. Guided workflows walk your team through compliance tasks step by step — built around the specific Standards that apply to your college.

+
+ +
+
03
+ +

Forms & Quizzes

+

Evidence captured at the point it's created. Built-in forms and quizzes capture evidence directly against the relevant Standard — at the moment the activity happens. No manual filing.

+
+ +
+
04
+ +

Evidence Register

+

Your audit response starts here. Documents, policies, and evidence stored, mapped, and retrievable in the format auditors expect — linked to the exact Standard they support.

+
+ +
+
05
+ +

Monitoring & Alerts

+

Stop things falling through the cracks. Automated alerts for upcoming deadlines, expiring records, and compliance gaps — before they become audit findings.

+
+ +
+
06
+ +

Risk Indicators

+

Know your risk before ASQA does. Purpose-built risk indicator frameworks — mapped to NVR, ESOS, National Code, and ELICOS — give you structured visibility into compliance exposure.

+
+
+ +
+ See all features → +
+
+
+ + + +
+
+
+ +

Built by people who understand
the sector. Trusted by those who run it.

+
+
+
+
★★★★★
+

"We went into our ASQA audit with confidence for the first time. Everything the auditor asked for was already in RTOSure."

+
+ +
Compliance ManagerAustralian RTO, Victoria
+
+
+
+
★★★★★
+

"Our trainer currency records used to live in four different places. Now they're in one system, mapped to Standard 1.4. It took a week to set up and saves hours every month."

+
+ +
RTO DirectorCRICOS Provider, NSW
+
+
+
+
★★★★★
+

"We're a small RTO. We don't have a dedicated compliance team. RTOSure effectively gave us one."

+
+ +
Chief ExecutiveELICOS College, QLD
+
+
+
+
+

Customer case studies and verified outcomes are being finalised for launch. Quotes above are illustrative of the outcome language we are collecting from early adopters.

+
+
+
+ + + +
+
+
+
+
Already using TEAMS?
+

RTOSure connects directly with your TEAMS data.

+

Student enrolments, staff records, employer relationships and agent details flow through automatically — no double entry, no manual imports. Your existing data. Your new compliance system. Zero friction.

+
+ +
+
+
+ + + +
+
+
+ +

RTOSure covers all three.

+

Each compliance layer is purpose-mapped — not configured in. Choose the combination that matches your registration.

+
+
+
+
RTOSure
+
Domestic RTOs
+
NVR Standards 2025
+

ASQA audits, trainer currency, AVETMISS, FPPR compliance. The complete NVR Standards 2025 framework — mapped to your obligations from day one.

+ Explore RTOSure → +
+
+
CRICOSSure
+
CRICOS Providers
+
ESOS Act + National Code 2018
+

International student compliance, PRISMS reporting, CoE management, welfare obligations. Every ESOS and National Code requirement in one place.

+ Explore CRICOSSure → +
+
+
ELICOSSure
+
ELICOS Colleges
+
ELICOS Standards 2018
+

English Language course compliance, teacher qualifications, contact hours, under-18 welfare. Parts A–E of the ELICOS Standards — fully mapped and monitored.

+ Explore ELICOSSure → +
+
+
+ Many Australian colleges operate under two or all three frameworks simultaneously. RTOSure covers them all in one system — with clean, separate compliance layers for each regulatory obligation. +
+
+
+ + + +
+
+
+

Get started

+

Stop managing compliance in spreadsheets.
Start managing it in RTOSure.

+

Book a 30-minute demo and we'll show you RTOSure mapped to the frameworks your college actually operates under — NVR, ESOS, National Code, or ELICOS. No generic walkthrough. No hard sell.

+ +
+
30-minute session
+
Tailored to your frameworks
+
No commitment required
+
Australian-based team
+
+
+
+
+ + + + + + + + + diff --git a/integrations.html b/integrations.html new file mode 100644 index 0000000..cec85b8 --- /dev/null +++ b/integrations.html @@ -0,0 +1,255 @@ + + + + + + + TEAMS Integration — RTOSure + + + + + + + + + + +
+
+
+ Integrations +

Already using TEAMS?
RTOSure connects directly.

+

Student enrolments, staff records, employer relationships and agent details flow from TEAMS into RTOSure automatically — no double entry, no manual imports. Your existing data. Your new compliance system. Zero friction.

+
+
+
+ + +
+
+
+ +

Your TEAMS data.
Your RTOSure compliance layer.

+
+
+
+
Your data source
+
TEAMS
+
Students · Enrolments · Staff · Agents · Employers
+
+
+
+
Your compliance layer
+
RTOSure
+
NVR · ESOS · National Code · ELICOS
+
+
+ +
+
+ +

Student & enrolment data

+

Student records and enrolment data from TEAMS populate RTOSure's student compliance objects — attendance monitoring, CoE status, welfare obligations.

+
+
+ +

Staff records

+

Trainer and assessor records from TEAMS inform RTOSure's trainer currency registers, qualification tracking, and CPD monitoring.

+
+
+ +

Agents & employers

+

Agent and employer relationships from TEAMS populate the third-party compliance objects in RTOSure — monitoring obligations, agreements, and performance records.

+
+
+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/pricing.html b/pricing.html new file mode 100644 index 0000000..7311c38 --- /dev/null +++ b/pricing.html @@ -0,0 +1,295 @@ + + + + + + + Pricing — RTOSure + + + + + + + + + + +
+
+
+ Simple, transparent pricing +

Start with the framework
you need today.
Scale as you grow.

+

Three plans matched to three regulatory contexts. Upgrade or add frameworks at any time — no migration, no data loss. Pricing below is indicative for v1 planning; confirmed figures to be published at launch.

+
+
+
+ + +
+
+
+ + +
+
Domestic RTO
+
RTOSure
+
TBC / month
+

NVR Standards 2025 compliance management for ASQA-regulated RTOs. The complete compliance foundation for domestic providers.

+
    +
  • All 19 NVR Standards 2025 mapped
  • +
  • Compliance dashboard & reporting
  • +
  • Evidence register
  • +
  • Checklists & guided workflows
  • +
  • Risk indicators framework (180+)
  • +
  • Automated monitoring & alerts
  • +
  • TEAMS integration (optional)
  • +
+ Book a demo +
+ + + + + +
+
Complete compliance
+
All Frameworks
+
TBC / month
+

RTOSure + CRICOSSure + ELICOSSure. The only system that covers all three Australian regulatory frameworks in one place.

+
    +
  • Everything in RTOSure + CRICOSSure
  • +
  • ELICOS Standards 2018 — Parts A–E
  • +
  • Course-type specific ELICOS compliance
  • +
  • 56+ ELICOS risk indicators
  • +
  • Teacher qualification tracking
  • +
  • Under-18 welfare obligations
  • +
  • Priority support
  • +
+ Book a demo +
+ +
+ +

Pricing is indicative for planning purposes. Confirmed subscription figures and Enterprise pricing will be published at launch. Contact us for an early-access quote.

+
+
+ + +
+
+
+ +

Pricing FAQ

+
+
Can I start with one framework and add others later?
Yes. RTOSure, CRICOSSure, and ELICOSSure are separate modules. You can start with the framework relevant to your current registration and add modules at any time — no migration, no data loss, no re-setup required.
+
Do I need TEAMS to use RTOSure?
No. RTOSure is a standalone product and does not require TEAMS. The TEAMS integration is an optional add-on for existing RTO Software clients who want to eliminate double-entry of student, staff, and enrolment data.
+
What does onboarding involve?
Onboarding is guided by the RTOSure team. In your first week, we set up your compliance frameworks, import your scope of registration, and walk your team through the key workflows. Most colleges are operationally live within 5–7 business days.
+
Where is our data stored?
RTOSure data is hosted on Australian servers. We do not store or process compliance data offshore. Full details are available on our security page.
+
What contract length is required?
Annual subscriptions are the default. Month-to-month options are available — contact us to discuss. Enterprise and multi-campus arrangements are negotiated separately.
+
Is there a free trial?
We don't offer a self-serve free trial — because a compliance management system genuinely set up for your college is more useful than a blank sandbox. Instead, we offer a 30-minute live demo tailored to your frameworks. Book one here.
+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/privacy.html b/privacy.html new file mode 100644 index 0000000..0a6fb32 --- /dev/null +++ b/privacy.html @@ -0,0 +1,246 @@ + + + + + + + Privacy Policy — RTOSure + + + + + + + + + + +
+
+
+ Legal +

Privacy Policy

+

This Privacy Policy explains how RTO Software Pty Ltd (“we”, “us”, “our”) collects, uses, and handles personal information in connection with RTOSure and rtosure.com.au. It is prepared in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).

+

Last updated: [Date to be confirmed before launch] | Version 1.0

+
+
+
+ +
+
+
+ +
+

1. Who we are

+

[PLACEHOLDER — Company name, ABN, registered address, contact details for privacy enquiries. To be completed by legal counsel before launch.]

+
+ +
+

2. What information we collect

+

We collect personal information in connection with:

+
    +
  • — Demo bookings (name, organisation, email, framework information)
  • +
  • — Account creation and subscription management
  • +
  • — Product usage data for the RTOSure platform
  • +
  • — Support and customer service communications
  • +
  • — Website analytics (anonymised where possible)
  • +
+

[PLACEHOLDER — Full collection detail to be completed by legal counsel.]

+
+ +
+

3. How we use your information

+

[PLACEHOLDER — Use cases, legal basis, third-party sharing. To be completed by legal counsel before launch.]

+
+ +
+

4. Storage and security

+

Personal information collected through RTOSure is stored on Australian servers. We apply reasonable technical and organisational measures to protect your information from unauthorised access, disclosure, or loss. See our Security page for detail.

+
+ +
+

5. Your rights

+

Under the Privacy Act 1988, you have the right to access personal information we hold about you, and to request corrections where it is inaccurate. To make a request, contact us at privacy@rtosure.com.au.

+
+ +
+

6. Contact

+

Privacy enquiries: privacy@rtosure.com.au
For complaints unresolved after contacting us, you may contact the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

+
+ +

This is a v1 privacy policy draft for planning purposes. It must be reviewed and finalised by a qualified Australian privacy lawyer before RTOSure launches and collects any personal information.

+
+
+
+ + + + + + + \ No newline at end of file diff --git a/resources.html b/resources.html new file mode 100644 index 0000000..5fbd835 --- /dev/null +++ b/resources.html @@ -0,0 +1,286 @@ + + + + + + + Resources & Free Tools — RTOSure + + + + + + + + + + +
+
+
+ Free tools & resources +

Practical compliance resources.
No login required.

+

Free tools, guides, and templates for Australian RTO and college compliance teams. Use them to benchmark your current state, prepare for audit, or help your team understand their obligations.

+
+
+
+ + +
+
+
+ +

Start here — no account needed.

+
+
+
+
Free Tool
+
+

NVR Standards 2025 Self-Assessment

+

Rate your college's current compliance maturity against every NVR Standard. Takes 15 minutes. Generates a gap report you can act on immediately.

+ Start the assessment → +
+
+
+
Free Tool
+
+

CRICOS Compliance Gap Checker

+

Run a structured gap check across all 11 National Code 2018 Standards and key ESOS Act obligations. Identify your highest-risk areas before an audit does.

+ Start the gap check → +
+
+
+
Free Download
+
+

Trainer Currency Register Template

+

A structured register template for tracking trainer and assessor currency and competency against NVR Standard 1.4 requirements.

+ Download template → +
+
+
+
+
+ + +
+
+
+ +

Deep compliance content
for the Australian VET sector.

+
+
+
+
Guide
+
+

NVR Standards 2025 — Plain English Overview

+

What every NVR Standard actually requires, explained without the legalese. Quality Areas 1–4, Compliance Requirements, and FPPR in plain English.

+ Read the guide → +
+
+
+
Article
+
+

The Rules Behind the Rules — Compliance Requirements & FPPR

+

A deep dive into the Compliance Requirement Divisions and Fit and Proper Person Requirements — what they mean in practice for RTO governance.

+ Read the article → +
+
+
+
Coming soon
+
+

RTOSure vs Spreadsheets — Why Australian RTOs Are Moving On

+

A practical comparison of spreadsheet-based compliance management versus a purpose-built system. Addresses the most common objection before a demo call.

+ Coming soon +
+
+
+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/rtosure.html b/rtosure.html new file mode 100644 index 0000000..c9d8e76 --- /dev/null +++ b/rtosure.html @@ -0,0 +1,258 @@ + + + + + + + RTOSure — NVR Standards 2025 — RTOSure + + + + + + + + + + +
+
+
+ RTOSure — Domestic RTOs +

NVR Standards 2025.
Every Standard. Every obligation.
Mapped in.

+

All 4 Quality Areas, 19 Standards, 3 Compliance Requirement Divisions, and Fit and Proper Person Requirements — built into RTOSure from the regulatory text up. Not configured. Not templated. Built in.

+ +
+
+
+ + +
+
+
+ +

Complete NVR Standards 2025 coverage

+

Every Quality Area, Standard, and requirement — mapped to risk indicators, evidence requirements, and compliance workflows.

+
+
+

Quality Area 1 — Training & Assessment

Standards 1.1–1.7 covering training and assessment strategies, trainer qualifications, AQF outcomes, RPL, and student support.

+

Quality Area 2 — Governance & Operations

Standards 2.1–2.4 covering governance, financial viability, legal obligations, and registered scope management.

+

Quality Area 3 — Learner Engagement

Standards 3.1–3.4 covering learner support, access and equity, industry engagement, and learner records.

+

Quality Area 4 — Integrity

Standards 4.1–4.4 covering marketing accuracy, enrolment, fees, and third-party arrangements.

+

Compliance Requirements — Divisions 1–3

Information transparency, training product integrity, third-party arrangements, and fee protection obligations.

+

Fit & Proper Person Requirements

FPPR obligations for governing persons — background checks, declarations, ongoing monitoring, and record-keeping.

+
+
+
+ + +
+
+
+
+ +

180+ risk indicators.
Mapped to Standard level.

+

RTOSure's NVR Risk Indicators Framework covers six compliance object types — Units of Competency & Qualifications, Trainers & Assessors, Management & Governing Persons, Third Parties & Agents, Employers & Industry, and Students.

+

Each indicator is prioritised (Critical / High / Medium) and mapped to the specific NVR Standards it monitors. This is not a generic risk register — it is a purpose-built framework developed from the regulatory text of the NVR Standards 2025.

+ See the risk framework → +
+
+
180+
Risk indicators
+
19
Standards covered
+
6
Object types
+
4
Quality Areas
+
+
+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/security.html b/security.html new file mode 100644 index 0000000..4e4fe04 --- /dev/null +++ b/security.html @@ -0,0 +1,259 @@ + + + + + + + Security & Data — RTOSure + + + + + + + + + + +
+
+
+ Security & data +

Your compliance data.
Kept in Australia.
Kept secure.

+

RTOSure handles sensitive compliance data for Australian colleges — trainer records, student welfare files, audit evidence, governance documentation. We take that responsibility seriously.

+
+
+
+ + +
+
+
+ +

What we do to protect your data

+
+
+
+
+

Australian hosting

+

All RTOSure data is stored on Australian servers. We do not host or process compliance data offshore.

+
+
+
+

Encryption

+

Data encrypted in transit (TLS 1.2+) and at rest. Audit evidence, personal records, and governance documents are protected at every layer.

+
+
+
+

Access controls

+

Role-based access control means staff only see what they need to. Admins manage permissions. All access is logged.

+
+
+
+

Privacy Act compliant

+

RTOSure is designed to support compliance with the Australian Privacy Act 1988 and the Australian Privacy Principles.

+
+
+
+
+ + +
+
+

Security detail

+
Where is our data stored?
RTOSure data is hosted on Australian servers. [Specific hosting provider and region to be confirmed — e.g. AWS Sydney, Azure Australia East.] We do not store or process your compliance data offshore.
+
How is data encrypted?
All data in transit is encrypted using TLS 1.2 or higher. Data at rest is encrypted using AES-256. This includes all compliance documents, student records, trainer credentials, and governance files stored in your evidence register.
+
Who can access our data?
Access is controlled at the college level. Your nominated administrator manages user roles and permissions. RTOSure staff do not access your data without your explicit permission, except for the purposes of support and system maintenance (logged).
+
What happens to our data if we cancel?
On cancellation, you can export all your evidence, registers, and compliance records in standard formats before your account closes. Data is retained for [30 days / 90 days — to be confirmed] after cancellation, then permanently deleted.
+
Is RTOSure compliant with the Australian Privacy Act?
RTOSure is designed to support your obligations under the Privacy Act 1988 and the Australian Privacy Principles. Our Privacy Policy details how we collect, store, and handle personal information. [Link to privacy policy once published.]
+

Security detail is v1 — to be reviewed by technical team and legal counsel before launch.

+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file diff --git a/styles.css b/styles.css new file mode 100644 index 0000000..d23cf13 --- /dev/null +++ b/styles.css @@ -0,0 +1,353 @@ +/* ============================================================ + RTOSure Design System — styles.css + Version 1.0 | May 2026 + The single source of truth for all RTOSure web styles. + All pages must import this file. + ============================================================ */ + +/* ── Google Fonts ─────────────────────────────────────────── */ +@import url('https://fonts.googleapis.com/css2?family=DM+Serif+Display:ital@0;1&family=DM+Sans:ital,opsz,wght@0,9..40,300;0,9..40,400;0,9..40,500;0,9..40,600;0,9..40,700;1,9..40,300;1,9..40,400&display=swap'); + +/* ── Design Tokens ────────────────────────────────────────── */ +:root { + /* Brand colours */ + --color-navy: #0f2744; /* Primary — deep navy */ + --color-navy-mid: #1a3a62; /* Slightly lighter navy */ + --color-teal: #00a896; /* Primary accent */ + --color-teal-dark: #007a6e; /* Teal hover */ + --color-teal-light: #e6f7f5; /* Teal tint background */ + --color-teal-mid: #b3e8e2; /* Teal mid tone */ + + /* Sub-brand accent colours */ + --color-cricos: #2563eb; /* CRICOSSure blue */ + --color-cricos-light: #eff6ff; + --color-cricos-text: #60a5fa; /* CRICOSSure on dark backgrounds */ + --color-elicos: #7c3aed; /* ELICOSSure purple */ + --color-elicos-light: #f5f3ff; + --color-elicos-text: #a78bfa; /* ELICOSSure on dark backgrounds */ + + /* Semantic status colours */ + --color-amber: #f59e0b; /* Warning / due items */ + --color-amber-light: #fef3c7; + --color-green-success: #10b981; /* Compliant / complete */ + --color-green-light: #d1fae5; + + /* On-dark surface utilities */ + --color-on-dark-text: rgba(255,255,255,0.72); /* Body text on navy/dark */ + --color-on-dark-secondary: rgba(255,255,255,0.55); /* Secondary text on dark */ + --color-on-dark-muted: rgba(255,255,255,0.35); /* Muted / labels on dark */ + --color-on-dark-border: rgba(255,255,255,0.08); /* Borders on dark */ + --color-on-dark-surface: rgba(255,255,255,0.04); /* Subtle card bg on dark */ + --color-on-dark-surface-hover: rgba(255,255,255,0.07); + + /* Sub-brand on-dark tints (for dark bg hover states) */ + --color-teal-on-dark-bg: rgba(0,168,150,0.10); + --color-teal-on-dark-border: rgba(0,168,150,0.40); + --color-cricos-on-dark-bg: rgba(37,99,235,0.10); + --color-cricos-on-dark-border: rgba(37,99,235,0.40); + --color-elicos-on-dark-bg: rgba(124,58,237,0.10); + --color-elicos-on-dark-border: rgba(124,58,237,0.40); + + /* Neutral palette */ + --color-dark: #0d1b2a; /* Near black */ + --color-charcoal: #1e293b; /* Dark text */ + --color-slate: #475569; /* Secondary text */ + --color-muted: #94a3b8; /* Muted / labels */ + --color-border: #e2e8f0; /* Dividers */ + --color-surface: #f8fafc; /* Off-white panels */ + --color-white: #ffffff; + + /* Typography */ + --font-display: 'DM Serif Display', Georgia, serif; + --font-body: 'DM Sans', system-ui, sans-serif; + + /* Spacing scale */ + --space-xs: 4px; + --space-sm: 8px; + --space-md: 16px; + --space-lg: 24px; + --space-xl: 40px; + --space-2xl: 64px; + --space-3xl: 96px; + --space-4xl: 128px; + + /* Layout */ + --container: 1200px; + --radius-sm: 6px; + --radius-md: 10px; + --radius-lg: 16px; + --radius-xl: 24px; + + /* Shadows */ + --shadow-sm: 0 1px 3px rgba(0,0,0,.08), 0 1px 2px rgba(0,0,0,.06); + --shadow-md: 0 4px 16px rgba(15,39,68,.10), 0 2px 6px rgba(15,39,68,.06); + --shadow-lg: 0 12px 40px rgba(15,39,68,.14), 0 4px 12px rgba(15,39,68,.08); + --shadow-teal:0 4px 20px rgba(0,168,150,.25); + + /* Transitions */ + --ease: cubic-bezier(.4,0,.2,1); + --duration: 200ms; +} + +/* ── Reset & Base ─────────────────────────────────────────── */ +*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; } + +html { + scroll-behavior: smooth; + -webkit-text-size-adjust: 100%; +} + +body { + font-family: var(--font-body); + font-size: 17px; + line-height: 1.65; + color: var(--color-charcoal); + background: var(--color-white); + -webkit-font-smoothing: antialiased; +} + +img, svg { display: block; max-width: 100%; } +a { color: inherit; text-decoration: none; } +ul, ol { list-style: none; } +button { font-family: inherit; cursor: pointer; border: none; background: none; } +input, textarea, select { font-family: inherit; } + +/* ── Container ────────────────────────────────────────────── */ +.container { + width: 100%; + max-width: var(--container); + margin-inline: auto; + padding-inline: var(--space-xl); +} + +@media (max-width: 768px) { + .container { padding-inline: var(--space-md); } +} + +/* ── Typography Scale ─────────────────────────────────────── */ +.display-xl { + font-family: var(--font-display); + font-size: clamp(42px, 5.5vw, 72px); + line-height: 1.08; + letter-spacing: -0.02em; + color: var(--color-navy); +} + +.display-lg { + font-family: var(--font-display); + font-size: clamp(34px, 4vw, 54px); + line-height: 1.1; + letter-spacing: -0.02em; + color: var(--color-navy); +} + +.display-md { + font-family: var(--font-display); + font-size: clamp(26px, 3vw, 40px); + line-height: 1.15; + letter-spacing: -0.01em; + color: var(--color-navy); +} + +h1, h2, h3, h4, h5, h6 { + font-family: var(--font-body); + font-weight: 600; + line-height: 1.25; + color: var(--color-navy); +} + +h1 { font-size: clamp(32px, 3.5vw, 44px); } +h2 { font-size: clamp(28px, 2.5vw, 34px); } +h3 { font-size: clamp(22px, 2vw, 24px); } +h4 { font-size: 18px; } +h5 { font-size: 15px; text-transform: uppercase; letter-spacing: 0.08em; font-weight: 600; } + +p { line-height: 1.7; } + +.text-lead { + font-size: clamp(17px, 1.8vw, 20px); + line-height: 1.6; + color: var(--color-slate); + font-weight: 400; +} + +.text-sm { font-size: 14px; } +.text-xs { font-size: 12px; letter-spacing: 0.04em; } + +.text-teal { color: var(--color-teal); } +.text-navy { color: var(--color-navy); } +.text-slate { color: var(--color-slate); } +.text-muted { color: var(--color-muted); } +.text-white { color: var(--color-white); } + +.label { + font-size: 12px; + font-weight: 600; + text-transform: uppercase; + letter-spacing: 0.1em; + color: var(--color-teal); +} + +/* ── Buttons ──────────────────────────────────────────────── */ +.btn { + display: inline-flex; + align-items: center; + gap: var(--space-sm); + padding: 14px 28px; + border-radius: 8px; + font-size: 15px; + font-weight: 600; + font-family: var(--font-body); + transition: all var(--duration) var(--ease); + white-space: nowrap; + line-height: 1; + cursor: pointer; +} + +.btn-primary { + background: var(--color-teal); + color: var(--color-white); + box-shadow: var(--shadow-teal); +} +.btn-primary:hover { + background: var(--color-teal-dark); + transform: translateY(-1px); + box-shadow: 0 6px 24px rgba(0,168,150,.35); +} + +.btn-outline { + background: transparent; + color: var(--color-navy); + border: 1.5px solid var(--color-navy); +} +.btn-outline:hover { + background: var(--color-navy); + color: var(--color-white); +} + +.btn-outline-white { + background: transparent; + color: var(--color-white); + border: 1.5px solid rgba(255,255,255,0.5); +} +.btn-outline-white:hover { + background: rgba(255,255,255,0.1); + border-color: var(--color-white); +} + +.btn-ghost { + background: transparent; + color: var(--color-teal); + padding: 14px 0; + gap: var(--space-xs); +} +.btn-ghost:hover { gap: 10px; } + +.btn-lg { padding: 17px 34px; font-size: 16px; } +.btn-sm { padding: 10px 20px; font-size: 13px; } + +/* ── Section utilities ────────────────────────────────────── */ +.section { padding-block: var(--space-3xl); } +.section-sm { padding-block: var(--space-2xl); } +.section-lg { padding-block: var(--space-4xl); } + +.section-label { + display: inline-block; + font-size: 12px; + font-weight: 700; + text-transform: uppercase; + letter-spacing: 0.12em; + color: var(--color-teal); + margin-bottom: var(--space-md); +} + +.section-heading { + font-family: var(--font-display); + font-size: clamp(28px, 3.5vw, 46px); + line-height: 1.1; + letter-spacing: -0.02em; + color: var(--color-navy); + margin-bottom: var(--space-md); +} + +.section-subheading { + font-size: clamp(16px, 1.6vw, 19px); + line-height: 1.65; + color: var(--color-slate); + max-width: 640px; +} + +.centered { text-align: center; } +.centered .section-subheading { margin-inline: auto; } + +/* ── Cards ────────────────────────────────────────────────── */ +.card { + background: var(--color-white); + border: 1px solid var(--color-border); + border-radius: var(--radius-lg); + padding: var(--space-xl); + box-shadow: var(--shadow-sm); + transition: box-shadow var(--duration) var(--ease), transform var(--duration) var(--ease); +} +.card:hover { + box-shadow: var(--shadow-md); + transform: translateY(-2px); +} + +/* ── Divider ──────────────────────────────────────────────── */ +.divider { + width: 48px; + height: 3px; + background: var(--color-teal); + border-radius: 2px; + margin-block: var(--space-lg); +} +.divider.centered { margin-inline: auto; } + +/* ── Badge / Tag ──────────────────────────────────────────── */ +.badge { + display: inline-flex; + align-items: center; + gap: 6px; + padding: 4px 12px; + border-radius: 100px; + font-size: 12px; + font-weight: 600; +} +.badge-teal { background: var(--color-teal-light); color: var(--color-teal-dark); } +.badge-navy { background: rgba(15,39,68,.08); color: var(--color-navy); } +.badge-cricos { background: var(--color-cricos-light); color: var(--color-cricos); } +.badge-elicos { background: var(--color-elicos-light); color: var(--color-elicos); } + +/* ── Responsive grid helpers ─────────────────────────────── */ +.grid-2 { display: grid; grid-template-columns: repeat(2, 1fr); gap: var(--space-xl); } +.grid-3 { display: grid; grid-template-columns: repeat(3, 1fr); gap: var(--space-xl); } +.grid-4 { display: grid; grid-template-columns: repeat(4, 1fr); gap: var(--space-xl); } + +@media (max-width: 1024px) { + .grid-4 { grid-template-columns: repeat(2, 1fr); } + .grid-3 { grid-template-columns: repeat(2, 1fr); } +} +@media (max-width: 640px) { + .grid-2, .grid-3, .grid-4 { grid-template-columns: 1fr; } + .section { padding-block: var(--space-2xl); } + .section-lg { padding-block: var(--space-3xl); } +} + +/* ── Utility ──────────────────────────────────────────────── */ +.mt-sm { margin-top: var(--space-sm); } +.mt-md { margin-top: var(--space-md); } +.mt-lg { margin-top: var(--space-lg); } +.mt-xl { margin-top: var(--space-xl); } +.mb-md { margin-bottom: var(--space-md); } +.mb-lg { margin-bottom: var(--space-lg); } +.mb-xl { margin-bottom: var(--space-xl); } +.gap-sm { gap: var(--space-sm); } +.gap-md { gap: var(--space-md); } +.flex { display: flex; } +.flex-center { display: flex; align-items: center; } +.flex-between { display: flex; align-items: center; justify-content: space-between; } +.font-semibold { font-weight: 600; } +.font-bold { font-weight: 700; } +.italic { font-style: italic; } +.sr-only { position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0,0,0,0); } diff --git a/terms.html b/terms.html new file mode 100644 index 0000000..d20bb4f --- /dev/null +++ b/terms.html @@ -0,0 +1,218 @@ + + + + + + + Terms of Service — RTOSure + + + + + + + + + + +
+
+
+ Legal +

Terms of Service

+

These Terms of Service govern your use of RTOSure and the services provided by RTO Software Pty Ltd. By subscribing to or using RTOSure, you agree to these terms.

+

Last updated: [Date to be confirmed before launch] | Version 1.0

+
+
+
+ +
+
+
+ ⚠ Placeholder document +

This Terms of Service document is a structural placeholder for v1 planning. The final Terms of Service must be drafted and reviewed by a qualified Australian commercial lawyer before RTOSure launches and accepts any paid subscriptions. Key items to address: subscription terms, permitted use, data ownership, liability limitations, Australian Consumer Law compliance, and termination conditions.

+
+ +
+

1. The service

[PLACEHOLDER — description of RTOSure, service tiers, access terms. To be drafted by legal counsel.]

+

2. Your account

[PLACEHOLDER — account setup, user responsibilities, authorised users, security obligations.]

+

3. Subscriptions and fees

[PLACEHOLDER — billing, renewal, pricing changes, refund policy in accordance with Australian Consumer Law.]

+

4. Acceptable use

[PLACEHOLDER — permitted use, prohibited use, compliance with applicable law.]

+

5. Your data

You retain ownership of all data you upload to RTOSure. We use it solely to provide the service and as described in our Privacy Policy. We do not sell or share your data with third parties for commercial purposes. See our Security page for data handling detail.

+

6. Limitation of liability

[PLACEHOLDER — liability cap, exclusions, Australian Consumer Law guarantees. To be drafted by legal counsel.]

+

7. Governing law

These Terms are governed by the laws of [State/Territory to be confirmed]. Disputes will be resolved in the courts of [jurisdiction]. Nothing in these Terms limits rights you may have under the Australian Consumer Law.

+
+
+
+ + + + + + + \ No newline at end of file diff --git a/tools.html b/tools.html new file mode 100644 index 0000000..3229113 --- /dev/null +++ b/tools.html @@ -0,0 +1,256 @@ + + + + + + + Free Compliance Tools — RTOSure + + + + + + + + + + +
+
+
+ Free compliance tools +

Assess your compliance
before the auditor does.

+

Structured self-assessment tools built on the same frameworks that power RTOSure. Use them standalone, or use them to understand exactly where RTOSure would make the biggest difference for your college.

+
+
+
+ + +
+
+
+
+
+ NVR Standards 2025 +

NVR Self-Assessment Tool

+

Rate your current compliance maturity against every NVR Standard 2025. The tool uses the same risk indicator framework built into RTOSure — structured across Quality Areas 1–4, Compliance Requirements, and FPPR obligations.

+
    +
  • Covers all 19 NVR Standards
  • +
  • Takes approximately 15–20 minutes
  • +
  • Generates a downloadable gap report
  • +
  • No account required — email to receive your report
  • +
+ Start the NVR self-assessment → +

[Tool to be embedded or linked — currently placeholder]

+
+
Tool embed placeholder — NVR self-assessment widget or gated landing
+
+
+ +
+
+
Tool embed placeholder — CRICOS gap checker widget or gated landing
+
+ National Code 2018 & ESOS +

CRICOS Compliance Gap Checker

+

A structured gap check across all 11 National Code 2018 Standards and key ESOS Act obligations. No equivalent tool exists freely in the Australian market — this is the one.

+
    +
  • Covers all 11 National Code Standards
  • +
  • Includes key ESOS Act obligations
  • +
  • Identifies highest-risk areas by priority
  • +
  • Email-gated — receive a full gap report
  • +
+ Start the CRICOS gap checker → +
+
+
+
+
+ + +
+
+
+
+

See RTOSure in action.

+

30 minutes. Tailored to your framework. No hard sell.

+
+ +
+
+
+ + + + + + + \ No newline at end of file