Append-only rows keyed on job and snapshot time, carrying the job info, the estimate, the customer total, material total, dimensions and contact fields, plus the source of the snapshot. Bulk archiving is throttled to five concurrent writes. Writes are fire-and-forget and never block the user-visible sync.
Also called: job history · estimate snapshot · deleted in SmartBuild · long term retention
- 1Sync, Send Estimate or Start Project triggers an archive write.
- 2The job info and estimate are JSON-normalised to strip non-serialisable fields.
- 3A row is inserted with the current timestamp — never updated in place.
- 4Bulk archiving batches at five concurrent writes.
The module states the two purposes: 'Drives long-term retention regardless of SmartBuild deletions, and provides a clean training corpus for AI insight features. Never updated in place — only inserted into. The (job_id, snapshot_at) primary key means each Sync produces a new row, building a time series the platform can mine later.' Failures are silent by design: 'Archive writes are background telemetry... the user-visible operation already succeeded by the time we get here.'
- Estimator history was lost when upstream records were deleted or edited.
- There was no time series of how a job's numbers evolved.
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 →