surehand
Deployments

Three kinds of work we run.

Claims that need sorting. Invoices that need matching. Questions that need a cited answer. Different work, same controls.

All three run on Gatehouse, the software we built and operate.

The three cases

W/01Composite caseInsurance

Every claim checked before a handler opens it.

The problem

Every file had to be checked for completeness before a handler could start.

What changed

The first pass runs around the clock. Every routing decision carries its reason.

Controls used
  • E/02 Runtime enforcement
  • A/04 Approvals
W/02Composite caseDistribution

The real mismatches, found. The small ones, cleared.

The problem

Real mismatches got lost among the small differences.

What changed

Clean invoices go through as ERP drafts. Every exception shows its sources.

Controls used
  • S/05 Spend controls
  • R/03 Record
W/03Composite caseInternal operations

Every answer cites its clause. Or a person answers.

The problem

The same easy questions every day. The hard ones waited behind them.

What changed

People only get answers the library backs up. Every correction becomes a worked example.

Controls used
  • L/06 Least privilege
  • A/04 Approvals
Same five gates

Same checks, same order, all three.

What changes is the scope, the role, the limits and who approves. Read a row across to see one gate on all three.

GateW/01 · InsuranceClaims triageW/02 · DistributionInvoice matchingW/03 · Internal operationsPolicy answers
01SCOPERead the intake channels · write to the intake queue onlyRead the AP inbox, purchase orders and goods receipts · write ERP drafts and match resultsPolicy library, read-only · answers with a cited clause
02ROLEClassify and route · never decide or reject a claimMatch and draft · never post a final paymentAnswer policy questions · never act outside the policy library
03LIMITSA spend limit on each run, set in the signed manifestA spend limit on each run, checked before the actionA spend limit on each run, set in the signed manifest
04REVIEWwhere it stops for a personLow-confidence files held for a named claims handlerOver the limit, outside tolerance or a changed bank detail → the AP lead, by nameBelow the confidence threshold → named support lead
05SEALEach routing decision in the audit trail, with its reasonEach match, draft and hold in the audit trail, with its sourcesEach answer with its clause in the audit trail
How we write these

Real work. No names.

01

What a composite case is

Each case draws on more than one engagement. Names and figures are changed, anonymised by agreement. No case names a customer. Each one is labelled.

02

The short version

Each write-up names the Gatehouse parts it uses, and each part has its own page. The seven parts

Start here

Bring us the queue nobody wants.

Tell us what comes in, who handles it and where it breaks. A person replies, usually inside two business days.

support@surehand.io