Construction · weekly

Budget vs actual, before the overrun lands

Drop in a job-cost export; get back budget vs actual/committed with variance and % spent per cost code, rolled up by category, plus projected over/under at completion.

Drop in

job cost lines (JSON or CSV)

Required columns
cost_codedescriptioncategorybudget_usdactual_cost_usdcommitted_cost_usd

Optional: min_budget_usd (0 = all), project_label

Get back

  • cost_line_items register
  • by_category summary
  • total_variance_usd
  • projected_variance_usd
  • total_overrun_usd

Cost overruns caught — computed from your data

Sample outputs
total_overrun_usd
projected_variance_usd
overall_pct_spent

These fields appear in the XLSX/PDF artifact after a run on your own data.

How it runs

What every run guarantees

Deterministic

Byte-identical replay, 100% across 10,200+ controlled runs.

Fast

Compiled logic runs in seconds. Batches process at 25,000+ rows/sec.

Confirmed

A named human confirms the compiled logic once — the model is out of the loop on every run.

Auditable

Every artifact is SHA-256 content-addressed and hash-linked.

Usage-based

You pay per run, not per seat.

Output: XLSX / PDFTTV: 1 actionDeliverable (tier B)Inputs: 6

Run it on your file

10 free runs. No credit card. No setup. Drop in your export and get the register back in seconds.

Already have an account? Sign in →