Primitive versus attribute
Most platforms let you record a location against a record and filter on it. That is location as an attribute, and it exists only on the objects where someone added the field: so leads may carry a branch while attendance records, invoices and tickets do not, each with its own populating convention and its own drift.
Location as a primitive means branch lives in the shared data core, so every module inherits it. Permissions are configured once and apply identically across leads, attendance, payroll cost and support tickets; branch comparison requires no setup; and adding a location is configuration rather than a project.
Branch, center and owner
Three related axes. Branch-wise scopes by geographic operating unit: office, showroom, depot, clinic. Center-wise is the education and training equivalent, where a center has its own enrollment pipeline, center head and fee collection. Owner-wise scopes by responsible individual, which is where coaching actually happens. A branch at the network average may contain one strong performer and two who need support.
Who needs it
Franchise networks, multi-branch service businesses, multi-center coaching institutes, multi-clinic healthcare groups, dealer and distributor networks, and any business running field teams. The cost of getting it wrong does not appear during evaluation: it appears at the second location, after migration.