**In short:** governing brand assets in franchises and cooperatives requires three structures: a central library with the approved version of each piece, permissions by unit profile and distribution that only delivers validated material. Without all three, standardization depends on policing, and policing does not scale.

Headquarters finds out through a screenshot in the group chat. One unit posted the old campaign, another recreated the artwork in Canva with the wrong font, and the brand team spends Monday putting out fires that should not exist. Anyone who runs a network knows the scene.

The problem is not bad will at the edge. The unit publishes what it finds, and what it finds is the outdated folder someone emailed in March.

## The three structures that replace policing

1. A central library, with approved versions only.
2. Permissions by profile, unit and region.
3. Active campaign distribution, with final material and controlled editables.

A brand manual in PDF, in my opinion, is a document of good intentions: it describes the right brand and does not prevent the wrong piece. Real governance happens where the file lives, not where the rule is written.

## How the big Brazilian networks run this

A major national beauty group governs multiple brands with hundreds of approvers on Wikimee, with an approval workflow before any piece reaches the edge. One of the largest cooperative networks in the country has distributed brand material to dozens of cooperatives and thousands of users for nearly a decade through the same structure: central portal, per-cooperative permissions and packaged campaigns, instead of email with attachments.

The pattern common to both cases: the edge's autonomy was not cut, it was delimited. The unit chooses what and when to publish, within a library where everything is already approved. Frontify and Bynder attack part of this problem with brand portals, strong on guidelines. Wikimee's framing is the complete cycle in Portuguese: the piece is born in the workflow, approved with an audit trail and reaches the unit through the portal, without leaving the environment.

For the retail team, two topics complement this: managing digital publications in retail, and brand positioning. The complete distribution process for networks is in the [Academee Distribution journey](https://academee.ai/jornadas/distribuicao/), in Portuguese, including the Approved Material Only trail.

## The life cycle of a network campaign

Asset governance becomes concrete when you follow a campaign from birth to the edge. Headquarters creates and approves with an audit trail. The campaign is packaged: final pieces, editables with controlled fields, usage guidance and validity period. The units receive it through the portal, each seeing the scope of its region and profile. Local adaptation happens inside the controlled editable, without touching brand and layout. And measurement closes the cycle: which units downloaded, what was adapted, what sat untouched.

The last point is the least practiced and the most valuable for the next planning cycle. A campaign with 30% adoption at the edge is a diagnosis, not a failure: either the material did not fit local reality, or the deadline ignored the unit's calendar. Without measurement, that learning does not exist and the network repeats the mistake in the next campaign.

## Signs that governance has broken

1. The WhatsApp group became the file channel.
2. Units recreating pieces in Canva.
3. An old campaign circulating months after it ended.
4. Headquarters discovering publications by accident.

Any of the four points to the same underlying problem: the official path became slower or harder than improvisation. The fix is never demanding more policing, it is reducing the friction of the right path until it wins on convenience.

## Roles and responsibilities: headquarters, agency and unit

Network governance works when the three roles have written boundaries.

**Headquarters** sets the standard, approves institutional material and publishes packaged campaigns. Its responsibility ends where local reality begins: a headquarters that wants to approve each store's Mother's Day post becomes a national bottleneck within a week.

**The network's agency** produces inside the environment, submits to headquarters approval and sees the distribution to calibrate formats. An agency outside the environment is guaranteed rework: every delivery becomes someone's manual upload, and the metadata dies along the way.

**The unit** operates the portal: downloads the current material, adapts within the released fields, publishes on its market's schedule. And it returns the data headquarters does not have, local performance, closing the cycle for the next campaign.

The maturity test for the boundary is asking who approves what and getting the same answer from all three sides. When the answers diverge, outdated material at the edge is not indiscipline, it is consequence.

## Frequently asked questions

**How do we handle a unit that needs to adapt the piece locally?**
With controlled editable material: fields released for address and local offers, brand and layout locked. Adaptation happens inside the limit, not outside it.

**Does headquarters need to approve everything, always?**
No. Institutional pieces require approval. Tactical pieces adapted from an approved template can flow straight through. The criterion is defined by material type, not case by case.

**How long does it take for a network to adopt this model?**
One real reference: a major national beauty group onboarded multiple brands in a matter of weeks, starting with the campaign with the widest circulation.

**What about units that resist the change?**
Adoption comes when the approved path is faster than improvisation. If downloading from the portal is easier than asking in the group chat, the group empties out on its own.

**Cooperatives have real statutory autonomy. Does the model not violate that?**
No, because adoption happens by convenience, not imposition: the portal delivers faster than improvisation can. The local cooperative remains the owner of its decisions, now with current material in hand.

**Who pays for the platform in a federated structure: headquarters or units?**
The most common model: headquarters contracts it and the units operate at no cost of their own, because standardization benefits the whole system. Cost-sharing exists, but it adds political friction exactly where the project least needs it.

To see governed distribution operating in your network structure, [explore the platform](https://www.wikimee.com/pt_br/produtos/) and book a demo with the franchise and cooperative use case.

### Sources and references

- Canto, The State of Digital Content 2026, research on digital content, DAM and the ROI of connected workflows: [canto.com/resources/state-of-digital-content](https://www.canto.com/resources/state-of-digital-content/)
- Wikimee customer cases are cited anonymously due to confidentiality agreements. Verifiable details are available in a sales conversation, subject to customer approval.