One life event. How many public services?

Imagine someone sitting at a kitchen table after a family bereavement. There are letters to open, organisations to contact and practical decisions to make at a time when concentration is difficult.

To the institutions involved, these are separate processes. To the person at the table, they are all part of the same thing that has happened.

That difference in perspective sits at the heart of a useful public-sector conversation. How much work do we ask residents to do simply because public services are organised into separate parts?

The question is not whether every organisation should become one. It is whether a person should have to understand the boundaries before they can find their way through them.

The resident experiences the whole journey

A service can complete its own task successfully while leaving someone uncertain about what happens next.

The form has been accepted. The call has ended. The department has done what it was set up to do. Yet the person may still need to establish which other steps remain, whether information has reached another organisation and whom to ask when the answer is unclear.

This is not necessarily a story about unhelpful staff. The person answering the phone may recognise the difficulty and still lack the authority or arrangements to resolve it.

That makes the handover between services a serious design question. It is where an organisation’s tidy process meets a person’s untidy circumstances.

The experience should be examined from both sides of that boundary, rather than judged only by whether one part reached its endpoint.

There is already a practical example

Tell Us Once offers a concrete illustration. GOV.UK describes it as a way to notify most government organisations of a death through one service. Its stated eligibility covers people who were living in England, Scotland or Wales, with conditions; it is not available where the person was living in Northern Ireland. Official Tell Us Once guidance.

It does not settle every consequence of a death. The guidance explains that organisations such as banks and utility providers still need separate contact. That boundary is part of understanding the service, not a reason to dismiss it.

The interesting principle is that some administrative repetition can be removed without pretending the whole of someone’s situation has been resolved.

For public-service leaders, that is a more practical ambition than promising a single perfect front door to everything. Identify a difficult transition, establish what can genuinely be handled together and explain clearly what remains.

A better website cannot repair every handover

Digital services can make straightforward tasks easier to complete. But a person who moves from a web page to a telephone call is still trying to accomplish the same thing.

The Government Service Standard describes a service experience spanning the channels users need, which may include online, phone, paper and face-to-face contact. It also calls for frontline staff to understand the online service and for changes to be considered across channels. This is about the appropriate mix, not every channel operating in every circumstance. Service Standard: working across channels.

Consider an imagined resident who starts online but needs help interpreting a question. If calling for help means beginning the explanation again, the service has changed channels without preserving the journey.

The issue may be wording. It may be responsibility. It may be the way one team hands a question to another. A new interface can help with some of these things, but cannot substitute for agreeing who will resolve the underlying problem.

This is why staff who deal with exceptions deserve a place in service design. They encounter the situations that the neatest process diagram can overlook.

Joining things up does not mean building something enormous

There is a fair objection to this kind of ambition: public bodies have different responsibilities, resources and legal constraints. A project that tries to unite everything can become difficult to deliver and difficult to use.

The Government Service Standard acknowledges that tension. Its guidance on solving a whole problem warns against overly complicated services and supports incremental improvement, with scope shaped around users’ needs. Service Standard: solving a whole problem.

For a team choosing where to start, a modest question can be revealing: what happens immediately before and after the part we control?

Perhaps people repeatedly arrive without something another service was expected to provide. Perhaps a completion message sounds like the end when it is only the start of another step. Perhaps staff know the next contact but residents are left to find it themselves.

These are possibilities to investigate with users and staff, rather than assumptions about a particular organisation. A smaller, well-understood improvement can be more valuable than a grand promise with no clear owner.

Clarity is part of care

Some repetition is necessary. Different decisions can need different evidence, and private information should not flow between organisations simply because sharing it would be convenient.

The resident needs to understand what a service will do, what it will not do and what choices or permissions are involved. Removing a repeated question is useful only if the resulting process remains trustworthy and understandable.

The same applies when a request cannot be resolved. A clear explanation and a reliable next step may be more helpful than an optimistic reassurance that leaves someone waiting without a route forward.

This is a discussion about the quality of public service, rather than a promise that administrative design can remove grief, hardship or the complexity of a person’s life.

It can, however, avoid adding unnecessary confusion at precisely the moment someone has least capacity to manage it.

Follow the person beyond the department

The person at the kitchen table is not trying to test an organisation chart. They are trying to deal with what has happened and understand what to do next.

A thoughtful service respects that perspective. It completes its own responsibilities, explains its limits and makes the transition to the next part as clear as possible.

For the public sector, that is a demanding but concrete standard of ambition: fewer moments when someone must become the coordinator of several services just to get through one event in their life.