How do you govern multi-BU Marketing Cloud?

Scale without a freelance clearinghouse

Enterprises with many business units cannot let every BU invent sending standards. Shared naming, shared suppression truth, and shared escalation paths are deliverability and throughput controls, not bureaucracy for its own sake.

RHG’s enterprise work includes multi-BU patterns at IHOP-scale Marketing Cloud estates (~260 internal BUs). The lesson is not “hire more freelancers.” The lesson is an operating standard with teeth.

What must be shared

Federate brand expression. Centralize these.

• Naming conventions for data extensions, journeys, and content
• Suppression and consent truth
• Send classification discipline
• Authentication / SAP / domain change control
• QA gates before major launches
• After-hours escalation path
• Orphaned BU detection and cleanup

What can stay local

Creative, local calendar priorities, and BU-specific journey logic that respects shared standards. Local teams still need a path to request exceptions without inventing shadow systems.

Ownership model

Governance without an operating unit becomes a PDF. Someone has to run the weekly rhythm, police forks, and absorb peak weeks with people who already know the stack.

That can be a strong internal core, a Cell, or a hybrid with clear boundaries. See in-house vs outsourced Cell. Fake-managed retainers that invoice one line while every BU freelances standards will fail at scale.

How to install standards without a revolt

Start with one painful shared control: suppression truth or naming. Publish the standard, offer migration help, measure reopen tickets and launch slips before/after. Widen once the rhythm is real. Big-bang governance resets recreate old handoffs at higher volume.

RFP and partner language

Ask partners how they handle naming standards, shared QA, and orphaned BUs. Vague “we support multi-BU” answers are not enough. Use RFP questions and the scorecard.