What you saw, what you concluded, and the gap between

Consider three sentences that could all appear in the same paragraph of the same document. “The letter was mailed on the ninth; no response was received by the deadline.” “The household did not understand the letter.” “The household was not interested in keeping the service.” They are formatted identically and read at the same speed. They are completely different kinds of claim.

The first is description. It is what the record shows, and anyone with the file can check it. The second is a conclusion: it might be true, it might be well founded, and it requires something behind it — a conversation, a returned call, a note from an interpreter. The third is a judgment about what people wanted, which almost nothing in an ordinary file can support and which, once written, will be repeated by everyone who reads the document afterward.

The editing skill that matters most in public-administration writing is being able to look at your own paragraph and say which of the three each sentence is. Not to delete the conclusions — a document with no analysis is not useful — but to make them visible as conclusions, with their basis attached. A reader can weigh a conclusion that says what it rests on. A reader cannot weigh a conclusion dressed as a fact, and neither can the person in the document if it is ever read back to them.

There is a second, quieter version of the same problem: the sentence with no actor in it. “The notice was not returned.” “Documentation was not provided.” “Communication was not established.” Each of these describes a two-sided process while naming only one side, and the side it names is always the person outside the division. Putting the actor back in — who sent what, to which address, in which language, with how long to respond — is often the entire fix.

This program uses a familiar map of intercultural development — Denial, Polarization, Minimization, Acceptance, Adaptation and Integration — to describe how organizations and the people in them change over time. It describes the work and the organization. It is never a label, a score or a record about any individual, and nothing you do in this module is assessed or kept.

In documentation, Minimization has a particular sound: “I write about everyone the same way, so my writing is neutral.” It is sincerely meant, and it is the position most professional writing training produces. The difficulty is that a single standard way of describing people is not neutral — it is the description that fits the writer's own expectations, and it treats everything outside those expectations as a deviation to be explained. That is how “did not respond” becomes “was not interested,” and how a ten-day English-only window disappears from a finding entirely.

Acceptance in this work is recognizing that a document lands differently depending on who is in it and who reads it, and that this is a real feature of the document rather than a sensitivity. Adaptation is changing the writing: naming the actor, attaching evidence to every explanation, stating what a number cannot support, asking what the process required of a person before concluding anything about what the person did. None of that is softer writing. It is more exact writing, which is why it also survives an audit.