Publish a menu update with an owner and review date

The decision this workflow supports

A menu change can leave old links, images and downloadable files in circulation. The publishing task is not complete when a new file is uploaded; guests must also reach the intended current version.

Put the review process in place

Have the menu owner approve the content before publication. List every public link that should point to it and remove obsolete promotional references. Keep an internal version note so staff can identify what changed when a guest reports a discrepancy.

Worked example for your team

Imagine the menu owner approves a new version while an older file is linked from an event page. Updating only the main menu button leaves a conflicting route. The reviewer should follow the known public links and identify any stale copy before closing the task. Keep the old version identifiable internally so a guest’s screenshot can be understood later. A check of the file name alone is insufficient: open the destination and read the relevant content. The publishing outcome is a coherent guest journey to approved information.

Sample wording to approve

“This is the menu information currently published by the restaurant. Staff confirm current availability and any specific questions; the website does not accept an order through this information page.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need menu version, approval date, affected links, content owner, and reported discrepancy route. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

The main menu link opens the approved version. An old promotion is not shown as current. Staff can identify the version a guest was viewing. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides