Estimate activity log

A date-and-time-stamped record of every estimate event on a job — versions created, links sent, opens, approvals, intake, contract, signatures — so 'was this approved at that amount?' is answered by a log, not by memory.

What it is

A timeline derived from the version, link and contract records rather than a second event store. Customer-facing milestones render bold; internal edits render quieter. It carries status chips for opened, approved and signed, and names who did what — including the SmartBuild-side edits with their pre-markup figures marked as internal.

Also called: audit trail · history of this quote · was it approved at that amount · who changed what

See it
Estimate activity log
Prepared for
Sutter Kline
1140 Ridge Line Rd · Fair Play
Shell package$36,530
Concrete & site$10,606
Doors & windows$7,070
Trim & finish$4,714
Total
$58,920
Signature
EstimateActivityModal — dark tracking-bar header with a live dot and Opened/Approved/Signed chips over a diamond-bulleted timeline with timestamps. Sample data — no customer information appears here.
How it works
  1. 1Versions, links, contracts and approval unlocks are fetched together and merged into one chronological list.
  2. 2Each event is written in plain English with its amount: 'APPROVED — customer locked link #2 at $48,814.00'.
  3. 3Every unlock for revision earns a bold line because it explains any edits that follow an approval.
  4. 4Works for both engines — keyed by job id for SmartBuild estimates and by design id for in-house ones.
Why we built it

Was this approved at that amount? The answer came from memory, or from a search through somebody's inbox, usually while the customer was on the phone. Every estimate event on a job is now a date-and-time-stamped line — versions created, links sent, opens, approvals, intake, contract, signatures — with the name of whoever did each one. It is derived from records that already carry those timestamps rather than written into a new log, which means full back-history for every existing job from day one and no second record to drift out of step with the first.

The problem
  • Disputes settled from memory
  • No authorship on estimate changes
  • History starting the day the feature shipped
Sound familiar?
What you get
Full back-history for every existing job from day one
Every amount in the log is the amount that was live at that moment
Post-approval edits are explained by the unlock line above them
What's inside

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →