Brief method
Put the out-of-scope line in the brief
A brief can be checked only when it says what the work will not do, in the same place as the promise.
A promise without a boundary grows during the work. This guide puts one out-of-scope line next to the outcome so a later check can say what was never part of the job.
Write the outcome and the boundary together
The outcome says what a reviewer can observe. The boundary says what this piece of work will not decide.
A fictional brief says: the page shows the saved title after refresh. Out of scope: phone layout, account permissions, and search ranking. Both lines stay in the same note.
Use the boundary when someone adds a task
A new request is either inside the outcome or past the boundary. If it is past the boundary, write a new brief. Do not silently widen the first one.
If you do widen it, keep the old boundary and date the change. A brief that only shows the latest scope hides what was agreed.
Check the work against both lines
A pass means the outcome happened. It does not mean the out-of-scope items were done. Mark those items not in this brief.
A fail on an out-of-scope item is the wrong fail. It means the check used a promise the brief did not make.