Logo system
Primary, compact and single-color use
Branding & visual identity
A recognisable identity helps people connect your website, presentations and everyday communications to the same business. The work begins with what the organisation needs to communicate and where the identity will be used, then turns those decisions into a practical set of visual assets.
Discuss your projectA shared delivery plan
The proposed process connects creative decisions to real applications. The agreement defines whether we create or refine an identity, which languages and assets are included, and how feedback and revisions are managed. Each stage gives the next decision a concrete basis. Naming is a separate scope decision.
We agree the stages, outputs and responsibilities in your project scope. Select a stage to explore the work and decisions.

A worked example · illustrative
Illustrative identity structure: the positioning guides the visual choices, and real applications test whether the choices work together.
Primary, compact and single-color use
Arabic and English hierarchy and licensing
Palette, contrast, spacing and composition
Profiles, presentations and agreed templates
Agreed master files + exports + usage guide + asset-license record
From scope to operation
Open each stage to see the work, your role, the deliverables and the check before moving forward. Feedback can return a decision to an earlier stage.
Define what the business needs to communicate and where the identity will appear.
Review audiences, existing assets, practical uses and the elements worth retaining; clarify the problem behind the request.
Provide approved names and wording, current source files, relevant references and one consolidated decision-making route.
The brief distinguishes business objectives, practical constraints and personal preferences.
Review loop Revisit the brief when stakeholders disagree about the audience or the purpose of the change.
Compare visual approaches against the brief and intended uses.
Prepare the agreed concept work and explain the choices behind typography, colour and visual character.
Review the directions against the brief and provide coordinated reasons for the preferred approach.
A direction is approved with specific reasons and clear requirements for development.
Review loop Return to the brief if no direction can satisfy an unresolved requirement.
Refine the selected direction into consistent elements and usable variations.
Develop agreed logo variations, typography and colour choices, checking Arabic and English relationships where included.
Confirm wording, naming and priority uses; approve refinements through the agreed review process.
The elements work together and the team can explain which variation belongs in each use.
Review loop Revisit the direction when a required language or application exposes a fundamental conflict.
Show how the identity works in the materials your team actually needs.
Prepare selected templates or assets, such as business cards and social formats, using realistic content.
Supply final contact details and application requirements, and review work in the intended editing tools.
The applications accommodate the approved content and can be used in their intended format.
Review loop Return to the identity system when a recurring application needs an unsupported variation.
Review the identity at practical sizes and in relevant contexts.
Check legibility, backgrounds, mixed-direction text and agreed export formats; record applicable font and image licences.
Approve final wording and applications, confirm supplied-asset rights and arrange any separate trademark or printing review.
Agreed checks pass and remaining external checks have a named owner.
Review loop Return to development or application work when a check reveals an unsuitable treatment.
Organise the approved files and explain how to apply them consistently.
Deliver agreed editable sources, ready-to-use exports and guidance on variations, colours, fonts and application examples.
Confirm receipt and access, nominate a brand owner and test a representative update where templates are included.
The nominated owner can locate the right files and distinguish editable assets from final exports.
Review loop Revisit packaging or guidance when the team cannot complete an agreed everyday use.
A new business may need a starting identity. An established team may need to refine an existing mark, resolve inconsistent materials or bring its Arabic and English presentation together. The brief should identify what must be retained, what is no longer working and which applications matter most.
A useful identity can be applied by the people producing the company’s materials. That means considering legibility, document layouts, digital formats and everyday constraints alongside the visual concept. A striking presentation of a logo is only one part of judging whether the system will work in practice.
The proposal identifies the assets, applications and review rounds included. The work can cover:
| Choice | What to consider |
|---|---|
| Refresh or redesign | Recognisable elements may be worth retaining. Decide whether the problem is the identity itself or inconsistent application. |
| English and Arabic typography | Choose compatible fonts with the required character coverage, readable sizing and appropriate licences. Check real words and mixed-direction layouts. |
| Brand palette and interface colours | A brand colour is not suitable for every text/background combination. Define usable pairings for everyday documents and digital interfaces. |
Your team provides the business name and approved wording, existing source files where available, intended uses and references that explain your preferences. A named decision maker should gather feedback into a clear response. If several stakeholders are involved, agree how conflicting requests will be resolved before design reviews begin.
Review the shortlisted direction on realistic applications, including a small screen, a simple document and a one-colour treatment where relevant. For bilingual materials, check Arabic shaping, alignment and the balance between scripts. Final handover should distinguish editable source files from ready-to-use exports and identify who controls the licences. Registration, trademark clearance, printing and ongoing content production are separate matters to define if needed.
Yes, a refinement can be considered when the current identity still represents the business. The brief should identify the elements to preserve and the practical problems to solve, such as inconsistent files or poor small-size readability.
Both languages can be included in the agreed brief. That requires decisions about naming, approved wording, font licensing and how the scripts appear together across the selected applications.
The proposal should list the exact deliverables and editable formats. A logo package, a brand guide and social templates are different items; confirm the versions, tools and usage rights your team needs before production.
Handover & ongoing care
New applications and ongoing production need an agreed scope. Keeping an owner for the identity helps later materials remain consistent without assuming every future format was included in the original project.
A useful next step
A sample document, the systems you use and the decision you need to make are enough to start a focused conversation.
Talk to Lava ↗