Measuremeasurement, BoQ and elemental estimating
AAQS elemental cost planning and trade-measured bills of quantities, both versioned, both linked, and both able to start from your practice's own structures.
Two documents, never conflated
The elemental estimate and the trade bill are separate documents with separate structures, and QSNAPP keeps them that way — while letting an element component point at the BoQ items that justify it.
Bill of Estimates
bill → section → element → component
Elemental cost planning on AAQS element names. Components carry compositions and named constants, so a rate is derived rather than typed twice.
Bill of Quantities
bill → section → item
The trade-measured document. Items carry units, quantities, rates, locations and constants — the bill that goes out to tender and is valued against later.
The estimate
is more than a total
Thirteen screens over one estimation version — preliminaries, contingencies, escalation and professional fees each resolve against the same elemental breakdown, and roll into total project cost, cash flow and return on investment.
- Version control
- Overview
- Elemental Breakdown
- Preliminaries
- Contingencies
- Escalation
- Professional Fees
- Total Project Cost
- Cash Flow
- Return on Investment
- Rates
- Notes
- Settings
Professional fees include ASAQS stage apportionment, with per-consultant fees split across the work stages.
Estimates and bills are versioned
Both the elemental estimate and the bill of quantities are scoped to a version. Creating a new one clones the whole structure — sections, elements, components, items, locations and constants — so an earlier version stays exactly as it was priced.
Elements link to the items behind them
An elemental component can be linked to the BoQ items that make it up. The estimate shows the linked items, and each one deep-links straight to its place in the bill.
House standards live at the practice, not the project
The organisation library holds the structures and mappings every job starts from, so a new project inherits the practice's way of working instead of the last project's copy of it.
Elemental structures
House standard element trees once, then start a project estimate from one instead of a blank bill.
BoQ structures
Standard trade bill structures, kept at organisation level and cloned into the project that needs them.
Unit maps
How imported unit strings resolve to the units your bills actually use.
Currency maps
Currency handling defined for the organisation rather than re-decided per project.
Font maps
Weight and style per bill element type, so every bill in the practice reads the same way.
Bring the WinQS bill across
An import job reads a WinQS library and produces estimation and quantities versions marked with where they came from. Item locations and named constants come with the items, and measurement expressions are kept readable rather than flattened to a number.
One import, every downstream document
The same import path produces elemental bills, bills of quantities, tender rounds, valuations, variation orders and final accounts — so contract history arrives with the bill rather than after it.
Measure once, price everywhere
Measure is priced per active seat, on its own or in the Bundle with Stages and Manage.