Translate specification requirements into priced work, supporting obligations and visible clarifications instead of treating the specification as background reading.
- The specification contains cost without containing quantities
- Control the document basis
- Build a requirements register
- Read by work package
- Translate requirements into pricing actions
- Reconcile the specification with drawings and schedules
- Treat performance requirements carefully
- Carry uncertainty visibly
- Issue a traceable pricing scope
- How Quotify supports specification review
A drawing may show a wall. The specification can determine what that wall costs.
It may define the board type, insulation, fire performance, acoustic requirement, framing, fixings, joint treatment, samples, testing and workmanship standard.
None of those requirements is safely priced merely because the estimator measured the wall area.
Turning a construction specification into an estimate is therefore not a matter of reading it once and keeping it open beside the spreadsheet.
The estimator needs to convert requirements into work packages, pricing lines, supplier enquiries, supporting obligations and clarifications.
The specification contains cost without containing quantities
Specifications commonly describe products, performance, execution, testing and quality. Drawings and schedules may provide the location and quantities. Preliminaries and tender instructions can add project-wide obligations.
The estimate has to bring those sources together.
Government procurement guidance describes the specification as the document that explains what the buyer requires, while its guidance for SMEs bidding for government contracts distinguishes the specification from the pricing response document. Private building projects use different forms and processes, but the estimating lesson transfers: requirements and prices often live in different documents and must be reconciled deliberately.
The specification does not always tell the estimator which spreadsheet row should carry each cost. That translation is skilled work.
Control the document basis
Before extracting requirements, record:
- specification title, author, date and revision
- sections or work packages issued
- addenda and tender clarifications
- documents referenced but not supplied
- drawings and schedules to be read with it
- contractor-design portions
- stated precedence or document-status rules
Do not assume an undated file is current because it arrived in the latest email. If the basis cannot be confirmed before the tender deadline, record the version used and raise the gap.
Build a requirements register
A requirements register turns specification text into reviewable estimating actions.
| Field | Example content | Estimating purpose |
|---|---|---|
| Requirement ID | Section and clause reference | Preserves traceability |
| Work package | Drylining, roofing, finishes or services | Assigns commercial ownership |
| Requirement | Product, performance, workmanship or test | States what must be allowed |
| Related document | Drawing, schedule or detail | Links description to location and quantity |
| Pricing action | Measure, rate, enquire, allow or clarify | Converts text into work |
| Estimate reference | Package and line item | Shows where cost was carried |
| Status | Confirmed, assumed, allowance, clarification or excluded | Makes uncertainty visible |
Do not copy every clause into the estimate. Capture the requirements that change scope, method, cost, programme, evidence or risk.
Read by work package
Reading the specification only from page one to the end can hide cross-package obligations.
Review it by package and search for the different ways a cost can be expressed:
- named or proprietary products
- acceptable alternatives
- performance criteria
- workmanship and installation standards
- samples, mock-ups and approvals
- inspection, testing and certification
- protection, cleaning and handover records
- interfaces with other trades
- contractor design and coordination
Assign each item to a package owner even if the final procurement route has not been decided. Unowned specification clauses are easy to omit because every trade assumes somebody else has priced them.
Translate requirements into pricing actions
Every material requirement should lead to an action.
- Measure: obtain a quantity from the drawings, schedules or model.
- Rate: apply a supportable labour, material, plant or composite rate.
- Enquire: send a defined requirement to a supplier or subcontractor.
- Allow: carry a visible amount where the scope exists but cannot yet be priced firmly.
- Clarify: ask where the requirement is incomplete, contradictory or commercially important.
- Exclude: state deliberately when the work sits outside the proposed price.
“Read specification” is not a completed pricing action. The estimate should show where the commercial consequence landed.
Reconcile the specification with drawings and schedules
Check each important requirement against its location, quantity and detail.
Common conflicts include:
- a product described in the specification but absent from the drawings
- a drawing note calling for a different build-up
- a schedule using a type reference that the specification does not define
- a performance requirement without a complete tested system
- general clauses that appear to apply to several packages
- a later addendum changing one document but not the others
Do not resolve a contradiction privately in the estimator’s head. Record the chosen pricing basis and raise a clarification where necessary.
The related guide to creating a scope of works from construction drawings explains how to reconcile plans, sections, elevations and schedules. The specification review should connect to that same controlled scope rather than create a second, disconnected list.
Treat performance requirements carefully
A performance requirement can transfer design, coordination, evidence and testing work to the contractor or specialist supply chain.
Before pricing, identify:
- who selects or designs the compliant solution
- what calculations, drawings or submissions are required
- who coordinates interfaces
- what testing or certification demonstrates compliance
- what programme time is needed for review and approval
Do not assume that buying a named product covers the design responsibility or evidence required around it.
The UK government’s risk allocation and pricing guidance emphasises that fixed pricing depends on clarity of scope and specification. Although written for public procurement, the commercial principle is relevant to contractors: ambiguous requirements create uncertainty that should be resolved, qualified or priced visibly.
Carry uncertainty visibly
Not every specification gap can be closed before tender return.
Use the treatment that best describes the situation:
- an assumption for the basis used to price included work
- a PC sum for a defined supply selection where appropriate
- a provisional sum or allowance for work not sufficiently defined
- a risk allowance for an identified exposure
- an exclusion for work deliberately outside the offer
- a tender clarification requesting the missing decision
These are not interchangeable labels. The quote should explain what the amount covers and how a later change will be treated.
Use the guide to PC sums and provisional allowances when selections or incomplete work need a clearer commercial basis.
Issue a traceable pricing scope
Before final review, confirm that each material requirement is:
- included in a measured or priced item
- covered by a supplier or subcontract quotation
- carried as a visible allowance or risk
- raised as a clarification
- or stated as an exclusion
Then reconcile the requirements register with the estimate and client-facing quote. A requirement recorded in an internal note but absent from both the cost and the quote wording is not controlled.
Use the construction estimating checklist to complete the wider scope, commercial build-up and issue-control review.
How Quotify supports specification review
Quotify analyses uploaded drawings, specifications and supporting project information to create a structured first-pass estimate and make assumptions, scope and missing information available for review.
The contractor remains responsible for interpreting project requirements, confirming the pricing basis, applying rates and approving the final quote.
If you have a live specification to price, run the project pack through Quotify and compare the structured first pass with your current review process.
FAQs
How do you price a construction specification?
Control the document revision, extract cost-relevant requirements by work package, connect them to drawing quantities and convert each requirement into a measurement, rate, enquiry, allowance, clarification or exclusion.
Can a construction estimate be prepared from a specification alone?
Sometimes an early allowance can be prepared, but a detailed fixed-price estimate will usually need quantities, locations, interfaces and project conditions from drawings, schedules, site information and other tender documents.
What specification clauses should an estimator review?
Review clauses affecting products, performance, workmanship, testing, samples, approvals, contractor design, coordination, protection, handover and interfaces between trades.
How should conflicts between drawings and specifications be priced?
Record the conflict, check any stated document-precedence rules, seek clarification and state the basis used if the tender must proceed before the conflict is resolved.
What should happen when a specification requirement is unclear?
Raise a clarification where possible. Otherwise use a clearly stated assumption, allowance, risk treatment or exclusion that matches the commercial situation rather than pretending the requirement is certain.
Use this thinking on a real project pack
Send drawings, specifications, notes or a current quote. Quotify will show how the project can be structured for review.
