Client-handover checklist

The client onboards themselves using the Editor guide and Onboarding. Share those links and verify access before closing the project.

Logins and rolesLink to this section

• Create named accounts for each client editor.
• Assign the narrowest role that covers each person's work.
• Verify editing, publishing and user management with the actual accounts.
• Test login and password reset for the client email addresses.
• Keep agency developer accounts separate from client accounts.
• Document explicit grants for any custom collections.
• Store credentials and recovery codes in the agreed password manager.

Client onboardingLink to this section

• Share the Editor guide link.
• Share the Onboarding link and ask the client to start there.
• Ask a client editor to complete a draft edit and preview themselves.
• Verify the publishing owner can publish an approved change.
• Explain which pages and fields have locale-specific publish states.
• Add a short note for project-specific blocks or approval rules.
• Confirm the client can replace media and review an enquiry submission.

OwnershipLink to this section

• Record the client owner of domain registration and DNS.
• Record hosting, database and media-storage ownership.
• Record the email sender, provider account and form-notification recipients.
• Record analytics and captcha accounts where used.
• Transfer access to the source repository and deployment process as agreed.
• Record billing and renewal contacts.
• Verify recovery access without relying on a shared agency login.

Maintenance and recoveryLink to this section

• Record the installed Systhema version and deployed revision.
• Record backup schedule, retention and restore owner.
• Record the last successful restore test.
• Agree who reviews and applies future upgrades.
• Agree the support contact and escalation process.
• List known limitations and remaining work with owners.
• Obtain the client's acceptance of the handover record.

See Handover for the record template and Access control for role behavior. Use Upgrading a client site for maintenance.