Client Training Portal Handoff (Handoff)

Client Training Portal Handoff (Handoff)

1. 01

   Freeze the training build and tag the release version before any access changes

   Record the course count, portal count, and last content edit date so the receiving client team can prove what they inherited. A frozen build stops scope drift during the transition window.

2. 02

   Map every admin role to a named person on the client side, not a shared inbox

   Platforms such as LearnUpon and Absorb LMS separate super admin, portal admin, and reporting-only roles. Assign each seat to an individual and log the date the invite was accepted.

3. 03

   Transfer ownership of billing, domain, and SSO credentials in one scheduled session

   Walk through the payment method, custom domain DNS records, and identity provider connection live. Screen-share the change and confirm the client can log in before the call ends.

4. 04

   Document the content pipeline the client will run without the agency

   List who authors, who reviews, and who publishes, plus the expected turnaround for each stage. Note any AI drafting tools in use, since platforms like Docebo and TalentLMS generate draft modules that still need a human review step.

5. 05

   Set the reporting cadence and name the metric the client will be judged on

   Agree on completion rate, time-to-competency, or compliance pass rate, and pick the day of the month the report lands. One metric beats a dashboard nobody opens.

6. 06

   Run a 30-day support window with a written escalation path

   Give the client a single contact, a response-time expectation, and an end date. Anything unresolved at day 30 converts to a paid retainer or a documented open item.

7. 07

   Hold a 60-day review to confirm the portal is still in active use

   Check login counts and course completions against the baseline captured at handoff. If usage has fallen, the fix is usually content relevance, not a platform change.