The operational decision
Review factual accuracy, scope handling and useful contact instructions together. A useful measurement answers an operational question, such as whether office facts are correct or whether the pilot fits its agreed allowance. A large call count alone does not show useful coverage.
Prepare the workflow
Use separate measures instead of one opaque score; include the number of reviewed examples and keep unresolved failures visible.
Example wording for approval
“The example scorecard records correct public facts, successful boundary redirects and clear contact instructions as separate results. A strong result in one does not erase another failure.”
Worked example
A fictional review checks ten calls: all public hours answers are correct, but two conversations fail to redirect patient requests. A combined average could make the launch look satisfactory. Show factual accuracy and boundary handling as separate measures, with the sample counts visible. The boundary defect requires correction even though the ordinary FAQ answers work. After fixing it, rerun both kinds of test so the team does not accidentally damage accurate public answers while strengthening the redirect.
Handoff record
Record these task-specific fields: metric definitions, review count, failure categories, action owner.
Acceptance check
Give the pilot perfect hours answers but a failed patient boundary. The scorecard should show the boundary failure plainly and trigger corrective action.
Try Ava with your business’s public information ↗