ProjectCostPro Construction estimating tools

Sources & data notes

How we calibrate the numbers behind each calculator, and why our estimates are ranges instead of single prices.

Why estimates are ranges

The same project can vary 30-100% depending on access, demolition required, regional labor rates, contractor backlog, season, material availability, and code requirements that change by jurisdiction. A single price would be wrong almost every time. A range, paired with the actual cost drivers shown as line items, gives you something you can act on.

Each calculator's range is wide enough to cover the realistic spread of project conditions, and narrow enough that the midpoint is a useful starting point for budgeting.

Source families

We don’t copy from any single source. Published rate rows are designed to draw from a category of public benchmarks plus clearly-labeled internal assumptions. Below is what each category covers and how we use it.

Public cost guides

HomeGuide, HomeAdvisor, Homewyse, Fixr, Angi, This Old House, Modernize. These give us national-average ranges and seasonal trends. We use them as one of several signals — not as the primary truth — because their numbers vary widely between guides for the same project.

Government labor + price data

We use Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) as a wage benchmark by trade. ProjectCostPro does not treat BLS wages as contractor prices directly; we model loaded crew billing rates by adding payroll burden, overhead, equipment, supervision, and contractor margin assumptions on top of the wage data. BLS Producer Price Index series are used as a broad signal for material-cost movement, not as a direct local price quote. IRS Form 5695 and 8911 inform federal energy / EV credit guidance; EPA standards inform radon, mold, and lead-paint scope.

Building code references

We use International Code Council model codes, trade standards, and common AHJ practices to structure scope items such as permits, inspections, venting, clearances, egress, energy requirements, and safety-related exclusions. Local code adoption varies by city, county, and state — many jurisdictions are on older model-code editions or have local amendments — so these references guide calculator logic but do not replace local permit review.

Manufacturer / supplier benchmarks

We use published MSRP, retail listings, and supplier-visible pricing snapshots from manufacturers and major retailers (Home Depot, Lowe’s, Schluter, Mitsubishi, Daikin, Rinnai, Bona, RadonAway, Aprilaire, Custom Building Products, and others) as material-cost benchmarks. These are not live quotes and may differ from local contractor pricing, distributor discounts, freight, minimum orders, and seasonal availability.

Industry standards

IICRC S520 for mold remediation containment levels. NRPP / NRSB for radon mitigation. NWFA for hardwood refinishing. NFBA for post-frame buildings. ICC for permit treatment. These define scope structure, not price — we use them to make sure our line items match the work that actually gets done.

Cost-book calibration

We use published estimating references only as internal calibration tools for unit logic, crew-hour sanity checks, and range reasonableness. We do not copy, republish, or expose protected tables, prices, descriptions, or formulas. Public site data is independently modeled from public sources, supplier benchmarks, and ProjectCostPro assumptions.

Internal assumptions

Where public data is thin — mobilization minimums, emergency call-out fees, access difficulty, regional friction, small-job premiums — we use internal assumptions calibrated against multiple public guides and supplier-visible pricing snapshots. We try to keep internal-only assumptions limited and clearly labeled in the data model (typically with a source_url of internal-assumption) so they can be audited and treated as planning logic, not source-quoted prices.

How we update rates

Rate tables are designed to carry source_url, source_date, and lastUpdated fields where applicable, so published rate rows can be audited and reviewed over time. Our target is to review high-impact rates regularly, refresh outdated source links, and re-check regional spread when material or labor markets move. If you spot a number that appears clearly wrong, tell us — we use that feedback to cross-check the relevant calculator and source assumptions.

What ZIP-zone pricing actually is

The ZIP / state input on each calculator applies a planning-zone adjustment to material, labor, and equipment costs — not exact local supplier or bid pricing. We use a curated set of metro zones plus state averages for the rest of the country, calibrated against published regional cost spreads. Two ZIPs in the same metro will return the same multiplier; real contractor pricing within a metro can still vary based on neighborhood, supplier proximity, and crew availability.

These methods make the estimates more useful for planning, but they do not replace a site visit, local code review, or a written contractor bid.

Why local quotes will differ

Use ProjectCostPro for planning. Always get 2-3 written bids from licensed contractors before signing.

Editorial, source, and correction policies

Editorial policy

Each calculator is built around the actual scope decisions for that trade — material grade, dimensions, access difficulty, demolition, and permits — rather than a single national-average number. Calculator structure, scope language, and assumptions are reviewed against published cost guides, manufacturer documentation, code references, and industry standards before any rate row is added or changed.

Source policy

We prefer durable, primary-leaning sources where they exist: government data (BLS, IRS, EPA, Energy Star), code references (ICC model codes, trade standards like IICRC, NRPP, NWFA, NFBA), manufacturer pricing pages, and major retailer listings. Public cost guides (HomeGuide, Homewyse, Fixr, Angi, HomeAdvisor) are used as one signal among several, never as a single source of truth. Cost-engineering reference books are used only for internal calibration and unit-logic sanity checks; we never copy or republish protected tables, prices, or formulas. Where public data is thin, internal assumptions are clearly labeled in the rate tables and treated as planning logic, not source-quoted prices.

Correction policy

If a published number looks clearly wrong, tell us — include the calculator name, the inputs you used, and what you got quoted locally. We re-check the source row, update the underlying CSV if warranted, and refresh the lastUpdated date so the change is auditable. We aim to acknowledge feedback within a few business days; resolution time depends on whether the change is a single-number tweak or a structural revision to the calculator.