Exclusions are anything that isn’t included as a deliverable or work for the project. It’s important to list exclusions in your scope documentation so there is no misunderstanding about features or deliverables once the product is complete. 

Think of exclusions as corporate or user assumptions all interested parties might make from the gist or title of your project.  For example,

Scope: Update to the latest Microsoft Office


  • Netherland users due to pending upgrade of European software
  • Accounting was upgraded at the beginning of this year
  • Only Engineering will receive the Pro version

Think of the lunchroom buzz about an “Office upgrade” and the expectation employees may have.  But how will they learn of accurate details?  Department meeting?  Water cooler chat?

No, your communication plan.