Suppose a Karlıtepe workshop plans to open late on two Saturdays. The site editor needs to enter both dates on Friday and leave the normal timetable in place for other weeks. Run that job during the CMS handover so the team can see what visitors will see at the beginning and end of each exception.
Give editors the same schedule to work from
Prepare a sample timetable that opens at 09:00 on Saturdays, with two dates that open at 11:00. Record the time zone, the two dates and the person authorised to approve changes. In preview, compare the shop page and any shared hours block with the timetable the editor received.
Observe the start and end of an exception
Use a test environment with its clock controlled, or place the test times a few minutes apart. Open the public preview on both sides of the start and end times. Check that the correct hours apply to the selected branch and date, and check again from a page that was already open before the change.
Rehearse two edits to the same date
Ask one editor to save 11:00 and a second to prepare 10:00 for the same Saturday. Check whether the CMS exposes the overlap or allows the second edit to replace the first. If there is no warning, make the approval step include a review of all exceptions for that date. Confirm which time actually appears after approval.
Recover from an approval mistake
In the test CMS, approve the wrong time deliberately and ask the duty editor to correct it. Check the preview, any shared block and the next regular Saturday after the two exceptions. Keep a record of who corrected the entry and which date changed so the next editor can confirm it without guessing.
Checklist before publishing
- Dated exceptions are scoped to a branch and time zone
- Opening hours tested before and after the exception
- Overlapping drafts visible during approval
- Regular schedule verified after correction