Make the boundary visible
Describe the deliverables, locations, dependencies, and responsibilities of each party. Identify who approves changes and how completion will be checked. A clear scope helps distinguish included work from later additions before a project begins.
Make acceptance criteria explicit
Define what completed work means before the project starts: agreed equipment, installed applications, user readiness, documentation, and handover approval. Name the project contact and record site-access or scheduling dependencies. Ask the proposal to separate included work, exclusions, optional items, and changes that need a revised quote. These details help a team compare the delivery with the scope it approved.
Your checklist
- Deliverables and exclusions
- Dependencies and responsibilities
- Acceptance criteria