Guides

Concrete Takeoff in Excel: How to Structure a Footing Spreadsheet

Updated 2026-07-12 · 8 min read

Most footing estimators start in Excel, and for good reason: it is on every machine, it is flexible, and a well-built sheet turns a plan into a billable linear-foot total in an afternoon. The trouble is that a badly built sheet does the same thing while hiding errors that surface at month-end.

This is how estimators actually structure a footing takeoff spreadsheet, the formulas that make it reliable, and the exact points where a spreadsheet stops being enough.

How should the columns be laid out?

A footing takeoff is a list of wall segments, one row each, measured off the plan. The column structure that works:

ColumnHeaderExamplePurpose
ASegment / locationNorth perimeterTies the row to the plan
BFeet17Whole feet as read from the drawing
CInches6Inch remainder as read
DDecimal feet17.50Formula: converts B and C for math
EWall typePerimeterGroups runs for subtotals
FRate3.00Per-foot rate for this run
GLine total52.50Formula: decimal feet times rate
HPads0Interior support pad count on this row

One row per segment is the whole discipline. You read a wall run off the plan, you enter its feet and inches, and the sheet handles the rest. Grouping by wall type in column E lets you subtotal perimeter, interior bearing, and any other category separately, which matters because those often bill at different rates or fall under different inclusion rules.

What are the formulas?

Three formulas do all the work.

Feet and inches to decimal feet (column D). This is the one that must be right, because you cannot multiply feet-and-inches by a rate directly. The conversion is feet plus inches divided by 12 (VDCI):

D2 = B2 + C2/12

So 17 feet 6 inches becomes 17 plus 6 divided by 12, which is 17.5. As one estimating reference puts it, everything has to be converted to a decimal to use it with a unit cost, because there is no way in Excel to price a linear-foot cost directly from feet and inches. The decimal value of a single inch is about 0.083, so an inch typed into the wrong column throws the total off by that much per row, which adds up fast.

Line total (column G):

G2 = D2 * F2

Decimal feet times the per-foot rate. Simple once the decimal conversion is trustworthy.

Subtotal by wall type using a conditional sum. To total decimal feet for perimeter runs:

=SUMIF(E:E, "Perimeter", D:D)

Repeat per wall type to see how your footage splits. A grand total of billable linear feet is a plain sum of column D across the rows you are billing, and total pads is a sum of column H. Those two numbers, total linear feet and total pad count, are usually what the invoice is built from.

How should rate cells be handled?

Put rates in their own cells and reference them, never type a rate straight into a formula. A common pattern is a small rate block at the top of the sheet: a base per-foot cell, a rebar per-foot cell, and a per-pad cell. Each line’s rate column then points at the right rate cell rather than repeating a hard number.

The reason is maintenance. If your base rate changes, or a job is negotiated at a different number, you edit one cell and the whole sheet re-totals. Rates buried inside formulas mean hunting through every row to change one number, and missing a row means an invoice that silently mixes two rates. A rebar run simply references the rebar rate cell; a base run references the base cell. The split between base and rebar footage, which the billing guide treats as its own discipline, falls out of the wall-type column automatically.

One rounding note: keep the decimal-feet column at full precision and only round the displayed line total. Rounding each segment’s feet to a tidy number before summing introduces creep that can move a large job’s total by a real amount. Let Excel carry the decimals and round once, at the presentation layer.

Why enter feet and inches separately?

Because that is how the plan reads, and because collapsing them invites the most common takeoff error. A plan gives you 17 feet 6 inches. If you type that as 17.6 into a single cell, Excel treats it as 17.6 feet, but 17 feet 6 inches is 17.5 feet. That one-tenth-of-a-foot slip, repeated across dozens of segments, is enough to make a bid wrong and an invoice disputable.

Separate feet and inches columns let the estimator enter exactly what they read, in the units they read it, and let a formula do the arithmetic that humans get wrong. It is a small structural choice that removes an entire class of error.

What are the failure modes of a spreadsheet takeoff?

A spreadsheet is a good tool with three predictable weaknesses. Knowing them tells you when to stop trusting the sheet.

  • No visual audit trail. The sheet holds numbers, not the plan. Nothing links row 14 to a specific wall on the drawing. When a GC questions a total, you cannot point at the plan and show which runs made it, because the connection lives only in the estimator’s head. This is the biggest structural gap.
  • Feet-inch entry errors. Even with separate columns, a mistyped inch or a run entered in the wrong wall-type category silently changes a subtotal. There is no built-in check that the rows match the drawing.
  • Version chaos. Plans get revised. Someone emails “footing takeoff FINAL v3,” another person edits an older copy, and now two invoices disagree. Spreadsheets have no inherent link to the current plan revision, so the wrong version can quietly become the billed one.

None of these mean a spreadsheet is wrong for the job. They mean it has limits.

When is a spreadsheet enough, and when isn’t it?

A spreadsheet is genuinely enough when the job is small to medium, one estimator owns it, the wall types are few, and the inclusion rules are simple. For a straightforward house with a clean perimeter and a handful of interior runs, a well-built sheet with the columns above is fast, cheap, and accurate.

It stops being enough when:

  • Jobs get large and the number of segments makes manual entry error-prone.
  • Edge cases multiply, with many wall types, partial runs, and inclusion decisions that need to be defensible run by run.
  • Several people bill against the same plans, where version chaos and the missing audit trail turn into real disputes.

At that point the missing piece is the link between each measurement and the plan. A takeoff tool like FootingTakeoff keeps the measured linear feet and pad counts tied to the marked-up drawing, so every number on the invoice traces back to a visible location on the plan, which is exactly the audit trail a spreadsheet lacks. Until you hit that wall, a clean spreadsheet backed by the free linear feet of footing calculator for spot checks does the job.

Build the sheet with separate feet and inches columns, a decimal-conversion formula, subtotals by wall type, and a pad count, and you have a reliable footing takeoff. Just know its three blind spots, and know that the moment your jobs outgrow a numbers-only record, the fix is tying those numbers back to the plan.

Frequently asked questions

How do you convert feet and inches to decimal feet in Excel?
Divide the inches by 12 and add them to the whole feet. If feet are in column B and inches in column C, the formula is B2 plus C2 divided by 12. For example, 17 feet 6 inches becomes 17 plus 6 divided by 12, which equals 17.5 decimal feet, the form Excel needs before multiplying by a per-foot rate.
How should a footing takeoff spreadsheet be organized?
Use one row per wall segment with separate columns for feet and inches, a formula column that converts to decimal feet, a wall-type column, and a rate column. Add a pad-count column and subtotal linear feet by wall type. This keeps each measurement auditable and lets you sum billable footage and apply rates cleanly.
Why do estimators enter feet and inches in separate columns?
Because reading a plan gives measurements in feet and inches, but Excel cannot multiply feet-and-inches by a unit rate directly. Separate feet and inches columns let the estimator enter what they read, then a formula column converts to decimal feet for the math. This avoids the common error of typing 17.6 when the measurement was 17 feet 6 inches, which is actually 17.5.
When is a spreadsheet not enough for a concrete takeoff?
A spreadsheet holds numbers but not the plan, so it has no visual audit trail linking each row to a location on the drawing. When jobs get large, edge cases multiply, or several people bill against the same plans, the lack of a marked-up drawing and the risk of feet-inch entry errors and version chaos start causing disputes. At that point a takeoff tool that ties measurements to the plan is worth it.

FootingTakeoff

Do this takeoff automatically.

FootingTakeoff reads footing plans and returns linear feet, pad counts, and an invoice at your rates.

Get early access