Build n BloomFit Call
Fit Note
- What we saw
- What you told us
- What we think might be true
- What we do not know
- One useful next step
Written byBuild n Bloom
To keep whether or not you proceed.
NDIS providers
Keep the useful systems. Keep responsibility visible.
Our newer work changes nothing about what we owe current NDIS clients. Existing agreements are honoured as written. The rest of this site describes newer work for other markets; none of it rewrites a commitment made to you.
New NDIS work is considered one bounded workflow at a time, with an accountable owner and a human decision before anything consequential moves.
Book a Fit Call
A 25-minute call. No files, no homework. A written note either way.
Existing clients: use your established support path, or the contact page.
What continues, what is considered, what stays with people
Existing clients: delivery remains supported.
Current client commitments, installed workflows and agreed support paths continue under their existing scope and terms.
New enquiries: selective fit review.
New NDIS work is considered only where the workflow is bounded, owned and safe to operate with named human review.
Non-delegable: people keep authority.
Participant decisions, clinical judgement, incident determinations, compliance sign-off and service responsibility remain with authorised people.
Duty of care cannot be automated away
Preparation and coordination can move faster. The useful boundary is not an AI agent for NDIS. It is a specific recurring job where evidence, exceptions and review can be designed into the operating path.
Structured intake.
Capture complete information, identify missing fields and route the record to the right accountable person.
Boundary: no autonomous incident or safeguarding determination.
Evidence preparation.
Recover applicable policies, records and source material so reviewers can inspect what supports the prepared work.
Boundary: no unsourced compliance assertion.
Operational coordination.
Make routine handoffs, exceptions, reminders and writeback visible without hiding ownership inside an automation.
Boundary: no release without the named control.
Measured improvement.
Baseline the current workflow and test cycle time, rework, completeness and exception handling after installation.
Boundary: no guaranteed external or regulatory outcome.
What counts as proof
A demo is a mechanism. A client record is proof. A promise is neither.
Every prospective system must distinguish what is demonstrated, what is modelled, what has been verified in delivery and what remains unproven for that provider. Fit, baseline, control design and acceptance are established for the provider and the workflow before any implementation claim is made.
Continuity is governed by the actual engagement. Existing scope, support, acceptance criteria and obligations remain the authority for current delivery, not a newly written page.
Everything NDIS lives here
These pages stay public because providers still use them. Each one says plainly whether it shows a working mechanism, a demonstration on sample data, or guidance, and none of them changes any client agreement.
- Existing NDIS services.
The retained NDIS page.
- NDIS mechanism library.
Mechanism write-ups on sample data, not client results.
- Compliance Agent overview.
System page.
- Referral outreach system.
System page.
- Referral Agent.
System page.
- Coordinator dependency assessment.
Assessment.
- NDIS AI readiness assessment.
Assessment.
- NDIS compliance checklist.
Guidance.
- Partners.
Start with the boundary, not the tool
For a new NDIS workflow, the Fit Call tests ownership, consequence, data sensitivity, human review and whether a safer ordinary automation would be enough. Twenty-five minutes with a founder, free, and a written note either way.
Existing clients should use their established support path, or the contact page.