One Project. Five Organizations. Whose Brand Is It? A St. Louis Guide to Better Co-Branded Communication
Partnerships become difficult to recognize when every organization tries to lead visually. Strong co-branded communication defines who owns the message, how partner identities appear, what stays shared, and what can vary before the first brochure, presentation, campaign, or event asset is designed.
The project involves five organizations.
Each is important.
Each has:
a logo;
brand colors;
preferred fonts;
communications team;
approval process.
The first flyer arrives for review.
Organization A wants its logo larger.
Organization B wants its color used more prominently.
Organization C asks why its full legal name is missing.
Organization D wants the layout redesigned around its brand guidelines.
Organization E says:
“Can we just make all the logos the same size?”
The designer makes revisions.
Now there are five logos across the top.
Five colors.
Three typography styles.
Two taglines.
A partnership statement.
A disclaimer.
And almost no room left for the actual message.
Everyone is represented.
The communication is not.
This is the central problem of co-branded design.
The goal is not to fit every partner’s brand onto one page.
The goal is to create one understandable communication system for a shared initiative while giving each organization the appropriate level of recognition.
That requires decisions before design begins.
Start With the Relationship, Not the Logos
Before arranging logos, determine what kind of partnership actually exists.
A joint initiative may involve:
a lead organization;
equal partners;
supporting organizations;
funders;
sponsors;
delivery partners;
technical contributors.
Those roles are not identical.
They should not automatically receive identical visual treatment.
Ask One Question First: Who Is Speaking?
When the audience sees the communication, who should they understand is responsible for the message?
Is it:
one organization with partners?
Two organizations jointly?
A completely separate initiative?
A coalition?
A sponsored program?
The answer changes the identity structure.
Model 1 — Lead Brand With Supporting Partners
One organization owns the initiative.
Others support or participate.
A practical visual structure may be:
Lead Brand
Primary identity.
Supporting Partners
Secondary recognition.
The lead organization’s system can usually provide:
typography;
color;
layout;
graphic language.
Partner identities appear in an agreed supporting area.
Do Not Pretend the Partners Are Equal if the Relationship Is Not Equal
Artificial equality creates confusing communication.
If one organization:
owns the program;
manages delivery;
receives applications;
handles customer service,
it should usually be clear.
Equal logo sizes should not obscure operational responsibility.
Model 2 — Equal Partnership
Two or more organizations genuinely share ownership.
Now neither brand should appear as a decorative addition to the other.
The communication may require:
a shared campaign system;
neutral visual territory;
balanced attribution.
This does not necessarily mean merging every brand together.
It means designing an appropriate shared space.
Equal Partnership Does Not Require Visual Sameness
The logos may have different proportions.
One is horizontal.
Another is compact.
Making them numerically identical in width can make one appear:
much larger.
Use optical balance, not arbitrary measurement.
Model 3 — Independent Initiative Endorsed by Partners
Sometimes the program itself needs recognition.
For example:
a multi-year workforce initiative;
industry partnership;
community program;
joint research effort.
The initiative may have:
its own name;
visual language;
communications system.
Partner identities then appear as:
founding;
supporting;
participating;
endorsing organizations.
Do Not Automatically Create Another Logo
A new initiative does not always need:
another permanent identity.
Ask whether the program has:
sufficient lifespan;
independent audience;
ongoing communication;
strategic importance
to justify one.
Sometimes a clear campaign title within an existing system is enough.
Model 4 — Coalition Communication
A coalition can include:
many organizations;
different sectors;
different levels of involvement.
Trying to make every brand lead equally can make the communication impossible to scan.
Coalition design needs:
a shared message first;
member recognition second.
The Audience Should Understand the Initiative Before Reading the Logo Strip
This is an important test.
Cover all the partner logos.
Can the viewer still understand:
what this is;
why it matters;
what action is expected?
If not, the design is relying too heavily on organizational recognition.
Sponsorship Is Different From Shared Ownership
This deserves a clear distinction.
A sponsor may deserve:
recognition.
A co-owner needs:
authorship.
Those are not the same thing.
Our earlier Nashville article focused on sponsor hierarchy inside event communication.
This St. Louis article addresses a different problem:
how organizations jointly communicate when several brands genuinely participate in creating or delivering the initiative.
Define the Brand Roles in Writing
Before design begins, create a simple hierarchy.
For example:
INITIATIVE
Primary communication identity.
LEAD ORGANIZATION
Operational owner.
CORE PARTNERS
Joint delivery.
SUPPORTING PARTNERS
Secondary contributors.
SPONSORS
Recognition according to agreement.
Now design can reflect an agreed structure.
Do Not Let the Designer Negotiate Partnership Politics
If stakeholders disagree about:
whose logo is first;
who is described as lead;
which organization owns the program,
resolve that before visual production.
Design should visualize the partnership structure.
It should not invent it.
Create One Shared Message
Multiple partners often arrive with multiple descriptions.
Organization A calls the initiative:
a workforce development program.
Organization B calls it:
an industry training partnership.
Organization C calls it:
a talent pipeline initiative.
All may be partially correct.
The audience should not receive three competing explanations.
Approve a Core Description
Create one short statement that answers:
What is the initiative?
Then use it consistently across:
website;
brochure;
presentation;
social content;
event material;
emails.
Partner-specific communications can adapt the introduction.
The central meaning should remain stable.
Build a Message Hierarchy
A useful structure is:
WHAT
What is the initiative?
WHO
Who is it for?
WHY
Why does it matter?
PARTICIPATION
What can the audience do?
PARTNERS
Who is involved?
Notice that:
partner logos are not the first question.
Design the Shared Communication Before the Partner Area
This helps prevent the partner strip from taking over the composition.
Start with:
message;
audience;
action;
information hierarchy.
Then allocate partner recognition appropriately.
Create a Logo Architecture
Instead of manually arranging partner logos for every asset, define a system.
For example:
PRIMARY
Initiative or lead identity.
SECONDARY
Core partners.
TERTIARY
Supporting organizations.
This creates consistency.
Logo Order Should Have a Rule
Possible rules include:
role hierarchy;
contractual agreement;
alphabetical order.
Choose one.
Do not change it depending on:
who requested the asset.
Alphabetical Order Can Reduce Unnecessary Debate
For genuinely equal partner groups, alphabetical ordering may be a practical neutral option.
It is not always appropriate.
But it can remove subjective ranking.
Define Logo Spacing Once
Partner strips often become inconsistent because each designer:
moves;
resizes;
reorders
the marks.
Create:
minimum spacing;
maximum height;
alignment;
background treatment.
Then reuse the same lockup.
Give Logos Enough Breathing Room
Do not force marks together to save space.
Partner logos may contain:
different shapes;
colors;
taglines.
Crowding them reduces legibility.
Consider a Separate Partner Panel
Not every logo needs to sit beside the headline.
For some materials, recognition can appear in:
footer;
back cover;
closing slide;
dedicated partner page.
This protects message hierarchy.
The First Slide Does Not Need Every Partner Detail
A presentation opening might contain:
initiative name;
primary message;
small approved partnership line.
A later slide can explain:
partner roles.
This is often clearer.
Create an Attribution Line
For example:
An initiative led by Organization A in partnership with Organizations B and C.
Or:
Delivered jointly by Organizations A, B and C.
The exact wording should reflect the actual relationship.
Text can sometimes explain partnership structure more effectively than logo sizing alone.
Do Not Invent Partnership Language
Words such as:
official partner;
strategic partner;
founding partner
can carry meaning.
Use only approved descriptions.
Choose a Shared Visual Language
Now decide how the initiative should look.
Three common approaches are useful.
Approach 1 — Use the Lead Brand System
This works when one organization clearly owns the communication.
Use its:
typography;
color system;
layout;
graphic devices.
Partner identities remain appropriately visible.
Approach 2 — Build Neutral Shared Territory
For equal partnerships, avoid making the communication feel like:
Organization A’s campaign with extra logos.
Create a restrained neutral system.
It might use:
a shared typography approach;
neutral base palette;
limited accent color;
common imagery direction.
Partner marks remain themselves.
Approach 3 — Create a Dedicated Initiative System
For large or long-term programs, create:
a defined initiative title;
graphic language;
templates;
usage rules.
Partner identities support it.
This can make repeated communication much easier.
Do Not Mix Every Partner’s Brand Colors
Five partner brands may contain:
blue;
red;
green;
purple;
orange.
Using all five as equal campaign colors does not create fairness.
It creates noise.
Choose Functional Color Roles
For example:
PRIMARY COMMUNICATION COLOR
Used for structure.
ACCENT
Used for emphasis.
NEUTRAL
Used for supporting information.
Partner brand colors remain inside:
their own logos.
This keeps the initiative coherent.
Typography Should Also Be Shared
Partner A uses:
serif.
Partner B:
geometric sans.
Partner C:
humanist sans.
The campaign does not need all three.
Select one approved communication typography system.
Logos Keep Their Identity
The surrounding campaign uses:
one shared type system.
That separation usually creates more clarity than trying to blend every brand language together.
Photography Can Unite the Partnership
A shared imagery direction can create recognition even when the logos differ.
Define:
subject;
tone;
crop;
lighting;
people;
environment;
technical imagery.
Use Real Context Where Appropriate
If the initiative involves:
manufacturing;
bioscience;
professional services;
mobility;
technology,
authentic sector imagery can help explain the program.
Do not depend only on:
abstract partnership graphics.
Graphic Devices Can Become the Shared Thread
A recurring:
line;
frame;
shape;
pattern;
grid
can help materials feel connected.
The device should support:
recognition
without pretending to be another corporate identity.
Build the Core Template System
A multi-partner initiative may repeatedly need:
presentation;
one-pager;
social graphic;
report;
event visual;
email header.
Create the recurring formats once.
Each Template Should Reserve Partner Space
The partner area should not be rebuilt from scratch.
Define:
placement;
Get Graphicdigits’s stories in your inbox
Join Medium for free to get updates from this writer.
maximum height;
spacing;
background.
Then the communication system stays stable.
Create Short and Long Partner Treatments
A small social graphic may not have space for:
six full logos.
A detailed report may.
Define acceptable treatments.
Digital Asset
May use:
initiative identity + short partnership attribution.
Report
May include:
complete partner panel.
Event Slide
May include:
approved partner strip.
The specific solution depends on agreements and brand requirements.
Never Hide Required Partner Recognition
Space limitations should be solved through:
format;
hierarchy;
placement.
Not by violating agreed recognition requirements.
Build a Partnership Asset Kit
A simple shared asset library can contain:
approved logos;
approved partner strip;
initiative colors;
fonts;
templates;
image library;
messaging;
usage guide.
This prevents every organization from rebuilding the system independently.
One Shared Library Is Better Than Five Email Chains
If each organization stores:
different logo versions;
old templates;
different copy,
the system will drift.
Create one current source.
Mark Approved Assets Clearly
For example:
CURRENT
Approved for use.
WORKING
Under development.
ARCHIVE
Do not use.
This makes distributed production safer.
Co-Branded Projects Need Approval Governance
Visual design can be solved in one afternoon.
Approval can take three weeks.
That is often the larger challenge.
Decide Who Approves What
For example:
MESSAGE
Program lead.
PARTNER REPRESENTATION
Partner communications contacts.
TECHNICAL CONTENT
Subject-matter owner.
FINAL RELEASE
Project owner.
Now every stakeholder does not need to approve every detail.
Do Not Give Five Organizations Unlimited Design Veto
If every organization can request:
any visual change,
the system may become impossible to manage.
Define review boundaries.
Partner Review Should Focus on Their Representation
For example:
Is the logo correct?
Is the organization named correctly?
Is the role accurate?
Is the approved claim correct?
They do not necessarily need to redesign:
the entire campaign.
One Project Owner Should Consolidate Feedback
Avoid:
five separate comment threads.
The project owner should resolve conflicts where possible.
Use One Review File
Not:
PartnerA_v3.pdf
PartnerB-comments.pdf
New-final.pdf
Create:
one controlled review version.
Define the Approval Deadline
Multi-organization projects often slow down because feedback arrives:
whenever each partner has time.
Use an agreed review window.
Explain What Happens After the Deadline
For example:
no response = approval
only if:
that rule has been formally agreed.
Do not assume silence means approval without agreement.
Build an Exceptions Process
Sooner or later, a partner will request:
a special version.
Perhaps:
their conference;
their audience;
their email campaign.
Decide what customization is permitted.
Core System + Partner Variation
A good model is:
FIXED
Initiative name.
Typography.
Core colors.
Partner hierarchy.
Primary messaging.
FLEXIBLE
Audience introduction.
Relevant image.
Supporting copy.
CTA.
This provides useful flexibility without fragmentation.
Do Not Let Every Partner Create a Different Version of the Same Initiative
If Organization A uses:
blue campaign.
Organization B:
red campaign.
Organization C:
green campaign,
the audience may think these are different programs.
Shared initiatives benefit from recognition.
Partner Channels Can Still Feel Native
A partner posting on:
its own social channel
may use:
its own account context.
The shared initiative creative can remain recognizable.
That balance is possible.
Co-Branded Presentations Need Special Attention
Joint presentations often create:
title-slide politics.
Whose logo goes first?
Whose template?
Whose contact information?
Solve this before the presentation is built.
Create a Shared Presentation Master
Define:
title slide;
section divider;
content slide;
data slide;
partner slide;
closing slide.
Then everyone works inside the same presentation language.
Speaker Identity Can Be Separate From Project Identity
A slide can identify:
speaker;
organization;
role
without turning the entire deck into:
their company’s presentation.
Reports Need Consistent Authorship
A joint report should make clear:
who produced it;
who contributed;
who funded it;
who endorsed it.
Those are distinct relationships.
Use an Attribution Page When Necessary
Instead of forcing every role onto:
the cover,
use a dedicated section.
This keeps the cover readable.
Joint Events Need Two Systems
Often there is:
the initiative identity
and:
event-specific communication.
Do not create:
a third disconnected brand unnecessarily.
Use the Initiative as the Parent
Then adapt:
event title;
date;
venue;
program.
The partnership remains recognizable.
Webpages Need Similar Discipline
A shared initiative may have:
one landing page
hosted on:
one partner’s website.
Make the partnership visible without making the user wonder:
whether they left the initiative.
One Primary CTA Is Better
If five organizations each add:
their own link,
the page becomes confusing.
Define the main action.
Secondary Partner Links Can Follow
Perhaps:
Learn About Partners
or:
Participating Organizations.
The primary user journey should remain obvious.
Email Communication Needs Sender Clarity
If Organization A sends the email but the initiative is jointly owned, clarify:
why the recipient is hearing from them.
Use a Consistent Subject-Line Pattern
For example:
[Initiative Name] — Registration Opens
or:
[Initiative Name] — Program Update
This builds recognition over time.
Accessibility Still Applies
Partner marks should not reduce:
contrast;
text size;
readability.
Do not squeeze the entire communication because:
another logo was added.
Information Comes Before Decoration
If partner requirements leave:
too little space for readable content,
change the format.
Do not solve it by:
shrinking everything.
Test the System at Small Sizes
A six-logo footer may work on:
a report.
It may fail on:
mobile social creative.
Prepare an approved small-format treatment.
Define the Minimum Recognition Treatment
For example:
initiative mark;
partnership line;
full partner panel on destination page.
The correct approach depends on partner agreements.
Do Not Create Fake Logo Equivalence
Some organizations have:
long horizontal marks.
Others:
compact symbols.
Use optical sizing.
Test in Grayscale
This can reveal whether:
one partner mark dominates only because of color.
Balance should work structurally.
Test on Dark and Light Backgrounds
Partner logos may have:
different background requirements.
Create approved variants where available.
Never recolor a partner’s logo without permission.
Do Not Rebuild Partner Logos
Use official assets.
No approximations.
No screenshot logos.
No improvised monochrome versions unless supplied or approved.
Create a Partner Asset Request Checklist
Ask each organization for:
approved vector logo;
PNG if needed;
dark-background version;
clear-space requirement;
usage restrictions;
approved organization name.
Collect these before design begins.
Brand Guidelines Should Be Reviewed Early
One partner may prohibit:
placing its logo below a certain size.
Another may require:
specific clear space.
Another may restrict:
color backgrounds.
Find those constraints before final layout.
Resolve Conflicting Brand Requirements
If two guidelines cannot both be satisfied in the available format, the project owner must negotiate:
an approved solution.
Do not quietly violate one.
Co-Branding Can Reveal Weak Governance
If the project team does not know:
which logo file is current;
who approves representation;
what each organization should be called,
the visual problem is exposing an operational problem.
Fix both.
Create a Partnership Brand Sheet
It does not need to be long.
One page can define:
logo order;
logo sizing;
initiative typography;
colors;
approved attribution;
partner naming;
approval contact.
This can prevent dozens of future questions.
Use Examples
Show:
correct social post.
Correct presentation title slide.
Correct report cover.
People understand examples faster than abstract rules.
Include “Do Not” Examples Sparingly
For example:
Do not stretch logos.
Do not rearrange partner order.
Do not apply partner colors to the whole initiative.
Keep the guidance practical.
Co-Branded Communication Should Scale
The partnership may begin with:
one announcement.
Then expand into:
events;
reports;
presentations;
campaigns;
digital content.
The visual system should be able to grow.
Design the System Before Volume Arrives
Once five organizations have created:
thirty inconsistent assets,
standardization becomes harder.
Start early.
St. Louis Is a Useful Context for Partnership Communication
Greater St. Louis describes the region as a large bi-state economy with strengths across advanced manufacturing, bioscience and health innovation, digital transformation, financial and business services, and mobility and transportation. Greater St. Louis, Inc.
Initiatives that bring together:
businesses;
industry organizations;
institutions;
technical partners;
community stakeholders
can therefore require communication that represents several contributors without losing clarity.
The design principle remains the same:
many participants do not require many competing visual systems.
When Professional St. Louis Graphic-Design Support Becomes Useful
When joint initiatives, partnerships, industry programs, professional collaborations, or multi-organization campaigns need brochures, presentations, reports, event materials, infographics, or digital creative, structured design support can help establish one coherent communication system while preserving appropriate partner recognition.
Explore GraphicDigits Graphic Design Agency St. Louis
The objective is not making one organization disappear.
It is making the partnership understandable.
Use This Co-Branded Communication Audit
Before approving the first partnership asset, ask:
1. Ownership — Who is actually speaking?
2. Roles — Which organizations lead, co-own, support, fund, or sponsor?
3. Message — Is there one approved explanation of the initiative?
4. Hierarchy — Does visual prominence reflect the real relationship?
5. Logos — Are order, sizing, spacing, and approved versions defined?
6. Visual System — Which typography, colors, imagery, and graphic language govern the shared communication?
7. Templates — Are recurring formats already defined?
8. Approvals — Who approves message, partner representation, and final release?
9. Variations — What can individual partners customize?
10. Assets — Is there one current shared library?
If those ten answers are clear, the partnership is much less likely to become a logo-management exercise.
The Audience Needs One Experience — Even When Many Organizations Are Behind It
Partnerships are often valuable precisely because:
several organizations bring different strengths.
The design should communicate that collaboration.
It should not make the customer decode:
organizational politics.
A strong system makes clear:
what the initiative is;
who it serves;
what action matters;
who is responsible;
who contributes.
Then partner recognition supports the message rather than competing with it.
For St. Louis organizations collaborating across business, industry, institutional, technical, and community initiatives, that is the standard worth aiming for.
Do not begin with:
“Where should we put all the logos?”
Begin with:
“What does the audience need to understand?”
Then define:
the relationship;
the hierarchy;
the shared message;
the visual system;
the approval rules.
Because successful co-branding is not about making every organization equally loud.
It is about making the collaboration feel:
clear, credible, and intentional.
Build One Clear Visual System for Your St. Louis Partnership
Multi-organization communication can remain consistent without erasing the identities involved.
Define the roles.
Clarify the message.
Control the partner hierarchy.
Create reusable shared assets.
