Article guide
  1. Use a fixed template
  2. Write observable steps
  3. Describe exceptions
  4. Maintain the page
  5. Common questions

Standard work is a shared reference for a repeatable task. It should help a new or covering receptionist act correctly without hiding important exceptions in tribal knowledge.

Use a fixed template

Start with purpose and trigger. Then list the normal steps, decision points, record to update, accountable owner, backup, escalation route, and review date. Link to the current policy or script rather than copying a second version.

Write observable steps

“Check the queue” is vague. “Open the unassigned callback view, sort by due point, and assign each item to the approved owner” is testable. Use exact field or status names when that helps staff find the right place.

Describe exceptions

Include only exceptions that change the next action, such as an identity mismatch, possible urgency, missing authorization, or unavailable owner. Say what staff should do and what they should not promise.

Maintain the page

Give the document an owner and review it when a policy, system, staffing model, or service changes. Archive old versions according to retention rules. Ask staff to report friction so the standard work reflects the real day.

Common questions

The template makes correct work easier and outdated work harder. It is not a substitute for clinical judgment, privacy policy, or local legal review.

Sources and verification notes

Sources support the specific guidance identified above. Policies, prices, and service scope can change; verify current details before relying on them.

Common questions

What sections should standard work include?

Include purpose, trigger, steps, decision points, owner, source record, escalation route, and review date.

How long should a standard-work page be?

As short as possible while covering the normal path and important exceptions. Link to detailed policies instead of duplicating them.