Assign one owner to website opening hours

The decision this workflow supports

Hours can appear in a footer, contact page, menu and chatbot answer. Without an owner, a change may reach one surface and leave the others behind. Start with a small inventory of where the schedule is displayed.

Put the review process in place

Name the manager who approves hours and the person who publishes them. Store each change with an effective date and affected service. Check every listed surface after publication, including the answer the phone assistant gives for that same date.

Worked example for your team

A fictional schedule update moves one lunch opening time but leaves dinner unchanged. The publishing owner should update the relevant entries and test both questions on the live website and assistant. The dinner answer should remain as approved. Ask a second reviewer to compare the footer, contact page and phone reply without access to the editor’s notes. Any disagreement should be recorded with its location. This makes the check about the information guests actually receive rather than whether a single internal document was successfully edited.

Sample wording to approve

“These are the restaurant’s published service hours for [date]. If you need information about a different service or a special arrangement, staff can review that question.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need approved schedule, effective date, affected pages, publishing owner, and verification result. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

The contact page and footer agree. A dated exception overrides only the intended service. The assistant reads the same approved information as the website. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides