
Ready for a better website?
Serious about growing your business online?
Agree who owns the project, domain, billing and connected services, with named people rather than a shared password list.
Rehearse five everyday tasks: edit content, add a CMS entry, test an enquiry, check a mobile page and recover a mistaken change.
Separate content approval from publication. Give people the access their role requires and check any seat costs before adding editors.
Keep a short operating guide with the actual project links, content rules, form destinations and escalation contacts.
Accept the handover when your team can repeat the tasks without live coaching. Record unresolved issues and support responsibilities separately.
The website is ready. Your marketing lead opens the editor to replace a project image, hesitates over the publish button, and sends the change back to the designer. The design may be finished, but the handover is not.
A useful Framer website handover leaves your team able to run the website’s ordinary tasks and recognise when a change needs specialist help. Access matters, but so do the small decisions behind it: which image belongs in which field, who checks a new enquiry, and what happens if the wrong version reaches the live domain.
We recommend accepting the handover through a short rehearsal using your real content. Ask the person who will maintain the website to complete five tasks while the designer watches. Turn every hesitation into a clearer instruction or a simpler editing experience before signing off.
Start with the work your team will actually do
A tour of the editor can look impressive while teaching very little. Watching someone build a component does not prepare a practice manager to update office hours on a Friday afternoon.
Before the handover, list the recurring jobs. A contractor might need to add a completed renovation, replace a testimonial with the client’s permission, and update service-area content. A consultancy might publish articles, change team biographies and update a booking link. These are different maintenance needs even if both websites use the same platform.
For each task, identify the person doing it, how often it happens and the consequence of an error. Use those answers to decide what belongs in the CMS, what needs a fixed layout and what should stay with a designer. A frequent update should have a clear editing route. An occasional structural change does not need to become an everyday responsibility for the office team.
This is also a useful acceptance question when you are comparing a Framer website design approach. Ask the agency to demonstrate an update with unfamiliar content. A polished example filled with perfectly sized copy can hide a fragile editing experience.
Choose the rehearsal tasks before the meeting. That gives the designer time to prepare sensible field names, example content and any missing instructions. The aim is to test readiness, not surprise someone with an edge case.
Put ownership and access in writing
Create an ownership record that distinguishes the website project from everything connected to it. The domain registrar, website plan, form destination, booking account and analytics property may have different owners. Knowing who designed the website does not tell you who can renew a domain or restore access to an inbox.
Use named business-controlled accounts where possible. Record where recovery details are held without putting passwords, recovery codes or API keys into the handover document. Keep secrets in your organisation’s password manager and give access through its sharing controls.
A practical ownership table can be short:
Area | Responsible person | What to record | Acceptance check |
|---|---|---|---|
Website project | Business owner or website lead | Correct project and workspace | Owner can open the intended project |
Domain and renewal | Business owner | Registrar, renewal responsibility and contact | Authorised person can reach domain settings |
Routine content | Marketing or operations lead | Allowed edits and review process | Editor completes a sample update |
Publication | Named approver | Who may release a change | Team can identify the final approval step |
Enquiries | Sales or office lead | Form destination and backup contact | Test enquiry arrives and is acknowledged |
Technical support | Agency or developer | Scope, response expectations and escalation route | Both sides agree who handles failures |
Framer distinguishes workspace access from access to an individual project. Its advanced Design, Content and Deploy permissions depend on the plan, and editing access can affect billing. Check the actual setup before promising that everyone can edit or that every editor can publish. Framer’s permissions documentation explains those distinctions.
For a business with several unrelated projects, consider whether a person needs workspace-wide access or just the website they maintain. Record that decision and review it when somebody changes role or leaves the business.
Rehearse five tasks with real content

Ask the eventual editor to share their screen. Let them work from the guide before offering help. A task completed only through the designer’s running commentary is a useful signal that the guide or editing setup needs improvement.
1. Update a small piece of existing content
Change a genuine heading, contact detail or short paragraph in a safe preview. Check the surrounding layout, link destination and mobile wrapping. The editor should understand where the content comes from and how to recognise whether they are editing a shared component or one page.
Use a deliberately longer sentence than the original. A layout that only works with the designer’s exact wording needs either clearer limits or a more resilient design.
2. Create a realistic CMS entry
Use a real project or article that is suitable for the website. Add a title, description, image, alternative text and any category or relationship fields. Explain which fields affect the listing card and which affect the detail page.
Preview the entry in both places. Check whether the image loses its important subject when cropped, whether an empty optional field leaves an awkward gap, and whether the title wraps naturally. Keep the entry unpublished until it has been reviewed.
3. Test an enquiry from the visitor’s side
Submit a clearly labelled test enquiry through the intended test environment or an agreed live test. Confirm the visitor sees a useful success state, the right inbox or CRM receives the message, and the assigned person knows what to do next.
A successful animation is not proof of delivery. Open the destination and inspect the received information. Include one test with a realistic message rather than a single word, so you can see whether important detail survives the handoff.
4. Check a changed page on a phone
Use a real phone where available. Open the navigation, follow the primary action and inspect the changed content at a normal reading size. Check tap targets, long headings and any sticky elements that could cover the content or submit button.
The editor does not need to become a responsive designer. They need to recognise a problem and know whether they can fix it within the documented controls or should send it back for design work.
5. Rehearse recovery without risking production
Make an agreed harmless change in a safe preview, then practise the documented route back to the approved state. Explain the difference between recovering an editor change and deploying a previously published version. Keep the exercise away from the public website unless a controlled live test has been agreed.
Framer’s version links stay associated with a particular published version. Where staging is configured, the base domain can be used to test changes before deploying to the connected custom domain. Confirm what is enabled on this specific site and record the approved version link. Framer’s staging and versions guide provides the platform details.
Define the content rules that protect the design
A CMS field called “Image 2” leaves too much to interpretation. A field called “Project card image” is clearer, but the team still needs to know what kind of picture works there.
Document the intended image shape, useful subject placement and any approved export guidance. Include an example that works and a short explanation of why. For a kitchen project, a wide room photograph may work better on a listing card than a tight portrait crop of a cabinet handle. That is an editorial choice with a visible layout consequence.
Give titles and summaries practical limits based on the actual design. Avoid arbitrary character rules copied from another website. Show a normal example and a longer example that still fits. If important text is routinely cut off, improve the component rather than expecting every future editor to solve the crop.
Explain slugs separately from titles. Changing a visible title and changing a public URL are different actions. The runbook should direct editors to preserve existing URLs unless a planned redirect and link update are part of the change. This protects old links and avoids turning a routine copy edit into a migration task.
For service-area pages, specify what makes a page worth creating: genuinely relevant service information, accurate coverage and useful local detail. Do not teach the team to generate near-identical location pages just because a collection makes it easy. The same principle applies to articles: a new entry should answer a distinct question, not repeat an existing post with slightly different wording.
If a content change also changes the website’s structure or audience journey, revisit the service-business website structure before treating it as a simple CMS update.
Check the systems around the website
A handover should cover the journey after the visitor clicks. For each contact form, booking link and download, record the destination, account owner and expected result. Include the subscription or service dependency when one exists, so a later cancellation does not silently break a business-critical path.
Test lead routing with the person receiving enquiries. Agree who checks spam, who handles an incomplete submission and what happens when the usual recipient is away. For a service business, an attractive enquiry form has limited value if nobody owns the next response.
For measurement, ask the team to demonstrate where they would check visits, important actions and incoming enquiries. Distinguish a recorded button click from a completed booking or a qualified lead. If a dashboard shows a conversion, the handover should explain exactly what triggers it. Do not label a broad page visit as a sales enquiry because it makes the report look stronger.
Record a baseline at launch or acceptance: the reporting period, the metrics being monitored and the known limitations. A new website will not necessarily have enough data to show a trend immediately. Set a date for reviewing the first useful period rather than promising a result by a fixed day.
Also review privacy and consent implementation with the responsible business contact. The designer can demonstrate what is configured, while the business confirms whether it meets its requirements. Keep that responsibility explicit instead of assuming that a standard banner settles every question.
Separate acceptance from ongoing support
A handover can be technically complete while several optional improvements remain. Keep those separate from defects that stop the agreed website working.
An incorrect form destination is an acceptance issue. A request for a new calculator after the agreed build is usually new work. A confusing CMS field may be a handover issue if the agreed team cannot perform the promised update. Write these distinctions into a shared list with an owner and next action.
For each unresolved item, record the expected behaviour, current behaviour, evidence and who is responsible. A short screen recording or exact URL is more useful than “the site feels broken.” Prioritise by visitor impact and business risk, not by which request arrived most recently.
Agree what ongoing support includes. Content changes, design development, integration monitoring and strategic improvements are different services. If you are considering a retainer, compare the responsibilities with the original website redesign scope so you can see what is maintenance and what is additional development.
Do not remove the agency’s access before confirming that ownership, billing and recovery routes work for the business. Equally, access should not remain indefinitely by accident. Agree a review date and keep only the access needed for the continuing relationship. Framer’s invitation guidance is useful when checking how project members are added and what their role permits.
Keep the operating guide short enough to use
The most useful handover document is the one someone opens while doing the task. Start with a one-page index linking to the project, preview, live domain, CMS instructions, form destinations and support contact. Add short task recordings where a visual explanation helps.
Give each recording one job. “Add a completed project” is easier to find and revisit than a ninety-minute walkthrough containing every feature. Use the real website, explain the decision points and show the preview check at the end.
Finish with a small acceptance record: who completed the rehearsal, which tasks passed, which issues remain and the agreed follow-up date. That record gives both sides a clearer boundary than a vague confirmation that the website looks good.
Next steps
Before your next handover meeting, choose the five tasks your team needs to perform and assign a person to try them. Bring one realistic piece of content, one enquiry scenario and the ownership table. Use the session to close the gaps those tasks reveal.
We recommend making this rehearsal part of the original website brief. A website is easier to maintain when the editing experience has been designed alongside the public pages. If you are comparing partners, use the agency selection questions to ask for a practical handover demonstration before committing to the build.



