When you have multiple physical buildings units you need to manage, setting up a Site is a straight-forward process. But what happens if you have multiple areas in a single Site? e.g. You have 50 locations to manage nationwide, and each of them has a group of 3-5 buildings, and each building has between 3-5 areas. Which one would you mark as a Site in your system?
To define your Site you need to envision your future needs. Orders will be linked to Sites; thus, you'd need to setup your Sites not necessarily following physical locations but more like a logical structure that makes sense to your work accomplishments. Don't forget in platforms like Sweven you also have Assets, you can use them to note the lower-level item on each Site. Also, you have Clients as the upper-level item to Sites. And you have Projects and Sub-Projects for further definition. Using all these levels you could properly accommodate your data in a way that ensures consistency at the time of accountability. For example, going back to our first example, each large location could be a Client in your Project X, inside each location each building could be a Site, and each Area inside a Site could be an Asset. You could execute orders grouped in Sub-Projects so you can track cost and other variables on a per Contract item level.