Frequently asked questions

What it is, what it does, and what it does not do.

What OutcomeReady is

Is this clinical software?
No. OutcomeReady is documentation and evidence enablement software. It structures existing support activity into clearer, more consistent evidence. It does not provide clinical assessments, diagnoses, or treatment recommendations.
Does this replace clinicians or support workers?
No. Clinicians and support workers remain the authority. OutcomeReady helps structure what they already do into clearer documentation. Human sign-off is required before any sensitive external output.
What is OutcomeReady actually?
It is the evidence layer between support delivered and funding recognised. It turns session notes, observations, and daily activity into structured, goal-linked evidence that holds up in claims, plan reviews, and audits.
What is Thriving Kids?
Thriving Kids is the flagship cohort pathway within OutcomeReady, designed for children with disability or developmental delay. It connects home, school, and support settings into one continuous evidence loop — capturing daily progress, not just session outcomes.

Claims and plan reviews

How does this help with rejected claims?
OutcomeReady pre-checks documentation against common rejection triggers before submission — missing fields, pricing mismatches, unsupported service lines. It also tracks rejection patterns so you can identify and fix systemic issues.
How does it improve plan reviews?
Instead of rebuilding the evidence story each time, OutcomeReady accumulates goal-linked progress over time. When a review comes around, the pack is mostly ready — structured, measurable, and clearly linked to goals.
Can it guarantee funding outcomes?
No. OutcomeReady improves documentation quality and evidence continuity. It does not guarantee claim acceptance or plan approval. Funding decisions are made by NDIA or plan managers.

Data, consent, and privacy

What data is stored?
Participant and provider data is stored in a secure, RLS-protected database (Supabase, hosted in Australia). Each organisation sees only their own data. No cross-tenant visibility.
How is consent handled?
Consent is captured at the participant or family level before data collection begins. Participants can request data removal. Consent records are maintained with timestamps and version history.
Is data used for anything else?
No. Participant data is not used for advertising, model training, or any purpose outside direct service delivery and evidence generation for the relevant provider.

Deployment and integration

Can this work with our current systems?
OutcomeReady is designed to sit alongside existing tools — not replace them. It ingests notes and records, produces structured outputs, and can export to common formats. Full integration depends on your stack.
How long does onboarding take?
The 30-day pilot gets you to working output in week 2. Full onboarding for ongoing subscriptions takes 2–4 weeks depending on organisation size and complexity.
What does the pilot include?
10 claim packets reviewed and restructured, 2 full plan review packs, rejection and leakage analysis, provider-specific templates, 1 staff training session, and an outcomes summary report.

The continuous system

What is the continuous support layer?
This is OutcomeOS — the autonomous infrastructure layer that runs signals, pattern detection, risk surfacing, and evidence generation in the background. It is what makes OutcomeReady more than a documentation tool. It works between sessions, not just during them.
Does it work without staff doing extra work?
That is the goal. Once configured, the system captures signals, builds evidence, and flags issues automatically. Staff input shapes it, but the system does not depend on staff memory or manual documentation to function.
Still have questions?
We are happy to talk through your specific context before you commit to anything.
Get in Touch