Comparable components only
Map unit-price items such as asphalt, concrete, aggregate base, excavation, drainage, fencing, striping, and selected electrical work. Never use a highway contract total as a complete residential-project price.
Transparent planning estimates
How Property Improvement Estimator builds planning prices
A planning estimate starts with reviewed bid-derived installed estimates stored in Admin Pricing, then applies the project measurements and options you choose. Local data and public bids affect a result only through documented, reviewed, and published rules. A contractor's site review and proposal remain the final price.
Calculation sequence
Six checkpoints from baseline to contractor bid
- 1
Start with published bid-derived pricing
The active Admin Pricing model stores reviewed bid-derived low, middle, and high installed estimates.
- 2
Apply the selected scope
Dimensions, quantities, style, preparation, access, removal, equipment, and add-ons determine which priced rows are used.
- 3
Resolve the location
An address or ZIP identifies matching state, county, metro, climate, soil, demand, and market records.
- 4
Apply only published factors
A source affects the installed estimate only after its mapping and bounded adjustment have been reviewed and published.
- 5
Show the planning range
The result keeps assumptions and source effects visible; it is not converted into a guaranteed bid.
- 6
Verify with contractors
A contractor confirms field measurements, products, access, utilities, permits, schedule, and final scope.
Source of truth
Published Admin Pricing stores the bid-derived baseline
Calculators and mapped estimates resolve bid-derived active style and component rows from the same published model. Draft edits remain private. Each published row can carry low, middle, and high values, a unit basis, formula metadata, mobilization, and minimum project totals.
Browser catalog values are continuity fallbacks when remote pricing is unavailable; they are not intended to override a matching active row. Internal fallback diagnostics are kept out of customer-facing copy.
Source matrix
What each source measures and how it can be used
A source can set a baseline, support a calculation, benchmark a component, or provide context only. Those roles are intentionally different.
Bid-derived installed-price baseline
The active Admin Pricing model stores the reviewed bid-derived estimates used for the starting installed range and cost buckets.
| Source and role | What it measures | Price relationship | Applicability and review |
|---|---|---|---|
| Published bid-derived estimatesProperty Improvement Estimator Admin PricingBid-derived baselineOfficial source | Reviewed bid-derived low, middle, and high installed estimates, style choices, option prices, mobilization, and minimum project totals. Reviewed when pricing inputs change | The starting bid-derived installed price before approved local adjustments. Keeping reviewed bid-derived estimates in one controlled model makes the same project scope consistent across calculators, map estimates, and quote packets. | Every supported calculator and mapped project type. A saved draft does not change customer estimates until a main administrator publishes the pricing model.No currently published record was returned for this source. |
Labor, materials, and regional markets
Published economic factors can adjust the part of the estimate they actually measure.
| Source and role | What it measures | Price relationship | Applicability and review |
|---|---|---|---|
| Material price movementU.S. Bureau of Labor StatisticsCan change materialsOfficial source | Producer selling-price movement for selected material and construction-related series. Monthly source data | The installed estimate for mapped project and material families with an approved series. Material markets can move at a different rate than wages or general consumer prices. | Projects with a defensible material-series match, including fencing, paving, concrete, courts, fields, decks, walls, pools, and lighting. Used only when the series-to-project mapping and resulting modifier have been reviewed and published.No currently published record was returned for this source. |
| Trade wage levelsU.S. Bureau of Labor StatisticsCan change laborOfficial source | Employment and wage estimates for construction occupations by national, state, and metropolitan area. Annual source release | The installed estimate where the location and trade mapping are available. Installed work depends on local trade wages, not only national material prices. | All labor-bearing project types, using the relevant occupation group rather than one wage for every trade. The wage factor must be imported, mapped to the project, reviewed, and published.No currently published record was returned for this source. |
| County contractor marketU.S. Bureau of Labor StatisticsCan change labor contextOfficial source | Construction employment, establishments, and wages at county and state levels. Quarterly and annual source data | Labor-market pressure where contractor supply and wage conditions differ from the baseline. A tight local contractor market can affect scheduling and installed labor pricing even when material prices are unchanged. | Project types mapped to the relevant construction industry group. Only the reviewed project-specific factor is applied; raw employment counts never change a total directly.No currently published record was returned for this source. |
| Regional price levelU.S. Bureau of Economic AnalysisCan change regional contextOfficial source | Differences in overall price levels across states and metropolitan areas relative to the nation. Annual source release | A reviewed broad regional adjustment without presenting the statistic as a contractor quote. The same nominal project can operate in meaningfully different local cost environments. | Supported project types where a broader regional factor is published and does not duplicate a more specific adjustment. Applied only after review for overlap with wage and material factors.No currently published record was returned for this source. |
Demand and site conditions
Project-specific conditions can affect preparation, scheduling, durability, and risk allowances.
| Source and role | What it measures | Price relationship | Applicability and review |
|---|---|---|---|
| Permit and building activityU.S. Census BureauCan change demand contextOfficial source | Residential construction authorization activity by state and local permitting area. Monthly source data | A bounded construction-demand or scheduling-pressure factor where published. High construction activity can tighten crew availability and scheduling without changing the physical project. | Labor-intensive project types for which local construction demand is relevant. Permit counts are normalized into a bounded suggestion and require publication before use.No currently published record was returned for this source. |
| Weather and climateNOAA and National Weather ServiceCan change site preparationOfficial source | Temperature, precipitation, freeze, snow, wind, and seasonal climate context. Normals and periodic source updates | Project-specific preparation, curing, coating, excavation, base, or durability allowances. Freeze, moisture, heat, and application windows affect different scopes in different ways. | Concrete, asphalt, courts, fields, pools, fences, decks, retaining walls, and buried lighting work when the factor is relevant. Climate never applies as one universal markup; a project-specific reviewed rule is required.No currently published record was returned for this source. |
| Soil and base-preparation contextUSDA Natural Resources Conservation ServiceCan change ground workOfficial source | Broad soil characteristics related to drainage, clay, rock, frost, and excavation difficulty. Periodic source updates | Base preparation, drainage, excavation, or site-work buckets rather than finish and equipment prices. Subgrade and drainage needs can change the work below a project even when its visible dimensions stay the same. | Ground-supported and excavated projects such as paving, concrete, pools, courts, fields, fences, walls, and buried lighting. Broad soil data is planning context and requires field verification; only reviewed bounded factors affect estimates.No currently published record was returned for this source. |
| Elevation and terrain contextU.S. Geological SurveyCan change site preparationOfficial source | Elevation, elevation variation, and derived slope context from the 3D Elevation Program. When source elevation products change | A reviewed terrain, grading, excavation, access, or earthwork allowance where slope changes the work. Slope and elevation change can affect cut and fill, drainage, access, retaining needs, and equipment movement. | Concrete, asphalt, pools, courts, fields, retaining walls, decks, fences, and buried lighting when terrain is relevant. Terrain data remains informational unless a bounded project-specific modifier is reviewed and published.No currently published record was returned for this source. |
| Flood hazard contextFederal Emergency Management AgencyUsually explanatoryOfficial source | Mapped flood-hazard context and Special Flood Hazard Area coverage from the National Flood Hazard Layer. Quarterly source review | A project-specific drainage or preparation allowance only when an applicable factor is explicitly published. Flood context can identify questions for drainage and site review without deciding parcel-level conditions. | Scopes where reviewed flood context changes drainage or preparation; otherwise it remains explanatory context. It is not a parcel hazard determination and does not alter price unless a reviewed project rule is active.No currently published record was returned for this source. |
Benchmarks and location context
Comparable public bids can support reviewed component benchmarks; Census geography explains the location but is not a quote.
| Source and role | What it measures | Price relationship | Applicability and review |
|---|---|---|---|
| Public responsive bid benchmarksState and local public works agenciesReviewed benchmarkOfficial source | Responsive contractor unit prices for defined public-work bid items, kept separate from agency engineer estimates. Monthly registry review and import | Comparable component suggestions for asphalt, concrete, aggregate base, excavation, drainage, fencing, striping, and selected electrical work. Item-level bids provide market evidence, but public-project conditions can differ substantially from private property work. | Only a mapped component with compatible scope, unit, quantity band, date, and geography; never a complete unrelated residential project. At least 10 observations across 3 contracts and 3 bidders are required before admin review; acceptance updates a draft Admin Pricing row, not live pricing.No currently published record was returned for this source. |
| Population and property contextU.S. Census BureauContext onlyOfficial source | Population, housing, occupancy, home age, and broad property characteristics. Annual five-year release | Location-page explanations and coverage context, not a project price by itself. It explains the type and scale of a local market without pretending demographic data is a contractor quote. | City, state, and local project information pages. Never used as a direct price multiplier.No currently published record was returned for this source. |
| Location and boundary referenceU.S. Census BureauContext onlyOfficial source | State, county, place, ZIP Code Tabulation Area, centroid, and boundary relationships. Annual and service updates | Location matching, nearby-page navigation, and the geographic scope used to look up reviewed data. Reliable geographic keys prevent a city, county, or ZIP factor from being attached to the wrong area. | Location search, coverage, city/state pages, and source lookup. Geography selects context; it does not set construction prices.No currently published record was returned for this source. |
Public bid benchmarks
Useful evidence, with strict comparability limits
State and local bid tabs can contain real contractor unit prices. They also reflect public-contract scale, quantities, specifications, timing, geography, traffic control, bonding, and site constraints. The system therefore treats them as supplemental evidence for comparable components, not as homeowner quotes.
Responsive bids stay separate
Contractor unit bids are analyzed separately from agency engineer estimates, and bidder identities are anonymized in normalized records.
Enough independent evidence
Require at least 10 usable observations across 3 contracts and 3 bidders before an aggregate can enter review.
Time and quantity matter
Use a primary 24-month window, extend to 36 months only when necessary with lower confidence, and compare work within quantity bands.
Outliers and inflation are controlled
Use canonical units, interquartile-range filtering, recency weighting, and applicable PPI normalization before calculating low, median, and high benchmarks.
Two approvals before use
Admin acceptance copies the reviewed benchmark into a draft Admin Pricing row. The normal Admin Pricing publication step is still required before customer estimates change.
The nationwide registry tracks all 50 states and the District of Columbia with an honest status. Missing states are not silently replaced with neighboring-state data. Review the official WSDOT bid tabulations and WSDOT Unit Bid Analysis guidance for examples of the evidence and comparability limits this workflow is designed around.
Review controls
Imported data and live pricing stay separate
Every path into customer-facing pricing has a visible draft and publication boundary.
- 01Import
Raw public datasets and bid tabs are stored with source, date, unit, and run metadata. Importing data does not change an estimate.
- 02Map and qualify
A project-specific mapping, canonical unit, quantity band, recency window, outlier rule, and evidence threshold determine whether a suggestion can be reviewed.
- 03Review into draft
A main administrator reviews scope compatibility, evidence, confidence, and the comparison with the current price before accepting a value into draft Admin Pricing.
- 04Publish
Only the normal Admin Pricing publish action moves a reviewed draft into the active model used by calculators and mapped estimates.
- 05Validate
First-party contractor quotes remain separate evidence. They can support later calibration only after enough comparable records meet the platform's review thresholds.
What this is
A transparent planning range
Useful for comparing scope choices, organizing a property plan, preparing questions, and deciding when to request contractor review.
What this is not
A survey, permit decision, engineering opinion, or guaranteed bid
Final pricing depends on field measurements, products, site access, utilities, drainage, code, taxes, schedule, and the contractor's complete scope.
Accountability
Built and maintained by Christian Speelman
Christian is a software engineer and project manager. The platform does not claim that software replaces contractors, estimators, surveyors, or engineers. Its credibility rests on transparent calculations, documented sources, administrative review, and comparison with contractor feedback as enough data becomes available.
About the founder and platform