Brand authority
Name who can approve voice, offers, factual claims, sensitive topics and exceptions for each brand.
Governance should help a team make the next decision safely. It is not a long document nobody checks during production. A useful multi-brand system defines who owns each brand, which facts and risks need escalation, how access is separated, what approval protects, when publishing stops and which evidence closes the loop. The rules stay close to the work and change through a named process.
This guide is an operational framework, not legal or regulatory advice. Adapt retention, escalation and review requirements to the organisation, markets and content risk.
Name who can approve voice, offers, factual claims, sensitive topics and exceptions for each brand.
Standardise access, versioning, delivery evidence and incident states without making brands identical.
Give every policy change an owner, reason, effective date and affected work so rules do not drift silently.
List every active brand, legal or business owner, operating team, approver, publisher, destinations, markets and languages. Add the service boundary and risk level. A shared workspace should increase visibility without granting every operator access to every client, token or sensitive draft.
Use a responsibility matrix for recurring decisions. Brand owners approve positioning and claims. Operators prepare and route work. Publishers control eligible destinations. Analysts define measurement windows. Incident owners can pause future delivery. One person may hold several roles, but the role being exercised must remain visible.
Separate stable product facts, time-sensitive offers, comparative claims, customer evidence, regulated statements and creative opinion. For each class, state the accepted source, reviewer and expiry rule. A public page or approved brief can support a claim only within its real scope.
Keep prohibited claims and known uncertainties alongside approved language. When a source changes, identify scheduled and reusable assets that depend on it. The policy should make it easier to say “not verified yet” instead of rewarding confident wording with no evidence.
Grant access by named brand and task. Separate creating, reviewing, scheduling, publishing and viewing metrics. Contractors and clients should see only their assigned work. Removing a user revokes future access while keeping historical attribution on decisions they already made.
Route approval according to risk. Low-risk evergreen content may use approved patterns or sampling. Price, legal, sensitive event, client account and high-impact campaign content can require blocking review. Publish the rule and test bypass attempts so speed never depends on hidden exceptions.
A calendar state is not remote delivery. Define eligible account, supported format, current consent and evidence required before publication is called successful. Unknown provider outcomes remain unknown until reconciled. Manual paths stay explicit and receive a named owner.
Create a pause rule for sensitive events, compromised access, invalid offers and provider failures. State who can stop a brand, campaign or destination, how future items are found, what happens to in-flight work and who authorises restart. Practice the rule before a real incident.
Track policy exceptions, expired claims, unapproved attempts, access reviews, delivery uncertainty, manual interventions and time to resolve blocks. These measures show whether controls work. Reach and revenue remain separate campaign or business outcomes.
Run a short monthly portfolio review. Retire obsolete rules, assign unresolved exceptions and sample evidence from several brands. Record the next effective version. Governance stays useful when it reduces ambiguous decisions and leaves an understandable history, not when it accumulates pages.
These Cascads pages define product, approval and reporting boundaries. They do not replace organisation-specific legal review.
It is the operating system for ownership, claims, access, approvals, publishing, incidents, evidence and controlled change.
Brands need distinct context and authority. Shared controls can standardise access, states and evidence where the risk is genuinely common.
Name a portfolio policy owner and one accountable owner per brand. Specialists can advise, but each decision still needs authority.
Review on a fixed cadence and after material brand, team, provider, policy or incident changes.
Validate the workflow, permissions and evidence before expanding the scope.
Create a Cascads workspace