Internal Compliance Review Escalates Over Unapproved Acronyms And Procedure
An internal review intended to assess one team's paperwork has expanded into a multi-year governance matter, with the unit insisting its irregular use of acronyms and informal procedure delivered consistently strong results.

News Intro
A routine internal review of one investigative unit's working practices has expanded into a sprawling, multi-year governance matter, after auditors flagged what they described as persistent irregularities in procedure, documentation and, most contentiously, the team's use of unapproved acronyms.
The review was originally commissioned to assess a small number of case files. It is now understood to span several departments, multiple senior managers and at least three earlier reviews, each of which was itself the subject of a further review.
According to people familiar with the process, the central difficulty has been one of definition. The unit under examination is itself the body that normally examines other units. Investigators tasked with investigating the investigators have, on more than one occasion, been investigated.
Much of the friction has centred on terminology. The unit routinely refers to colleagues, suspects and one another using a dense system of three-letter codes, several of which auditors say do not appear in any approved glossary. Meetings convened to clarify the acronyms have generated further acronyms.
A number of senior figures have been interviewed under formal conditions. Several of those interviews have themselves become the subject of complaints regarding procedure, including the precise wording of cautions, the handling of disclosure, and whether the correct form was used to authorise the form that authorised the interview.
The organisation maintains that standards must be upheld and that no individual is above scrutiny. It has declined to confirm how many of the people conducting the scrutiny are now themselves being scrutinised, citing the ongoing nature of the review.
The file that led to another file
Note for file: governance, terminology, and the integrity of the process
People sometimes ask whether the review has got out of hand. I don't accept that characterisation. The process is the process, and the process is working exactly as the process is designed to work.
We began with a small concern about paperwork. That is how these things should begin. You follow the file. The file led to another file. That file led to a meeting, and the meeting raised legitimate questions about who had authorised the first file, which I am obliged to pursue.
I am aware that some colleagues feel the use of acronyms has become a sticking point. I would simply say that if a unit cannot account for what its acronyms mean, in writing, on the approved form, then I am entitled to ask. I asked. The answers raised further questions. That is not me escalating; that is the answers escalating.
I have interviewed senior officers. I have interviewed officers more senior than those officers. At one point I was interviewed, which I welcomed, because nobody is above the process, including me, including the people reviewing me, who I have also asked to account for their procedure.
Some say nothing has been concluded. I would point out that a great deal has been documented. We have established who said what, when, on which form, and whether that form was the correct form. The matter of whether anyone did anything wrong remains, I accept, open. But the integrity of the process has never been stronger.
I will be opening a further strand shortly. It concerns the review of the review.
Oversight points at itself
The structural problem here is that the oversight function has been pointed at itself. Once the body that audits everyone else becomes the thing being audited, you lose your reference point. There is no longer an outside. Every finding generates a new file, and every file requires a reviewer, who in turn becomes reviewable. It is less a governance failure than a governance perpetual-motion machine.
The acronym question is more serious than it sounds. If a unit operates a private vocabulary that does not map to any approved glossary, then its entire documentary record becomes difficult to interpret, and therefore difficult to rely on in any formal proceeding. You cannot caution someone, or disclose to them, in a language only your own team speaks. The procedural objections are, in my view, the only part of this that is fully coherent.
Observers note that the review has now outlasted several of the cases it was originally meant to examine, and at least one of the managers originally meant to conduct it.
The calm centre of every escalation
What I find striking is the reviewing officer's sincere belief that he is the calm centre of all this. He describes the process "escalating" as though it were weather, something happening to him rather than through him. In conflict resolution we'd note that a review which keeps generating reviews of itself is usually telling you something about the reviewer, not the reviewed.
Responses requiring an approved form
u/Definitely_DefinitelyDS_77 · 41208 points · 6h ago
"We began with a small concern about paperwork" is the most terrifying sentence I have ever read.
u/Bent_Copper_Theory · 30551 points · 6h ago
Mate has interviewed everyone in the building including himself and still hasn't told us what a single one of the acronyms stands for.
u/CautionWordingPedant · 18847 points · 6h ago
The genuinely funny part is that he thinks the answers are escalating. The answers are not escalating. You are. With a clipboard.
u/Glossary_Compliance_Now · 12390 points · 6h ago
"Meetings convened to clarify the acronyms have generated further acronyms." Send help. Or a form. Whichever is approved.
u/Fella_In_The_Interview · 204 points · 6h ago
You weren't there. Some of those acronyms were load-bearing.
u/CautionWordingPedant · 88 points · 6h ago
@Fella_In_The_Interview a load-bearing acronym is exactly the problem.
Community Poll
Community Poll
Latest reader breakdown
Was the compliance review proportionate?