Start with the service promise
Before choosing colours, write down who the service is for, what people can expect and what they should do next. A visitor service might help someone plan a day out. A community programme might need to explain eligibility and how to join. Those are different communication jobs, even when they sit under the same organisation.
Ask staff which questions they repeatedly answer. Review the material people actually receive. This gives the identity work a practical purpose and prevents a new visual style from carrying the same confusing explanation.
Build on what people already recognise
A refresh does not always need a new name or logo. Existing recognition may be valuable, particularly when the public already connects a symbol with a trusted service. Examine what can stay and what needs clearer rules: headings, photography, colour use, tone or the relationship between a parent organisation and a programme.
For a regional visitor service, the useful change might be a shared layout across several town guides. Each place keeps its character while maps, opening information and visitor advice become easier to follow.
Compare directions in real applications
A mood board gives an impression; an application shows whether the idea works. Develop a small number of distinct directions and apply each to the same practical items. A guide cover, mobile page, poster and sign can expose different strengths and weaknesses.
Judge each direction against the brief. Can someone recognise the service? Is the important message readable? Does the system accommodate a long place name or a translated heading? Record the reasons for the decision so later design choices follow an agreed purpose rather than personal preference.
Give the team tools it can use
The handover should cover the materials staff produce repeatedly. This might include presentation layouts, social tiles, an email heading, event posters and a simple document template. Explain which elements can change and which should remain consistent.
A compact guide with worked examples is often more useful than a large collection of rules with no examples. Include correct and incorrect applications, file formats and instructions for choosing imagery. Make sure the people maintaining the service can find the current files without asking the original designer each time.
Test the identity beyond launch day
Use the system on an ordinary piece of work before expanding it. A routine notice, a longer publication and a small-screen page will test different constraints. Ask someone unfamiliar with the project to explain what the material tells them and what they would do next.
The output is a coordinated identity, a set of usable applications and a clear way to maintain them. Review the templates when the service changes, rather than letting outdated messages persist inside a visually consistent design.
Explore our Brand positioning and visual identity, related services and Turn one public-service brief into useful content.

