W/01Composite case
Claims triage at a regional TPA.
- Runtime enforcement
- Approvals
- The problem
- Incoming claims needed first-pass document checks, sorting and routing.
- The outcome
- The first pass now runs around the clock.
Claims triage, invoice matching and policy answers. Full write-ups are on the Surehand site.
Three composite cases
Each case in brief.
Case details
How each case was built.
Each case is a composite, with names and figures changed. Filter by capability, or open a row to see its simulated screen.
W/01Composite case
W/01, Claims triage at a regional TPA.
- The problem:Incoming claims needed first-pass document checks, sorting and routing. Opens the simulated screen for W/01 below.
- What was built:Low-confidence files wait for a named claims handler, with the evidence gathered. The manifest lets only a person reject a claim. Opens the simulated screen for W/01 below.
- What the record showed:Each routing decision is saved in the audit trail with its reason. Opens the simulated screen for W/01 below.
- The outcome:The first pass now runs around the clock. Opens the simulated screen for W/01 below.
The setupAn agent runs first-pass document checks, then sorts and routes incoming claims around the clock, under a signed manifest.
manifest signed · around the clock
held low-confidence file
rule only a person can reject
route named claims handler
evidence gathered
record routing decision · reason in trail
Simulated screen. insurance · runtime enforcement · approvals.
The full write-up is on the Surehand site.
Read the W/01 case studyW/02Composite case
W/02, Invoice matching for a distributor.
- The problem:Invoices needed a three-way match, under a spend limit. Opens the simulated screen for W/02 below.
- What was built:Matches the agent is sure of post to the ERP as drafts under a spend limit. Some invoices go to the AP lead by name before anything is final. These are amounts over the limit, lines outside tolerance and changed supplier bank details. Restarting a held run counts as an approval and is logged as one. Opens the simulated screen for W/02 below.
- What the record showed:Each run lists its spend limit. Each exception shows its sources and the AP lead's decision. Opens the simulated screen for W/02 below.
- The outcome:Clear invoices go through as ERP drafts, and each exception shows its sources. Opens the simulated screen for W/02 below.
The setupAn agent runs three-way matching under a spend limit. Matches it is sure of post to the ERP as drafts, and each exception shows its sources.
match three-way · confident · ERP draft
held supplier bank detail changed
rule spend limit · per run
route AP lead · by name
resume logged as an approval
record exception · sources listed
Simulated screen. distribution · spend controls · record.
The full write-up is on the Surehand site.
Read the W/02 case studyW/03Composite case
W/03, Policy answers with named escalation.
- The problem:Policy questions needed answers, with least-privilege access to the policy library. Opens the simulated screen for W/03 below.
- What was built:Each answer cites the clause it comes from. Below the confidence threshold, the question goes to a named support lead. Opens the simulated screen for W/03 below.
- What the record showed:Each answer links to its clause. Corrections are saved as labelled examples. Opens the simulated screen for W/03 below.
- The outcome:People only get answers the system can back up. Opens the simulated screen for W/03 below.
The setupAn agent answers policy questions and cites the clause each answer comes from. It has least-privilege access to the policy library.
access least privilege · policy library
answer cited · clause
held below confidence threshold
route support lead · by name
record clause cited per answer
feedback correction · labelled example
Simulated screen. internal operations · least privilege · approvals.
The full write-up is on the Surehand site.
Read the W/03 case studyAbout the cases
How we write up client work.
The cases show which capabilities each deployment used. Client names stay private.
A case built from more than one client engagement, then anonymised by agreement. No customer data appears on this site.
On the Surehand site. Each case above links to its own write-up.
All three write-ups on the Surehand siteThe team behind Gatehouse
Tell us your process.We'll walk you through it.
Book a walkthrough
Surehand built Gatehouse and runs its client deployments on it. For a written study of one of your own processes, book a teardown with Surehand.