Brand Identity Design: What to Brief Beyond the Logo

A request for a new logo can describe several different problems. The mark may be hard to use. The team may lack shared rules for colour and type. Or the organisation may still be deciding what it offers, whom it serves and what people need to understand. Those situations call for different briefs and handovers.

Before asking for a quote for brand identity design in Nigeria, decide what needs to work differently when the project is finished. The answer might be a corrected logo and usable files. It might be a visual identity system the team can apply across reports, digital pages and partner materials. Or the visual work may depend on wider decisions about the organisation’s purpose, audience, position and messages.

The right scope depends on the problem. A broad engagement is not automatically better, and a polished mark may not answer a team’s need for consistent application. The brief should name the work the organisation needs and the uses the provider is expected to support.

Identify what needs to work differently

Start with materials people already encounter: the website, proposals, reports, event materials, programme documents, social posts, product packaging or service information. Look at a few current examples side by side. Where does the organisation become hard to recognise, understand or represent consistently?

Then separate three questions that teams may bundle together:

1. Is the mark itself the problem? Its files may be missing, it may become illegible at a small size, or the organisation may need a version for a particular background.
2. Are people applying the identity differently? The mark may be usable while colours, type, layouts and supporting elements vary from one material to another.
3. Are the decisions behind the design unsettled? The organisation may still be deciding whom it serves, what it offers, how it differs or what it wants audiences to understand.

A file problem may need a narrow correction. Inconsistent use may call for a visual identity system and practical guidance. Unsettled meaning may need strategic or verbal decisions before, or alongside, the visual work. One scope does not automatically include the others.

Write the observed issue in one sentence: “Our current materials make it difficult for [audience] to [recognise, understand or use something important] when they encounter us through [priority setting].” If the sentence describes a mark, a focused repair may fit. If it describes recurring inconsistency or unresolved meaning, ask the provider how the proposal will address that part. When a brief names only the file, the proposal may replace the mark while leaving inconsistent use unresolved.

For the hypothetical example below, that sentence could read: “Our customer sheet and partner presentation use different colours and type, so staff cannot apply the identity consistently.” Naming the two materials and the exact failure gives a provider something specific to investigate.

Choose a scope that answers the problem

Ije treats strategic and verbal identity decisions as related to, but distinct from, visual identity and its application. Use this comparison to discuss the work with a designer or studio. Providers may name or combine services differently, so compare what each scope resolves and what the team receives.

Logo repair or refresh

It may fit when: The organisation’s meaning and visual direction are settled, but the mark or its files do not work in priority uses.

Specify before work starts: Which versions are needed; where the mark will appear; what must remain recognisable; who makes the final decision.

Check at handover: Correct, organised master and export files; versions for the agreed backgrounds and uses; guidance on which file goes where.

Visual identity system

It may fit when: The mark may be usable, but the team needs a consistent way to apply the identity across recurring materials.

Specify before work starts: Priority audiences and applications; assets to retain; colour, type and layout rules; who will use and maintain the system.

Check at handover: Agreed logo suite; usable colour and type specifications; examples for priority applications; concise guidance staff can follow.

Strategic, verbal and visual work

It may fit when: The organisation’s purpose, audience, offer, position or explanation is still changing or conflicting, and design depends on resolving those questions.

Specify before work starts: Which decisions are open; who contributes; what informs the decisions; how strategic and verbal outputs connect to visual design.

Check at handover: A record of decisions and rationale, agreed verbal and visual assets, application guidance, and next responsibilities within the scope.

A project can include more than one scope, but the proposal should explain the sequence. If the team first needs to agree what it is saying, ask how that decision will be made before the visual direction is finalised. If strategy is already settled, ask why a broad strategy phase is included and what it adds to the named design task.

Take the problem sentence you wrote above and match it to the scope description whose fit condition applies. Choose the narrowest scope that resolves that problem; if none fits, note what the three options leave unresolved before agreeing a proposal.

A package name can hide whether the applications, files and guidance the team needs are included. Compare the named work and handover items instead of relying on the package label.

Give the designer a brief they can act on

A brief does not need to solve the design problem in advance. It should make the organisation’s context, constraints and open decisions clear enough for a provider to propose a process.

Describe the organisation as it operates now. State its purpose, current work, offer or programmes, and the people it serves. Distinguish existing work from plans. If a programme is still being tested, do not present its proposed name or promise as settled.

Name the audiences and important settings. Identify whose recognition or understanding matters for this assignment, then name the first places they meet the organisation: perhaps a service page, proposal, annual report or product label. Include print or digital conditions that affect the design.

Show current materials and identify the problem. Share representative files rather than an unfiltered mood board. Describe what fails in each: a mark disappears at small sizes, two teams use different colours, or staff cannot tell which logo file is current. State what already works and should be retained.

Separate settled choices from open questions. List approved names, messages, audience priorities and programme facts. Put unresolved choices elsewhere in the brief. The provider can then identify which decisions design can proceed with and which need agreement first. If an unapproved choice is presented as settled, the concept review may reopen it and require a scope decision before design can continue.

Set the working conditions. Name the decision-maker, contributors, feedback route, timing constraints and team that will use the files. State relevant language, accessibility, partner or production requirements. Agree how concepts will be reviewed and how revisions are handled.

A compact brief can use these fields:

• Project need: The current problem and why it matters to the organisation’s work.
• Audience and use: Who needs to recognise or understand the organisation, and where.
• Current assets: The files, rules or materials the designer should review.
• Keep and change: What should remain, what should change, and why.
• Open decisions: Questions the organisation has not settled.
• Priority applications: The first materials the proposed identity must work on.
• Decision and feedback: Who approves, how comments are consolidated, and how revisions work.
• Handover: Files, guidance, access and staff orientation needed to use the result.

Before you request proposals, apply these fields to one identity-design task your organisation is actually preparing. Use a current logo, page, report or other material as the starting point. Write the audience, first applications and known constraints from your records; put any unapproved audience, offer or message choice under open decisions. Then compare the problem sentence with the three scope descriptions above and select the narrowest scope that answers it. The example below illustrates how the fields work; your own current task should determine your brief.

Worked example: a hypothetical social enterprise provides cold storage to food businesses. Its existing logo remains legible, but staff use different colours and type across its website, customer information sheet and partner presentation, and they cannot identify the print-ready logo file.

• Project need: make the existing visual identity consistent across three current materials and identify the right files for print.
• Audience and use: food businesses reviewing the service; partners considering how the service works.
• Current assets: the existing logo, website, customer sheet and partner presentation.
• Keep and change: retain the service description and assess whether the mark works in the named uses; standardise the applications that vary.
• Open decisions: confirm the print and digital formats, who approves the system, and which staff members need the source files.
• Priority applications: the website, customer sheet and partner presentation.
• Decision and feedback: name one person to approve the direction and one route for collecting staff comments.
• Handover: identify approved files, colour and type specifications, examples for the three applications and guidance the team can use.

If the team has not agreed on an audience, service detail or application, list that as an open decision; do not fill the blank with an assumption.

Compare proposals by the work they make possible

Two proposals can use different labels and still be compared. Read past package names and ask what decisions, applications and handover each one covers.

• What will you review before recommending a direction? The answer should connect the organisation’s current work and materials to the proposed design decisions.
• Which applications are included? Ask for the priority items, not an undefined promise that the identity will work “everywhere.”
• What will the team receive in editable and export-ready form? Confirm formats, access and who can open, revise and reproduce them.
• What usage guidance is included? Ask how staff will know which version, colour, type and layout to use.
• How will feedback and revisions work? Confirm who consolidates comments, when decisions are due and what counts as a new direction.
• What is outside the fee, and who owns or licenses each asset? Clarify relevant production, implementation and third-party material terms before agreeing the scope.
• What will the team need to maintain the result? Ask about file organisation, access, templates and a handover walkthrough when staff will produce materials themselves.

If your team already has proposals, apply the same questions to the actual documents before choosing. For each one, record the named application, included files and guidance, revision limit, rights or licences, provider responsibilities, and work expected from your team. Mark a missing answer as unresolved instead of assuming it is included.

Use the example brief to compare two hypothetical proposals. Proposal A offers a redraw of the mark and new print and digital exports. Proposal B includes a reviewed logo suite, colour and type specifications, examples for the three named applications and a short usage guide. Because the example’s recurring problem is inconsistent application and the mark remains legible, Proposal B answers more of that brief. For a file-only problem with settled identity rules, Proposal A would be the closer fit.

The organisation should also check what each proposal expects from its team. The provider describes process and deliverables; the organisation supplies accurate information, names a decision-maker, consolidates feedback and confirms which materials are current. If either side’s responsibility is vague, ask for it to be made explicit before the work starts.

Choose after the written scope identifies the priority applications, handover items, rights, roles and exclusions well enough for both sides to agree what the work includes.

Review what the team will actually receive

Do not assess a handover by file count or the polish of a mock-up. Test it against the priority uses in the brief.

Open the files on the device and software the team will use. Check that the names make sense and staff can identify the approved master. View the mark at the sizes and on the backgrounds named in the brief. For a visual identity system, apply its rules to one real priority document and one digital use. Ask someone who will use the files to follow the guidance without extra explanation.

For the hypothetical brief above, test the customer sheet and partner presentation—not just a cover mock-up. Check whether staff can choose the right logo, reproduce the specified colours and type, and update the files with their available software. If a needed file, instruction or access permission is missing, record the gap and agree whether it belongs to the current scope or a separate task. A presentation mock-up alone does not show that staff can use the final assets.

For your current project, write down the exact file, instruction, application or access permission the team could not use during the test. Name the person who will confirm whether that item belongs in the agreed handover and give it a date for resolution. If a required file is missing, assign the repair to the current scope or a separate task.

If staff cannot locate a required file or do not have permission to open it, they cannot complete the application named in the brief until that handover gap is resolved.

When the brief points to wider brand work

Visual identity is one part of how an organisation becomes recognisable and understood. If the audience, offer, position and message are settled, a designer can focus on expressing those decisions in the agreed applications. If those choices conflict, identify which questions need agreement before expecting design files to resolve them. In the hypothetical example, if the team has not decided whether it serves retailers or households first, that audience choice belongs in the open-decisions list before the visual direction is finalised. For your current brief, mark the audience, offer, position or message choice that is genuinely unsettled; if none is open, keep the design scope focused. Wider work belongs in the discussion only when a named decision changes what the visual identity needs to express. A visual handover can express agreed choices; it cannot settle an unresolved audience or offer on the team’s behalf.

For social enterprises, Ije’s Social Enterprises page describes the connected mission and market decisions relevant to that audience. When the brief raises questions about identity alongside proof, story and public presence, Ije’s Brand-Power System explains how that wider work connects. Nonprofit teams considering those broader questions can read the nonprofit branding strategy guide.

Before requesting proposals, write down the problem in the current materials, the first applications the work must support, and what the team needs in order to use the handover. Those details give a designer a brief to answer and help the organisation compare the work each proposal actually covers.