Handover Checklist
Use this when preparing and executing the handover to the university.
Scope of Handover
- System: Maintenance management platform (API + frontend + DB + storage + caching).
- Ownership: They own the source code; no paid license; runs on cost-efficient stack (e.g. CF Pages, Workers, Neon, R2).
- Commitment: Up to 12 months of support/maintenance from us after go-live, with knowledge transfer so their IT can take over (target: weeks to one month).
Pre-Handover
- [ ] Production deployment on agreed domains
- [ ] Environment and secrets configured for them (or handover of config process)
- [ ] API and deployment docs finalized (from main
docs/guides/) - [ ] Training and knowledge-transfer materials ready (in
for-institution/) - [ ] Walkthrough materials for IT (impact-focused: cost, audit, workflow, roles — not tech hype)
- [ ] Portability Q&A prepared (Postgres, S3, Hono; DO/cache consistency if they ask on-prem) — see our-planning/positioning-and-strategy.md
- [ ] Presentation readiness: pitch framed as solution (cost efficiency, audit transparency, workflow); security as layered (no overconfident claims)
Handover Deliverables
- [ ] Access to repo / source (as agreed)
- [ ] Deployment and operations guides (from main docs)
- [ ] Training and admin docs (from
for-institution/) - [ ] Written 12-month support/maintenance commitment (scope and boundaries)
- [ ] Contact and escalation path for support
Post-Handover
- [ ] Feedback collection in place
- [ ] Clear handover sign-off (what they own, what we support for how long)
- [ ] Schedule for knowledge-transfer sessions if needed
Success Criteria
- System deployed and stable
- Their IT can operate and maintain it (clarity over cleverness)
- Documentation and commitment are clear; positioning and removal/leave rules are in our-planning/files-to-remove-and-leave.md