Worked example: publish a change to practice hours

One change across several places

This scenario uses fictional operating details and is not a customer case study. A practice wants to change Wednesday telephone availability from 08:00–12:00 to 09:00–12:00. The information appears on its contact page, in an FAQ and in its website assistant's knowledge. Consultation hours stay unchanged. The request must preserve that distinction.

Create one approval record

The responsible person records the old value, new value, effective date and affected locations, with the instruction “telephone availability only”. Drafts are produced from those facts. Medical statements, patient names and explanations about individual staff do not belong in this task.

The German and English versions must express the same fact. “Telephone availability” must not become “opening hours”. A second person checks both versions against the approval record and approves the exact version.

Publish in a controlled sequence

Save the CMS draft and inspect its preview first. Publish after approval, then update the assistant's knowledge from the same approved information. If that connection has not been configured, record the knowledge update as an outstanding task rather than assuming it happened.

Test three outcomes

• The German and English contact pages show Wednesday 09:00–12:00 specifically as telephone availability.
• The FAQ agrees with the contact page and leaves consultation hours unchanged.
• Asking the assistant “Can I call at eight on Wednesday?” produces the updated information or an honest reference to the contact page.

Keep a recovery path

Retain the previous content as a version. If the update is wrong, restore that version to a draft, review it and publish it. Record when the change happened, the approving role and the checks that passed. The useful measure here is completeness across the affected locations. This worked example does not establish fewer calls or saved staff hours.