Quick Fix
BoQ software keeps yelling about a missing preamble? In your 2025-compliant editor, hop into document properties, click the “Preliminaries & Preamble” tab, check “Include standard preambles,” and save. Most packages will auto-fill the clauses for you.
What’s Happening
A bill of quantities preamble is basically the rulebook that kicks off every construction project. It lays out the contractual, technical, and procedural rules before anyone starts pricing or swinging hammers. Don’t confuse it with the “Whereas” clauses you’ll find in a contract. The preamble usually covers:
- Why the project exists and what it’s supposed to achieve
- Plain-English definitions of every term used in the BoQ
- Where to find the contract documents (drawings, specs, standards)
- How measurements work and what provisional sums are allowed
- Any weird little conditions that might mess with pricing
Step-by-Step Solution
Here’s the exact click-by-click for the big three BoQ packages in 2026:
| Software | Menu Path | Action |
|---|---|---|
| CostX 2026.2 | Document → BoQ Properties → Preliminaries & Preamble | Tick the “Standard preambles” box, then glance through the auto-generated clauses—edit anything that looks off. |
| Bluebeam Revu 2026 | Tools → Quantity Tools → BoQ → Preamble | Grab the preamble text block from the template library and drop it in. |
| Buildsoft Cube 2026.1 | Settings → Project Settings → Preliminaries and Preamble | Pick the right standard (NRM 2 2024, MMHW 2021, etc.) and double-check your unit prices. |
Once you’re done editing, hit the built-in validator—F7 in CostX, “Validate BoQ” in Cube, or “Check Compliance” in Revu—to catch any missing mandatory clauses flagged by the standard method of measurement.
If This Didn’t Work
Still getting the red flag? Try these three fallback moves:
- Manual import: Grab the latest preamble template from your professional body (RICS, AIQS, or CIQS) as a .docx, copy the text, and paste it into the software’s text box. Save it as a reusable snippet so you don’t have to do this again.
- API patch: If your firm runs a cloud BoQ API (e.g., Procore BoQ v3.4.1), push an update via POST /api/v3/preamble with the JSON payload containing the preamble object ID—just make sure the response code comes back 200.
- Consultant review: If the BoQ still gets rejected, fire off an email to the quantity surveyor who issued the tender. Include the exact clause number and wording from your standard (NRM 2 clause 2.6 as of 2024) and ask for confirmation.
Prevention Tips
Want to stop preamble headaches before they start? Build these habits into your workflow:
- Template library: Keep a shared OneDrive folder stocked with current preambles aligned to NRM 2 (2024), MMHW (2021), and ASMM (2023). Update them every year—no excuses.
- Validation rule: In your BoQ software, set a project-level rule that flags any BoQ missing the “Preamble” section before you export. The rule triggers once you hit 95 % completion, so you’ll catch it before it’s too late.
- Contract synch: After you sign the contract, run a quick diff between the signed contract’s recitals and the BoQ preamble. Terminology mismatches have sparked disputes in 18 % of cases reported to the RICS in 2025, so don’t skip this step.
