Putting the Allegations in Writing
What an allegation letter has to contain, how specific it has to be, and why a vague letter produces a meeting nobody can prepare for.
An allegation letter has to tell the person what they are said to have done, when, and what the possible consequences are — specifically enough that they could prepare a defence without guessing. A letter that refers to "concerns about your conduct" and invites somebody to a meeting on Thursday fails at the first requirement and makes everything after it harder.
The decision process in “Putting the Allegations in Writing” needs evidence that can be checked without turning one activity signal into a conclusion. When reviewers consider daily schedule template with accountable controls for daily schedule template, its time and project records can provide operational context, but allegations, employee responses and consequential decisions still require a fair human process.
Specificity feels aggressive to write and is actually the opposite. A vague letter produces a meeting that drifts, a person who cannot respond to anything in particular, and a decision on matters that were never put to them.
For an independent reference relevant to “Putting the Allegations in Writing”, consult the Proofpoint insider-threat reference. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
What goes in the letter
- What is alleged, as facts with dates: what happened, when, and where.
- Which rule, policy or standard that is said to breach, if the case rests on one.
- The evidence being relied on, enclosed or clearly listed.
- The date, time and place of the meeting, far enough ahead to prepare.
- Who will be present and in what role.
- That the person may be accompanied, and by whom.
- The range of possible outcomes, including dismissal where that is genuinely possible.
The last item is the one organisations soften and should not. Somebody who attends a meeting believing the worst case is a warning, and is dismissed, has a complaint that is entirely avoidable by one sentence.
How specific is specific enough
The test is whether the person could prepare. "You were rude to a colleague" cannot be prepared for. "On 14 May, in the warehouse office, you are alleged to have sworn at a colleague during a discussion about the delivery schedule, in front of two other members of staff" can be.
That level of detail also disciplines the organisation. Writing the allegation out forces somebody to check that the date is right, that the witnesses exist, and that the thing alleged is actually a breach of something. A surprising number of cases change shape at this point.
Allegations that multiply
Where there are several matters, list them separately and number them. A single paragraph containing four allegations produces a decision that upholds "the allegations" without anyone being able to tell which ones.
Numbering also prevents a common drift: new matters appearing during the process. If something else emerges during the investigation it has to be put to the person separately, with the same specificity and the same time to respond. It cannot be added to the decision.
Tone, and what it costs
The letter is a formal document that will be read by people who were not involved, possibly years later. It should be plain, factual and free of characterisation.
Describe what is alleged to have happened. Do not describe the person, their attitude, or how anybody feels about it. A letter that editorialises gives the person something to be aggrieved about that has nothing to do with the facts.
This is also kinder. A letter that sets out six facts and a meeting date is easier to receive than one that explains at length how disappointed everybody is.
The evidence that goes with it
Send the evidence with the letter, not at the meeting. If something cannot be sent — a witness statement that would identify somebody who asked not to be named, material that cannot be copied — say so, say why, and take advice on what can be done instead.
Where statements are anonymised, the person still has to be able to respond to the substance. An allegation supported by evidence the person is not permitted to see is a difficult position and one that needs qualified advice before the meeting rather than after it.
The outcomes paragraph
Stating the possible outcomes is a single sentence and it is the sentence most often left out, because writing "one possible outcome is dismissal" feels like a threat. It is not a threat; it is the information the person needs in order to decide how seriously to take the meeting and whether to take advice.
Where dismissal is genuinely not on the table, say what the range actually is. An organisation that warns of dismissal in every letter as a matter of template has told the person nothing, and has made it harder to be believed on the occasion when it matters.
| What the letter says | What the person can do with it |
|---|---|
| "To discuss some concerns" | Nothing; arrives unprepared |
| "A disciplinary meeting" | Knows it is formal, not what about |
| "A disciplinary meeting concerning the allegations at 1-3 below" | Can prepare a response to each |
| "...one possible outcome of which is dismissal" | Can decide whether to take advice |
Each row down that table costs one more sentence to write and removes one more avoidable complaint.
Delivery and the date
Send it by a route that produces a record, and allow for the person being absent, on leave or signed off. A letter emailed to a work account that has already been suspended is a recurring and entirely avoidable failure.
Count the preparation time from receipt rather than from sending. Where somebody is unwell, the question of whether to proceed at all is a separate and harder one, and it is a question worth asking once, properly, with advice, rather than resolving by default because a meeting was already in the diary.