Quick Claim Submission on SharePoint
Quick Claim Submission, built by TechRam on SharePoint, replaces a form filled at the end of a shift and emailed to three inboxes. It is phone-first, with plan and participant lookups and validation at the point of capture, landing in one queue with an owner and a state. Failed claims route to a human rather than disappearing.
- Case & Claims Management
- NDIS & Disability
The problem it replaces
A form filled at the end of a shift, sent to three inboxes, with errors surfacing weeks later at reconciliation.
What it does
A phone-first form with plan and participant lookups, validated at capture, landing in one queue with an owner and a state. Failed claims route to a human rather than disappearing.
Under the hood
- Power Apps canvas app
- SharePoint list as the claim queue
- Power Automate for routing, retries and exception handling
Proof: Achieve Australia
Achieve Australia processed NDIS claim notifications by hand: opening every email, identifying its type, matching it to one of four geographic clusters and routing it to an admin. TechRam built Azure Functions that do all of it, with a weekly audit report, inside Azure's free monthly grant.
9
notification types identified and routed without a human
4
geographic clusters matched from the subject line
Zero
notifications opened by hand to triage them
Common questions
01. Do we need new licences for the app?
It is built inside the Microsoft 365 tenant you already pay for, and we do not resell licences or earn a margin on them. Where something genuinely is not covered we say so before you commit, not after.
02. Can a support worker submit from a phone?
It is phone-first, with plan and participant lookups and validation at the point of capture. What it replaces is a form filled at the end of a shift and sent to three inboxes.
03. What happens to a claim that fails?
It routes to a human rather than disappearing. Errors surfacing weeks later at reconciliation is the failure this is built to remove.
04. Can our own team change quick claim submission later?
Yes, and that is why it is built on SharePoint and Power Automate rather than in code. We hand over the documentation and the access, and anyone who can edit a list can add a field.
05. How long does quick claim submission take to build?
Weeks rather than months for something this size. The scope is agreed in writing first, and the number does not move afterwards because the work turned out harder than we expected.