Avoidable contact in the public sector is rarely a mystery. A resident rings, emails or visits because they cannot see where their application has got to, or because the first form did not collect enough for anyone to act. The second contact is the expensive one. Status clarity and better intake design reduce that repeat work without cutting the service people actually need.
Teams feel this as a queue that never thins. Officers spend mornings answering the same question: has it been received, who has it, when will a decision come. The case itself may be progressing. The person on the outside cannot tell, so they contact again. That is not demand for more service. It is demand for a straight answer the organisation already holds.
What avoidable contact actually is
Avoidable contact is the contact that happens because the organisation failed to tell, capture or route something the first time. It is the chase call. It is the email that says just checking. It is the visit to a reception desk to ask whether a form arrived. It is the resident who submits twice because nothing acknowledged the first attempt.
It is not the contact that needs a human judgement: a safeguarding concern, a complex eligibility question, a complaint that requires listening, a case that has genuinely gone wrong. Those should stay. Closing a phone line, hiding an email address, or putting a script in front of a dead process does not reduce avoidable contact. It hides it until it arrives angrier.
The pattern is consistent across councils, housing, benefits, licensing, planning and health administration. Work enters through a form, a letter, a portal, a phone call or a counter. A record may or may not be created. The resident is told the request has been received, or they are told nothing. Days pass. They have a life to organise around the decision. They contact. An officer opens a system, or several, and reads out a status the resident could have been shown. Volume then looks like demand. A large part of it is the organisation talking to itself through the resident.
Status clarity stops the chase
People contact when they cannot see progress. That is the whole mechanism. If they can see a reference, the stage the work is at, what the organisation is waiting for, and a window the diary can keep, most of them wait. If they cannot, the rational move is to ring.
An acknowledgement that only says thank you, we have received this, is a delay with a stamp. It needs a reference the resident can quote. It needs a named type of work so they know they did not land in a general heap. It needs a true next step: an officer will check completeness, a visit will be booked, a decision will be issued in a stated window. If you are closed, say so. If a statutory clock applies, say what the clock is and what starts it. Cheerful vagueness trains a second contact.
The status the public sees has to match the status staff use. When the portal says in progress and the officer’s screen says awaiting documents, the phone call is inevitable. One record, two views of the same facts. Staff should be able to open the same case the resident is looking at, not reconstruct it from email.
Do not invent precision you cannot keep. A date that slips every week is worse than an honest range. Waiting-for-you is the most useful status of all. If the case is stuck because a document, a fee or an answer is missing, say exactly what is missing and how to send it. A large share of chase contact is the resident asking whether you have what they already posted, or you asking them for something they did not know you needed. Put that in the open and the second loop often does not start.
Intake design that does not force a follow-up
The other source of avoidable contact is a first capture that cannot be acted on. The form asked for a name and a story. The case officer still needs a property reference, a date, a type of request, and a way to reach the person at a time they will answer. So the first official act is a call to complete the form. That call is avoidable contact you designed in.
Design backwards from the next officer action, not forwards from a template. Who opens this? What decision do they make? What must exist on the record before they can start? If a field does not write a column, a routing rule or a completeness check, drop it. Extra questions make the form longer and still leave the officer short.
Structure beats a blank box. A free-text description feels kind. It is expensive because a human has to parse a story into the fields the rest of the organisation uses. Prefer a small set of structured questions and one notes field for the exception. Match the website, the phone script and the counter so all three write the same record. If the channels ask different things, the next working day is translation work, and translation work generates chasing.
Destination matters as much as fields. A form that only emails a shared inbox is not intake. Write a stored record on submit, assign an owner, and notify. Give the resident the reference immediately. Route unlike work before a human sorts the pile: a new application, a change to an existing case, a where-is-my-decision message and a complaint are different jobs. One mega-form with every field optional produces empty records and a team that treats the website as noise.
Cut chasing without cutting the service
The temptation, when contact volumes rise, is to make contact harder. Shorter opening hours. A web-only rule. A phone tree that never reaches a person. That can suppress the count for a while. It does not reduce the need. The case still exists. The resident still does not know the status. The contact returns as a complaint, a member enquiry, or a visit to a desk that was supposed to be closed to this kind of work.
Real service is the judgement, the visit, the decision, the help for someone who cannot complete a form. Avoidable contact is the extra loop around that work. You protect the first by removing the second. Officers get the morning back for the cases that need them. Residents who can check status themselves stop competing with residents who cannot.
Do not measure success as fewer calls in isolation. A drop in calls with a rise in complaints is not a win. Look at repeat contacts on the same case. Look at how often the first capture is complete enough to start work. Look at whether the public status matches the officer status. Those are operational facts. They require looking at a week’s work honestly, not a survey.
Keep a human route for the people who need it. Clear status and cleaner intake are how you stop using that human route as a status line. The person who cannot get online, or whose case is genuinely stuck, should still reach someone. That is easier to staff when the queue is not full of people asking whether a form arrived.
- Give every request a reference the resident can quote on every channel.
- Show the same status to the public and to staff: stage, owner, and what is being waited on.
- Acknowledge with the actual next step and a time window the diary can keep.
- Use waiting-for-you as a first-class status, with the missing item named and a way to send it.
- Design intake from the next officer action. Drop fields that do not write a column, a route or a check.
- Use structured questions plus one notes box. Do not make a story the primary record.
- Write a stored record on submit. Treat email as a notification, not the archive.
- Match website, phone and counter so all three create the same case shape.
- Split new applications, existing-case changes and complaints once they share one pile.
- Keep a human route for stuck and complex cases. Measure repeat contact on the same case, not only total volume.
Make the first contact enough
A public body does not reduce avoidable contact by making itself harder to reach. It reduces it by making the first contact complete and the status visible. When people can see where they are, and when the first form can actually be worked, they stop ringing to ask. The service remains. The chase does not.
Lightning Business Solutions designs that layer for UK organisations: websites, workflow, email infrastructure, communications, integrations, and the joins between them. If officers are spending the morning narrating cases that already exist, start with status and intake, not with another channel.
Talk through the pathways that matter on our contact page, or see how the pieces fit under capabilities.