← All guides
Evidence stored on our servers · EU or US region
Where your data lives. Claims stores evidence and notices on our servers so the office and the field share one tamper-evident record. You choose the storage region (EU or US) when you create the project, and it is fixed there unless you request a move. Everything is held under an append-only, hash-chained audit trail.
Claims is the Prove step of Construction. It takes the evidence your team captures on site and helps the office build a grounded, defensible notice — every sentence traceable to a piece of evidence — then carries it through approval and dispatch to a verifiable claim pack. The tool assembles and checks; the people decide and sign.
Stage 1 of 5 · On site
Capture evidence
Site staff record what happened, sealed and timed, the moment it matters.
What you see
- A Site Evidence screen: photo, note, delay event or weather
- An optional link to a plan activity or section
- Optional location capture
What you do
- Capture a photo or write a note describing the event
- Link it to the activity it affects
- Submit — it queues and syncs if you're offline
What you get
- Each item sealed with a content fingerprint and a device timestamp
- A durable offline queue so nothing is lost on a bad signal
- Capture needs only a field seat
Stage 2 of 5 · Office
Evidence register
Everything captured, gathered into one reviewable register.
What you see
- Captured evidence grouped by activity and claim head
- Photos on a signed, time-limited link
- A flag where the device time and server time differ
What you do
- Review the register and open the photos
- Group the evidence behind the heads you're claiming
- Publish the activity list field staff link their evidence to
What you get
- A single, consolidated view of the evidence base
- Integrity checks surfaced, not hidden
- A clean foundation for the notice
Stage 3 of 5 · Office
Assemble the notice
A grounded draft built from your evidence — never invented.
What you see
- A drafted notice assembled from the grouped evidence
- One-to-one provenance: each claim line maps to its evidence
- A regulatory notice framing the document
What you do
- Read the drafted sections against the evidence
- Edit the wording where you need to
- Save it ready for approval
What you get
- A notice where every sentence is traceable to a source
- A grounding check that catches anything not in the evidence
- A document that stands up to scrutiny
Heads up. The tool assembles and checks against your evidence; it does not invent facts or decide your claim. The wording and the decision stay with you.
Stage 4 of 5 · Office
Approve and dispatch
An ordered sign-off, with the one moment data leaves made explicit.
What you see
- An approval chain with ordered approvers
- Approve, request changes, or resubmit
- A dispatch consent step
What you do
- Submit the notice to the approvers you choose
- Approvers approve or send it back with a reason
- On full approval, confirm dispatch at the consent prompt
What you get
- Dispatch is blocked until every approval is in
- A clear, logged consent at the point data leaves
- Reminders chase pending approvers so nothing stalls
Stage 5 of 5 · Office
Claim pack
A single, verifiable export of the whole claim.
What you see
- A claim-pack download
- Evidence, notices and the full audit trail together
- A chain-verification result
What you do
- Generate the claim pack for the project
- Check the chain verifies
- Hand it over with confidence
What you get
- A self-contained, tamper-evident record of the claim
- Proof the audit chain is intact
- One file that tells the whole story
Data residency
Claims is a deliberate, disclosed exception to Stratbridge's on-device model: to let the office and the field share one tamper-evident record, evidence and notices are stored on our servers. You choose the storage region — European Union or United States — when you create the project, with the data-processing terms shown and accepted up front. The region is fixed for that project unless you ask to change it.
Moving a project's evidence between regions is a supported, assisted migration — copy, verify, then securely erase the old copy — not an instant switch. Request it from Add-ons & Storage; our team reviews and schedules it, then confirms with you. Everything throughout is held under an append-only, hash-chained audit trail, and only the workspace owner can request a region change.