Bills of quantities

A bill that survives contact with the project

Divisions, sections and locations to hang the lines on, a lifecycle to get them approved, and the arithmetic done where you can see it.

Build it either way

From the library when the element exists, by hand when it doesn't.

Pull priced elements straight from the element library, or write a line from scratch.
Every line sits in a division — that is mandatory, so nothing ends up in an unnamed bucket.
Sections organise the bill under those divisions, and are renamed, reordered and deleted as the scope moves.
Each project carries its own location tree, so quantities read per floor, per room, or per whatever the project is divided into.
Dimensions can be entered and read in imperial units where the project calls for it.

A bill arrives as a spreadsheet and leaves as one.

Import from Excel or CSV, with the file checked before anything is written.
Export the bill back to Excel or CSV at any point.
Move, delete and reorder lines in bulk instead of one at a time.
Choose which columns you look at, and group the table by division, section or location.
Totals by location sit beside the bill rather than being rebuilt afterwards in another file.

The bill is not what gets approved. The lines are.

Every line walks the same chain: draft, internal review, internally approved, sent to client, client approved.
The PM can request changes internally, or pull back a line the client is already looking at.
The client can send a line back for changes; the creator reworks it and puts it in again.
A line's badge is its phase — one state, not a pair of statuses that can disagree with each other.
Move a whole selection through a phase at once, with a preview of exactly what will move and what will not.

Markup, contingency and VAT are settings, not spreadsheet formulas someone has to trust.

Each line carries a budget rate and a client rate — what it costs you, and what it is billed at.
Markup ladders are configured for the organisation and overridden per project.
Contingency and VAT are applied from the totals bar and shown as part of the total, not buried in it.
A rate already agreed with a vendor can be applied to a line directly.
The totals bar keeps a running figure as the bill changes underneath it.
An element's cost is split back onto the line, so a line built from the library still shows where its number came from.

The bill is where procurement starts.

A client-approved line is marked ready for procurement, and only those lines can enter an RFQ.
Each line keeps its own version history — what changed, when, and by whom.
Each line carries an activity timeline alongside that history.
Lines link back to the drawings that price them, in both directions.

Access is by invitation. Tell us about the studio and we'll set you up.