Residential remodeling / general contractors Operations Questions

The questions that recur in residential remodeling share one shape: commitments are made before discovery is complete, and the contract is asked to absorb what sequencing should have prevented. The same pattern appears in estimating models that stop being true past a size threshold, and in milestones that reward starting over finishing. The corrections below are structural rather than contractual.

• Change-order disputes cluster on jobs where clients selected finishes before demolition revealed structural conditions. Contract language or discovery process?

  The discovery process. Finish selection is an Activity scheduled before its true predecessor, demolition-based discovery, could define its input Specification. The precedence graph is broken, so the contract is asked to absorb what sequencing should have prevented. Make demolition a hard predecessor with a priced allowance gate.

  §3.2 predecessors, §9 CPM, D5, A8

• When a project goes sideways, is the first signal in job-costing reports or the client's tone of voice?

  The client's tone. Job-costing reports are lagging measuredBy KPIs on completed work. The client's tone is a real-time Event signaling a StateChange. The fix is not to abandon cost reports but to instrument leading process states (schedule slip, RFIs aging) so control is not outsourced to the customer's emotions.

  §0.3 measuredBy, §0.1 Event/State, §7 real-time execution & control

• Referrals from past clients convert far better than realtor referrals, yet the relationship budget goes to realtors. What is the budget optimizing for?

  Measurability, not conversion. A textbook Goodhart distortion: the channel with an attributable line item wins the budget regardless of order-winning power. Reallocate by conversion-weighted margin per channel, not spend visibility.

  §13 incentive-induced gaming / Goodhart, §1.1 OrderWinner, §1.3 performance measurement

• Our best carpenters produce their worst work in the final 10% of jobs. What does the punch-list sequence reward?

  Starting, not finishing. Payment and scheduling milestones treat substantial completion as the terminal Event, so the punch list is NVA work nobody is incentivized to close. Earned value is declared before value is actually earned. Tie final payment and crew release to punch-list closure.

  D3 VA/NVA, §13 incentives, §9 EVM

• Which subs cause cascading schedule slips we absorb as reputation damage instead of billing back, and why have we never measured it?

  Because no supplier scorecard exists. Slip propagation is an unmeasured external failure cost transferred to you by a coordination failure. Assign each sub a delay-cost ledger. What gets measuredBy gets negotiated.

  §11.2 supplier management/scorecards, §6.2 CoQ external failure, A8 traceability

• Would margins improve more from an 8% price rise or firing bottom-decile clients, and why cannot our books answer that?

  The books lack customer-level cost allocation. Revenue per client is visible, consumed Resource hours per client are not, so client-level margin is uncomputable. Implement job-costing by customer before choosing. Typically firing the bottom decile wins because it also frees bottleneck crew capacity.

  §4.1 Financial resource, §1.3 productivity metrics, §0.3 measuredBy

• Close rate collapses when the homeowner's spouse is not at the estimate. Who is the proposal written to convince?

  Only half the buying unit. The proposal is a one-sided Specification for a two-agent decision. The absent spouse later re-opens it, which reads as a stalled close. This is the SERVQUAL knowledge gap. You misread who the customer is. Route proposals through both decision-makers or design them to be re-presentable.

  §6.3 SERVQUAL knowledge gap, §2.3 demand management

• The production calendar jams every Sep-Oct while the pipeline looks healthy year-round. Where does the handoff lose the timing?

  At the missing tactical layer: sales promises start dates against infinite capacity because no S&OP-style aggregate plan converts pipeline into finite crew-weeks. Seasonal demand is a known Pattern. The jam is a capacity buffer never deliberately chosen.

  §7 S&OP/aggregate planning, §2.1 Demand Pattern seasonality, A4

• Where does warranty call-back money leak: workmanship, or scope documents that never defined done?

  Predominantly the scope documents. "Done" undefined means the Output has no enforceable Specification, so every call-back is arguable. Workmanship defects would cluster by crew, scope defects cluster by contract language. Trace claims via producedBy to their spec source before retraining anyone.

  §0.3 specifiedBy, §6.2 external failure, A8

• Our estimating model assumes margins grow with project size. Past $150k they fall. Where does the model stop being true?

  At the point where coordination complexity outruns the learning curve. Larger jobs move you off your Product-Process Matrix sweet spot into longer critical paths, more interfaces, and more rework loops. The model fails where project risk stops scaling linearly with revenue. Re-price using size-conditional historical margins.

  §1.2 ProductProcessMatrix, A9 learning curve limits, §9 schedule risk

How these answers work

Each answer names the operational mechanism the question is circling, then states the directive that follows from the ontology in Part One of the book. Bracketed citations point to the ontology sections and axioms that produced the answer. Figures inside the questions describe each stipulated scenario. They are not industry benchmarks.

Related industries

• Plumbing operations questions
• Solar installation operations questions
• HVAC operations questions
• Appliance repair operations questions
• Electrical contractors operations questions

Keep reading

• All 100 industries and the full book
• Download the PDF
• Free diagnostic tool
• Methodology

Scope of This Material