Home/Product/Gates & readiness
Gates & readiness
A scorecard that is allowed to say no.
Every implementation has a moment where somebody has to decide whether to switch it on. This is the part of the product that exists so that decision is made against evidence rather than optimism and a Thursday deadline.
Phase gates
Seven gates. One at the end of each phase.
A gate is a row in the plan flagged as a gate, not a task with the word written in it. That distinction is the whole point: the dashboard can count how many are still open, and a phase cannot quietly be reported as finished while its sign-off is outstanding.
Counted, not labelled
Open Gates is a headline number on the dashboard beside weighted percent complete. Two open gates in phase four is a sentence you can say to a steering committee.
Visible on the timeline
Gates render as a gold diamond rather than a bar, because they take no time. They mark permission to continue.
Carries a role
A gate is a WBS row, so it carries the role responsible for it and can be pinned to real start and finish dates when the client gives you them.
UAT Tracker
Testing that produces a decision, not a feeling.
Nine scenarios ship seeded across financials, order to cash, procure to pay, manufacturing and warehouse, and cross-module. Each one arrives with its expected result already written, which is the part teams skip and then argue about.
| Field | Values |
|---|---|
| Module | Financials, OTC, PTP, Mfg/WMS, Cross-module |
| Scenario | What the tester does |
| Expected Result | Written before testing starts, not after |
| Actual Result | What happened |
| Outcome | Pass · Fail · Blocked |
| Severity | P1 · P2 · P3 |
| Tester | A named person |
| Status | Open, Fixed, Retest Pass, Closed |
What the severities mean here
- P1 — blocks go-live. No workaround. One open P1 turns the client status report red without anyone deciding to.
- P2 — serious, but there is a workaround the business can live with for a short period.
- P3 — minor or cosmetic. Goes on the post go-live list.
Readiness
Ten criteria. Five dimensions. Eighty percent.
Each criterion is scored 0 to 100 and carries a weight. The shipped weights sum to exactly 1.00. The weighted total is the readiness score, and 80% is the bar.
The five dimensions
- Technical — configuration complete, integrations running, environments ready.
- Data — migrated, reconciled and signed off, not merely loaded.
- Process — the business knows how the new process runs on day one.
- People — trained, with runbooks, and enough of them.
- Support — a path for when something breaks at 7am on Monday.
Changing the weights is an import. Scores are typed in the tab; the ten weights are set by importing the readiness CSV. If you rebalance them, keep the total at 1.00 — nothing checks it for you, and weights that undershoot quietly cap your maximum score below 100%.
Weighted readiness
Threshold is 80%. Data and People are below the line.
Score your next go-live before you commit to the date.
Import the scorecard weighted the way your firm weights it, and find out in week nine rather than the night before.