What the product must do, for whom, and what is deliberately out of scope.
Agents are enthusiastic about scope. A requirements document with an explicit out-of-scope list is the cheapest way to stop one building the feature you already decided not to build.
# Product requirements ## Problem Clinics lose around one appointment in ten to no-shows, and rebooking by phone takes staff hours each week. ## Who it is for - Reception staff booking on behalf of patients - Patients rescheduling from a text message ## What it must do - Book, move and cancel in under a minute - Send a reminder 24 hours before ## Out of scope - Payments - Clinical notes ## How we will know it worked - No-shows fall below one in twenty - Staff stop keeping a paper diary alongside it