A Framework for Measuring Make Ready Cost Variance

Published October 12, 2026

Comparing final invoice totals with an initial estimate can mislabel legitimate scope changes as poor performance and hide rework inside a larger project. A useful cost-variance study starts at the scope-line level, preserves condition evidence, and separates quantity, price, scope, delay, and correction effects. It supports management review but does not determine the technical necessity of a repair.

Define the comparison baseline

Freeze the approved original scope, quantities, unit assumptions, taxes, permits, travel, disposal, contingency, and schedule. Record who approved it and when. Establish rules for alternates, allowances, owner-supplied materials, and emergency work. A budget assembled after work begins is not a valid original baseline.

Create a variance taxonomy

Classify differences as quantity, unit price, omitted condition, approved scope enhancement, jurisdiction requirement, access or travel, schedule effect, vendor error, owner change, rework, or unresolved. Permit multiple contributing codes with one primary code. Do not force unknown causes into vendor performance categories.

Normalize home and project context

Capture home age band, size, occupancy state, location, move status, utility availability, initial inspection completeness, project type, and major system categories. These fields support cautious stratification; they do not create perfect comparability. Sparse groups should be combined or described rather than ranked.

Reconcile financial evidence

Match purchase orders, contracts, approved changes, delivery receipts, time records where applicable, invoices, credits, and payments to scope lines. Preserve tax and overhead treatment. Report both gross and net changes and identify costs that shifted to another project or accounting period. Sample reconciliations back to source documents.

Measure more than the final total

Report variance amount and percentage, change-order frequency, estimate-to-start time, active duration, rework rate, unresolved closeout value, and evidence completeness. Use medians and ranges alongside totals. A favorable cost variance paired with missing work or an extended vacancy is not automatically a favorable operational outcome.

Use results for controlled improvement

Inspect recurring variance codes and representative files before changing estimator rules, vendor panels, contingencies, or approval thresholds. Pilot one change at a time and monitor safety, quality, resident impact, and cycle time. Findings describe the observed portfolio and period, not a universal repair-cost benchmark.

Reproducibility package

For the mobile-home-make-ready-cost-variance-framework protocol, retain the approved question, version, data dictionary, source inventory, extraction timestamp, cleaning log, eligibility flow, calculation code or steps, quality-review notes, disclosure review, and final tables. A second qualified reviewer should be able to reproduce the reported values or identify precisely which source is no longer available. Record deviations rather than quietly adapting definitions after seeing results.

Public sources and context

• GAO Cost Estimating and Assessment Guide, public context for definitions, controls, or study design; local applicability requires review.
• HUD Manufactured Housing Programs, public context for definitions, controls, or study design; local applicability requires review.
• NIST measurement resources, public context for definitions, controls, or study design; local applicability requires review.

The sources above provide context for A Framework for Measuring Make Ready Cost Variance, not validation of an operator-specific result. Source pages can change, so preserve access dates and the version used.

Conclusion

Scope-level variance analysis helps leaders distinguish estimation error from changed facts. Its strongest output is a documented question for review, supported by reconciled evidence, rather than a simplistic league table of homes or vendors.