Skip to content

Budgets and BOQ

Turn the approved construction budget into a living control baseline

A baseline should remain visible after the project changes. Import cost codes through CSV, enter budget lines in the product, and route later budget changes through governed revisions. Native BOQ or budget-file import is planned, not live.

Where control breaks

Recognise the warning signs

  • The baseline is overwritten
  • Cost-code files contain duplicates or invalid hierarchy
  • Budget changes have no approval trail

The CostGrid control path

01

Basic cost-code CSV setup

Paste simple comma-separated cost-code rows before manually entering and approving the project budget. Quoted-field and hierarchy validation, and BOQ import, are not included.

02

Original and approved

Preserve the original baseline while showing approved budget changes separately.

03

Current version view

Review one budget version and its approval metadata at a time. Side-by-side diffs and explicit submitter/approver columns are planned.

Operational outcome

Every later cost decision has a stable, approved plan to compare against.

Control one live project before expanding

Start with one live project, keep the control trail intact, and expand only after the workflow proves useful.