How We Calculate Concrete Costs
All cost estimates on SlabCalc are derived from the winning bids on public sidewalk contracts, read line by line from state Department of Transportation and city bid tabulations, then adjusted for residential project scale. Here is exactly how — including what the numbers mean and where they fall short.
Data Sources
We collect the unit prices contractors bid on public concrete sidewalk work — road, municipal and public-facility contracts — from each agency's published bid tabulations. For every metro we use its own agency district's contracts for the standard 4-inch concrete sidewalk item, let from 2023 on, and keep the winning bidder's unit price on every contract line of at least 300 sq ft. The low, median and high figures are the 25th, 50th and 75th percentiles of those lines; the count is the number of distinct contracts. Prices are as bid, not inflation-adjusted.
Every agency behind the index is listed below, backing 26 of our 30 metros with 1233 contracts. Every bid line is kept in the pipeline with the agency URL and a checksum of the document it came from, and a metro is only labelled as bid data when at least five contracts qualify. This table is generated from the cost matrix itself, so it cannot fall out of step with the figures on the cost index.
Notes the table cannot carry on its own. Four metros are not in this table. San Diego (three Caltrans District 11 contracts in the window) is modelled from Los Angeles, Boston (MassDOT's line-item tabs are behind a Bid Express login) from Philadelphia, and Las Vegas (NDOT's tab portal is gone; Clark County's needs a login) from Denver, each scaled by a labor-cost ratio; Phoenix (four ADOT contracts) is derived from national indices. Atlanta is priced from Gwinnett County's contracts for the GDOT 4-inch sidewalk item, because GDOT's own itemized tabs are behind a login. Chicago uses IDOT's 5-inch sidewalk item, the District 1 standard; Caltrans prices minor concrete sidewalk per cubic yard, converted at 81 sq ft per CY.
Correction, October 12, 2026. An audit found that several metros labelled as DOT data were not read from DOT records: St. Louis and Kansas City carried prices never read from MoDOT data, Minneapolis and Columbus served fallback constants after their source files went offline, and New York was a fixed estimate. Bid counts for Denver, Charlotte, Raleigh, Minneapolis, Columbus, St. Louis, Kansas City and New York were typed in rather than counted, and other metros shared one statewide average or had a range made by multiplying an average. Every metro was rebuilt from line-level bid records on this date, and the eight metros previously modelled from other states now use their own (except Boston and Las Vegas).
Correction, November 1, 2026. Until this date the low end of every metro's range was published at 75% of the 25th-percentile winning bid, while the methodology described it as the 25th percentile itself. The low ends now are the 25th percentile, as described. High ends, contract counts and the order of metros are unchanged; every low end rose by a third (New York from $13.68 to $18.24, Atlanta from $3.33 to $4.44) and the national median moved from $9.89 to $10.97. Figures published before this date are superseded.
How We Process the Data
The raw bid data goes through three steps before appearing on the site:
- Unit price extraction. We read the winning unit price for the 4-inch concrete sidewalk item from each contract's bid tabulation, convert it to dollars per square foot, and drop lines under 300 sq ft. The installed price covers the sidewalk item as bid; removal, traffic control and mobilization are separate pay items.
- Project-type adjustment factor. DOT contracts cover large-volume infrastructure pours. Residential projects are smaller, which increases unit cost — a 5-yard residential pour costs more per yard than a 500-yard highway pour. We apply a project-type factor to account for this scale difference.
- Material and labor split. Installed costs (per square foot) are derived by applying standard industry ratios to separate material cost from labor and overhead. The split varies by project type and metro.
Correction, October 8, 2026. City cost pages said Texas, Missouri, Colorado, Nevada, Ohio and Tennessee have no state prevailing-wage law. All six do (Tex. Gov't Code ch. 2258, RSMo 290.210–290.340, C.R.S. 24-92-201 et seq., NRS ch. 338, Ohio Rev. Code ch. 4115, and Tenn. Code 12-4-401 et seq. for state highway work). The six states are now classified correctly, using each metro's cement-mason highway rate (DOL Davis-Bacon, base plus fringe). A wage premium is removed only where that rate is above the local BLS market wage. That lowers residential estimates by about 21–24% in St. Louis, Kansas City and Columbus, where highway rates are $51.70–$58.59 an hour. Texas and Denver are unchanged, because their highway rates ($20.61–$25.93) sit below the market wage. Modelled metros now remove the wage premium in the bids they are modelled from, not their own state's: Las Vegas and Nashville are unchanged, Boston (+33%), Philadelphia (+22%) and Detroit (+14%) rise because their Denver and Charlotte source bids carry no premium, and Seattle and Portland fall about 4% to Chicago's ratio. Contractor (DOT) prices and the cost index figures did not change. The public CSV column formerly named has_prevailing_wage_law is now pw_premium_adjusted, true where the model removes a prevailing-wage premium. The prevailing-wage chart on the cost index has been rebuilt on the corrected classification ($6.83 vs $5.99, previously $7.08 vs $5.99).
What the Numbers Mean
The price ranges shown on SlabCalc — for example, $5.59–$11.96 per square foot for a Tampa patio — are benchmarks, not quotes.
- Lower bound reflects an efficient contractor working in favorable site conditions with standard materials.
- Upper bound reflects a more complex project: difficult access, premium materials, decorative finishes, or a high-demand contractor market.
Actual contractor quotes may fall above or below these ranges. Site-specific factors — soil conditions, slope, existing concrete removal, permit requirements, and seasonal timing — all affect final pricing in ways our model cannot predict for an individual project.
Always get at least three contractor quotes for any project over 100 square feet.
Coverage
We currently cover 30 metropolitan areas across the United States:
Atlanta, GA — Austin, TX — Boston, MA — Charlotte, NC — Chicago, IL — Columbus, OH — Dallas, TX — Denver, CO — Detroit, MI — Houston, TX — Kansas City, MO — Las Vegas, NV — Los Angeles, CA — Miami, FL — Minneapolis, MN — Nashville, TN — New York, NY — Orlando, FL — Philadelphia, PA — Phoenix, AZ — Portland, OR — Raleigh, NC — Riverside, CA — Sacramento, CA — San Antonio, TX — San Diego, CA — San Francisco, CA — Seattle, WA — St. Louis, MO — Tampa, FL
Limitations
There are important differences between DOT infrastructure contracts and residential concrete work:
- Scale. Government contracts involve hundreds to thousands of cubic yards per pour. A residential driveway uses 3–15 yards. Smaller pours carry higher unit costs due to mobilization, minimum delivery charges, and less efficient labor deployment. Our project-type adjustment accounts for this, but the adjustment is modeled, not directly observed.
- Labor agreements. Some DOT contracts require prevailing wages or union labor. Residential contractors typically operate under different labor cost structures.
- No contractor quote data. We do not have access to a database of residential contractor quotes. Our estimates are derived from DOT data — they are not a direct comparison to what contractors charge homeowners.
- Seasonal and market variation. Concrete pricing moves with material costs, fuel, and local demand. Our data reflects contracts let from 2023 on, as bid; rapid market changes may not be reflected immediately.
Calculations are estimates. Always verify with local suppliers and licensed contractors.
See the Data in Use
These estimates power SlabCalc's 180 city-level cost pages and inform guides like the concrete driveway lifetime cost guide, which uses cost-per-yard data to calculate annualized ownership cost by thickness. For broader context on what concrete costs:

