In this article
Corporate identity scope should follow the brand's actual needs rather than a ready-made stationery list. Logo, colour and typography form the core; business cards, presentations and other surfaces apply those decisions. Photography, website development and printing may relate to identity, but are not automatically the same deliverable. Thinking in these layers helps reveal missing work when requesting proposals. It also clarifies whether you need a design presentation, usable templates or support with implementation, so each part can be defined and assessed separately.
Quick answer
Corporate identity usually includes a logo family, colour, typography, visual language and usage rules. Documents, presentations, digital templates, packaging and signage applications are added according to need. Define guidelines and file delivery separately. Printing, production, content, website development and licences should not be assumed to be included; describe them through the proposal's inclusions and exclusions.
Separate the core system from applications
The core comprises decisions used when creating new materials: logo arrangements, colour relationships, text hierarchy, imagery and supporting graphics. A business card applies those decisions to a particular surface and content. This distinction explains why the same core elements appear across several deliverables.
An existing logo can be retained while the core develops elsewhere. Distinguish new logo design from refinement or preparation of usage rules in the scope list. An identity project does not necessarily require a new mark; it should address the actual gaps in the system.
Build the application list around tasks
Consider how the business shares information and what employees prepare. Sending a proposal, introducing a product, guiding a visitor and announcing an event have different needs. List the surfaces used for each task to identify practical applications.
| Task | Possible application |
|---|---|
| Corporate communication | Business card, letterhead, email signature |
| Sales explanation | Proposal, presentation, product information sheet |
| Digital announcement | Profile assets and content templates |
| Physical recognition | Signage, wayfinding or vehicle graphics |
| Product presentation | Identity adaptation for labels or packaging |
Make application variations explicit
Does business card mean one person or the whole team? Does a presentation include only its cover or content slides as well? Templates may require separate language and size variations. Listing these under each application reduces differences in expectations later.
A hypothetical product brand serving both retail and business buyers needs different materials for a price label and a technical proposal. One communicates quickly, the other carries detailed information. The identity can be shared while the deliverables remain distinct. Describe each around its intended use rather than grouping everything under a broad label.
Include the assets needed to use the system
Guidelines explain decisions; files enable use or editing. Review logo variations, agreed digital and production exports, templates and asset information together. State which files are editable and what software they require, so the team can use the delivery as intended.
Adobe Fonts requires clients directly accessing fonts to edit designs to hold their own licence. Separate asset delivery from licence acquisition. Discuss the resources staff and suppliers will need before the work moves into daily use.
Do not assume related services are included
An identity adaptation for packaging differs from designing a complete product family's packaging. Setting a visual direction for the web does not itself include developing a working website. Photography, copywriting, translation, printing and production coordination can likewise be separate tasks.
Being related to identity does not make a service automatically included in its fee or delivery. Distinguish included, optional and excluded items in the proposal. Identify responsibility, required content and expected output for each, so adjacent services do not remain hidden assumptions in the project.
Complete your scope list in two passes
First list the touchpoints you will use. Then add required files, variations and rules for each. This turns a list of stationery names into a practical delivery brief. Existing materials can make a scope discussion with BOCW more concrete.
- Separate priority deliveries from later applications.
- Specify language, staff, product and size variations.
- Assign content and production responsibilities.
- Mark which applications the guide should explain.
- Decide how to test the delivery with real content.
Key takeaways
- Define the visual core separately from individual applications.
- Describe variations and editing needs for every deliverable.
- Classify additional content, production and development services explicitly.
Frequently asked questions
Must identity include business cards and letterhead?
They are common, but needs differ. Presentations and proposal templates may be more important for a digitally focused team. Choose applications around actual touchpoints instead of automatically adding materials the business will not use.
Is a website part of identity scope?
Web visual rules or representative page designs may be included. Development, content entry and technical management can require a separate scope. Check the precise outputs in the proposal and who will implement them rather than relying on the website label.
Can packaging and signage be added to the project?
Yes. Define them through sizes, product families, materials and production needs. Adapting identity to these surfaces differs from detailed packaging development or sign fabrication. List the required tasks separately so the project covers the intended work.
