If you are in the Civil Service and the disciplinary allegations against you are unclear, I would treat that as a serious problem straight away.
I mean wording like “concerns about your conduct”, “issues with professionalism”, “poor judgement”, or “inappropriate behaviour” without clear dates, examples, evidence, or policy wording.
That kind of vague wording can feel soft at first. My view is that it can become dangerous very quickly. If you answer too soon, you may end up defending yourself against the wrong issue. Worse, you may give your line manager or HR extra material they did not already have.
I cover this kind of situation in more detail in Surviving Discipline and Performance Management in the Civil Service, because vague allegations are one of the easiest ways people lose control of the process early.
I would not give a full answer until the allegation is clear
If this was me, I would not send a long explanation until I knew exactly what I was being accused of.
I would ask for the allegation in writing. I would want the date, the conduct relied on, the evidence, the policy breach, and the possible outcome. If the allegation is serious enough to sit inside a civil service disciplinary process, it should be clear enough for you to answer.
A useful line would be:
“Please can you confirm the specific allegation I am being asked to respond to, including the evidence relied on and the policy provision said to be engaged?”
I once helped someone who was told there were “concerns about their behaviour” after a tense Teams call. The first thing I told them was to stop trying to explain the whole relationship with their manager. We asked for the exact words being relied on, who had complained, and whether the meeting was informal or part of a formal HR process. That changed the whole tone, because HR had to define what the issue actually was.
I go through this type of response wording in the full Civil Service discipline and performance guide.
I would check the intranet policy before replying
The bit people miss is that your department’s policy matters.
Do not rely on a manager saying “this is just a quick chat” or “we only want your side”. I would go straight to the intranet and download the disciplinary policy. If performance is mixed into it, I would also get the civil service performance management or capability process guidance.
Then I would check what the policy says about allegations, notice, evidence, accompaniment, formal warning outcomes, and appeal rights.
If the policy says allegations should be clear, and yours are vague, that is useful. If it says evidence should be shared before a meeting, and you have received none, that is useful too.
When I represented a colleague who was accused of “failing to follow a reasonable instruction”, I asked for the actual instruction. It turned out the instruction had changed twice over email, and the manager had only included the version that helped their case. I told the colleague to focus on the written trail, rather than getting dragged into a debate about attitude.
That is why I put policy-checking into my guide on surviving Civil Service discipline and performance management.
I would create my own clean record
If allegations are unclear, I would start a file immediately.
I would save the invite, the email chain, the Teams messages, any 1:1 notes, and the policy. I would also write a short timeline of what happened and when. Keep it factual. Do not write angry notes that make you look chaotic later.
If your line manager sends a vague summary after a meeting, I would correct it calmly.
For example:
“Thank you for the note. I want to clarify that I did not accept the allegation. I asked for the specific examples being relied on, as the concern was unclear.”
That sort of wording protects you without making you sound difficult.
This matters because vague allegations often become clearer later, after the department has gathered more material. If you have your own record from the start, you are in a better position to challenge inaccurate notes, selective evidence, and unfair wording.
I explain the evidence-file approach properly in the tactical guide I wrote for civil servants facing HR action.
I would involve support before the wording hardens
If the matter could lead to a formal warning, final written warning, or dismissal risk, I would speak to a union rep quickly.
Send them the invite, the policy, and your short timeline. Keep the first message tight. Do not send a massive emotional account. A rep can help you work out whether to ask for more detail, delay the meeting, request evidence, or prepare a written response.
If health, stress, disability, or reasonable adjustments are relevant, I would raise that carefully too. For example, if you need written questions in advance because you struggle to answer under pressure, ask for that before the meeting.
I once helped someone whose vague conduct allegation was linked to anxiety during meetings. I told them to ask for written questions, time to respond afterwards, and Occupational Health input. That made the process more controlled and created a record that their ability to take part fairly mattered.
If you are worried unclear allegations could turn into a disciplinary issue, PIP, capability process, formal warning, managed move problem, or dismissal risk, I cover the practical steps in Surviving Discipline and Performance Management in the Civil Service. It is the guide I wrote for people who need to protect their position before and during the process.