Post-go-live 30/60/90 checklist
For Service manager, Tech lead, Account management, Service desk & technicians
MSP Stockroom / Free working sheet / October 7, 2026
Read https://mspstockroom.com/guides/first-90-days.html for the complete method.
Day-90 handoff record
- Active arrangement: [services / hours / support route].
- Checks still unknown: [evidence needed / owner / due date].
- Service corrections: [outcome tested / remaining impact].
- Exceptions: [reason / safeguards / authority / review date].
- Recurring work: [service owner / queue or standard reference].
- Roadmap decisions: [business reason / dependency / cost basis].
- Client decision: [accept arrangement / accept with open actions / resolve gap].
- Next review: [date or event].
Transfer remaining work to a receiving owner who accepts it. The post-go-live sheet includes this checklist, so the evidence can travel with the handoff instead of staying in a guide tab.
Post-go-live evidence checklist
For every row, record a status, safe evidence reference, check date, owner and next action. The check below describes the evidence to obtain; it does not authorize a production change.
| Check | Evidence to obtain |
|---|---|
| Support route | A user can reach the agreed channel; urgent requests reach the right queue. |
| Service hours and escalation | Desk, client and after-hours contact understand who owns each window. |
| Sold scope | Included work, exclusions and outstanding project items match the handoff. |
| Registrar ownership | Client's authorized representative confirms the registrar account owner and renewal responsibility. |
| DNS ownership | Record the DNS host, change authority and support route; verify access through the approved process. |
| Administrative access | Authorized support staff can use the approved access method for systems in scope. |
| Emergency access | Technical owner completes an approved verification and records result, date and secure reference, never secrets. |
| Line-of-business support | Record application owner, vendor contact, support entitlement and escalation hours. |
| Critical dependencies | Map the business process to its application, identity, network and hosting dependencies. |
| Backup responsibility | Identify protected systems, exclusions, retention and who acts on failures. |
| Restore evidence | Obtain a recent authorized restore-test record with scope, result and unresolved failures. |
| Recovery handoff | Service team can find the recovery instruction and accountable owner. |
| Licence true-up | Reconcile purchased, assigned and billed quantities; explain mismatches and renewal dates. |
| Agent inventory | Reconcile expected assets with RMM/security/backup coverage and check-in age. |
| Stale or duplicate agents | Confirm whether each suspect record is retired, offline or duplicated before removal. |
| Documentation | Another technician can find ownership, support and dependency records. |
| Monitoring handoff | A controlled, authorized test reaches the responsible queue with a receiving owner. |
| User impact | Check the outcome of the first significant fixes with affected users. |
Before using this sheet
Choose the owner, scope and period. Use safe references rather than private customer exports. Keep missing evidence marked unknown.
Use and license status
License: adapt internally for your MSP and the clients you support; do not resell or redistribute the source files. See https://mspstockroom.com/terms.html.