Operating guide
The lead-to-closeout residential remodeling workflow
A practical operating sequence for moving a remodeling project from inquiry through warranty without losing decisions between teams.
By Tyler Thompson, residential remodeling contractor and product founder · Updated 2026-08-24
Answer first
A reliable remodeling workflow makes each phase produce the information the next phase needs, with an owner, an approval state, and one project record.
1. Qualify the lead
- Confirm project type, property, service area, decision makers, timing, and fit
- Assign the next action and follow-up date
- Record why a lead is declined or deferred
2. Run the site walk
- Capture rooms, existing conditions, affected trades, access, protection, permits, design needs, and photos
- Separate observed facts from assumptions
- Leave with explicit estimating and client follow-ups
3. Build and review scope
- Translate discovery into complete work sections
- Identify exclusions, allowances, unknowns, and owner-supplied items
- Review labor, materials, subs, fees, markup, and client presentation
4. Lock decisions before production
- Record accepted scope and commercial terms
- Create the selection schedule
- Confirm permits, long-lead items, responsible people, and milestone logic
5. Control production and changes
- Keep current schedule, tasks, field records, purchases, and subcontractor assignments attached to the project
- Price and approve changes before work when practical
- Reflect approved changes in billing and project value
6. Close and carry warranty
- Resolve punch items and missing documents
- Deliver closeout records
- Archive decisions and preserve warranty obligations with dates and ownership
One fictional project, six accountable outputs
| Phase | Required output | Release question |
|---|---|---|
| Lead | Fit decision, property facts, next action, and responsible person | Why should this lead advance to a site walk? |
| Site walk | Room evidence, existing conditions, affected trades, protection, permit and lead-safe questions | Which facts are known, assumed, or still unresolved? |
| Estimate | Versioned scope, exclusions, allowances, internal review, and client document | What exactly is the client accepting? |
| Preconstruction | Selections, permits, purchases, responsibilities, and milestone constraints | Is the project ready to release to production? |
| Production | Current tasks, field evidence, approved changes, purchasing, and billing state | Which decision is blocking the next safe action? |
| Closeout | Punch, financial reconciliation, permits, documents, and warranty ownership | What remains open, who owns it, and when is it due? |
Limits and audit questions
- No software workflow proves that scope, price, contract, code, permit, engineering, or product choices are correct.
- Ask who can approve client commitments, commercial changes, schedule promises, and closeout states.
- Require each phase to retain the accepted version and unresolved assumptions rather than overwriting history.
- Verify what exports as data, what remains a file URL, and which audit records have a limited window.
- Run the trace with one of your own projects before changing the company's operating process.