For Australian RTOs · Standards 2.7 & 2.8

Never miss a complaint.Prove it to ASQA.

Compleo reads your RTO's inbox and builds your complaints and appeals register as the emails arrive — so the record exists before the auditor asks for it.

  • Read-only access to Gmail, Outlook or IMAP
  • We never send email on your behalf
  • Australian-owned and operated · Export everything, leave any time

No signup · Ten sample emails · One complaint hiding in them

from: karen.mitchell@gmail.comTue 14:32

RE: Question about my course

Following up on my last two emails about my assessment. Still nothing back — I'm starting to get pretty frustrated.

from: ops@hartleycivil.com.auTue 15:07

Re: Apprentice sign-off

That's the second time this month the trainer's cancelled on our apprentices. We can't keep losing site days.

from: d.nguyen04@gmail.comTue 16:41

RPL outcome

Thanks for sending my result through. Is there any way to have the decision looked at again?

Assessment handling — Karen Mitchell

reg-0142 · due 26/08/2026

Complaint

Trainer cancellations — Hartley Civil (employer)

reg-0143 · due 26/08/2026

Complaint

RPL decision review — Dana Nguyen

reg-0144 · due 09/09/2026

Appeal

Filed before anyone had to remember to.

Reads from
Gmail / Google WorkspaceOutlook / Microsoft 365Any IMAP inboxread-only, always

The problem isn't that RTOs ignore complaints. It's that most of them never look like complaints.

They arrive as "just checking on my assessment", a reply-all from an employer, a frustrated third email in a thread. Under the 2025 Standards you need to capture those, act within a reasonable timeframe, document the outcome, and show ASQA the trend analysis. Most RTOs assemble that register from memory the week before an audit. Compleo assembles it as the emails come in.

Complaints, appeals & compliance events

The register ASQA asks for, kept for you.

Every complaint, appeal and compliance event in one place, with status, owner, due date and outcome. Most entries are created from email automatically; anything else — a phone call, a conversation in the corridor — you add in a minute. Every change is logged, so the audit trail is a by-product of doing the work, not a separate job.

  • Complaints and appeals tracked from receipt to outcome, mapped to Standards 2.7 and 2.8
  • Response-due dates with overdue alerts — "reasonable timeframe" measured, not remembered
  • One-click export of the register, response times and trend analysis when the auditor asks
Compliance Register
export csv
  • Assessment handling — Karen Mitchell

    complaint · reg-0142 · due 26/08/2026

    Acknowledged
  • Refund dispute — employer, BSB50420

    complaint · reg-0139 · 3 days overdue

    Overdue
  • Appeal — assessment outcome, CHC33021

    appeal · reg-0137 · independent review offered

    Resolved
full audit trail · who did what, whenstandards 2.7 / 2.8
enquiries@yourrto.edu.auread-only
  • Enrolment for Cert IV in Business

    Can you send me the start dates for…

    enrolment
  • RE: Question about my course

    …really disappointed with how this has been handled

    complaint ↗
  • Invoice #2044 — payment plan

    Following up on the instalment we discussed…

    payment
flagged → filed in the register · staff keep working in Outlook or Gmail

How entries get there

Read from the inbox your RTO already uses.

Connect a shared mailbox with read-only access. Compleo reads incoming mail, recognises what matters for compliance — a complaint that doesn't call itself one, a withdrawal with a deadline, a third frustrated email in a thread — and files it against the register with the original email attached. Staff still handle mail in Outlook or Gmail; nothing changes for them.

  • RTO-specific categories: enrolment, withdrawal, complaint, assessment, certificate, payment, USI
  • Flags escalating tone and deadlines across a whole thread, not just single messages
  • Never sends email on your behalf — draft replies are suggestions your staff review

One-click "Log as complaint" is also built into our Outlook and Gmail add-ins — see the full feature list.

Built for Standards 2.7 & 2.8

The ASQA Practice Guide on Feedback, Complaints and Appeals outlines what RTOs must demonstrate. Here's how Compleo helps.

Standard 2.7 — Complaints Management

Capture informal complaints — AI detects complaint language even when it's buried in other correspondence

Reasonable timeframes — Response due dates with overdue alerts ensure nothing ages without action

Document outcomes — Full outcome tracking with notes, corrective actions, and resolution status

Continuous improvement — Trend analysis shows patterns across complaints to inform process changes

Standard 2.8 — Appeals Management

Track appeals — Dedicated appeals tracking with full documentation of the appeal process

Procedural fairness — Complete record of all communications and decisions for transparency

Reasonable timeframes — SLA tracking ensures appeals are actioned within specified periods

Independent review — Document escalation to external parties when internal resolution fails

AI You Can Trust

Powerful intelligence with full human control.

Read-Only Email Access

Compleo reads and analyses your emails. It never sends emails on your behalf. You review suggestions and decide what action to take. Full control, always.

You Review Before Sending

Draft replies are suggestions only. You review, edit, and approve every response before it goes to students. The AI assists; you decide.

Built for Australian RTOs

Designed with ASQA requirements in mind. RTO-specific categories, Standards 2.7 & 2.8 alignment, and compliance documentation that auditors expect.

Secure & Private

Your RTO data is protected with industry-standard security. Configurable retention policies. Full compliance with Australian privacy laws.

D

Why I built Compleo

I'm Dylan, and Compleo is built in Australia by me — not a product team, not an offshore agency.

The same thing kept happening at the RTOs I saw: a complaint would surface at audit that three people had read in email months earlier. Nobody had ignored it. It just never made it from the inbox to the register, because that step was a human remembering to do it on a busy Tuesday.

The tools on the market either wanted the RTO to change how it worked, or gave it another form to fill in. I wanted the register to fill itself in from the way RTOs already work — which is email.

What that means for you

  • You deal with me directly — onboarding, support, and the "is this actually a complaint?" questions. My details are on the contact page.
  • I'm onboarding a small group of founding RTOs at founder pricing — five places. In return I want your honest feedback and, if it earns it, a reference.
  • I never send email from your accounts, and you can export everything and leave at any time. I'd rather you trust the product than be locked into it.

Dylan

Founder, Compleo Pty Ltd

dylan@compleo.com.au

Interactive demo · No signup

See what's hiding in a real RTO inbox.

Ten sample emails. One is a complaint under Standard 2.7. See whether you'd have caught it — then see what Compleo does with it.

Real RTO email scenarios · Talk to us when you're ready