Handle disciplinary actions fairly and consistently

Before anything else, you need to understand what actually happened. Talk to the manager who raised the concern and anyone who witnessed the incident. Don't jump to conclusions - your job right now is to gather facts, not make judgments. Write down dates, times, and specific behaviors (not opinions or feelings). "John was rude" isn't enough - you need "John raised his voice at a client during the 2pm meeting on March 5th." **Common mistake:** Many HR teams skip this step and go straight to a formal meeting. That's a problem because you might discover the issue doesn't warrant disciplinary action at all - or that it's more serious than initially reported. **Tip:** Keep your notes factual and neutral. These could end up as evidence in a tribunal, so avoid writing anything you wouldn't want read aloud in court.

Now dig deeper into the facts. Review any relevant documents, emails, CCTV footage, or records. Interview witnesses separately and privately - don't let them compare stories beforehand. Keep detailed notes of who said what and when. Your goal is to build a complete picture before taking any action. Ask yourself: is there a pattern here, or is this a one-off? Has the employee been told about this expectation before? Are there mitigating circumstances you should know about? **Common mistake:** Using the employee's direct manager as the sole investigator. If they're the one who reported the issue, they shouldn't also be investigating it. That's a conflict of interest that could undermine the whole process. **Documentation warning:** Keep a clear investigation file from day one. If you can't prove you investigated properly, it won't matter how justified your final decision was - it'll look unfair. **Tip:** If the allegation is serious (e.g., theft, harassment, safety violations), consider whether you need to suspend the employee on full pay while you investigate. Don't suspend without pay unless your contract specifically allows it.

Send a written invitation with at least 48 hours notice (longer is better). Your letter should clearly state: - What the concerns are (be specific enough that they can prepare a response) - The date, time, and location of the meeting - Their right to bring a colleague or union representative - Any evidence you'll be relying on (attach copies so there aren't surprises) Keep the tone professional, not accusatory. You're inviting them to discuss concerns, not announcing a verdict. **Common mistake:** Being vague about the allegations. If you write "we need to discuss your recent behavior," the employee can't properly prepare their defense. That alone could make the whole process unfair. **Legal pitfall:** Forgetting to mention their right to be accompanied is one of the most common procedural errors - and it's an easy one for tribunals to spot. Always include it, even if you think they won't bring anyone. **Tip:** If the employee asks to reschedule, try to accommodate them at least once. Refusing without good reason looks heavy-handed.

Present your concerns clearly and let the employee respond fully. Listen without interrupting. Ask clarifying questions. Take detailed notes of everything said - or better yet, have a second person there specifically to take notes so you can focus on the conversation. This is the employee's chance to give their side of the story. They might raise things you hadn't considered - personal problems, misunderstandings, or context that changes the picture. Make sure they feel genuinely heard, even if you disagree with what they're saying. **Meeting structure that works well:** 1. Explain why you're here (briefly) 2. Present the evidence 3. Ask for their response 4. Explore any mitigating factors 5. Adjourn to consider your decision (don't decide on the spot) **Common mistake:** Making your decision during the meeting. Even if the evidence seems clear-cut, always adjourn and take time to think. Snap decisions look predetermined - and tribunals hate that. **Legal pitfall:** If the employee breaks down or becomes too upset to continue, offer a break or reschedule. Pushing through when someone can't engage properly weakens your process. **Tip:** Never record the meeting without telling everyone present. If you want a recording, say so at the start and get agreement.

Review all the evidence and carefully consider what the employee said in the meeting. Be consistent - check how similar cases were handled before. If you gave someone else a verbal warning for the same thing last year, you can't jump to a final written warning now without a good reason. Your options typically are: - **No action** - the concerns weren't substantiated - **Informal warning** - a conversation noting the issue without formal consequences - **First written warning** - usually stays on file for 6-12 months - **Final written warning** - the last step before dismissal - **Dismissal** - only for gross misconduct or after previous warnings haven't worked Document your reasoning clearly. Write down what you considered, what weight you gave it, and why you chose this specific outcome. **Common mistake:** Skipping straight to dismissal because you're frustrated. Unless it's genuine gross misconduct (theft, violence, serious safety breach), you typically need to work through the warning stages first. **Tip:** Consider the employee's length of service, previous record, and any mitigating circumstances. Two people who did the exact same thing might reasonably get different outcomes based on their history.

Send the employee a formal letter within 5 working days of the decision. Don't delay - the longer you wait, the more it looks like you weren't sure about your decision. Your letter should include: - A summary of what happened and what was discussed - The action being taken (warning level, conditions, etc.) - When it takes effect and how long it stays on file - What improvement you expect and by when - What happens if they don't improve - Their right to appeal (with the deadline and who to contact) Keep a copy in their personnel file and send it by a method you can prove they received (hand delivery with signature, recorded mail, or company email with read receipt). **Common mistake:** Using vague language like "we expect improvement." Be specific - "You need to arrive by 9am every day for the next 3 months" is far better than "we expect better timekeeping." **Documentation warning:** This letter is often the single most important document if the case goes to a tribunal. Take time to get it right. Have someone else review it before you send it. **Tip:** If you're issuing a warning, include a review date. It shows you're giving the employee a real chance to improve rather than just building a paper trail to fire them.

Tell the employee they can appeal the decision and explain exactly how to do it. Set a clear deadline for appeals - usually 5 to 10 working days from receiving the outcome letter. If they do appeal, it's essential that a different manager (ideally more senior) reviews the case. The person who made the original decision shouldn't hear the appeal - that's not a real review, it's just the same person defending their own call. **What the appeal reviewer should consider:** - Was the procedure followed correctly? - Was the evidence strong enough to support the decision? - Was the penalty proportionate and consistent with how others were treated? - Did anything new come to light that should change the outcome? The appeal can result in the original decision being upheld, reduced, or overturned entirely. **Common mistake:** Treating appeals as a formality. If the employee feels the appeal was a rubber stamp, they're much more likely to take the matter to an employment tribunal. **After the process is complete:** Set a reminder to check in with the employee at the review date. If they've improved, acknowledge it. If they haven't, you'll need to move to the next stage of the process. Either way, follow up - don't just file the paperwork and forget about it. **Tip:** Keep all documentation from this entire process together in one file. If this employee has further issues down the road (or if a similar case comes up with someone else), you'll need to reference it.