How to Write a Rebranding Brief for an Agency

A strong rebranding brief gives an agency the context and constraints it needs to make sound strategic and creative decisions. It should explain why the change is necessary, what must be preserved, who the brand needs to reach, how success will be evaluated, and what the rollout must include.

The brief is not a replacement for brand strategy or a list of visual preferences. It is a decision-making document. The best briefs help an agency distinguish a focused refresh from a more fundamental change, identify risks early, and develop work that serves the business rather than simply looking different.

What a rebranding brief should accomplish

Before writing, define the job the brief needs to do. A useful rebranding brief should:

• Explain the business reason for change in specific terms.
• Separate symptoms from the underlying problem.
• Identify valuable brand equity that should not be discarded casually.
• Define the audiences, markets, and competitive context involved.
• Clarify whether the project is a refresh, a partial repositioning, or a full rebrand.
• Set practical boundaries for deliverables, stakeholders, timing, and approvals.
• Describe how the organization will judge the recommended direction.

Keep the brief focused on decisions and evidence. Statements such as “the brand feels dated” may be true, but they do not tell an agency whether the issue is the logo, the messaging, the customer experience, the website, or a change in market position.

1. Start with the business reason

Open with the business context, not a request for a new logo. Describe the event or problem that created the need for change. Common triggers include a merger, a new audience, international expansion, a shift in positioning, a portfolio restructure, poor differentiation, or inconsistency across customer touchpoints.

Use concrete language. For example, “The company is moving from a regional service provider to a national enterprise offering and needs a system that can support multiple product lines” is more useful than “We need to look more sophisticated.”

Also state what happens if the organization does nothing. This may include confusion between business units, weak recognition, difficulty communicating a new offer, or costly inconsistency in sales and marketing materials. The goal is not to dramatize the project; it is to establish why the work matters.

2. Document the current brand and its equity

A rebrand should not erase recognition without a reason. Explain what currently works, what does not, and which elements carry meaning for customers, employees, partners, or prospects.

Consider documenting:

• Current name, logo, colors, typography, imagery, and graphic assets.
• Brand associations the organization wants to retain.
• Assets with strong recognition or legal importance.
• Customer trust signals built over time.
• Visual elements that are difficult to use across digital, print, environmental, or product applications.
• Known inconsistencies in existing materials and channels.

Be specific about preservation requirements. “Keep the blue” is ambiguous. “Retain the primary blue if it continues to meet accessibility and reproduction requirements” gives the agency a usable constraint while leaving room for improvement.

3. Decide whether the project needs a refresh or a full rebrand

One of the most important decisions in the brief is the expected level of change. A refresh generally improves or modernizes an existing identity while preserving substantial recognition. A full rebrand may change the positioning, architecture, name, identity system, or experience more fundamentally.

The brief does not need to force a final answer if discovery will determine the scope. It should, however, state the starting assumption and the conditions that would justify expanding or narrowing the work. For a related decision framework, see logo refresh vs. logo redesign.

4. Define the audiences and buying context

List the audiences that matter, but do not stop at demographics. An agency needs to understand how people encounter the brand, what they need to believe, and what could prevent action.

For each priority audience, describe:

• Their role in the buying or adoption decision.
• The problem they are trying to solve.
• What they currently believe about the organization.
• What the organization wants them to understand or feel.
• Important objections, proof requirements, or category expectations.
• The touchpoints where the brand must perform well.

Include internal audiences when employees, sales teams, partners, or franchisees will use the identity. A rebrand that works in a presentation but is difficult for teams to apply will not produce consistent results.

5. Describe the strategic direction

Give the agency a clear picture of the intended position without prescribing the final creative solution. Include the organization’s purpose, value proposition, differentiators, personality, and relevant category context.

Useful inputs may include:

• Current or proposed positioning language.
• Primary customer promise.
• Reasons to believe the promise.
• Competitors and alternatives customers consider.
• Words the brand should evoke and words it should avoid.
• Examples of organizations that represent the desired qualities, with an explanation of what is relevant about each example.

Avoid turning the brief into a mood board of personal preferences. References should clarify strategic territory, not dictate imitation. “Confident and precise” is a starting point; “make it look like this competitor” is usually a constraint that narrows thinking without explaining the business need.

6. Set the scope and deliverables

Separate required deliverables from possible recommendations. Scope often changes depending on what discovery reveals, so define both the baseline and the decision points.

Potential workstreams include:

• Brand research and stakeholder discovery.
• Positioning, messaging, or brand architecture.
• Naming evaluation or development.
• Logo and visual identity development.
• Typography, color, imagery, illustration, iconography, and layout principles.
• Brand guidelines and editable templates.
• Website or digital product direction.
• Launch assets, internal communications, packaging, signage, or sales materials.
• Implementation support and asset migration.

Do not assume that every brand project includes every workstream. If the brief needs a visual identity only, say so. If strategy is unresolved, identify it as an expected discovery task rather than treating it as an invisible addition to the project.

For broader context on related identity deliverables, review the distinctions between brand identity design and individual logo design.

7. Explain technical and operational requirements

Creative decisions must work in the environments where the brand will be used. Document practical requirements early so the agency can test directions against real conditions.

Include information such as:

• Primary digital platforms and content management systems.
• Print, packaging, signage, apparel, environmental, or product applications.
• Accessibility requirements for color, type, and digital interfaces.
• File formats, production specifications, and localization needs.
• Existing templates, asset libraries, and technology limitations.
• Legal, regulatory, trademark, or naming review requirements.
• Languages, regions, or business units that need to be supported.

If the rebrand will affect a website, clarify whether the agency is expected to address structure, content, user experience, visual design, implementation, or only brand application. A brand brief should not quietly become a website redesign brief without an explicit scope decision.

8. Establish stakeholders, governance, and approvals

List the people who will contribute information, make decisions, approve work, and use the final system. Distinguish those roles. A large review group may provide valuable input, but it can also create conflicting direction if no single decision owner is accountable.

Define:

• Executive sponsor and day-to-day project owner.
• Required subject-matter contributors.
• Final approver or approval committee.
• Legal, compliance, accessibility, and technology reviewers.
• Expected review windows and feedback format.
• How disagreements will be resolved.

State who has authority to approve strategy and who approves execution. This protects the project from late-stage feedback based on personal taste rather than agreed criteria.

9. Provide timing, dependencies, and budget context

A reliable timeline depends on scope, stakeholder availability, research needs, review cycles, legal checks, production, and rollout complexity. Include the date the work must be ready, the date it must launch, and any immovable business events.

Identify dependencies such as a merger announcement, product launch, funding event, website migration, office opening, or sales conference. Also note internal availability for interviews and review.

If a budget range is available, include it. If not, explain whether the agency should recommend options at different levels of scope. Avoid treating a deadline or budget as confidential when it materially affects the quality and feasibility of the work.

For planning context, see the related guide to a rebranding timeline.

10. Define success and evaluation criteria

Success criteria should connect the rebrand to the original business problem. They may include clearer differentiation, stronger internal adoption, improved consistency, a usable system across markets, or a successful transition without disrupting recognition.

Separate project acceptance criteria from long-term business outcomes. The agency can be evaluated on whether the strategy is coherent, the identity is distinctive and usable, the system meets technical requirements, and the guidelines enable adoption. Market performance may require additional measurement after launch.

Write down how decisions will be made. For example, concepts may be assessed against strategic fit, audience relevance, differentiation, flexibility, accessibility, production practicality, and ability to scale. This is more useful than asking whether stakeholders “like” the work.

Rebranding brief checklist

Before sending the brief, confirm that it answers these questions:

• Why is the organization considering a rebrand now?
• What business problem must the work solve?
• What existing equity should be protected?
• Is the expected scope a refresh, a partial change, or a full rebrand?
• Who are the priority audiences and decision-makers?
• What should the brand communicate, and what should it avoid?
• What deliverables are required, optional, or out of scope?
• Where will the identity be used?
• What technical, legal, accessibility, or production constraints apply?
• Who owns decisions and approvals?
• What timing, dependencies, and budget context should the agency know?
• How will strategic and creative recommendations be evaluated?

Common mistakes to avoid

Starting with visual preferences

Preferences can be recorded, but they should not replace the business case. Explain the desired effect and audience response before discussing colors, symbols, or styles.

Assuming everything must change

Change is not the same as progress. Identify what has value and require recommendations to account for recognition, trust, and implementation cost.

Leaving scope ambiguous

Terms such as “complete rebrand” can mean different things to different teams. List deliverables and identify unresolved questions.

Ignoring rollout

A new identity is only useful when it can be adopted. Include priority touchpoints, ownership, templates, asset migration, training, and launch sequencing as appropriate.

Collecting unstructured feedback

Invite relevant expertise, but establish a decision owner and evaluation criteria before creative work begins.

How to use the brief after kickoff

The brief should remain a shared reference throughout discovery and development. An agency may recommend changing the scope after research, but any change should be tied to evidence or a clear business decision.

At each major stage, compare the work with the original problem, audience needs, preservation requirements, and success criteria. If a recommendation is attractive but does not support the stated objective, the brief makes that gap visible.

For a broader view of the work before commissioning an agency, read the guide to rebranding strategy. When the organization is ready to discuss a broader engagement, the rebranding overview provides the relevant service context. General design planning guidance is also available on design services.

A well-written rebranding brief does not try to solve the entire project in advance. It gives the agency enough business context to investigate the right problem, protect meaningful equity, recommend the appropriate level of change, and plan a controlled implementation.