MS1 Scope BuilderScope Builder MS1 LocationsLocations enertiv.com ↗
Project delivery

The Implementation Flow

Contract to completed install. Every stage proves it's complete — at a gate — before the next one starts.

Browse the Tools Repo the flow is the story — the tools are how you act on it
11Stages
4Gates
~12Weeks
1Parallel track
The delivery flow
Stage Gate Decision Document Parallel track Role — click to highlight
Walk
Drag to pan · Ctrl+scroll to zoom · click anything for detail
Before you start

The short-hands

Four acronyms you'll see across the flow and the turnover documents — click one for a zoomable example.

Quality gates

Four gates. One rule: the acceptor verifies.

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.

The tooling

Tools, mapped to stages

Each tool plugs into one point of the flow. The full set lives in the Tools Repo.

Run across every stage

Continuous threads

Four things belong to the whole project, not to any single stage.

Client comms & core team

The Scoping PM, Implementation PM, and Survey lead are on client communications from Gate 1 — one consistent team end to end.

Single cloud repository

Turnover documents, survey packages, and scoping sheets follow one standard folder structure — one place, one format, per project and site.

COI / insurance track

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.

Schedule visibility

The tentative completion date set at Gate 1 is carried and refined at each gate, so the client always has a current, credible schedule.