Exclusion is a decision, not an oversight
A scope that lists only inclusions leaves everything else ambiguous, and the ambiguity always resolves in favour of assumed coverage. A site manager reading a comprehensive-sounding contract will reasonably believe the boiler room is included. When it emerges that it was not, the conversation is about what the contract meant rather than about who should have been servicing the room.
Naming exclusions removes that entirely. It takes a paragraph and it tells the site precisely where its own arrangements need to extend. It also prompts a useful review, because a site listing its excluded rooms sometimes finds one that has no arrangement of any kind and has not been entered for a considerable time. Recording the exclusions in the same document as the inclusions is what removes the ambiguity, since a separate list is rarely read alongside the scope.
