The operational decision
Help practice teams find useful operating guidance without navigating a wall of similar titles. The website should let a visitor find public office information without starting an intake conversation. Build each page around a concrete visitor task and keep the route to the practice visible.
Prepare the workflow
Group resources by hours, directions, boundaries, testing and maintenance; use descriptive labels and link from each task to the next practical step.
Example wording for approval
“Choose the task you are working on: public office facts, caller boundaries, launch checks or ongoing review. These resources do not provide clinical advice.”
Worked example
The fictional resource index has twenty titles beginning A guide to better calls. A receptionist trying to correct holiday hours cannot tell which page helps. Replace that presentation with task categories and concrete titles such as Maintain a holiday-hours calendar. Link to the specific expiry or testing guide when it is the next step. The navigation test gives the reviewer a real operational task and records whether they find the correct procedure, not how many pages they visit.
Handoff record
Record these task-specific fields: category label, destination page, related task, editor.
Acceptance check
Give a reviewer a parking-update task and a boundary-testing task. They should find different relevant guides without opening several indistinguishable pages.
Try Ava with your business’s public information ↗