Project scope statement

A project scope statement is a shared, written record of a project's purpose, results, exclusions, constraints, and acceptance criteria, agreed by stakeholders before work begins.

Its job is to settle, in writing, what a project is and — just as importantly — what it is not, so that scope disagreements get resolved once at the start rather than repeatedly during execution. Kanbai's version is drawn from the 17-book project-management corpus (specifically Project Management for the Unofficial Project Manager) and structures the answer into five sections: the project's purpose, the concrete results that will exist when it's done, explicit exclusions, constraints on time/cost/resource/quality, and the acceptance criteria that will be used to judge completion. It's one of Kanbai's seven corpus-grounded instruments — fillable per-project, or standalone with no account needed — and exports as Markdown identical either way. A scope statement differs from a statement of work in emphasis: the scope statement is about boundaries and acceptance (what's in, what's out, how we'll know it's done), while a statement of work formalizes the working relationship among stakeholders — deliverables, cost/schedule estimates, and chain of command.