How to Compare Foundation Bids for a New Home

Choose the foundation proposal that is complete and comparable, not simply the one with the lowest subtotal. Put both bids against the same approved plan revision, permitting jurisdiction, geotechnical assumptions, dimensions, excavation, reinforcement, drainage, waterproofing, insulation, penetrations, inspections, backfill, allowances, exclusions, and responsible parties. Price or assign every unresolved row before signing, then record who verifies concealed work before the next trade or backfill.

Compare scope before you compare price #

A foundation bid is comparable only when both contractors are pricing the same approved design, site assumptions, work boundary, quality requirements, inspection gates, and handoffs. A low subtotal can be a complete proposal, an incomplete proposal, or a proposal that moves large pieces of work into allowances and exclusions. Your first decision is therefore not “Which contractor is cheaper?” It is “Can I explain the difference between these two totals without guessing?”

The comparison is for a new United States home during foundation and structural-stage procurement. The actual permitting jurisdiction controls local requirements. If the project is in Seattle, Washington, use Seattle Department of Construction and Inspections resources and the approved permit set for that address. If it is in Austin, Texas, use Austin Development Services and the active permit record. If it is elsewhere, replace both examples with the responsible city, county, or state authority. A web page from Seattle or Austin can illustrate a process; it cannot establish your project's inspection sequence.

This guide helps you compare proposals and create questions for the owner, design professional, general contractor, excavator, concrete contractor, waterproofing installer, energy professional, and building official. It does not tell you how to size footings, choose reinforcing steel, design a retaining wall, certify soil, sign off remotely, enter an excavation, or promise a completion date. Structural and site-specific conclusions remain with the qualified professionals responsible for the design and work.

The answer you should be able to give after comparing

At award, you should be able to state all of the following in one project record:

• Which approved plan revision and detail sheets each bidder used.
• Which site and soil assumptions are documented, which are measured, and which remain conditional.
• Which foundation type, dimensions, elevations, openings, steps, thickened areas, slabs, crawlspace floors, or basement areas are included.
• Who performs excavation, shoring or protective-system work, spoil loading, haul-off, rock removal, dewatering, temporary drainage, and site access.
• Who supplies and installs concrete, formwork, reinforcement, embedded items, sleeves, anchor items, joints, curing protection, and cleanup.
• Who owns foundation drains, sumps, discharge, dampproofing or waterproofing, drainage board, exterior insulation, vapor control, and backfill.
• Which inspection or special-inspection gates must occur while work remains visible, who schedules them, and what record proves passage.
• What each allowance includes, what unit or quantity it assumes, who can authorize a change, and how the final amount will be reconciled.
• What is excluded, who must procure it, by what date, and whether the exclusion blocks the next trade.
• Who verifies each concealed item and where the verification record lives before concrete, insulation, soil, or backfill hides it.

If any of these answers is “we will decide in the field,” the bid is not yet a clean comparison. That does not necessarily disqualify the contractor. It identifies a decision that must be clarified, assigned, priced, or made conditional before the award.

Compact originality brief

Current answers often compare slab, crawlspace, and basement types, publish generic price ranges, provide quote forms, or explain one inspection, safety rule, or moisture detail at a time. Those answers are useful inputs but leave the homeowner to translate two different scopes into one decision.

The missing decision is whether two foundation proposals describe the same work, responsibilities, verification points, and downstream risk. The original contribution here is the Source-linked foundation-bid normalization worksheet and handoff ledger: a reusable row-by-row record that converts each proposal into included, excluded, allowance, or owner-supplied status and then connects each row to a responsible party, evidence record, verification gate, and next handoff.

The method is: Normalize both bids row by row against the approved plan revision and geotechnical assumptions; label each row included, excluded, allowance, or owner-supplied; record the responsible party, evidence record, verification gate, and next handoff; then run an illustrative sensitivity by moving one allowance or omitted scope into the total without claiming a market price.

The limitations are: This worksheet does not design a foundation, interpret structural engineering, establish local code, replace a permit inspection, verify soil conditions, set a contractor price, or promise completion; the permitting jurisdiction, design professional, qualified contractor, product instructions, and site records control.

You can check the contribution by giving the same approved plan set and site information to each bidder, asking each to complete the same rows, tracing every unresolved row to a named person and record, and rerunning the comparison when an allowance is replaced by a written price. If two totals still cannot be reconciled after that, the difference is not a shopping preference; it is an unresolved scope decision.

Why a subtotal is a poor first screen

Foundation work crosses several trade boundaries. Excavation may be priced by a site contractor, concrete by a foundation contractor, waterproofing by a specialist, drainage by a plumber or civil contractor, insulation by an energy or framing trade, and inspections by the permit holder or general contractor. A proposal can call itself “foundation” while stopping at the outside face of a wall, the top of a footing, the bottom of a slab, or the placement of concrete. The word has no universal scope.

A bid may also contain terms that appear equivalent but are not:

The point is not to force every contractor into the same construction method. It is to make method differences visible. One contractor may include a membrane and drainage board while another proposes a different specified assembly. One may price export of excess soil while another assumes it remains on site. Those can be valid alternatives only when the approved design, product compatibility, jurisdiction, and downstream responsibilities are documented.

A practical comparison rule

Do not compare a “bid total” until each proposal has a status for every material row:

• Included: the bid clearly includes the defined scope, quantity or unit, product or performance requirement, and normal execution responsibility.
• Excluded: the proposal expressly omits the scope. Record the person or contract that must take it over and the date by which it must be resolved.
• Allowance: money or quantity is reserved, but the final scope, product, quantity, unit rate, or authority to spend is not fixed. An allowance is not the same as inclusion.
• Owner-supplied: the homeowner or another named party must furnish something, but the installer, delivery point, storage, damage risk, and inspection record must still be assigned.

If a row is silent, mark it unresolved, then convert it to one of the four statuses in a written clarification. Silence should never be treated as included merely because it is customary in your region.

The next decision after this chapter is to freeze a common input packet. Without that packet, a contractor may be comparing a different building, a different site condition, or a different permit assumption.

Freeze the common design and site inputs #

Before requesting a final foundation proposal, give every bidder the same approved plan revision, site information, jurisdiction, and written assumptions; otherwise the bids are estimates of different jobs. A common input packet is the prerequisite that makes later scope rows meaningful.

Start with the approved plan revision

Collect the plan set that the permit authority has approved, or identify clearly that the project is still at a pre-permit pricing stage. Put the revision date or identifier on the bid request and ask the bidder to list the sheets and details used. Do not rely on a sales drawing, a floor-plan screenshot, or a structural sheet detached from the architectural and civil context.

Your input packet should include, as applicable:

1. Site plan showing property lines, setbacks, finished grades, access, existing structures, easements, utility conflicts, and surface-water paths.
2. Foundation plan showing exterior dimensions, steps, offsets, piers, crawlspace or basement boundaries, slab areas, openings, stairs, porch interfaces, and any special conditions.
3. Foundation sections and details showing elevations, wall and footing relationships, slab or crawlspace floor assemblies, drainage, waterproofing or dampproofing, insulation, vapor control, joints, penetrations, and backfill notes.
4. Structural drawings and schedules issued by the design professional, without asking the homeowner to reinterpret reinforcement, loads, bearing, or connection design.
5. Geotechnical report, soil assumptions, groundwater observations, bearing or fill conditions, seismic or expansive-soil notes where applicable, and any geotechnical recommendation relevant to excavation or foundation construction.
6. Civil grading and stormwater information, including where drainage is permitted to go and whether temporary erosion or sediment controls are required.
7. Energy-code or high-performance assembly requirements, including the project's jurisdiction and climate-zone lookup rather than a generic insulation target.
8. Product specifications and current installation instructions for the exact waterproofing, drainage board, insulation, vapor-control, sealant, or protection products named in the design.
9. Permit conditions, inspection list, special-inspection requirements, testing requirements, right-of-way or haul-route restrictions, and site-access limits from the actual authority.
10. The intended contract boundary: whether this bid is from excavation through backfill, concrete only, a trade package under a general contractor, or a complete foundation package.

The homeowner can assemble this packet. The homeowner should not convert the geotechnical report into a new footing design or resolve a structural conflict. If the drawings, soil report, grading plan, or product data disagree, send the conflict to the responsible design professional and the bidder for a written clarification before comparing totals.

Identify the actual permitting jurisdiction

Write the jurisdiction in the first row of the worksheet as a full place, not merely “U.S.” or a state abbreviation. Record whether the authority is a city, county, state, tribal, or other building department; the permit number if available; the adopted code edition; local amendments; required inspection names; and the official page or permit communication where you verified them.

Seattle, Washington provides a useful example of why timing matters: Seattle Department of Construction and Inspections lists a setback/foundation inspection before placement of concrete and a framing inspection before covering floor framing in its residential quick sheets. See the Seattle residential inspection quick sheets. That is a Seattle sequence example, not a national schedule. Your proposal should state who requests the applicable local inspection and who holds the work open until the authority or required special inspector has seen it.

Austin, Texas illustrates a different recordkeeping expectation. Austin Development Services says the contractor coordinates each construction stage with appropriate inspections, the contractor schedules the inspection, the latest city-approved plan set should be accessible on site, supporting documents such as photos and engineering reports may be uploaded, and prerequisite inspections should be completed before a final building inspection or certificate request. Those are Austin Development Services building-inspection instructions for Austin, Texas. They do not create a rule for Seattle, Washington or any other jurisdiction.

Ask the permitting authority or permit holder these questions for your address:

• Is this work under a residential, commercial, townhouse, accessory-dwelling, or other permit path?
• Which inspection must occur before footing or foundation concrete is placed?
• Are reinforcement, underslab utilities, vapor barriers, waterproofing, insulation, drains, or special conditions separate inspection gates?
• Does the authority require a paper or digital approved plan set on site?
• Who schedules the inspection: owner, builder, permit holder, or trade contractor?
• What happens if rain, groundwater, unsafe access, or incomplete work prevents inspection?
• Which documents must be uploaded or retained: photos, testing reports, special-inspection logs, revised details, or approvals?
• Are there local erosion-control, dewatering, haul-route, tree-protection, right-of-way, or noise constraints that affect the bid?

Do not ask the bidder to guarantee that an inspector will approve a detail. Ask the bidder to identify the prerequisite, the responsible scheduler, the visible condition required, and the record they will provide after the inspection.

Freeze dimensions and quantities without pretending they are measurements

Your comparison needs common quantities, but a plan quantity and a field measurement are different inputs. Use the approved plan for designed length, area, and elevation. Use the geotechnical report, survey, or qualified field verification for site conditions. Label every input as one of:

• Plan: shown on the approved drawing.
• Documented: stated in a report, permit, product instruction, or record.
• Measured: obtained by a qualified person using a stated method.
• Estimated: a bidder assumption that must be tested or converted into an allowance.
• Unknown: unresolved and potentially change-producing.

For each foundation proposal, freeze at least these units:

If the plan gives a quantity but the site may change it, keep the plan quantity in the base scope and create a separate conditional row. For example, “planned excavation: 410 cubic yards; possible unsuitable-soil replacement: unknown, owner decision after qualified observation.” Do not silently replace the designed quantity with a bidder's guess.

Resolve the handoff from design to procurement

The design professional owns design intent and revisions. The builder or owner-general contractor owns procurement coordination if that is their contract. The foundation contractor confirms that the proposal is based on the issued documents and identifies constructability questions. The geotechnical professional owns geotechnical interpretations within their engagement. The building official or special inspector owns the authority's inspection decision, not the contractor.

Ask for a written “bid basis” page that names:

• Document titles, sheet numbers, revision dates, and addenda.
• The assumed foundation system and any alternate system.
• Soil, groundwater, access, grade, weather, and haul assumptions.
• What happens if the field condition differs from those assumptions.
• The person authorized to answer a design question.
• The person authorized to spend an allowance or issue a change.
• The record that closes the question: revised detail, RFI response, field report, test, inspection result, photo log, or change order.

The next handoff is from a common input packet to a normalized scope. If a bidder will not name the documents or assumptions used, keep that proposal provisional rather than forcing it into a false comparison.

Normalize every foundation scope row #

Use one row structure for both proposals: scope item, design reference, unit or quantity, Bid A status, Bid B status, included detail, exclusion or allowance, responsible party, verification record, next handoff, and decision date. This converts a narrative estimate into a record that can survive procurement, construction, inspection, and backfill.

The normalization worksheet

Copy this table into a working spreadsheet or project record. Keep the wording specific enough that a person who did not attend the bid meeting can tell what is being compared.

The table is intentionally wider than a typical contractor estimate. Rows that look administrative—revision, inspection, record, next handoff—are where concealed work becomes either verifiable or disputable. Keep the rows even when both bidders say “included,” because the detail and record still need to be compared.

What “included” must mean

Treat a row as included only when the proposal answers four questions:

1. What: What physical work, product, quantity, and quality or performance basis is covered?
2. Where: Which plan detail, elevation, wall face, perimeter, opening, floor area, or site boundary does it cover?
3. When: Before which inspection, pour, cover, backfill, framing handoff, or other dependency must it be complete?
4. Proof: What record will show that it was completed or accepted?

“Per plans” can be useful when the referenced plans are identified, but it should not erase a trade boundary. Ask the bidder to confirm whether “per plans” includes labor, materials, equipment, layout, access, ordinary cleanup, testing, protection, and coordination with the next trade. If the bidder's exclusions modify the plan, request a marked-up scope or written alternate.

How to treat an exclusion

An exclusion is not a cost by itself; it is a responsibility gap. For every exclusion, add four fields:

• The work or material omitted.
• The contract or person taking it over.
• The latest date it must be completed.
• The dependency it unlocks.

For example, “waterproofing by others” should become “waterproofing by [named installer or GC], exact product [name], substrate repairs by [party], inspection record [record], complete before [protection board/backfill], decision date [date].” If nobody accepts the row, it is not a negotiated exclusion; it is an unpriced risk.

Do not fill an exclusion with a made-up market number. Obtain a written price from the responsible party, use a stated allowance with a clear reconciliation method, or record that the owner is accepting an unresolved budget exposure. The goal is honest scope, not an artificially precise total.

How to compare different methods

Two proposals can be different without one being wrong. A basement, crawlspace, slab, insulated concrete form, poured wall, masonry wall, exterior insulation, interior insulation, membrane, drainage-board, or other assembly may be appropriate in a particular design. The comparison questions are:

• Is the method permitted and shown or approved for this home?
• Does it satisfy the design professional's structural and architectural intent?
• Does the site and geotechnical information support the assumed excavation and drainage approach?
• Does the thermal and moisture assembly match the jurisdiction, climate, product instructions, and interior use?
• Does the method change another trade's work, inspection gate, or maintenance responsibility?
• Are the long-term records, protection, repair path, and warranty scope clear?

Do not award a method difference on the basis of a generic “better foundation” claim. Ask the bidder to show the alternate detail, the input that changed, and the handoff consequences. If a change affects structural design, send it to the design professional instead of trying to normalize it with a spreadsheet.

The next handoff is a clarification log. Every row with a different status, ambiguous wording, or changed method gets a question number, owner, due date, answer, evidence record, and updated bid status.

Price allowances, exclusions, and unknown site work honestly #

The comparable owner exposure is the bid total plus unresolved scope and allowance adjustments, not the headline subtotal. A useful comparison preserves uncertainty instead of hiding it inside a contingency or treating a zero-priced exclusion as free.

The normalization formula

For each proposal, use this structure:

owner-comparable exposure = stated bid total - included allowance amount + clarified replacement amount + priced exclusions + owner-supplied procurement exposure + explicit conditional scope

The formula is a recordkeeping model, not a market estimate. Use it only after each term is defined. If an allowance is already enough for the final scope, its adjustment is zero. If a proposal includes an allowance for one product but the approved design requires another product, replace the allowance with the written scope and record who approved the substitution.

For a quantity allowance, also record:

allowance adjustment = (final quantity - included quantity) × agreed unit rate + product or mobilization difference

Do not use that formula if the bid has no agreed unit rate or if the work changes the design. In that case, request a change proposal or design clarification.

Illustrative sensitivity using neutral cost units

The following is an illustrative modeled example, not a contractor quote or a market price. “Cost units” are placeholders so the arithmetic can be checked without implying that foundation work has a universal price.

Suppose two proposals describe the same approved foundation geometry:

Assume the clarification log later assigns the same drainage outlet to both proposals at 6 units and establishes that Bid A's export allowance is likely to need 16 units under the defined quantity basis. The normalized exposure is:

• Bid A: 100 - 12 + 16 + 6 + 5 = 115 cost units.
• Bid B: 92 - 0 + 16 + 0 + 0 = 108 cost units if Bid B's original exclusion is separately priced at 16 units and its drainage outlet is already included at 6 units.

That arithmetic is only illustrative. It does not say either proposal is cheap, expensive, or appropriate. It shows why the original 8-unit subtotal gap can shrink or reverse when one allowance and one exclusion are put on the same scope basis.

Now test sensitivity rather than choosing a single optimistic figure. If Bid A's export quantity could resolve at 12, 16, or 22 units, the total changes by:

normalized Bid A = 100 - 12 + export quantity + 6 + 5

The decision is not “use 12 because it is in the bid.” The decision is “what evidence will distinguish 12 from 16 or 22?” The answer may be a survey, geotechnical observation, civil quantity, haul ticket, defined over-excavation trigger, or written unit price. If no evidence can be obtained before award, retain the range in the budget and define the approval path.

Allowances need a scope, unit, and reconciliation rule

Ask these questions for every allowance:

• What physical work does the allowance cover?
• Is the amount for material, labor, equipment, delivery, tax, disposal, testing, or all of them?
• What quantity or unit does it assume: cubic yards, linear feet, square feet, loads, hours, or a product package?
• What unit price applies above or below the allowance?
• Who selects the final material or method?
• When must the decision be made so procurement and inspections are not delayed?
• Is unused allowance credited, and are approved overages added at cost, unit rate, or a markup?
• Does the allowance include the record or testing needed to close the scope?

An allowance for “rock” with no unit, trigger, disposal route, or approval authority is not a usable budget line. An allowance for “waterproofing” with no product or coverage can mask a compatibility problem. An allowance for “inspection” with no authority or testing scope can create a schedule and compliance gap.

Excavation is a site-risk package, not a single number

Excavation assumptions deserve their own meeting because they affect safety, structural stability, drainage, environmental controls, neighbors, utilities, and cost. Ask the excavator or GC to describe:

• Layout and how the excavation limits are established.
• Soil and groundwater assumptions from the geotechnical and civil information.
• Whether the excavation is expected to require sloping, benching, shoring, or shielding.
• How spoil piles, equipment, traffic, and adjacent structures are kept from creating unsafe surcharge conditions.
• Who handles rain, runoff, groundwater, pumping, discharge, and erosion control.
• What counts as unsuitable soil, rock, buried debris, or an unforeseen obstruction.
• The disposal site, haul distance basis, load-ticket record, and any contaminated-soil procedure.
• What temporary condition is maintained until footings or other permanent support are in place.

OSHA's excavation protective-system standard requires covered employees in an excavation to be protected from cave-ins by an adequate protective system, with limited exceptions including stable rock or an excavation less than 5 feet deep where a competent person finds no indication of a potential cave-in. This is a worker-safety boundary for the employer and site team, not a homeowner's permission to inspect the hole. A bid should identify who provides and manages the protective system; it should not invite the homeowner to decide whether an excavation is safe.

OSHA's Trenching and Excavation Safety fact sheet also describes inspection at the start of each shift and after rain or water intrusion and safe access and egress requirements within the standard's stated conditions. If a proposal assumes that the owner will enter the excavation to measure it, photograph it, or approve the subgrade, reject that handoff. Ask for contractor, geotechnical, survey, or inspection records instead.

Do not trade safety for a cleaner comparison

Some construction responsibilities cannot be made homeowner tasks merely because they are missing from a bid. Do not enter an excavation, stand beneath unsupported soil, approach equipment in operation, work near suspended loads, or direct a worker's protective-system decision. Do not operate pumps or electrical equipment in wet conditions unless the qualified site team has made the area safe. Keep children and visitors out of excavation and material-storage areas.

The safest homeowner actions are document review, written questions, accessible observations from outside controlled work zones, photographing exposed work only with permission and safe access, and retaining records. Excavation, dewatering, shoring, structural work, concrete placement, electrical connections, and testing belong to qualified professionals under the applicable safety program and jurisdiction.

The next decision is whether each unresolved cost is a priced scope, a bounded allowance, an owner procurement, or a reason to delay award until the site or design question is resolved.

Assign responsibility through every handoff #

A foundation proposal is ready for award only when each material action has one accountable party, one verification record, and one next handoff; “by others” without an identified successor is an unowned gap.

Responsibility is different from performance

The person who performs work is not always the person who coordinates it. For example, a waterproofing installer may apply the membrane, while the general contractor schedules the inspection, ensures penetrations are ready, protects the surface, and releases the excavator to backfill. The owner may select an alternate product, but the design professional or qualified installer may need to confirm compatibility and the authority may need to approve a change.

Use these role descriptions as a starting point, then replace them with names in the contract:

These assignments are not a substitute for the contract or local rule. They prevent a common failure in which everyone assumes that someone else will schedule the inspection, seal a penetration, protect a membrane, provide a drain outlet, or record the concealed condition.

The handoff ledger

Use one ledger row for each gate. “Complete” means the assigned person has supplied the stated record, not that the homeowner has glanced at the work.

The ledger should travel with the project record. If the general contractor uses a construction-management platform, put the row ID and link or file name in the worksheet. If the project uses paper, assign a binder tab and date. A photograph without location, date, plan revision, or description is weaker than a photograph tied to a row and gate.

Use stop-and-ask triggers

Pause the affected handoff and ask for written direction when:

• The excavation exposes soil, rock, water, buried debris, or neighboring conditions different from the bid basis.
• The foundation location, elevation, step, opening, or penetration does not match the current plan.
• Reinforcement, embeds, sleeves, or anchor items are missing or cannot be verified before concrete.
• The inspection is requested before the prerequisite work is complete or the inspector cannot access the approved plan set.
• The concrete contractor proposes a field change affecting a structural detail.
• The surface is wet, frozen, dirty, damaged, or not ready for the specified waterproofing product.
• Drainage, sump, outlet, or protection work is missing but backfill is being proposed.
• Insulation or vapor-control placement differs from the climate-specific assembly or product instruction.
• A bidder says “we will fix it after backfill,” when the fix would be concealed or inaccessible.

The response should identify the issue, responsible decision-maker, safety or design impact, revised scope, evidence needed, and release condition. A verbal assurance can be useful for immediate coordination, but it should be captured in the project record before the next irreversible step.

The next handoff is from responsibility to verification: decide what the homeowner can observe, what a professional must inspect, what the authority must approve, and what record must exist before cover.

Align inspection gates and verification records #

The inspection plan belongs in the bid comparison because the foundation changes from visible to concealed in stages, and the responsible local authority—not a generic article—sets the required gates. The proposal must show who schedules each gate, what must be ready, and what happens if work is not accepted.

Local examples, bounded correctly

For Seattle, Washington, the SDCI residential quick-sheet page identifies a setback/foundation inspection before concrete placement and later inspections before floor framing or other work is covered. Use that information to ask a Seattle project team to map the approved plan and foundation package to SDCI's current sequence. Do not copy the Seattle sequence into a different municipality or assume the list is complete for a special condition.

For Austin, Texas, Austin Development Services says inspections are coordinated after permit activation, scheduled by the contractor, and supported by access to the latest approved plan set and required documents. Its page also states that prerequisite inspections should be complete before requesting a final building inspection or certificate. Use those instructions for an Austin permit record, and verify the current local requirements before publication or construction because an active permit, project type, and adopted code path matter.

For all other locations, record the actual authority and ask it or the permit holder for the current inspection flow. Do not write “code requires” in the worksheet unless the specific code, jurisdiction, and scope have been verified. A contractor's habit, an inspector's informal comment, a product instruction, and a legal requirement are different kinds of evidence.

Map the gates to the work, not just the calendar

Foundation inspections are dependency gates, not generic calendar appointments. Build the sequence around the condition that must be visible:

1. Before excavation or mobilization: confirm permit, survey, access, utility locating, site protection, and the employer's safety controls.
2. At exposed subgrade: confirm the designed location and field condition through the person responsible for geotechnical or design observation when required.
3. Before footing concrete: verify layout, dimensions, forms, reinforcement, steps, embeds, sleeves, and local inspection prerequisites.
4. Before wall or pier concrete: verify current wall geometry, reinforcing, openings, penetrations, embeds, joints, and required inspection.
5. Before closing underslab or crawlspace work: verify fill, drainage, capillary or vapor control, insulation, sleeves, grounding or utility interfaces, and required tests or inspection.
6. Before waterproofing or protection is concealed: verify surface preparation, repairs, exact product, penetrations, terminations, coverage, drainage, and protection.
7. Before backfill: verify that required authority or special inspection is complete, the drain works, the membrane or system is protected, product timing permits backfill, and photographs or records are filed.
8. Before structural handoff: verify finished foundation elevations, open changes, drainage and grade responsibilities, plan revisions, inspection results, and the document package for framing or the next trade.

This is a coordination map, not a promise that your authority uses these exact names. Insert the actual local gate in each row. If no local inspection covers an item, the project team should still decide who verifies it and what record is retained.

Decide what counts as proof

Evidence should answer “what, where, when, and against which basis?” A useful verification record can include:

• A dated inspection result with comments and permit or project identifier.
• A pre-cover photograph that shows the location and a reference dimension or recognizable plan feature.
• A product label, batch or lot record, current installation instruction, and application log.
• A delivery ticket, test report, unit ticket, or disposal receipt where the contract requires it.
• A field observation or geotechnical report tied to the location and condition.
• A marked-up plan or RFI response showing the approved change.
• A signed checklist from the responsible trade and the GC's release record.
• A final grade or drainage record where the design or local authority requires one.

Do not use a photograph to prove a property it cannot show. A wide image may show that a drain exists but not its slope, outlet, connection, or continuity. A product bucket may show a brand but not coverage or thickness. A passed inspection confirms only what that inspection is authorized to evaluate; it does not transfer all design and warranty responsibility to the building official.

Do not backfill on a verbal release

Backfill is an irreversible handoff for many concealed items. Before the excavator begins, the ledger should show:

• Drainage installed, connected, and in the condition the approved design requires.
• Waterproofing, dampproofing, drainage board, or exterior insulation complete for the specified assembly.
• Penetrations, corners, joints, repairs, terminations, and protection documented.
• Any local inspection or special inspection passed or expressly resolved.
• The exact backfill material, equipment, sequence, and wall-protection method assigned.
• Weather, groundwater, and site access conditions acceptable to the qualified contractor.
• A photo and document record saved under the correct plan revision.

If any item is unresolved, the next action is not for the homeowner to inspect the trench. Ask the GC or qualified trade to state what is missing, who decides, and how the record will be closed. If the issue affects design, send it through the design professional. If it affects an authority's requirement, contact the authority or permit holder.

The next decision is whether the specified moisture, thermal, and backfill assemblies can be installed in the sequence shown by each bid.

Check moisture, insulation, and backfill as one assembly #

Compare the foundation's water, thermal, and soil-contact scope as a connected assembly: keep water away, provide drainage, manage capillary and vapor movement, meet the project's climate-specific thermal requirements, protect products, and assign the final-grade and maintenance handoff. A membrane line item alone is not a complete moisture strategy.

Ask what keeps water away and where it goes

Building Science Corporation describes a water-managed foundation as keeping rain away from the foundation perimeter and draining groundwater with sub-grade perimeter footing drains. It distinguishes dampproofing from waterproofing and describes free-draining backfill or drainage boards as drainage measures in its Groundwater Control information sheet. Use that as a system-level comparison question, not as a universal product specification.

For each bid, trace the expected water path:

• Where does roof and surface water go during and after construction?
• What prevents water from collecting against the wall perimeter?
• Where does groundwater enter the drain system, and where does the drain discharge?
• Is there a sump, daylight outlet, pump, backup, cleanout, or maintenance access, and who owns it?
• What is the capillary break or vapor-control layer under a slab or crawlspace floor?
• What happens at wall-to-footing joints, steps, corners, penetrations, sleeves, and porch or garage transitions?
• What protects the moisture-control layer from equipment, rocks, form ties, backfill, landscaping, and later utility work?
• Who maintains the outlet, grade, sump, gutters, and surface drainage after handover?

If a bidder says “waterproofing included” but does not show drainage, outlet, penetrations, or protection, ask whether they are pricing a barrier or a complete water-management scope. Do not assume that a coating can compensate for missing drainage or poor final grade.

Product instructions can change the handoff timing

If the design names Mar-Flex 5000 WB, compare the bid against the Mar-Flex 5000 WB residential installation instructions, not against a generic phrase such as “waterproof foundation.” The instructions identify the product as an exterior below-grade residential membrane, call for clean and dry walls, say poured concrete walls must be set, and require existing penetrations to be sealed. When the optional board or roll is used, the instructions say it should be installed immediately after membrane application to each section.

The same instructions state that backfilling should begin no sooner than 24 hours after application, must occur within 15 days, should use suitable fill free of debris and harmful material, requires foundation drainage to be installed and working, and says final grade must not rise above the membrane or system. They also list a minimum one-half-inch-per-foot slope away from the structure for the first 12 feet. These are product-specific instructions, not a national backfill rule. A different product may have different substrate, temperature, coverage, protection, and timing conditions.

This product check creates questions for the proposal:

• Did the bidder name the exact product version and application method?
• Who removes or patches ties, voids, honeycombs, ledges, and other surface defects before application?
• Who seals existing and newly added penetrations, and when are those penetrations complete?
• Who records coverage or wet-film/dry-film information if the product instructions require it?
• Who installs the board, roll, or insulation immediately after application when specified?
• What does the bid do if weather makes the wall wet or frozen, or if the product's timing window is missed?
• Who decides whether a damaged surface is repaired or the work is rejected before backfill?

Do not shorten a product's stated window to meet a schedule promise, and do not extend it to suit a contractor's sequence without written product-specific confirmation. If the specified product changes, update the worksheet, the handoff ledger, the warranty record, and any inspection requirement.

Match insulation to climate and moisture control

Insulation is not an interchangeable add-on. The DOE Building America climate-specific guidance points to a 2021 IECC Climate-Specific Building Assemblies Tool that looks up climate zone by county or ZIP code and provides foundation, wall, and roof assembly drawings for 2021 IECC and IRC envelope requirements. Use the actual project location to identify the climate basis, then verify the adopted energy code and local amendments with the permitting authority.

The DOE High-R Foundations guidance says foundation insulation levels are tied to climate zone and that effective installation avoids gaps, voids, compression, and misalignment with air barriers; it also calls for attention to moisture management when rigid foam or spray foam is installed inside basement walls. Those statements do not select your home's assembly. They tell you what to require in the comparison: a climate and code basis, exact product and thickness, continuous-air-barrier relationship, terminations, protection, and a record before cover.

For each insulation line, record:

• Surface: exterior wall, interior wall, slab edge, under slab, rim, crawlspace wall, or floor above unconditioned space.
• Climate zone and code basis used by the bidder.
• Product, thickness, R-value or U-value basis, facing, permeance, and fire or ignition protection where required.
• How seams, corners, penetrations, transitions, and fasteners remain continuous.
• How the insulation is protected from moisture, termites or other pests, impact, and later trades.
• Which inspection sees it before it is covered.
• Whether the proposal includes repair of damaged or compressed areas.

The DOE basement-insulation profile notes that exterior basement insulation must be protected from moisture during installation and may be unsuitable where termites are a problem. It describes interior insulation as requiring airtight installation and semi-permeable vapor control so moisture can dry toward the interior. Treat those as reasons to compare assembly behavior and local pest or code constraints, not as permission to copy an old detail into a new home.

Check vapor-control location, not just material name

The DOE guidance on vapor retarders for basements says the retarder should be selected for climate and location and should not trap moisture. It specifically cautions against placing Class I vapor retarders interior to fibrous insulation in basement and crawlspace assemblies and gives a conditional foam example tied to permeance and vapor-permeable finishes.

Therefore, a bid that says “poly vapor barrier” or “foam insulation” is incomplete until the assembly location and product data are known. Ask:

• Is the layer under the slab, on the exterior wall, on the interior wall, within a framed wall, or on the crawlspace ground?
• Is it a capillary break, vapor retarder, air barrier, waterproofing layer, or more than one of those?
• What climate and code basis supports the location?
• What is the product's permeance at the installed thickness?
• What happens at seams, walls, piers, pipes, conduits, drains, and slab penetrations?
• Is a finish, ignition barrier, or protective layer required?
• Which trade installs and verifies the transition to above-grade air and water control layers?

Do not infer compatibility from a product's name, color, or generic R-value. Request the current data sheet and installation instruction for the exact product, then ask the design professional or qualified building-science professional to resolve an assembly question.

Crawlspace floors need their own row

If the proposal includes a crawlspace, do not let the floor disappear into “foundation concrete.” DOE Building Science Education explains that soil can introduce liquid water or vapor into a crawlspace and lists a continuous ground-cover example with at least 6-mil polyethylene, sealed seams, sealed pipe penetrations, and a lap up walls and piers. See Crawlspace: Capillary Break at Crawlspace Floors.

Use the approved assembly and local requirements to decide whether the listed example is the project specification. In the worksheet, separate:

• Prepared crawlspace subgrade and drainage.
• Ground cover or capillary break product and thickness.
• Seam and perimeter sealing.
• Piers, walls, utility penetrations, and future access points.
• Whether the space is vented, unvented, conditioned, or otherwise treated in the approved design.
• Insulation and air-sealing boundary.
• Radon or soil-gas provisions where the design or local requirement calls for them.
• Inspection or photo gate before the next floor or framing work.

The point is not to tell a homeowner to seal a crawlspace personally. It is to stop a low bid from omitting the floor moisture boundary or assigning it vaguely to “framing.”

Backfill is a protection and drainage handoff

Backfill should appear as a separate scope row because it can damage the wall, drain, membrane, board, insulation, outlet, or final grade. Compare:

• Fill source, cleanliness, particle size or other product/design requirement.
• Whether the bid includes import, export, screening, rock removal, and disposal.
• Lift or placement method specified by the design or qualified contractor.
• Equipment restrictions near the wall and the protection method used.
• Drainage-layer continuity and connection to the outlet.
• Inspection and photo release before soil covers the system.
• Temporary and final grade, surface-water routing, and restoration.
• Who returns to repair settlement, blocked drainage, exposed membrane, or grade defects within the contract or warranty boundary.

If the bid uses a generic “backfill with native soil,” ask whether native soil is suitable for the specified drainage and product-protection function. If the product instruction requires debris-free fill or a specific timing window, put that requirement into the subcontract scope and handoff ledger.

The next handoff is a written award package: the selected proposal, clarification log, allowance schedule, exclusions assignment, inspection map, product records, and ledger must all agree.

Award the proposal and manage failure branches #

Award the foundation package only after one proposal has a closed scope, an explicit responsibility map, a local inspection plan, product-compatible sequencing, and a written process for site conditions that differ from the bid basis. The winner is the proposal with the clearest controlled exposure, not automatically the lowest initial number.

Use a decision matrix rather than a score made of vibes

Score only after normalizing the rows. A simple matrix can use “pass,” “clarify,” or “not acceptable for award” rather than pretending that a precise score measures engineering quality.

A “pass” means the proposal is documented enough to move to contract review. It is not a structural approval or a guarantee of performance. A “clarify” item may be easy to close. A “do not award yet” item means the bid is not ready for a fair comparison.

Failure branch: the lowest bid omits drainage

If the lowest proposal omits foundation drainage, do not compare its subtotal against a complete proposal. Ask whether the omission is intentional, where the drain is shown in the design, who installs the pipe and outlet, how it is verified, and whether the omission changes waterproofing, backfill, sump, or final-grade responsibilities.

If the answer assigns drainage to the GC or another trade, add a written row, price or allowance, inspection gate, and next handoff. If no qualified party accepts it, the proposal is incomplete. If the alternate drainage method changes design intent, send it to the design professional and the permitting authority as applicable.

Failure branch: soil or groundwater differs at excavation

If the actual site differs from the report or bid basis, keep workers out of unsafe conditions and stop the affected work through the qualified site team. Ask the GC to document the location, condition, immediate protection, and proposed decision path. Ask the geotechnical or design professional for the field interpretation within their engagement. Reconcile the change with a written scope and price basis before proceeding.

Do not allow a homeowner to make a bearing, shoring, slope, dewatering, underpinning, or foundation-dimension decision from a photograph. OSHA's excavation standard places protective-system requirements on covered employers and requires adequate protection from cave-ins within its stated scope. Your role is to preserve the record and ensure the responsible professionals are engaged.

Failure branch: inspection is delayed or fails

If the inspection cannot occur because work is incomplete, the site is inaccessible, the approved plan is unavailable, or conditions are unsafe, reschedule through the permit holder or contractor according to the actual jurisdiction. Do not cover the work to protect the schedule. Record the inspector's comments, correction owner, new gate date, and any effect on the next trade.

Austin's current building-inspection page says the contractor schedules inspections, that the latest city-approved plan set should be available on site, and that supporting documents may help inspectors verify compliance. Seattle's quick-sheet page explains the purpose and sequence of its residential inspection checkpoints. These local examples show why “inspection included” is not enough; the award package must assign scheduling, access, plans, documents, corrections, and release.

Failure branch: waterproofing is ready but the wall is not

If a named product requires a clean, dry, set, or otherwise prepared surface and the wall is wet, frozen, damaged, or incomplete, do not approve an application merely because the excavator is waiting. Use the product's current instructions, the qualified installer, and the GC's sequence to define the remedy. For Mar-Flex 5000 WB, the manufacturer instructions identify substrate preparation, penetrations, and timing conditions that should be reflected in the bid and ledger.

Record whether the remedy is surface repair, drying, a product-approved change, a rescheduled application, or a design clarification. Record who pays and who verifies. Do not treat a later interior sealant or paint as an automatic substitute for a missed exterior moisture-control step.

Failure branch: bids use different insulation locations

If one bidder prices exterior foundation insulation and another prices interior insulation, do not normalize them as equivalent square feet. Compare climate-zone basis, moisture behavior, air-barrier continuity, vapor-control location, termite or pest constraints, fire or ignition protection, finish boundary, and future repair access. DOE's climate-specific guidance, High-R Foundations page, and basement-insulation profile support treating those as assembly questions rather than interchangeable products.

Send a changed assembly to the design professional and, where needed, the code or energy reviewer. Ask the bidder to price the approved alternate after the assembly is resolved. A spreadsheet can reveal a difference; it cannot approve an envelope design.

Failure branch: backfill is proposed before records are closed

If backfill is scheduled before inspection, drainage, waterproofing, protection, or product timing is resolved, move the handoff date. Ask the GC for the release checklist and the excavator for the planned material and method. If the exact product is Mar-Flex 5000 WB, compare the timing and drainage conditions with the current manufacturer instructions; do not use a generic schedule assumption.

Take pre-backfill photographs from safe locations with permission, but do not enter the excavation or direct the crew. Store the images with the plan revision and row IDs. If the work is already covered, record the lost verification and ask the responsible contractor what alternative record or investigation is available; do not claim that an inaccessible condition has been verified.

Contract language to request before signing

Ask for a final exhibit or scope clarification that contains:

• Plan and specification references, revision date, and defined foundation boundary.
• Included quantities, units, products, and performance requirements.
• Allowance schedule with quantity, unit, inclusion, unit rate, markup, reconciliation, and approval authority.
• Exclusions with named successor, date, dependency, and budget path.
• Site-condition triggers for rock, unsuitable soil, groundwater, buried debris, access loss, and weather delay.
• Inspection and special-inspection responsibilities for the actual permitting jurisdiction.
• Pre-pour, pre-cover, waterproofing, insulation, drainage, and pre-backfill release requirements.
• Product submittals and current installation instructions for named moisture and insulation products.
• Change-order, RFI, and design-clarification process, including who can authorize work.
• Record package: inspection results, photos, tickets, tests, product records, warranties, and as-built or closeout information.
• Safety boundary stating that excavation and structural work are performed by qualified site personnel under the applicable safety program.

Do not sign a scope that says “all standard foundation work” if the work boundary is the subject of the comparison. Define “standard” or remove the word.

The next decision after award

The next decision is not “wait for concrete.” It is whether the pre-mobilization release is complete. Before work begins, the owner or GC should confirm the contract exhibit, current approved plan set, permit status, survey/layout, access and utility controls, site safety responsibilities, product submittals, inspection contacts, and the first handoff record. The selected foundation contractor should confirm receipt and return a list of conflicts rather than silently pricing assumptions.

At each subsequent gate, ask the same four questions:

1. What must be true before this work starts?
2. Who is responsible for doing and verifying it?
3. What record proves it before it is concealed?
4. What next trade or authority receives the handoff?

If a row has no answer, it belongs in the clarification log before the next irreversible action.

Use the worksheet at the bid meeting and on site

The worksheet is most useful when both bidders complete it before award and the same ledger continues through construction. A document that is used only to rank totals cannot protect a concealed drain, an inspection gate, or an unowned exclusion.

Send the same request to every bidder

Give each bidder:

• The same drawing set and revision list.
• The same geotechnical, survey, civil, climate, and permit information.
• The same foundation scope rows.
• The same definitions for included, excluded, allowance, owner-supplied, and unresolved.
• The same request for quantities and units.
• The same questions about drainage, waterproofing, insulation, penetrations, inspection, backfill, records, and warranty.
• The same deadline for questions and the same process for addenda.

If one bidder receives a field answer or revised detail, distribute it to all bidders. Otherwise, later price differences may reflect unequal information rather than contractor value.

Bid return checklist

Request these attachments or written responses with the proposal:

• Bid-basis sheet naming plans and revisions.
• Scope table with every row marked included, excluded, allowance, owner-supplied, or unresolved.
• Quantity schedule and units for excavation, concrete, reinforcement, drains, membranes, insulation, and backfill.
• Product names and current instructions for waterproofing, drainage board, insulation, vapor control, and sealants.
• Site-condition assumptions and change triggers.
• Inspection and special-inspection map for the actual jurisdiction.
• Responsibility matrix and handoff ledger starter.
• Allowance schedule and unit rates.
• Exclusions list with successor and due date.
• Safety and access responsibilities.
• Record and closeout list.
• Proposed clarification questions and alternates.

An answer such as “included as standard” is a prompt for a definition, not a completed row. Ask for the drawing detail, quantity, product, responsible party, and verification record.

Homeowner review procedure

Run this procedure in order:

1. Highlight every material phrase that appears in only one proposal.
2. Mark every blank or silent row unresolved.
3. Convert each exclusion into a named responsibility or a budget exposure.
4. Replace every allowance with its unit, quantity, authority, and reconciliation rule.
5. Check plan revisions and quantities against the same approved design.
6. Trace every moisture and thermal row through product, substrate, protection, inspection, and backfill or close-in.
7. Trace every concealed row to a record before the next gate.
8. Ask the qualified professional about any structural, soil, excavation, or assembly conflict.
9. Recalculate normalized exposure and show sensitivity where a condition remains uncertain.
10. Award only after the final clarification exhibit matches the contract and ledger.

The homeowner does not need to know the correct structural answer to identify an incomplete proposal. The useful question is often, “Who is responsible for answering this, what document will answer it, and before which work must the answer be recorded?”

Keep records through handover

Foundation decisions affect framing, insulation, drainage, landscaping, maintenance, and future repairs. Retain:

• Final approved plan set and all foundation-related revisions.
• Geotechnical reports, field observations, surveys, and approved clarifications.
• Bid comparison, contract scope, allowance reconciliation, exclusions assignment, and change orders.
• Inspection results, special-inspection records, tests, concrete tickets, disposal tickets, and product submittals.
• Pre-cover photographs identified by location, date, plan revision, and row ID.
• Waterproofing, drainage, insulation, vapor-control, backfill, and final-grade records.
• Warranty terms, maintenance responsibilities, outlet or sump information, and contact names.

The future homeowner or maintenance provider may need to know where a drain outlet, penetration, membrane transition, sump, insulation layer, or utility sleeve is located. A clear record now is less invasive than trying to discover concealed work later.

Final award test

Select the proposal that passes this sentence without qualifications:

“For the same approved plan and documented site assumptions in [actual jurisdiction], this proposal states what is included, excluded, allowed, or owner-supplied; identifies who owns each unresolved decision; prices or bounds each exposure; names the inspection and product sequence; and provides a record before every concealed handoff.”

If you cannot complete the sentence, keep comparing the scope. If the proposals are now comparable but one is still higher, ask whether the difference buys a documented method, stronger coordination, a better-defined site-risk boundary, an appropriate assembly, or a clearer record. If neither proposal is complete, request revisions from both or engage the appropriate qualified professional before award.

This is the practical endpoint of a foundation-bid comparison: not a universal foundation winner, but a defensible next decision with visible assumptions, named responsibility, verified gates, and no silent scope left between excavation and the structural stage.