The training session nobody remembers
The site launches. The developer offers an hour of training. The owner sits through it, nods, takes a few notes, and then does not touch the site for six weeks. When they finally need to change the opening hours, they remember none of it and email the developer, who charges for the change or does it free and resents it. Both feel the training was wasted, because it was.
Live training happens once, at the moment the client least needs it, and it evaporates. A recording happens once and is there every time.
What we send instead
On launch day, a screen recording, fifteen to twenty minutes, of the site's admin with a voice-over. Not a course. A walkthrough of exactly the things this client will do, on their actual site, with their actual content. Filed where they can find it, usually a link in the handover document and an email they can search for.
What it covers
The order is by how often each task happens, because the first five minutes are the ones people rewatch.
- Logging in. Where, with what, and what two-factor looks like. Thirty seconds, and the most common support question without it.
- Changing text on an existing page. Find the page, edit the block, save, check it live. This is 80 percent of what a small business owner will ever do.
- Swapping a photo. Upload, size guidance in one sentence, replace, save.
- Updating the recurring things. Opening hours, prices, staff list, whatever this business changes. If they live in fields, the video shows the fields. If there is a specific place for the holiday notice, it shows that.
- Adding a new item of a known type. A new service, a new team member, a new testimonial, a new post. Whatever the content model has.
- What not to touch. The settings menus, the plugin screens, the theme editor. Named, shown briefly, and explained as "this is where the site can break; ask us."
- Where the backups are and how to reach us. One sentence each.
That is the whole syllabus. Anything beyond it, adding a page type, changing the menu structure, is a developer task, and the video says so.
Why a recording works
It is there when the need is. Six weeks later, at 9pm, with the price list to update, the client opens the video, skips to minute four, and does it. No email, no wait, no charge.
It is on their site. Generic platform tutorials show a different theme, different fields, different names. The recording shows the client's own admin, so nothing has to be translated.
It can be paused. People learn a click-path by doing it alongside, and a live session moves at the trainer's pace.
New staff get the same onboarding. The receptionist who joins next year watches the same video. The knowledge does not leave with the person who attended the session.
It documents the decisions. "The prices are in this field and nowhere else, so they stay consistent" is a design decision captured in the place the client will look for it.
What it does not replace
A short call after launch to answer questions is still worth having, because some people need to ask before they will try. And the written handover document still exists for the things a video is bad at: lists of accounts, renewal dates, the plugin list. The video is for how; the document is for what.
Making your own
If you maintain your own site, or inherited one with no handover, record your own. Any screen recorder (the built-in ones on Mac and Windows are fine, or Loom). Talk through the six or seven tasks you actually do, on your real site, as you do them. Fifteen minutes. Save it where the next person, or you in six months, will find it. It is the cheapest piece of documentation a business website can have.
Where this sits
The recording is part of every website we deliver and every site onboarded onto a care plan, made the day the site goes live and updated if the admin changes meaningfully. It costs us half an hour. It saves the client the awkward email, and it is the reason the support requests we get are for things that genuinely need a developer.