Compare foundation repair estimates by first making their scopes equivalent. Two totals may represent different repair areas, methods, quantities, access plans, restoration responsibilities, plumbing or drainage assumptions, warranty terms, and exclusions. Price becomes meaningful only after those differences are visible.
Create a side-by-side worksheet and ask each company to explain its recommendation using the property evidence. More supports do not automatically mean a better plan, and a lower total does not automatically mean better value.
If you need a market-level reference before comparing written proposals, review the Dallas-Fort Worth foundation repair pricing guide. Keep those published planning ranges separate from the property-specific scope described in each estimate.
Begin with the inspection evidence
List the measurements, cracks, opening changes, exterior observations, foundation type, additions, drainage conditions, plumbing indicators, and prior work cited by each evaluator. If one proposal does not explain how its scope follows the inspection, ask for clarification before comparing methods.
Questions include:
- Which areas show the movement pattern?
- Which areas were inaccessible?
- What reference point was used for floor elevations?
- Are the measurements recent and comparable?
- Does the recommendation depend on plumbing testing or another specialist?
- Is monitoring a reasonable alternative?
If the evidence remains inconsistent, consider when a second foundation opinion helps.
Map every proposed repair location
Ask for a drawing that identifies each repair point, support line, beam, or work area. Confirm whether interior points, exterior points, porches, garages, chimneys, additions, or detached improvements are included.
Two estimates with the same quantity can still address different parts of the structure. Two estimates with different quantities may use different spacing, methods, or interpretations of the movement pattern. Ask why each location is necessary and what objective it supports.
Compare the repair method and installation scope
Record the named method, materials, installation process, verification method, and intended result. If proposals use steel piers, concrete piers, pressed components, drilled elements, helical systems, shims, beam work, or other terms, ask for a plain-language explanation.
The steel pier versus concrete pier guide can help organize questions, but the property inspection must still determine which methods are practical.
Separate drainage and plumbing responsibilities
One proposal may include drainage work while another treats it as a separate recommendation. One may require plumbing testing before or after adjustment while another excludes it.
Compare:
- Suspected leak findings and who performs testing
- Timing of plumbing tests or repairs
- Roof runoff, grading, low areas, and discharge observations
- Proposed drainage system and outlet
- Whether drainage work is required before structural work
- Utility locating and protection responsibilities
Do not assume a structural scope resolves water management or that drainage work replaces a supported structural recommendation.
Identify access and restoration differences
Interior excavation, concrete openings, crawlspace limitations, fences, decks, landscaping, pools, paving, utilities, furniture, and occupied spaces can change the work. Ask who provides access and who restores each affected surface.
Include soil handling, dust control, floor protection, concrete patching, landscaping, plumbing access, finish repairs, cleanup, and debris removal in the comparison. Verbal restoration promises should appear in the written scope.
Compare schedule assumptions
Record the expected start window, on-site duration, weather allowances, concrete or finish timing, inspection or engineering dependencies, and conditions that could delay completion. The guide to foundation repair timelines explains why project days and total calendar time can differ.
Ask how the property will be secured if work pauses and how occupants will access the building during the project.
Read warranty documents, not warranty labels
Compare the actual written warranty terms: covered work, duration, exclusions, maintenance requirements, transfer process, fees, claim steps, inspection rights, adjustment limits, and the legal entity responsible. “Lifetime” or “transferable” is not enough information.
Use the foundation repair warranty guide to build a document checklist. Verify that the company name on the warranty matches the contracting party.
Review exclusions and change orders
Highlight every exclusion. Common categories can include plumbing, drainage, utilities, landscaping, finish damage, hidden conditions, mold or pests, framing, engineering, permits, concrete color matching, and conditions outside the repair area.
Ask how unexpected conditions are documented, priced, and approved. A low estimate with broad exclusions may create different financial risk than a higher estimate with a more complete defined scope.
Compare payment and financing separately
List deposits, progress payments, final payment triggers, accepted methods, financing fees, interest, promotional terms, and cancellation conditions. Compare the total amount paid, not only the monthly payment.
Financial terms do not establish repair quality. Review them after scope and contract comparison, and seek appropriate advice for legal or lending questions.
Use a final comparison checklist
Before selecting a foundation repair proposal, confirm that each estimate clearly addresses:
- Inspection evidence and limitations
- Repair objective and locations
- Method, materials, and quantities
- Drainage and plumbing dependencies
- Access, protection, and restoration
- Engineering, permits, and specialist roles
- Schedule and delay assumptions
- Warranty terms and exclusions
- Change-order process
- Payment terms and total price
Review what affects foundation repair cost and what a repair proposal should include before signing. A fair comparison should make the evidence and obligations clearer—not simply identify the lowest number.