A familiar service, whichever door you use

What we found in the news

NHS England’s guidance on standardising community health services (opens in a new tab), first published in January 2025 and updated in March 2026, describes core service components while allowing local development. It asks systems to:

“adapt and develop the core components according to local need”

— NHS England, updated March 3, 2026

This guidance has a specific NHS scope. We are interested in the wider operational question it suggests: which parts of a service should people be able to rely on wherever they encounter it, and which parts should respond to the place and its community?

Consistency takes a little more thought than issuing the same timetable to every location.

Why this matters to us

Imagine two sites run by the same community organization. One has an established transport connection and a large activity room. The other serves a smaller neighbourhood from a shared venue.

People might reasonably expect the same clarity about how to join, whom to contact, and how to raise a concern. They may benefit from different opening times, activities, or welcome arrangements.

At genus, we think those differences deserve a deliberate conversation. Otherwise, an organization can mistake local creativity for inconsistency—or allow an important gap to hide behind the phrase “we do it differently here.”

Describe the essentials from a visitor’s point of view

Bring colleagues from the relevant locations together. Begin with what someone should be able to understand and do when approaching the service.

Can they find an accurate description of the offer? Can they ask about access arrangements? Will they know whether a request is being considered or has been confirmed? Is there a clear route for questions after the first visit?

Agree the essentials in language staff can use. Explain why each matters. A shared expectation is easier to apply when colleagues understand the purpose behind it.

Avoid making the list so broad that everything becomes mandatory in exactly the same form. Reserve close standardization for the things that genuinely need it.

Make room for differences that help

Ask each location what its community and working arrangements require. A venue may share an entrance. A local partner may offer a useful activity. Participants may prefer a different way to receive updates.

Discuss how those choices support the shared service promise. Where a local arrangement changes what someone can expect, describe it clearly in the relevant information.

Invite participants to examine the explanation. They may notice that an apparently small difference—such as where to wait or whom to call—has a practical consequence for them.

Record agreed exceptions and their reasons. That gives a new manager something firmer than inherited custom and gives colleagues a way to revisit an arrangement when circumstances change.

Keep the shared account current

Choose an owner for the common service description and a contact at each location. Agree how a proposed change reaches the other sites and who checks the information people see.

A local update can affect a partner making referrals or a colleague answering enquiries elsewhere. Include those connections in the review.

Periodically compare a few ordinary journeys across locations. Follow an enquiry, a first visit, and a request to change an arrangement. Ask where the experience matches the agreed essentials and where staff have to compensate for a gap.

Use those observations to improve the offer. The purpose is to learn where a common approach helps, not to make every place feel interchangeable.

What this means for the people you serve

People can choose more confidently when the differences between locations are clear. Explain what remains consistent and what is specific to a site. Invite questions about whether an alternative location actually fits the person’s preferences and practical arrangements before presenting it as an equivalent option.

The genus connection

Today, configured genus public and care-team experiences can bring service information, resources, schedules, and staff workflows together around an organization’s configuration.

Keeping those experiences accurate still requires agreed content ownership and local review. The platform does not determine which service differences are appropriate or guarantee consistency between independently managed locations.

One question for your next team meeting

Which part of our offer should feel dependable at every location, and which local difference helps people most?