The short answer
Handover starts during the build, not at the end. Give each person the right Webflow role, expose what they should change as component props and CMS fields, lock what they should not, write a short guide, and then have them publish a real change while you watch. A handover is finished when they can do it without you.
That last part is the one people skip. A recorded tour feels complete, but only a real edit shows whether the site can be run by the people who own it.
Choose the right role
Webflow's guide to building and editing content describes the first two roles below. Roles and plans can change, so check the current docs before you set up seats.
| Person | Role | What it is for |
|---|---|---|
| Copywriter, content manager, translator | Content editor | Updating content, translating, and updating site assets |
| Marketer who builds landing pages | Marketer | Drag-and-drop page building from pre-built, approved components |
| Designer or developer changing the system | A designer or site manager role | Changes to layout, classes and components |
Give people the lowest role that does their job. It protects them as well as the site, since they can work freely without worrying about what they may break.
If you came from an older Webflow site, note that Webflow has announced the end of the legacy Editor, and it describes client seats as the replacement for clients of freelancers and agencies. Our Webflow Editor entry covers the basics. Check the current docs for the dates and for what applies to your plan and workspace.
Build for the person editing
Most of the editing experience is decided while you build. These are the standards to hold to.
| Standard | What it looks like | Real example |
|---|---|---|
| Pages are made from parts | New pages use existing components, with no new classes | For example, your team adds pages from components. |
| Repeat use is cheap | Duplicate the page, fill the props, publish | Bailey duplicates the outreach page for every pitch, with client name, video and links set through props. |
| Rules live in the content | Tag a card, and the filter updates by itself | Bailey's filters build from each card's category. |
| Effects do not need a developer | Copy, logos and steps change in the Designer | The same is true on CUBE. |
| Bulk work has a route | New pages come from sending data | ClanX adds role pages through the CMS API, with no Designer work per page. |
| Simple sites stay simple | One clean class system on one page | Baraka Impact is easy for the team to edit later. |
Webflow notes that unbound content in a component changes across all instances, and that the canvas shows when an edit is global. Tell editors what that notice means before they first see it. Webflow also has settings for restricting what editors can change on an element, and for whether they can publish. Check the current docs for how those work on your plan.
What editors can do alone
Put this table in the guide, using your own site's details. It removes most of the "am I allowed to?" messages.
| Safe to do alone | Ask first | Leave to a developer |
|---|---|---|
| Change copy, images and links | Change a page slug, because it needs a redirect | Change classes or variables |
| Add or edit CMS items | Delete a page or a CMS item with a URL | Change custom code or scripts |
| Build a page from approved components | Unpublish a page that gets traffic | Edit interactions |
| Change SEO titles and descriptions | Change a form's destination | Change the CMS field structure |
| Add alt text | Add a new tracking script | Change DNS or hosting settings |
Decision rule If a change could break a URL, a form, tracking or the design on other pages, it is not a solo edit. Everything else should be, so the team does not wait on anyone for small things.
The handover pack
Keep it short enough that people will read it, and in a place the team already uses.
| Item | What it holds |
|---|---|
| One-page guide | How to log in, how to edit, how to publish, the table above, and who to ask |
| Style guide page | Live in the project: type, colours, buttons and components, each with its name |
| Component list | Each component, what its props do, and where it is used |
| CMS list | Each collection, who owns it, and a filled-in sample item |
| Motion list | The specs from chapter 4, and which script drives which effect |
| Integrations list | Forms, tools and scripts, with where each one sends data and who holds the account |
| Access list | Who holds what: Webflow, DNS, analytics, Search Console, and any CDN or API host. Names only, no passwords in the document. |
| Short recordings | Editing a page, adding a CMS item, and publishing |
If you are on a client's workspace, agree ownership before launch: who pays for the site plan, and who owns the workspace once the build ends.
The publish test
Run this live with the person who will do the work. They drive. You watch and stay quiet.
- Change a line of copy on the home page, and publish.
- Swap an image, and add alt text.
- Add a CMS item with an SEO title and description, and find it on the live site.
- Build a short landing page from components.
- Find the right person to ask about a slug change.
- Undo a mistake, or say how they would get it fixed.
Each time they hesitate, write down why. It is usually a poor prop name, a missing field note, or a gap in the guide. Fix those, because they are bugs in the handover. They are not the editor's fault.
Avoid the common handover problems
| What happens | Why | Standard |
|---|---|---|
| Editors break a layout with long text | The design was only tested with short copy | Test components with the longest real content |
| A heading in rich text breaks page structure | Field notes are missing | Say which heading levels to use, and where |
| Two people overwrite each other | No agreed process | Agree who edits what. Check the current docs for how Webflow handles two people editing at once. |
| A publish sends half-done work live | Nobody agreed who publishes, or when | Name who publishes. Check the current docs for your plan's publishing options. |
| A slug changes, and old links return 404 | Nobody knew it needed a redirect | Put it in the ask-first column, and link the redirect map tool. |
| A new tool gets added and speed drops | Scripts are added with no owner | New scripts are an ask-first item, and they get listed. |
After the handover
Plan for who looks after the site next, before the project ends. Our work includes 30 days of support after launch for safe changes: copy, image, colour and link updates, and fixes to what we built. It does not cover new sections or redesigns. After that, you can run the site yourself using the guide, hire Webflow development by the hour or the project, or use a care plan.
Our post on what comes after launch lists the kind of upkeep to plan for.
Done when The person who will run the site has published a real change, on their own, using the guide. Petavue was a one-time build, handed over ready for the team to edit. That is the standard for a project with no ongoing plan.


