At the service desk of a housing co-operative, Lucy hears the same sentence for the third time: “The application was declined because it did not meet the criteria.” The person in front of her does not know which criterion was missed, which document was judged insufficient, or whether correcting a record would help. The screen shows a decision. Lucy has been asked not to spend too long on answers: there is a queue, the team is small, and every explanation “takes time.” But the economy behind that instruction is misleading. A rule that cannot be explained without turning the worker into an improvised translator may not be saving work at all. It may simply be moving its cost onto the person who received the no.
A refusal that arrives without a map#
An opaque refusal leaves people at a door with no handle. It is not enough to say that criteria are published when they are a technical list, when no one says which one mattered in this case, or when the person cannot tell what to do next. Opacity hurts the service team as well. Lucy ends up inventing a route with the best intentions: she reads notes, interprets abbreviations, and suggests submitting papers again even though they may change nothing. Her capacity for care becomes a patch over an architecture that never decided how to speak to the people it excludes.
An opaque refusal leaves people at a door with no handle. It is not enough to say that criteria are published when they are a technical list, when no one says which one mattered in this case, or when the person cannot tell what to do next.
This problem is often dressed up as neutrality. “The rule is the same for everyone,” people say, as if uniformity removed the duty to make it intelligible. Yet a rule can be applied in the same way each time and still have unequal effects if it asks for evidence that is hard to obtain, mistakes a temporary address for a settled home, or ignores that someone shares documents with a controlling person. Explanation does not create those differences; it makes them visible. That is why some organisations fear it: it turns an abstract decision into a conversation about its real consequences.
Three sentences that force clear thinking#
A short answer can be respectful without being empty. In many cases, a three-sentence explanation is stronger than an administrative paragraph. The first names the verifiable reason: “It was not approved because the income evidence you sent covers two months and this grant requires three.” The second sets a boundary around the conclusion: “We are not saying that you have no income or that you do not need support.” The third opens a concrete action: “You can send the missing month, request a review if you cannot obtain it, or speak with a team member before the 18th.”
This pattern is not meant to hide complex decisions behind friendly language. It separates three things that are often confused: the evidence used, the judgement the institution is not making, and the next available step. If one of those is absent, a person receives an order rather than guidance. When all three are present, the worker no longer has to improvise. And when none of them can be written without ambiguity, the organisation has received a useful signal: it should not continue automating or closing cases until the rule is clarified.
Explaining is not oversharing#
Some people object that a detailed explanation lets people “game the system.” That risk exists in some procedures, but it does not justify handing every person a black box. The important distinction is between communicating relevant logic and publishing a mechanism that would let someone harm others or evade a safety control. Saying which document is missing, which date was used as a reference, or how to request a review does not disclose operational secrets. It is the minimum needed for a person to participate in good faith in a decision that affects them.
Explanation must not become another round of extraction either. If a refusal is caused by incomplete information, the answer should not be an automated demand for more intimate detail without a reason. A team can state what category of evidence is needed and offer proportionate alternatives: a statement from a trusted organisation, an appointment with human support, extra time, or a correction to a record. A rule shows its quality when it can resolve uncertainty with the least intrusion necessary, not when it collects proof just in case.
A test during one service afternoon#
Before redesigning an entire platform, an organisation can run a small test. Select ten recent negative decisions and ask two people outside the service team to answer three questions using only the information available: why was this decided, what does the decision not mean, and what can the person do now? Record the minutes required, the consultations needed, and the phrases that create confusion. The point is not to score workers or to treat their speed as if they were machines. It is to locate the point at which a case stops being an understandable story and becomes a pile of codes.
At the co-operative, the test uncovered something plain. Six of the ten refusals used the same abbreviation for two different situations: a missing document and an unreadable document. The follow-up answer was identical, but the correct actions were not. Changing the label and adding two routes reduced repeated queries without removing any safeguard. The improvement did not come from a more elaborate algorithm. It came from paying attention to the work of explaining. Explanation acted as an audit of usability and fairness at the same time.
Who can correct the official version#
A good explanation includes a way back. An email address that nobody answers, or an appeal written in legal language for exceptional cases, is not enough. The affected person needs to know who can review the record, what they can provide, what the deadline is, and what will happen while they wait. If a decision relies on third-party data, the explanation should also say how a discrepancy can be raised without forcing someone to prove from nothing that the record exists.
The route back protects the people applying the rule too. Lucy should not carry the informal authority to “make an exception” simply because she has heard a difficult story. Her job can be to identify the right channel and record that the explanation did not settle the question. The person responsible for review, in turn, needs to see patterns: how many people ask about the same sentence, how many corrections are accepted, and which groups face the most obstacles. Without that loop, each conversation ends in an individual workaround while the defect in the rule remains intact.
The right cost to count#
Reducing explanation to service minutes counts only the expense that appears on a spreadsheet. It leaves out repeated applications, unnecessary journeys, abandonment of an entitlement, anxiety caused by an incomprehensible answer, and staff time spent repairing conflicts that could have been avoided. It also leaves out a loss of information: when people do not understand why they were excluded, the institution stops receiving signals about badly designed forms, outdated sources, or criteria that do not fit everyday life.
That is why an explainability measure belongs beside measures of time and volume. There is no need to pretend that everything can be reduced to one number. Review a sample of answers each month and ask whether a person with no internal knowledge can describe the reason, the boundary, and the next step. When the answer is no, the finding is not an individual communication failure; it is design debt. Spending time to clear it is cheaper than indefinitely expanding a queue of confused people.
A rule that can withstand being told#
The next time Lucy has to communicate a refusal, she can try the three sentences before closing the screen. If she cannot name the reason without jargon, cannot prevent the person from hearing a judgement about their life, or cannot offer a possible action, she can flag the case for review. That flag does not delay efficiency for the sake of it. It prevents a decision from being presented as final when it is not yet understandable or correctable.
A quality rule is not the one that generates the greatest number of automatic replies. It is the one that can withstand being explained to the people who bear its effects. Test one this week with a real or simulated refusal. Write the three sentences, ask someone who is not part of the process to read them, and notice where they ask a question. That question is unfinished work for the rule, not an inconvenience caused by the person who receives it.
