Overview
Base inputs
Most pages start with area, volume, count, spacing, stock length, or project size, depending on the job.
Trust center
How BuildCostLab estimates are built
BuildCostLab combines basic measurement formulas with practical buying and budgeting logic. The aim is to produce a planning number that is more usable than raw geometry alone, while staying clear about uncertainty.
Overview
Practical adjustments
Waste, pack rounding, unit conversions, labour allowances, extras, and contingency are added where they improve planning usefulness.
Overview
Why results are ranges
Real jobs vary by access, product choice, finish level, site condition, supplier format, and local labour pressure, so a planning range is often more honest than one exact promise.
Base formulas
Core outputs are built from standard geometry and estimating logic: area for surface coverage, volume for fills and aggregates, counts for unit-based products, and stock-length calculations for trims, drainage, and similar items. Project-cost pages build on the measured scope first, then add rate-based planning assumptions.
Waste allowances and buying logic
Where it helps users make a better decision, the site adds waste allowances, whole-unit rounding, coverage checks, and buying-format prompts. The purpose is to move closer to a real order or planning budget, not to present a bare mathematical output that still needs several mental steps.
Unit conversions
Pages support metric and imperial input where practical. Conversions are treated as a convenience layer on top of the main estimating logic rather than a separate methodology.
Labour, material splits, and extras
Project-cost calculators separate the likely material line from labour, extras, and contingency so users can see what is moving the budget. These are planning allowances, not trade quotes, and should be pressure-tested against real local prices.
How regional adjustments are handled
Regional handling is intentionally high level. It is there to help users think about labour pressure, access, and pricing differences by area, not to claim exact local prices for every postcode or contractor. Live quotes and supplier prices should always override the planning layer.
Worked example
A simple material example: a 4m by 3m patio at 50mm depth gives 0.6m3 of material before waste. Add 10 percent waste and the planning quantity becomes 0.66m3. If the chosen buying format is a 0.85m3 bulk bag, the safe order rounds to one bulk bag rather than 0.66 of a bag. A project-cost page then takes the measured scope, applies planning rates for materials, labour, and extras, and keeps the result as a range because site conditions can still move the live quote.
Freshness and review
Methodology pages and calculator families are reviewed when formulas, assumptions, internal links, or support content need updating. The aim is to keep the workflow practical and current without claiming that a static page can replace live supplier or contractor information.
Related trust pages
Use these pages together when you want to understand how estimates are built, reviewed, and meant to be used.