- 0:00–0:06
Start with a task • Assign one unassigned visit. • Coordinator • V-104 · Unassigned • Assignee: — • Illustrative visit · no assignment yet
A visit awaits an accountable owner.
- 0:06–0: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.
- 0:12–0: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.
- 0:18–0: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.
- 0:24–0: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.
A silent 30-second explanation in five six-second beats. A visit assignment connects a defined task, permission rules and saved-record evidence for an acceptance decision.
Read the article: Custom Software Requirements: Write a Brief Your Team Can Accept