BUILT & BUILDING / 01

Traceable Metrics

A dashboard where every number opens up. Click a cost and keep going: category, vendor, the ledger entries, the invoice, the change order, the field event that started it, and who signed off.

STATUS
Working build
DATA
Illustrative
INDUSTRY
Construction
BUILT IN
ICARUS
The drill-through, start to finish. About fifty seconds, no sound.

WHY IT MATTERS

  • The question is always "where did this come from?" Owners, lenders and auditors ask it. Today the answer is a person, a spreadsheet and an afternoon.
  • The number and the proof live in the same place. Every level reconciles to the one above it, so the detail can't quietly drift from the total.
  • Explanations come from records, not prose. When a number moves, the system shows what moved it. No AI-written summary to second-guess.
  • Missing is a state, not a blank. If an approval doesn't exist, the screen says so. That's usually the most useful thing on it.
The short version.

The walkthrough

ILLUSTRATIVE DEMO DATA Projects, vendors, people and amounts are invented, and every screen says so. These are captures of the working software, not mock-ups. Orange outlines mark what to look at.

Start at the number
01Start at the numberEvery figure on the project overview is a versioned metric with a written definition behind it. Open Actual costs to see what it's made of.
Break it down
02Break it downThe total splits by cost category. The green bar confirms the pieces add back up to the number you clicked.
Down to the records
03Down to the recordsThree clicks in: the actual ledger entries, with cost code, period, and when each one was recorded.
Follow the chain
04Follow the chainEach entry links to its invoice, the subcontract it was charged against, the change order that amended it, and the field event that caused the change.
Who approved it
05Who approved itEvery approval shows who decided, when they decided, and when it was entered. The documents and field photos are attached.
Three clocks
06Three clocksWhen it happened, when it was recorded, and when a document first described it. This change order was decided October 12 and entered October 15. Both dates are kept.
Ask why it changed
07Ask why it changedWhy did electrical commitments rise $80,000? The answer is assembled from the source records, not written by AI: the driver, the change order, the field event, in the order they happened.
Gaps are stated, not filled
08Gaps are stated, not filledAn invoice posted to cost with no approval on record. The screen says so plainly. Nothing is guessed or filled in to make it look complete.
Access is enforced, and disclosed
09Access is enforced, and disclosedViewed as a subcontractor, records outside their access fold into one restricted line. The total still reconciles, and the screen says the detail is incomplete.
Pin it, prove it later
10Pin it, prove it laterA snapshot keeps the value, the exact records behind it, and the formula version. Verify recomputes it, so last month's number can be reproduced on demand.

WHAT THIS PROVES

Traceable records: every reported number reconciles to its source records, approvals, documents and timing.

Built

  • The drill-through, lineage, three clocks, explain-change, exceptions, restricted view and snapshots all run in the real software.
  • Captured on an illustrative construction project, against a test data store.

Not yet

  • Not yet connected to a live accounting or project-management system.
  • Runs on seeded demonstration data, not a customer's books.

Got a number nobody can explain? Let's trace it.

ASK FOR A WALKTHROUGH

Thirty minutes, on a screen share or at your office in Dallas.
Or write to bluedottechnology [at] outlook [dot] com