Control map
Match the decision and evidence to the implementation stage.
Stages overlap, but each one needs a visible question, proof, owner, and stop condition. Use this map as an educational planning aid, not a project certification or substitute for the actual agreement.
What result, boundary, ownership, and stop decision govern the work?
Working charter, role map, system context, assumptions, and phase gate.
A contract becomes a vague transformation promise.
Which operating slice can the nonprofit review and decide now?
Reviewable workflow, documented configuration, decision log, and controlled environments.
A large reveal hardens assumptions before users can challenge them.
What proves records move correctly and people can complete real work?
Migration rehearsal, reconciliation, user scenarios, defects, retests, and acceptance.
A successful demo substitutes for migration and operating evidence.
Can the organization continue service, support users, and reverse safely?
Cutover checklist, rollback, staffing, communications, support, and go or stop authority.
The calendar becomes the only reason to go live.
Which defects, exceptions, support demand, and adoption gaps still threaten operation?
Triage, severity, owner, response, service measures, and a stabilization exit gate.
The project declares victory while staff carry hidden workarounds.
Can the nonprofit operate, explain, maintain, recover, and exit the system?
Owned accounts, documentation, practice, support boundaries, access review, and review dates.
Launch ends but dependence remains undocumented.
Before the next stage expands
- Which nonprofit owner can approve the decision?
- What evidence is complete, incomplete, or contradicted?
- Which assumption changed time, cost, risk, access, or mission effect?
- What remains reversible, and who can pause the work?
- What must transfer to nonprofit control at this stage?