The first formal step in a disciplinary process where a manager notifies an employee that their conduct or performance is unacceptable and must improve, typically documented in writing despite the name.
Key Takeaways
A verbal warning is a formal conversation. The manager sits down with the employee, explains the problem, states what needs to change, and sets a timeline for improvement. It's the gentlest form of disciplinary action, but it's still disciplinary action. The biggest misconception is that a verbal warning is casual. It isn't. It's a documented step in a formal process. If the employee doesn't improve, the verbal warning becomes the foundation for the next escalation to a written warning. Without proper documentation of the verbal warning, that escalation becomes much harder to justify. Think of the verbal warning as a turning point. Before it, the issue was informal: a quiet word, a passing comment, a suggestion to do better. After the verbal warning, the issue is on the record. The employee knows the employer is serious, and the employer has started building the documentation trail.
Verbal warnings are appropriate for specific situations. Using them correctly means understanding both when they fit and when they don't.
Persistent lateness (after informal conversations have failed). Occasional unauthorised short absences. Minor dress code or grooming violations. Small lapses in work quality that aren't safety-critical. Failure to follow minor administrative procedures. Inappropriate but not serious workplace behaviour (e.g., personal phone use during meetings). The common thread: the behaviour is real, it affects the workplace, but it's not serious enough to warrant a written warning on the first occurrence.
Don't use a verbal warning for behaviour that's clearly more serious. Harassment, discrimination, safety violations, insubordination, theft, or breach of confidentiality all warrant stronger initial action. If a manager gives a verbal warning for something that should have been a written warning (or worse), they've set a precedent that makes future escalation harder. When in doubt, consult HR before issuing the warning.
Delivery matters. A poorly handled verbal warning damages the relationship without fixing the problem.
Before the meeting, gather specific examples of the behaviour or performance issue. Dates, times, and details matter. "You're always late" is vague and arguable. "You arrived 20+ minutes late on March 3, 8, and 14" is specific and documented. Check the employee's file for any previous informal conversations about the issue. Review the company's disciplinary policy to confirm a verbal warning is the appropriate step.
Hold the meeting in private. Never deliver a verbal warning in front of colleagues. Start by explaining the purpose of the meeting. State the specific behaviour, why it's a problem, and what the expectations are going forward. Give the employee a chance to respond. They may have a legitimate explanation you don't know about. End by confirming the expected improvement, the timeline, and what will happen if the behaviour continues. Keep the tone firm but respectful.
After the meeting, write a brief record that includes: the date and time of the meeting, who was present, the specific issue discussed, the employee's response, the agreed expectations and timeline, and when the warning will be reviewed. Give the employee a copy and ask them to sign an acknowledgement of receipt. The acknowledgement means they received the warning, not that they agree with it. File the documentation in the employee's HR record.
While formats vary, every verbal warning record should capture the same core information.
| Element | What to Include | Example |
|---|---|---|
| Date and time | When the verbal warning meeting took place | March 18, 2026, 2:00 PM |
| Attendees | Manager, employee, and any witness or HR representative | Sarah Jones (Manager), Tom Chen (Employee) |
| Issue description | Specific behaviour with dates and examples | Arrived more than 20 minutes late on March 3, 8, and 14 without prior notice |
| Impact | How the behaviour affects the team or business | Team meetings started late, colleagues covered reception duties |
| Employee's response | What the employee said when given the chance to respond | Acknowledged lateness, cited traffic but agreed it wasn't a valid ongoing excuse |
| Expected improvement | Clear, measurable expectation | Arrive by 9:00 AM daily; notify manager by 8:30 AM if delayed for any reason |
| Review date | When the warning will be reviewed | April 18, 2026 (30 days) |
| Consequences | What happens if improvement doesn't occur | Escalation to a formal written warning |
A verbal warning sits at the intersection of management practice and employment law. Getting the legal details right protects both parties.
The ACAS Code of Practice doesn't explicitly require a verbal warning as a separate step, but it expects employers to deal with issues informally before escalating. A verbal warning serves as evidence that the employer tried to resolve the matter at the lowest appropriate level. Employees don't have a statutory right to be accompanied at a verbal warning meeting (that right applies to formal disciplinary hearings), but offering accompaniment is good practice and reduces the risk of the employee claiming the meeting was a formal hearing without proper rights.
In at-will states, a verbal warning isn't legally required. However, it establishes a documented pattern of notice and opportunity to improve, which is crucial evidence in wrongful termination, discrimination, and unemployment insurance claims. Some state unemployment agencies deny benefits to employees terminated for documented misconduct where warnings were given. Without the documentation, the employer often loses the unemployment claim.
Always give the employee a chance to respond during the verbal warning meeting. Their response might change the situation entirely. Perhaps they were late because of a medical issue they hadn't disclosed. Perhaps a colleague gave them incorrect information about shift times. Record their response in the documentation regardless of whether it changes the outcome. A one-sided account looks like a predetermined decision if reviewed later.
These errors turn a simple, effective tool into a liability.
The verbal warning meeting is the beginning, not the end. What happens next determines whether the warning achieves its purpose.
Track the specific metrics or behaviours discussed in the warning. If the issue was lateness, record arrival times. If it was missed deadlines, track submission dates. Don't rely on general impressions. Objective data removes debate about whether improvement happened. Check in informally with the employee during the review period. A brief "How's it going?" shows you care about their success, not just compliance.
Acknowledge it. Tell the employee you've noticed the change and appreciate the effort. At the end of the review period, note in the file that the warning has lapsed due to satisfactory improvement. This closes the loop and gives the employee a fresh start. Many managers skip this step, which means the employee never knows if the warning is still hanging over them.
Escalate to a written warning. The documentation from the verbal warning provides the foundation: you gave notice, set expectations, allowed time for improvement, and the employee didn't meet the standard. This is exactly the kind of progressive, documented approach that holds up in legal proceedings. Don't wait until the last day of the review period if the problem is clearly continuing. Address it as soon as it's clear that improvement isn't happening.