Work/OrbitForm
OrbitForm, where a form becomes a record, a document and a signature
A forms and e-signature platform for NDIS providers. Most tools stop at Submit. OrbitForm starts there: it scores every response, writes the documents, files the record in the care platform, and sends it for a sealed signature.
- Client
- NexOrbit
- Industry
- Government-funded careNDIS
- Role
- UX Engineering / Product Design
- Services
- Product designService designUX and UI designDesign systemFront-end build
- Timeline
- 2026
- Status
- Live
Build, collect, process, review
Most form tools stop at Submit
For a disability provider, Submit is where the work starts. A referral has to become a client record. An incident has to reach the right person today. An agreement has to be signed before support can begin, and all of it has to stand up years later, in an audit. OrbitForm was designed around that gap.
- 01
Answers were typed twice
A referral arrives in a form tool, then somebody copies it into the care system by hand. Two records, two chances to get it wrong.
- 02
Agreements sat unfiled
Signed agreements stayed in inboxes, so the participant record was not updated and the service could not start.
- 03
Risk waited in an inbox
A serious incident looks the same as a feedback note until someone opens it.
- 04
Audits meant rebuilding the past
Evidence was gathered after the fact, from inboxes and folders, weeks before a review.
What was designed
- ForNDIS providers in AustraliaIntake coordinators, compliance leads and support workers
- CoversForms, submissions and signingOne tool from the first question to the sealed agreement
- PlatformsA studio for staff, phone forms for everyone elseForms keep working with no connection
- IntelligenceFive scores on every responseRules first, with an AI reading on top
- SigningOrbitSign, built inIdentity checks, sealed documents and a signing certificate
- Built inAbout four weeksDesigned and built, then launched with a provider
From a link to a signed agreement
The same journey seen from three sides: what the person filling the form does, what OrbitForm does for them, and what the provider gets back. It moves on by itself, and stops while you read.
- 01The linkNo account
- The person
- A link, a QR code or a personal link arrives, by email or text.
- OrbitForm
- The form opens on any phone, with no sign-up and nothing to install.
- The provider
- The view is counted once per visitor, so the numbers mean something.
- 02Filling it inSaves itself
- The person
- Questions come one at a time, and only the ones that apply.
- OrbitForm
- Every keystroke is saved, and the form keeps working with no signal.
- The provider
- The drop-off report shows the question where people stop.
- 03SubmitOne press
- The person
- One press, and a copy of the answers by email if the form offers it.
- OrbitForm
- The response is verified and stored, and six jobs are queued at once.
- The provider
- The bell rings the moment it lands.
- 04ScoredReasons, not guesses
- The person
- Nothing more to do.
- OrbitForm
- Rules score risk, compliance, evidence and confidence, then the AI reads it.
- The provider
- Every point shows the answer it came from.
- 05FiledNever retyped
- The person
- Nothing more to do.
- OrbitForm
- The documents are written and the record is created in the care platform.
- The provider
- A referral, client, incident or agreement, already in the right place.
- 06ReviewedCorrected in place
- The person
- Nothing more to do.
- OrbitForm
- Correcting an answer rescores the response and keeps the old version.
- The provider
- Mark reviewed, edit, or send it for signature without leaving the drawer.
- 07SignedSealed
- The person
- Identity is checked, consent is given, and the signature is typed or drawn.
- OrbitForm
- The content is hashed, the document sealed and timestamped, the certificate issued.
- The provider
- If an answer changed after sending, the envelope stops itself.
- 08Support startsThe point of it all
- The person
- The signed copy arrives.
- OrbitForm
- Signing fires the routing job.
- The provider
- The agreement is live in the care platform, and the service can begin.
Building a form should take minutes, not a meeting
A coordinator can describe the form in a sentence and let it be drafted, start from one of the NDIS templates, open a blank canvas, or photograph the paper form they already use and have it rebuilt. Forty-three field types cover the real work: costed line items, NDIS catalogue prices, a body chart to draw on, booking slots, consents and signatures.





Forms people can actually finish
Most people meet this product on a phone, in a kitchen or a car, often at a hard moment. The form asks one thing at a time, saves from the first keystroke, and can be picked up later from a private link. Out of range, it keeps working: the answers, and a signature drawn on the screen, wait on the device and send themselves when the signal comes back. Nobody has to make an account.




Six jobs run the moment a response lands
This is the part competitors leave to the team. A response is scored, the right people are told, the documents are written, and the record is created in the care platform. Staff can watch each job run in the response. Every five minutes a sweep picks up anything that failed and tries it again.
- 01ScoringThe rules run, then the AI reads the response
- 02Team alertThe right people are emailed straight away
- 03AutomationsThe team's rules run and signed webhooks go out
- 04Copy to the participantTheir answers, as a PDF, if the form asks for it
- 05DocumentsPDF, Word or Excel, attached to the response
- 06RoutingA referral, client, incident or agreement in the care platform
Rules first, AI second
Where vulnerable people are involved, a score has to be explainable. Every point traces back to a specific answer, and the reason sits beside the number. Claude then reads the whole response the way an intake coordinator would, and writes a short summary, a suggested next step and up to four concerns. It can raise risk by up to thirty points, never lower it, and it cannot clear a flag or close anything. The rule-only scores are kept separately, so its influence is always visible. If it is unavailable, the rules simply stand.
- 01
Completion
How much of the form was answered, with required questions counting double.
- 02
Risk
Points from the rules the team wrote, banded so attention goes where it is needed.
- 03
Compliance
Starts at 100 and drops for a missing consent, declaration or signature.
- 04
Evidence
Falls when a required signature or attachment is not there.
- 05
Confidence
Falls as required answers go missing, so a thin response is never read as a full one.
One inbox, and everything about a response in one place
The dashboard opens on what needs you today, not on a chart. In a response, staff see the answers, the scores with their reasons, the documents, the signature status and the jobs that have run, and can correct an answer, which rescores it, or send it for signature without leaving the drawer. Analytics only counts what it can prove: unique views, completion, time to fill, and the question where people stop.



Everything it handles
One tool covers the whole of it, from drafting a form to starting a service.
Twenty-eight everyday jobs, from drafting a form to starting a service
Signing data, not just documents
An e-signature tool knows where the boxes are, but not what is in them. OrbitSign reads the document, finds every place that needs a signature, pairs it with its date, and works out who should sign it from seven roles, following the NDIS supported decision-making model. When the last person signs, the agreement is filed and goes live in the care platform, and the service can start.
Consent, recorded
Signing opens with a versioned electronic records consent, naming the Electronic Transactions Act 1999.
Identity, checked
An email link, an access code or an SMS code before anyone signs. Codes are stored only as hashes.
Documents that fail closed
Content is hashed when it is sent and checked again before each signature. If an answer changed, the envelope stops itself.
A trail nobody can edit
Signing events are hash-chained, and the audit log is written by the database. Even an administrator cannot alter it.
Separated by organisation
Every table is row-level secured, so a workspace only sees its own data. The platform console shows counts, never details.
Versioned forever
Each publish freezes a version, and every response stays tied to the exact version it was filled in on.
What the provider gets back
Nobody spends an hour retyping a referral. Agreements reach the right file on their own, incidents are seen the same day, and the audit evidence is already collected because it was captured as the work happened. Legal wording, identity, consent, confidentiality and the record all live in one tool, so there is no gap between them for something to fall through.
- 43field types, in five groups
- 6jobs run after every submit
- 5scores on every response
- 0 to 30risk points the AI can add, never subtract
- 7signer roles recognised
- 5 minsafety sweep for anything stuck
Live, with a provider running on it end to end
Designed and built in about four weeks, and now in daily use by an NDIS provider, from the first referral through to the signed agreement. The public site claims only what the product does today, and that was a design decision as much as a marketing one.
