The Editable Website Illusion: A Pre-Sign-Off Test for UK Marketing Teams

There's a moment about three weeks after a website launch that should be studied by sociologists. The site looks brilliant. Lighthouse scores are green. The agency has been paid. And then someone in marketing asks, cheerfully, whether they can swap the homepage banner for a seasonal offer by Friday.

Cue a ticket, a scope conversation, and a small invoice for what is technically a ten-minute job.

That's the editable website illusion: a site that has been handed over in the technical sense (files delivered, invoice settled) but not in the practical one. Nobody has ever checked whether the people who actually run the site day to day can do so without help.

Handover is usually treated as an event, not a build item

The standard pattern goes like this: a two-hour training session, a screen recording, a PDF of instructions, an email with a link to the staging site. All genuinely well-meant. All essentially outputs rather than outcomes.

On the agency side there's often no budget line for handover beyond the training call, so it gets squeezed. On the client side, nobody senior sits through the training because launch week is busy. Six weeks later, the knowledge has evaporated and the only person who can confidently touch the templates has an agency email address.

That's not a conspiracy, it's just an unmeasured deliverable. Which means the fix is to measure it.

Test one: the twenty-minute edit

Pick a marketer who had nothing to do with the build. Give them a task with no coaching and no Slack channel to the developer. The task should be realistic, not a test of courage:

• Create a new landing page from an existing template
• Add a hero image, a headline, a short paragraph and a form
• Set the meta title and description
• Publish it, then schedule a redirect from an old URL

Time it. If the answer is forty minutes of guessing and one accidental unpublish, you've found the gap. A sensible target is twenty minutes for someone reasonably comfortable with a CMS, and critically, a result they'd be happy to show a customer.

The real question isn't speed. It's whether they'd attempt it again on a Friday afternoon without asking permission from three people.

Test two: dig into who actually holds the keys

Sit down with whoever owns the site's technical estate and make a list of every account that touches the site. Not the agency's internal list, yours. It should cover:

• Hosting and DNS registrar
• CMS admin access (not editor level)
• Google Tag Manager and Google Analytics 4 admin
• Search Console
• Email marketing and CRM connectors
• Payment gateway if relevant
• Cookie consent platform and the audit trail behind it
• Plugin licences, theme licences, any third-party subscriptions
• SSL certificates and backup system

If any of those are registered to an agency email, you don't control your own website. You're renting it. That's fine as a deliberate choice, but it becomes a problem the moment the relationship cools or your agency's head of delivery moves on.

For UK teams, there's a compliance angle too: your cookie consent configuration and form handling sit under UK GDPR, and the ICO's expectations don't pause while you wait for a third party to grant access to the tag manager.

Test three: the documentation sniff test

Most handover documentation is written by someone who already knows the answer, for someone who already knows the answer. It tells you which button to press and nothing about what's behind the wall.

Here's the sniff test. Can your docs answer these?

1. Where does this form actually send data, and what happens if delivery fails?
2. Which plugin is load-bearing, and what breaks if it's removed or updated carelessly?
3. How often are backups taken, where do they live, and who restores them?
4. What's the process for adding tracking to a new page without duplicating events in GA4?
5. Which components are locked by the agency for a reason, and which are locked by accident?

If the answer to any of those involves 'ask the developer', you have a support relationship disguised as a handover.

Test four: training that sticks

One session at go-live is a briefing, not training. People forget 70% of what they're shown within days when they haven't used it.

What actually works is unglamorous: two sessions spaced about six weeks apart, with real tasks in between. Small group, ideally three or four people including one who can authorise decisions. Short task-specific recordings rather than one sweeping ninety-minute epic nobody rewatches. And a named owner inside your team whose job is to know the CMS, not just be 'quite into it'.

Test five: the leaver test

Ask yourself a blunt question. If the developer who built this logs off tomorrow and never returns, what can't you do?

If the answer includes 'get a database export', 'change the hosting plan' or 'remove the staging environment's noindex', the site is more fragile than it looks. This isn't about trust. It's about basic business continuity.

The clauses to agree before the work starts

All of this is cheap to specify and expensive to retrofit. Add these to the contract, in plain English, before the build begins:

• A written handover checklist with acceptance criteria, treated as a deliverable, not a favour
• Final payment tied to handover sign-off, not to the launch date
• Training as a scoped number of days, with the second session occurring after go-live
• Documentation as a paid line item, reviewed by someone who didn't write it
• All accounts created in your ownership from day one, with agency access granted rather than given
• A named list of 'no-ticket edits' the team should be able to make unaided
• An exit clause covering asset export, licence transfer and a defined support window after any separation

The bit that rarely gets said out loud

Agencies aren't deliberately creating dependency. But dependency is commercially convenient, and unmeasured deliverables tend to fall to whatever is most convenient.

So make it measured. Run the twenty-minute edit before you sign off. Count how many accounts carry your name. Reread the docs as if you were new, because soon enough you will be. The site you bought is only worth what your team can do with it on a normal Tuesday, with the agency's phone on silent.