A request for a new logo can conceal several different needs. The business may be repositioning, struggling with inconsistent materials or simply missing usable files. Each calls for a different scope. Before starting an identity project, define the problem and what should remain recognisable. A thoughtful refresh preserves useful continuity; a new identity may be justified when the underlying direction has changed. Neither should be selected merely because a dramatic presentation seems more exciting.
Separate positioning from visual symptoms
Write what the business does, who it serves and what makes its offer meaningfully different. A hypothetical accounting practice moving from general services toward specialist advice may need clearer positioning before a new visual system. If that decision is unresolved, designers are being asked to represent an offer that the team itself cannot explain consistently.
List observed visual problems separately. The logo may be unreadable at small sizes, documents may use unrelated typefaces or campaign graphics may lack hierarchy. These are tangible issues that can be tested. Avoid assuming that every inconsistency requires a complete rebrand. Some can be solved through a better system, templates and ownership of the existing assets.
Inventory what already has value
Gather current logos, colours, typography, imagery and key touchpoints. Ask which elements customers recognise and which the team can legitimately reuse. Check asset provenance and licensing rather than assuming every file in an old folder is available for unlimited use. Identify where the identity performs well and where it becomes unclear or impractical.
For the accounting example, a longstanding name and distinctive symbol may be worth retaining while the document system and website typography need work. That is an illustrative possibility, not evidence about customer recognition. Real research and stakeholder input should inform the final choice. Keep the rationale explicit so a preference for novelty does not erase useful continuity without discussion.
Compare refresh and replacement options
Define a refresh option with specific changes and protected elements. Define a new-identity option that includes exploration, rollout and migration. Compare the effort required to update signage, stationery, templates and digital accounts. A logo deliverable alone understates the operational cost of changing identity across a business.
State the trade-offs in ordinary language. Preserving a symbol may maintain familiarity but constrain a new direction. Replacing it may create a clearer system but require explanation and a longer transition. Neither option guarantees recognition or commercial improvement. Decide what evidence would support the choice, and mark unresolved assumptions rather than converting them into confident brand claims.
Specify the system and its applications
List the applications the identity must support: a website header, an invoice, a proposal, social graphics or packaging. Use representative layouts during evaluation, not only a large logo on a neutral background. Test small sizes, one-colour use and longer text. A direction that works only in a presentation is not yet a usable identity system.
Include hierarchy rules, colour roles, typography and image direction in the scope. Define which templates are required at launch and who will edit them. A small practice may need a dependable proposal and document system more urgently than a large set of speculative merchandise mockups. Prioritise the touchpoints the business actually uses.
Agree approval and handover
Identify the decision-maker and the criteria used to review directions. Feedback should relate to the brief: suitability, recognition, readability and application fit. Collect stakeholder input in an organised way rather than sending contradictory individual revisions. Clarify revision stages and how a change in positioning will affect scope.
Document final asset formats, source-file access, usage guidance and licensing responsibilities. Provide naming conventions so the team can distinguish digital and print versions. Plan the transition, including replacing old assets and maintaining continuity where necessary. A handover should make routine use easier; a folder of unexplained files leaves future decisions to guesswork.
Identity scope checklist
- Clarify positioning and the practical design problem.
- Inventory existing recognition, assets and usage rights.
- Compare a defined refresh with a defined replacement.
- Include rollout effort beyond the logo itself.
- Evaluate directions in real, representative applications.
- Agree decision-makers, criteria and revision stages.
- Specify asset formats, guidance and transition ownership.
Bring the inventory and priority applications to the design discussion. The right scope should produce a coherent system the team can use, not simply a different mark. When the brief explains what needs to change and what deserves preservation, creative work has a stronger basis for meaningful decisions.