FDE 5: Handoff
Handoff is when the build stops being yours and starts being the tenant’s. A good handoff leaves trained humans, kept documents, and a short list of owned open items. Never a hallway “you are good to go.”
Pre-handoff gate: all must hold
Section titled “Pre-handoff gate: all must hold”- Pilot ran with real users on real goals (not staged demos)
- Environment spec, capabilities register, and approval matrix current (docs match reality)
- Probe sequence re-run after the last change (nothing regressed)
- Denial patterns reviewed and addressed (or explicitly accepted with rationale)
- Connector states honest: connected vs. requested vs. deferred, each labeled
- Open items ticketed with owners and dates, none verbal
Train each role on their slice
Section titled “Train each role on their slice”| Role | Training | Point them at |
|---|---|---|
| Users | Run sessions, decide approvals, find records | Tenant users, especially first session and approvals |
| Operators | Supervise sessions, approval discipline, escalation | User sessions path |
| Admins | Membership, roles, settings, requests to PRESHai | Tenant admins |
Train with live pairing, not slide decks: new operators pair on real approvals before solo rights; new users run their first session with you watching.
The handoff pack
Section titled “The handoff pack”- Scope doc (from Discovery): the agreed work, systems, exclusions.
- Environment spec (from Environment): context, tools, probes, connector states.
- Capabilities register (from Skills, tools and MCP): what is verified, when.
- Approval matrix (from Approvals): gates, roles, tuning log.
- Open items list: owner and date per item (connector requests, deferred scope, custom domain track).
- Rhythm one-pager: what the tenant does weekly (membership glance, denial-pattern review, request channel to the PRESHai team).
Post-handoff
Section titled “Post-handoff”- Week-2 check-in: sit in on live sessions, review recent approvals, catch drift early.
- Measure the pilot success criteria from the scope doc. Did the observable outcome happen?
- Feed platform learnings back: connector gaps, SDK friction, and recurring policy patterns go to ops and product, with examples, as the Ops and SDK sections expect.
- Close or re-date open items. An open item without a date is a promise without a plan.