In this article

Preparing to commission corporate identity takes more than collecting designs you like. The company needs to identify the problem, decide what to retain and understand who will use the new system. Designers can translate those inputs into visual decisions, while the business must clarify its priorities and approval authority. A well-prepared start moves reviews from individual preferences towards practical needs. It also helps the final files become part of everyday communication instead of remaining a presentation that few people know how to use.

Quick answer

To commission corporate identity, collect current materials, describe the audience and problem, and list priority applications. Appoint a decision owner and assign content and approval responsibilities. Review design directions through actual usage examples. Accept the final work by checking that files open, templates can be edited and rules can be applied, alongside evaluating its appearance.

Explain why the business needs a change

A new company, an expanding product family and fragmented communication are different starting points. Asking for a more modern look does not describe the problem. Saying that departments prepare sales documents differently reveals a need for templates and shared rules. Record separately whether recognition of the current mark must be retained.

Distinguish necessary changes from preferences open to investigation. Completing applications before the brand name is settled may create avoidable rework. Discuss these dependencies at the beginning rather than treating every decision as independent.

Prepare the content your team actually uses

Collect logo files, stationery, presentations and product examples into one starting package. Current company details, correct product names and language versions are design inputs. Examples built around incomplete content can hide text length and information density.

For a hypothetical technical consultancy, the brief might specify Turkish and English proposals, long service headings, comparison tables and presentations edited by the sales team. This describes the working conditions more clearly than a general stationery list. It also helps determine which templates and page types deserve attention first.

Bring internal decisions together

Management, sales and operations review materials from different perspectives. Establish who is consulted and who gives final approval. Combine contributions into one response rather than sending conflicting comments to the designer as separate instructions.

Content approval can be separated from approval of the visual direction. Checking a telephone number is a different decision from choosing how typography expresses the brand. Keeping that distinction helps reviews address the right question at the right stage, without expecting every detail to be resolved in a single discussion.

Write feedback around need and effect

Instead of only saying that you dislike a colour, identify where it causes a problem. Table headings are hard to distinguish from body copy, or a long product name is difficult to read in a narrow space, describes something actionable. Preference matters too, but becomes more useful when connected to the application.

Use common criteria for each proposed direction: character, recognition, information order and flexibility. Ask whether an impressive presentation detail can also be produced consistently in everyday work. This keeps reviews anchored to the system the business will need to operate.

Try the applications before final acceptance

Have your team use a representative part of the delivery. Add a service to a proposal, enter a long heading in a presentation or update an address. These exercises distinguish issues with the visual direction from problems in template operation. Arrange separate producer sample checks for important printed materials.

  • Do the files open in the agreed software?
  • Do text areas allow ordinary content changes?
  • Are the intended uses of different logo versions clear?
  • Can staff distinguish current templates from older files?

Treat adoption as part of the project

Old cards, website visuals and presentations may not disappear simultaneously. Decide which changes take priority and which versions remain in use during the transition. Store new files together and explain their use briefly, so employees can find the right assets without returning to familiar old versions.

Bringing current examples, a usage list and an approval structure to a BOCW discussion makes the requirement more concrete. Also agree how future applications outside the initial scope will use the identity rules, keeping the system useful after its first launch.

Key takeaways

  • Describe the communication problem before listing aesthetic preferences.
  • Consolidate feedback through one decision owner and explain practical effects.
  • Let the team test the files with actual content before handover.

Frequently asked questions

Does all copy need to be final before we start?

Not necessarily, but real content types, typical lengths and company information should be known. Record when outstanding content will arrive. Exact copy required for final artwork needs a separate approval, so provisional information does not accidentally become a finished deliverable.

How should we collect employee feedback?

Ask everyone the same usage questions and collect answers in one document. Resolve conflicting views internally before sending a combined response. Keep final decision authority clear instead of treating every opinion as an equally binding instruction.

Can we create new materials after handover?

If templates and rules are built for that purpose, your team can update the defined applications. A new channel or production condition may require additional design. Clarify which needs the guidelines cover when you receive the system, and who handles extensions.