Define readiness for this meeting
Synthetic kickoff K-254 needs a confirmed order scope and a named customer coordinator. Historical data cleanup is required later for configuration, but not for the kickoff. C-61 has both kickoff inputs and pending cleanup; C-62 lacks a coordinator. A blanket “all onboarding tasks complete” gate would delay C-61 unnecessarily. Readiness belongs to a specific decision, not the whole customer lifecycle.
| Customer | Order scope | Coordinator / later cleanup | Kickoff decision |
|---|---|---|---|
| C-61 | Confirmed O-61 | Named; cleanup pending | Ready for kickoff |
| C-62 | Confirmed O-62 | Not named; cleanup done | Hold for coordinator |
| C-63 | Draft scope only | Named; cleanup done | Hold for confirmed scope |
Schedule against the minimum agreed gate
- Read kickoff-specific requirements
- Check scope and coordinator
- Carry later tasks into their own plan
- Schedule ready kickoff
If a missing item is genuinely needed to make the meeting’s decision, add it to the agreed gate with a reason; do not invent generic reassurance steps.
C-61 has unfinished cleanup. Should its kickoff be blocked by this fixture?
Show the worked answer
No. Its scope and coordinator are confirmed. Keep cleanup pending for the later configuration gate.
Minimum inputs are authored for this meeting. This is not a project launch go/no-go or production release checklist.