For Operators
The operator owns the building's behavior in practice: the scope statement is yours to maintain, the parameters are yours to publish and honor, and the review rhythm is yours to keep. The standard asks nothing heroic — it asks that what the building does be defined, published, and held.
The publish-then-honor discipline
Most of the standard's hard obligations bind the building to parameters it publishes itself. Choosing the parameter is your freedom; publishing and honoring it is the requirement. The inventory below is every published parameter the expectations reference — together they are the operator's setup checklist:
| Published parameter | Defined in |
|---|---|
| Delivery notification timeframe · retention period · disposition notice | Deliveries × Clarity |
| Temperature-storage policy and duration | Deliveries × Care |
| Enhanced-verification categories for retrieval | Deliveries × Grace |
| Space rules: hours, capacity, guest policy, charges, safety requirements | Spaces × Clarity |
| Readiness standard per bookable space | Spaces × Grace |
| Allocation parameters: booking limits, advance window, no-show policy | Spaces × Care |
| Grace period · end-of-booking transition mechanism | Spaces × Harmony |
| Deactivation timeframe · post-move-out record access period | Lifecycle × Reliability |
| Notification lead times per deadline type | Lifecycle × Clarity |
| Self-service and approval boundaries, with processing times | Lifecycle × Control |
| Data policy: what is collected, retention, access and deletion | Lifecycle × Care |
| Monitoring disclosure: what is detected, what is not | Environment × Reliability |
| Environmental standards: comfort ranges, thresholds, maintenance schedules | Environment × Care |
| Fallback communication method | Environment × Care |
| Alternative methods: location and instructions per domain | Access × Care and the Care row |
A parameter no resident can find does not count. The scope statement — active domains, primary interface, and this inventory — is published where residents can read it (Conformance).
The review rhythm
Drift is the operator's permanent adversary: a notification rule disabled to quiet a complaint and never re-enabled, a workaround that became permanent, a vendor update that changed a default. The Introduction's governance principles apply to your operation directly — changes are intentional, the documented behavior is the reference, review is a rhythm, and governance is an assigned responsibility with a name. The Tests make self-examination concrete: a quarter's rhythm of running them, domain by domain, finds drift before residents do.
The standard and your satisfaction program
If you run a satisfaction or sentiment program, keep both: they answer different questions. Sentiment tells you how residents feel and where to look; the standard tells you what the building did and what to fix. A falling score in one touchpoint area, read against that domain's expectations and failure modes, usually resolves into a specific unmet behavior — the structural cause under the sentiment. Neither replaces the other; the pairing is the diagnostic.
When the operator changes
Run to the standard, the building you hand over — or inherit — carries its definition with it: scope statement, parameters, records, expectations. What that inheritance looks like from the owner's side is in For owners and acquirers; the obligations that typically sit in the management agreement are in Specifying the Standard.