Contract to completed install. Every stage proves it's complete — at a gate — before the next one starts.
Four acronyms you'll see across the flow and the turnover documents — click one for a zoomable example.
A stage can't begin until the prior gate clears. Hover any criterion for why it exists; the handoff and enforcement model are drawn out for each gate.
Each tool plugs into one point of the flow. The full set lives in the Tools Repo.
Four things belong to the whole project, not to any single stage.
The Scoping PM, Implementation PM, and Survey lead are on client communications from Gate 1 — one consistent team end to end.
Turnover documents, survey packages, and scoping sheets follow one standard folder structure — one place, one format, per project and site.
COI ownership for Enertiv and the installer is assigned at Gate 1 and cleared before any site mobilization — named early, not chased at install time.
The tentative completion date set at Gate 1 is carried and refined at each gate, so the client always has a current, credible schedule.
Owner, action, and target — weeks are relative to rollout.
| # | Action | Owner | Target |
|---|---|---|---|
| 1 | Build the Project Turnover Package template | Sales / Estimating lead | Rollout Week 1 |
| 2 | Build the Survey Completion Checklist | Survey lead | Rollout Week 1 |
| 3 | Build the Scoping → Implementation Turnover | Scoping PM | Rollout Week 2 |
| 4 | Build the Install Turnover Invite | Implementation PM | Rollout Week 2 |
| 5 | Launch the Weekly Installation Sync (helps in-flight projects too) | Implementation PM · agenda co-owned w/ Scoping | Rollout Week 1 · ongoing |
| 6 | Pilot the full flow on the next new project; refine checklists from what was actually missing | Operations team / project PM | Rollout Week 3 → adjust |
| 7 | Enforce gate sign-off — no stage advances until the prior gate clears | Operations team · each acceptor | Rollout Week 3 · ongoing |
A standing weekly meeting that walks every active installation — to surface blockers early and answer cross-team questions in real time. Notion and Slack capture the outcomes; the meeting carries the conversation. It helps projects already in flight, not just new ones.
