Client Enablement and Platform Handover (Handoff)

Client Enablement and Platform Handover (Handoff)

1. 01

   Confirm the client's named platform administrator and record their access level before handover begins

   A single accountable owner prevents the agency from becoming the permanent de facto admin. Capture their role, email, and whether they hold billing or publishing rights.

2. 02

   Deliver a written asset map that lists every course file, quiz bank, and media asset with its storage location

   Include source files, not just published versions. Clients who inherit only rendered output cannot edit without returning to the agency.

3. 03

   Run a live walkthrough of the authoring and publishing workflow with the client team

   Cover lesson creation, quiz editing, and release scheduling. Record the session and attach it to the handover folder so new client hires can self-serve later.

4. 04

   Document the platform's export and portability limits in plain language

   State which content formats move cleanly (SCORM packages, CSV quiz banks, MP4 media) and which stay locked to the vendor. This is the client's exit-cost disclosure.

5. 05

   Transfer ownership of payment, tax, and domain settings to the client's accounts

   Course revenue should never route through an agency-controlled Stripe or PayPal account after handover. Reconnect checkout to the client's merchant account and verify a live test transaction.

6. 06

   Define the post-handover support window and its boundaries in the retainer agreement

   A 30-day question window is common. Anything beyond that becomes a scoped change order, which protects margin on the original build.

7. 07

   Schedule a 60-day check-in to review learner completion data and flag content that needs revision

   Completion rates and quiz failure points surface stale modules faster than client feedback. Use the check-in to propose a paid update cycle.