Working proofs
Section 03
See the work move.
Complicated technology is easier to understand when you can watch a familiar workflow change. Each example below runs in your browser, at your pace.
Names and data are anonymized or simulated. Nothing here contains client information. Examples are labeled so it is clear what has been built and tested and what is an interactive concept.
Built tool / anonymized
Document reconciliation
Before
Someone opens two versions of the same fund report and compares them line by line, hoping not to miss a change.
Result
Turns a multi-report comparison into a focused list of changes that need human review.
Could adapt to
Grant reporting, monthly close packets, vendor statements, or any recurring report where only the differences matter.
Awaiting comparison.
Completed
- General · Febmatched
- Restricted · Janmatched
- Grant A · Marmatched
- Nothing matched yet.
Review queue
- Restricted · Aprno ledger entry
- Capital · Aprno ledger entry
- ,
Discrepancy report ready
2 items for human review, with fund, period and prior balance attached.
Two snapshots of the same fund report, taken a month apart. Nothing is compared yet.
Built tool / anonymized
Payroll preparation
Before
A scanned timecard packet gets retyped by hand every pay period, with handwritten notes interpreted on the fly.
Result
Reduces retyping while keeping flagged items in front of a human reviewer.
Could adapt to
Field service tickets, delivery logs, shop-floor production counts, or any paper form that becomes a spreadsheet.
Incoming document
Timecard page 1
Timecard page 2
Timecard page 3
3 pages, unread.
Calculation workbook
| Employee | Reg | Adj | OT | Flag |
|---|---|---|---|---|
| Employee 014 | , | , | , | , |
| Employee 021 | , | , | , | , |
| Employee 038 | , | , | , | , |
| Employee 042 | , | , | , | , |
| Employee 057 | , | , | , | , |
A multi-page timecard PDF arrives the way it always does: scanned, stapled, partly handwritten.
Prototype / interactive concept
Inventory and location management
Before
Stock is technically counted somewhere, but finding a specific item means asking the person who put it away.
Result
Know what you have, exactly where it is, and preserve custody when containers move.
Could adapt to
Parts rooms, tool cribs, sample storage, event equipment, or anywhere containers get relocated.
Receiving
Shelf 3
- Empty
Back room
Shelf 1
Open shelf space
Location › Shelf › Bin › Contents. The bin is the unit of custody.
Activity log
- No events recorded.
Nothing is in the bin yet. Scanning an item records what it is and exactly where it went.
Prototype / interactive concept
RFID-triggered workflow
Before
A physical action happens, then three digital steps depend on somebody remembering to do them.
Result
One simple physical action can reliably trigger several digital follow-through steps.
Could adapt to
Equipment checkout, gated access points, laundry or linen cycles, calibration returns, or asset transfers.
Physical
Idle. Waiting for a tap.
Digital follow-through
RFID tag tapped
Reader at the door, 09:14
Event logged
Asset 8841, reader R-02
System record updated
Status: checked out
Right person notified
Routed by asset owner
Follow-up task created
Return check in 3 days
Audit trail completed
Who, what, where, when
A tag and a reader. Physically, all anyone does is hold a badge or asset near the reader.
Interactive compliance concept
Controlled-medication tracking
Before
Custody lives on a clipboard, and variances get discovered during audit prep instead of the day they happen.
Result
Clearer custody, faster exception detection, and less manual audit preparation.
Could adapt to
Clinics, veterinary practices, school health offices, or any setting with counted, dated, secured stock.
Representative workflow only. A final implementation requires validation against the organization's applicable policies and regulations.
- 01
Lot received
Lot 22-118, qty 40, two witnesses recorded
- 02
Secure storage assigned
Cabinet 2, drawer B, access by role
- 03
Dispense recorded
Qty 2 administered, time and signer captured
- 04
Count reconciled
Expected 38, counted 37
- 05
Exception surfaced
Count variance of 1, plus a lot expiring in 21 days
- 06
Chain-of-custody log
Every event, in order, ready for review
Current state
- Lot
- 22-118 (simulated)
- Storage
- Unassigned
- Expected count
- 40
- Counted
- ,
- Variance
- ,
- Expiry
- ,
A simulated controlled-medication lot arrives. Nothing is recorded yet.
Our process
From Compass to a working solution
Before
Technology decisions get made before anyone has watched the work, so the tool arrives before the understanding.
Result
A recommendation grounded in evidence, and when it makes sense, the narrowest fix that solves it.
Could adapt to
Any workflow you can describe out loud but have never seen drawn end to end.
- 01
Observe a normal day
EvidenceShadowed intake, two handoffs, one workaround nobody had mentioned.
- 02
Map the real workflow
Evidence11 steps, 3 systems, 2 places the same data is typed twice.
- 03
Identify friction
EvidenceDelay at approval, duplicate entry at billing, no visibility after handoff.
- 04
Prioritize by effort and relief
EvidenceOne small change removes the duplicate entry. The rest can wait.
- 05
Build the narrowest responsible fix
EvidenceA single shared form and one automatic notification. Nothing more.
- 06
Test with real work
EvidenceTwo weeks of live jobs, with the old process still available.
- 07
Train and refine
EvidenceTwo adjustments after week one, then it stays out of the way.
Compass starts by watching the work happen, not by asking what software you want.
Recognize one of these?
If any of these workflows looked familiar, that is the conversation worth having. Tell us where the work gets stuck and we will tell you honestly whether we can help.