Partnerships can expand a quantum company's credibility and reach, but they also introduce more logos, claims, approval routes and publishing responsibilities. This guide provides a repeatable co-marketing approval workflow for university, cloud, hardware and enterprise partnerships, with practical tracking points for lockups, landing pages, events, press assets, technical language and version control.
Overview
Quantum technology partnerships often involve organisations with very different brand systems. A university may prioritise institutional identity and research attribution. A cloud or software partner may have strict requirements for product names and logo placement. A hardware company may need accurate descriptions of architectures, platforms or components. An enterprise customer may require confidentiality, procurement approval or carefully limited claims.
The purpose of partnership branding guidelines is not to make every asset look identical. It is to define how the brands appear together, who owns each communication, which claims are approved and where the final files are stored. A clear process protects both the relationship and the audience's understanding of what has actually been delivered.
Use this workflow whenever you launch a joint announcement, publish a partner landing page, prepare an event stand, produce a case study, issue a press asset or update a developer-facing resource. Treat the workflow as a living operational document rather than a one-time campaign checklist.
Start with a partnership record
Create one record for each active relationship. At minimum, record the partner category, legal entity name, approved short name, partnership status, internal owner, partner contact, agreement or permission reference, approved logo folder, claim restrictions, expiry or review date and escalation contact.
This record prevents a common problem: a campaign team using an old logo or outdated description because the latest guidance exists only in an email thread. It also gives marketing, product, sales and technical teams a shared source of truth.
What to track
Track the variables that can change between campaigns. The following register is suitable for a spreadsheet, project-management board or brand asset management system.
| Area | Track | Approval question |
|---|---|---|
| Partner identity | Legal name, trading name, product names and approved abbreviations | Are all names written exactly as the partner requests? |
| Logo use | Current logo files, clear space, minimum size, colour versions and prohibited treatments | Is each mark legible and used within both parties' rules? |
| Lockups | Order, relative scale, separator, background and ownership of the combined treatment | Does the arrangement imply an unapproved joint venture or endorsement? |
| Technical claims | Product capabilities, research status, benchmarks, integrations and availability | Can each material claim be supported and approved by the responsible team? |
| Campaign ownership | Publishing party, review lead, launch date, channels and takedown responsibility | Who has final authority to publish, amend or withdraw the asset? |
| Digital destinations | Landing-page owner, URL, redirects, forms, analytics and accessibility checks | Does the page explain the relationship without confusing either brand? |
| Events | Booth graphics, stage slides, badges, speaker names, demo labels and handouts | Are physical and presentation assets consistent with the approved campaign? |
| Press assets | Release copy, quotes, headshots, boilerplate, media contact and image rights | Has every quote, image and organisational description been cleared? |
| Version control | File owner, version number, approval date, expiry date and archive location | Can the team identify the exact approved file after publication? |
Use a logo decision table
Logo placement should follow the relationship, not the perceived importance of a partner. Use a simple decision table before design begins:
| Situation | Recommended treatment | Check before release |
|---|---|---|
| One party is sponsoring an event or resource | Use a sponsor acknowledgement area rather than a balanced joint lockup | Confirm sponsorship wording and placement |
| Two organisations are publishing a defined joint initiative | Use an approved co-brand lockup or clearly separated marks | Confirm order, scale and ownership of the initiative |
| A partner provides infrastructure or access | Credit the partner in the relevant technical or acknowledgement section | Avoid implying that the partner built or guarantees the entire product |
| A university or lab is contributing research | Identify the research contribution precisely and retain institutional attribution | Check researcher names, affiliations and publication permissions |
| A customer is featured in a case study | Use the customer mark only within the approved reference or case-study scope | Confirm approval covers the intended channels and duration |
When no approved lockup exists, do not create one by simply placing two marks side by side and calling it final. Use separate, correctly sized marks with a neutral relationship statement until both parties agree on a combined treatment.
For broader asset governance, connect this process to a quantum brand asset management workflow. Hardware teams can also use the quantum hardware brand guidelines template to keep product and partner identity aligned.
Cadence and checkpoints
A partnership workflow needs both event-based approvals and scheduled reviews. Event-based checks protect individual launches; scheduled checks catch silent changes in logos, contacts, product names and permissions.
Before planning
- Confirm that the relationship and proposed activity are covered by the relevant agreement or permission.
- Identify the internal owner and the partner's reviewer.
- Define the audience, campaign objective, channels and intended call to action.
- List any claims that require technical, legal, research or security review.
Before design
- Collect current logo files and brand requirements from an approved location.
- Agree whether the asset needs a lockup, separated marks or an acknowledgement line.
- Write the relationship statement in plain language before applying visual design.
- Decide who owns the source files and who can request later amendments.
Before publication
- Review every logo, name, title, quotation, diagram, screenshot and technical statement.
- Test landing-page links, forms, redirects, mobile layouts, contrast and accessibility.
- Check that calls to action do not promise access, performance or availability beyond the approved scope.
- Save the final approved files, approval evidence and publication date in the partnership record.
Monthly and quarterly review
Use a monthly review for active campaigns and a quarterly review for the wider partnership portfolio. Monthly checks should focus on live pages, scheduled social or email assets, event deadlines and open approvals. Quarterly checks should cover all active partner records, logo folders, claim libraries, contact details, expired permissions, archived assets and links to partner pages.
If your team already performs a broader quarterly quantum technology brand audit, add partnership branding as a dedicated section rather than creating a separate, disconnected review.
How to interpret changes
Not every change requires a full rebrand or campaign restart. Classify changes by risk and response.
- Low risk: a corrected file name, updated contact or replacement of a low-resolution logo. Update the record and replace unpublished files.
- Moderate risk: a new product name, revised partner description, changed landing-page destination or updated event treatment. Recheck all related copy and visual assets before publication.
- High risk: a change in ownership, research status, technical capability, commercial availability, endorsement permission or legal relationship. Pause publication and route the issue to the appropriate decision-maker.
Pay particular attention to language that compresses a complex relationship into a broad claim. “Powered by”, “in partnership with”, “available on” and “validated by” can communicate different levels of responsibility. Choose wording that reflects the actual contribution, and ask a technical owner to review claims involving hardware access, algorithms, benchmarks, security or production readiness.
When partners disagree, preserve accuracy and clarity over visual symmetry. A less decorative asset with precise attribution is safer and more useful than a polished lockup that implies an unsupported relationship.
For customer-facing pages, compare the partnership message with your wider vendor comparison page template and website content audit checklist. This helps prevent a partner claim from contradicting product pages, comparison language or technical documentation.
When to revisit
Revisit these quantum partnership branding guidelines on a monthly or quarterly cadence, and immediately when a material change occurs. The strongest triggers include a new partner, renewed or ended agreement, logo redesign, product rename, change in technical capability, new research result, revised approval contact, new event format, updated platform integration or a request to reuse an asset in a different market or channel.
Set a visible “next review” date on every partnership record. At each review, answer five questions:
- Are the logos and names still current?
- Are the relationship statements and technical claims still accurate?
- Do permissions cover every live and planned channel?
- Can a new team member find the approved files and approval history?
- Does the partnership still need the same prominence and presentation?
End each review with a clear status: approved, approved with changes, awaiting partner review, paused or archived. Assign an owner and due date for every exception. If a campaign is approaching quickly, use a short-form approval path for low-risk assets, but retain the same recordkeeping standards.
Finally, connect partnership operations to the rest of your brand system. Event teams can cross-check the quantum conference booth design checklist; product teams can align interfaces with the quantum design system checklist; and technical teams can review partner-facing software journeys through the quantum developer portal UX checklist. A partnership is easier to manage when its visual, technical and editorial decisions are recorded in the same operational rhythm.
Start with one active partnership this week: create its record, verify the logos, list the claims, assign the approvers and schedule the next review. The process becomes more reliable each time the team reuses it.