Let staff edit pages without publishing unfinished work

What this means for your practice

Match content permissions to the actual editorial process. Give editors a safe preview and make the distinction between saving a draft and publishing a change clear.

A practical example

For example, reception might correct contact information in a draft while a designated colleague checks and publishes it. The arrangement should suit the practice rather than add unnecessary steps to every typo. Ask what happens when someone changes a shared page layout or is away. A good result gives staff confidence to make routine edits while keeping unfinished or unreviewed information off the public website.

Use clear role names in the team's instructions. Staff need to know who can draft, review and publish, not interpret a technical permissions table. Review those responsibilities when people change roles, so website access continues to match the work the practice actually expects them to perform.

Make this improvement work

Describe the real publishing roles before configuring permissions. Some staff may prepare wording, others verify facts and a smaller group may release changes. The system should make a saved draft visibly different from a public page, with a preview that helps reviewers understand what visitors will see. Ask the supplier to demonstrate an unfinished fictional edit using each relevant role. Include the situation where an approver is absent so work does not become ownerless. Keep access under review as responsibilities change. The aim is a manageable editorial process with clear accountability, rather than granting publishing access to everyone because it avoids configuring a review step.

How to check the result

Track unintended releases and unclear publication ownership.