Project boundary sheet template
By Kivrelune Studio

Project boundary sheet
Make inclusion, exclusion and acceptance explicit before people commit to delivery.
Included work
Deliverable [name]: [specific output], for [audience], accepted when [test]. State quantity, versions or supported environments when relevant.
Outside the boundary
Excluded: [adjacent request]. The client or another team supplies [dependency] by [date]. If [assumption] changes, revisit [affected item].
Change agreement
Requestor records [change and reason]. Lead estimates [time and cost impact]. Approver [role] accepts or declines before the baseline changes.
Using this template
Review each proposed deliverable with its receiving owner and turn the boundary into a concrete acceptance test. Identify exclusions and client dependencies openly, then agree who assesses and approves any request that changes the baseline.
Questions & answers
Looking for more help? Visit the Help center.
What should we do with work that both teams assumed the other would provide?
Record the item as an unresolved dependency and quantify its effect on acceptance. Assign one provider and due date, then update the boundary with both teams' agreement.
What is included in this template?
Included work · Outside the boundary · Change agreement. Each section includes prompts you can adapt to your team.
How can the project team keep this current?
Give each open decision an owner and a due date. At the next checkpoint, update the milestone and record the work that changed since the last review.
How do I use my own copy?
Choose “Start with this doc” to open an editable copy on this device. You can also copy the Markdown or download the file and use it in your own editor.
