SureThink/Product/Pillar 01
Pillar 01 · Drop Zone intake
Intake is one door today, and it is the one your team already uses: the client emails the statements, and you drag them onto the account. Each file is fingerprinted on arrival and typed and read in the background — a file the model isn’t sure of waits for you to confirm it, rather than guessing.
Four moves. The first and the last are a person’s; the two in between run in the background while you get on with something else.
Drag the client’s files onto the account’s Files tab — PDF, Excel or Word, up to 50 MB each. The upload is recorded under your name by the database itself, the moment it lands.
No broker portal to roll out. No naming convention to enforce.
The Classifier types each file from the same 31 surety document types your team picks from — balance sheets, work-on-hand schedules, engineer’s estimates, indemnity agreements. Below the confidence you set, a person confirms it.
A type a person set is never overwritten by the model.
The Extractor lifts the figures with a confidence on each and the page it came from, and the account’s health profile updates from them. Low-confidence reads are marked, not smoothed over.
Every figure stays one click from its source page.
Start case on the account: choose a live, published pipeline and the bond. The case reads every document on file — no picking attachments, no uploading twice.
Already running on that bond? It says so, and opens the existing case.
Classification & evidence
The taxonomy is surety’s own, not “invoice, receipt, other”. And the original is kept exactly as it arrived, so everything downstream can point back to it.
5 files · 31 pages · added by P. Nair
✓ 4 typed from the taxonomy
✓ 1 sent to a person to confirm
✓ 5 fingerprinted · SHA-256
Sample account. Calder Land Group is a fictional demo company.
Completeness
Each pipeline carries a checklist of the documents a file must hold. A case missing one stops with the list of what’s missing — so nobody opens a file that was never going to be decidable.
A checklist per pipeline
The documents a file must hold are set in the pipeline editor, by type. The Completeness Gate checks them before any analysis runs.
The ask is tracked
Data Request records what is outstanding and who is chasing it. Today the assignee sends the request; an upload link for the broker is coming.
No starting over
Missing documents park the task. Uploading a document does not resume the case on its own; an assignee resolves the task before the workflow continues.
The other end
Cases that need a person arrive in My List, grouped by tray and most urgent first, with the reason they stopped written on the row.
Authority on every row
Above your signing limit, Approve steps aside for Refer up — and the case goes to someone whose authority covers it.
Nothing unowned
A case that is waiting sits in a named tray with an SLA on it, so “pending” always means pending on somebody, for a known time.
Why, not just what
Refer, hold, review, clear — and the sentence that caused it. You know what the case needs before you open it.
What’s next
Drop Zone is the way in today. The rest are designed and scheduled, not shipped — listed so you can plan a pilot around what exists.
We mark these honestly. One is live and the rest are not built yet — and we would rather you knew that before a pilot than after one.
Start with one workflow
Thirty minutes. Drop one real file — redacted however you need — onto a demo account, watch it get typed, read and fingerprinted, then start a case on it.