Make requirements reviewable
Silent video.

[0–6]
Start with a task • Assign one unassigned visit. • Coordinator • V-104 · Unassigned • Assignee: — • Illustrative visit · no assignment yet
A visit awaits an accountable owner.

[6–12]
Name the rules • Agree eligibility and permissions. • Permission check • Coordinator role • Active account • Service-team member • Agree eligibility; scope scheduling separately.
Assignment depends on agreed rules.

[12–18]
Keep exceptions separate • Check retry, conflict and denied access. • Retry • One assignment? • Conflicting edit • Which edit wins? • Denied access • Record unchanged • Separate scenarios, separate evidence
Different failures need separate checks.

[18–24]
Check beyond the screen • Compare the response, record and fresh page. • Request + response • V-104 · T-17 • Saved record • Fresh page • Expected fields · verify the actual values
A success message alone is insufficient evidence.

[24–30]
Record acceptance • Name the reviewer, build and evidence. • Review decision • Reviewer: record who • Build: record version • Evidence: record location • Pending until inspected
Acceptance follows inspection of a defined requirement.