Building a Consistent Scent Program Across Multiple Properties

Scenting one building is a purchasing decision. Scenting twenty is an operations problem, and the failure modes are completely different.

The thing that breaks is almost never the fragrance. It is consistency.

What consistency actually requires

Most multi-site programmes drift, and they drift for four identifiable reasons.

Different buildings, same specification. A twelve-foot lobby and a twenty-five-foot atrium need different coverage. If the same unit count is applied to both because it worked at the first property, one of them will be under-scented and read as a failure of the fragrance.

Different service cadences. If properties are serviced on different schedules, they are at different points in the cycle at any given moment. Walk two buildings in the same week and they smell different, and nobody can explain why.

Local substitution. Someone at a property runs out, buys something locally, and the portfolio now has two fragrances. This is far more common than anyone expects, and it is usually discovered by a regional on a site visit.

Formulation drift. Lower-cost fragrance materials are less stable and can vary between batches. What was specified and what is in the building eighteen months later are not always the same thing.

What a portfolio standard looks like

One fragrance, specified centrally. Not one per region, not one per property manager's preference. The recognition effect — the thing that makes scent worth doing across a portfolio at all — depends entirely on sameness.

Coverage specified per building, not per portfolio. This is the point most programmes get backwards. The fragrance is standard; the equipment specification is not. Each building gets a coverage calculation based on its own volume, zoning and air handling.

A named zone list. Decide once which spaces are in scope — lobby, leasing office, model units, corridors, amenity, fitness — and apply it everywhere. Ad-hoc zone decisions at property level are how portfolios diverge.

A single service relationship. One vendor, one cadence, one point of accountability. Programmes that are locally procured become locally variable within a year.

Documented intensity settings. Intensity should be a recorded specification per zone type, not something adjusted at each property by whoever receives the complaint.

How to roll it out

Pilot first, and pick the pilot carefully. Choose a property that is representative rather than flagship. A programme tuned on your best building will underperform everywhere else.

Run it long enough to stop being new. A week is enough to judge a fragrance; it is not enough to judge a programme. Watch for what staff say after the novelty passes.

Expand in batches, not all at once. Each batch teaches you something about specification that the pilot did not.

Decide in advance what you are watching. Resident or guest comment, staff feedback, complaint volume, and whether the leasing or sales team reports any difference. Deciding afterwards what counted as success is how programmes get cancelled on a hunch.

What to expect in year two

Programmes that survive have three things in common: someone owns the standard centrally, the fragrance has not been changed, and coverage was specified per building rather than copied.

Programmes that fail usually did one of two things — allowed local variation, or bought on unit price rather than coverage. The second is the expensive mistake. Coverage is what you are actually purchasing, and a lower price per unit that requires twice as many units is not a saving.

It applies across every vertical we serve, including apartment and multifamily scenting, casino scent marketing, senior living scenting, commercial property scenting, and hotel scenting. Related reading: Designing a Signature Arrival Experience for a Boutique Hotel Group, Building a Portfolio-Wide Scent Standard: A Playbook for Multi-Site Property Teams.