The public promise is that your team gets the repository, the documentation, and the training to make routine changes. Handover is launch week. The goal is that your editors can sign in, edit, publish, add a post, handle images and SEO fields, and ask for a change.

What you receive

A handover doc, "How to run your site," in the repository and as a copy you can share. It is filled with your names, URLs, collections, fields, and roles.
Short recordings on your staging site, using your content. They cover a tour, editing a page, adding a post, images and alt text, SEO fields, asking for a change, undo, and choosing staging or production.
Sanity Studio, with your editors invited.
A one-page cheat sheet of the edits your team does most.
Copy-paste prompts for drafting in any chat tool, which you then paste into Studio. The prompts are not a way to publish.
The GitHub repository in your organization, including the docs that say how the site is run.
The running-cost section of the handover doc, filled for your accounts.
A test suite that blocks a change when the checks fail.
An accounts list: every account, who owns it, what access Everbase still has, and when to remove that access.
A performance report at day 14 and day 30.
A live training session of 60–90 minutes in launch week, on a real edit your team is about to make.

A sample-page walkthrough happens earlier, at the end of week 2, so handover is not the first time you see how editing works.

The first day

Accept the invite. Sign in. Open one draft in Studio, save it, and open its preview. In the Console, confirm the shell shows your site only. Turn the weekly digest on or off. If any of that fails, stop and tell your Everbase contact before you publish.

Three ways to change the site

Use the lightest path that fits.

Annotate. On a preview or staging page, during the build and refinement, click the thing that is wrong and leave a note. This is not on the public production site by default. After handover it is there only if your care plan still includes it.
Sanity visual editor. Text, images, sections, and SEO fields you already have permission to edit.
A Console request. New section types, layout, redirects, and integrations. Name the page, the change, and what done looks like.

Saving a draft is not publishing. On a static site the live page updates after the rebuild, usually a minute or two. Never paste a secret into a note or a chat.