Procedures exist to make work consistent, safe, compliant, and easier to coordinate. When an employee repeatedly ignores them, the problem can affect quality, customer trust, team morale, and sometimes workplace safety. Yet a rushed confrontation can make matters worse, especially when the procedure is unclear, outdated, or poorly communicated. The right response is neither automatic punishment nor passive acceptance. It is a fair process: establish what happened, understand why it happened, explain the standard, provide reasonable support, and hold the employee accountable for following it.
How to Deal With an Employee Not Following Procedures Professionally
#1. Confirm the Procedure and the Actual Conduct
Before speaking with the employee, make sure you understand both the required procedure and what actually occurred. Review the written policy, workflow, checklist, training material, or manager instruction that applies. Then separate observable facts from conclusions. “The quality-control checklist was not completed on three orders” is more useful than “Jordan is careless.”
Also consider whether the procedure was accessible, current, and practical. Employees sometimes appear noncompliant because instructions conflict, required tools are unavailable, workload makes the process difficult, or a supervisor informally encouraged a different method. These possibilities do not excuse repeated disregard, but they affect how you should address the situation.
Gather specific details such as:
- What step was missed or changed?
- When and how often did it happen?
- What was the effect on customers, coworkers, safety, cost, or quality?
- Was the employee trained and previously told about the expectation?
- Did the employee have a legitimate reason for departing from the procedure?
A factual foundation allows you to address conduct fairly instead of relying on rumor, frustration, or assumptions about the employee’s attitude.
#2. Assess Whether the Matter Requires Immediate Escalation
Not every procedural lapse deserves the same response. A minor first-time omission may call for clarification and coaching, while bypassing a safety control, falsifying a required record, or exposing confidential information may require immediate action under your organization’s established process.
Assess the seriousness by considering the potential harm, not only the outcome this time. An unsafe shortcut may not have caused an injury, but that does not make it acceptable. Similarly, a data-handling procedure may exist to prevent a serious risk even when no problem has yet occurred.
If there is an urgent safety, security, financial, regulatory, or ethical concern, take reasonable steps to contain the risk first. Notify the appropriate manager, HR representative, compliance contact, or other responsible internal resource according to your workplace procedures. Do not conduct an improvised investigation while an immediate hazard continues.
For less urgent matters, preserve normal fairness. Avoid treating a routine mistake as deliberate misconduct before you understand the circumstances.
#3. Speak With the Employee Privately and Promptly
Discuss the issue privately rather than correcting the employee in front of colleagues. A prompt conversation reduces confusion and gives the employee a reasonable opportunity to explain what happened while the details are still clear. Choose a setting where you can speak without interruption, but avoid making the meeting feel unnecessarily intimidating.
Begin with the observed behavior and its impact. Do not lead with labels such as “uncooperative,” “lazy,” or “a rule breaker.” Those descriptions attack character and make it harder to discuss the actual workplace expectation.
You might say:
I want to discuss the process used for yesterday’s customer refunds. The required approval step was not recorded before the refunds were issued. That creates a problem because the team cannot verify who reviewed the transaction.
I’d like to understand what happened from your perspective, and then we can clarify the process for future refunds.
Allow the employee to respond without interrupting unnecessarily. Listen for relevant facts, such as unclear instructions, a system problem, conflicting priorities, or a misunderstanding about when the procedure applies. Listening is not the same as agreeing; it is how you distinguish a correctable obstacle from a conscious refusal.
#4. Clarify the Reason for the Procedure
Employees are more likely to follow a process when they understand what it protects or enables. You do not need to give a long lecture, but explain the practical reason behind the requirement. Connect the procedure to accurate records, consistent service, safety, legal or contractual obligations, data protection, or the work of another team.
For example, instead of saying, “Because that is the policy,” explain that completing the handoff form allows the next shift to identify outstanding tasks and prevents customers from receiving conflicting information. The explanation should make the standard meaningful without suggesting that employees may ignore it whenever they disagree with the rationale.
You should also clarify whether the procedure is mandatory or whether it allows professional judgment. Some processes contain required controls alongside flexible methods. If employees are expected to use judgment in certain circumstances, define the boundaries and explain when they must ask for approval.
A useful clarification includes:
- The exact action required.
- When the action must occur.
- Which exceptions, if any, are authorized.
- Whom the employee should contact when the normal process does not work.
- What record or evidence must be kept.
Clear expectations prevent future disputes about whether the employee understood the standard.
#5. Remove Obstacles and Provide Targeted Support
Accountability works best when the employee has a genuine opportunity to meet the expectation. If the process is complicated, observe the work or walk through a real example. Check whether the employee knows where the relevant form, system function, checklist, or reference guide is located. If a technical problem is involved, document it and involve the appropriate support person.
Support should be targeted rather than vague. “Please be more careful” does not tell someone what to change. A better plan might include completing the next five transactions using the checklist, asking a designated coworker to verify the first two entries, or meeting with the supervisor after one week to review questions.
Support does not mean lowering the standard or transferring the employee’s responsibilities to someone else indefinitely. It means addressing reasonable barriers and confirming competence. If the employee says the procedure conflicts with another instruction, resolve that conflict rather than expecting the employee to guess which direction matters.
Document the assistance provided, especially when the issue may continue. Keep the record factual: what was explained, what resources were supplied, and what the employee agreed to do differently.
#6. Set a Clear Expectation and Follow-Up Date
End the conversation with a specific expectation, not a general request for improvement. State what the employee must do, when the change begins, and how compliance will be assessed. If the process involves several steps, identify the critical ones rather than assuming a broad instruction will be remembered accurately.
For example, an expectation might be: “Starting today, complete the inspection record before releasing each shipment. If the system is unavailable, notify the shift lead and record the issue using the backup form.” That standard is observable and gives the employee a defined alternative when the normal process fails.
Agree on a follow-up date appropriate to the seriousness and frequency of the issue. A brief check-in after a few shifts may be sensible for a recurring operational problem; a longer review may be appropriate for a process used less often. Explain that the purpose is to confirm the procedure is being followed and address questions early.
You can close with wording such as:
Going forward, the approval must be recorded before the refund is processed. If the system prevents you from entering it, pause the transaction and contact me or the shift lead. I’ll review the next few refund records with you on Friday so we can confirm the process is working.
Ask the employee to summarize the expectation in their own words. This helps reveal misunderstandings before they become another failure.
#7. Respond Consistently if the Pattern Continues
If the employee follows the procedure after coaching, acknowledge the improvement and continue ordinary monitoring. If the problem continues, do not repeatedly restart the same informal conversation without changing your response. Review what was previously discussed, identify the specific recurrence, and explain that continued noncompliance is now a performance or conduct concern.
At this point, follow your organization’s established performance-management or disciplinary process. That may involve a written warning, a formal improvement plan, additional training, reassignment of certain duties, or another response appropriate to the circumstances. Do not invent penalties, threaten consequences you cannot authorize, or treat similar employees differently without a legitimate reason.
The employee should know:
- Which expectation was not met.
- When the earlier coaching or instruction occurred.
- What evidence shows the issue continued.
- What improvement is required.
- What may happen if the requirement is not met.
A recurring failure may reflect unwillingness, confusion, capacity issues, or a process design problem. Investigate enough to act responsibly, but do not let uncertainty become an excuse for endless inaction. If the employee disputes the facts, consider the response carefully and involve HR or another appropriate internal resource when the matter becomes formal, sensitive, or potentially consequential.
A Practical Conversation for an Employee Who Ignores Procedures
A manager should adapt the conversation to the facts, the employee’s role, and the seriousness of the issue. The following example is useful for a repeated but non-emergency problem, such as skipping documentation, omitting a required review, or using an unauthorized shortcut.
I want to talk about the equipment check process. I reviewed the records from Monday, Wednesday, and Thursday, and the pre-use check was not recorded on those occasions.
This check is required before the equipment is used because it helps identify problems early and gives the next shift a reliable record. Can you walk me through what happened on those days?
I understand that the morning schedule was compressed and that you believed the equipment was operating normally. The time pressure is important to address, but the check still needs to be completed. If the schedule makes that difficult, tell me before starting the work so we can adjust the assignment or find an approved solution.
From today forward, complete the check before use and record it in the system. If the system is unavailable or the check identifies a problem, stop and contact the shift lead. We will review the records together next week.
This wording is firm without being accusatory. It identifies the conduct, explains the effect, invites relevant information, and establishes a measurable expectation. If the issue is more serious, use the same factual approach but follow the appropriate formal process rather than relying on an informal script.
When the Employee Says the Procedure Is Inefficient
An employee may have a legitimate criticism of the procedure. The process may contain duplicated steps, depend on an unreliable system, or no longer fit the way the work is performed. Do not dismiss useful feedback simply because the employee raised it while explaining a failure to comply.
At the same time, a reasonable criticism does not automatically authorize the employee to abandon the procedure. Explain the distinction clearly: the employee may recommend a change, but until an authorized person approves that change, the current requirement remains in effect. This protects consistency while giving the organization a chance to improve a flawed process.
You can respond in this way:
I’m open to reviewing whether this step is still necessary, and I’d like you to show me where it creates the most difficulty. Until the procedure is formally changed, however, it still needs to be followed. If you believe it cannot be completed as written, raise the issue before taking an alternative approach.
Ask the employee to provide a specific suggestion rather than a general complaint. What step causes the delay? What risk might the proposed alternative create? How would the organization preserve the same control? Practical feedback is easier to evaluate and more likely to lead to a useful improvement.
When the Procedure Is Unclear or Inconsistent
Sometimes the central problem is not one employee’s behavior but an inconsistent system. Different supervisors may give different directions, written instructions may contradict actual practice, or new employees may receive incomplete training. In these circumstances, correcting only the individual will not solve the underlying problem.
Review how the procedure is communicated across the team. Ask several employees to describe the process independently, compare their answers with the written guidance, and identify where interpretations diverge. Check whether the required forms, software permissions, equipment, or staffing levels are available. These checks can reveal why reasonable people are performing the task differently.
If the process needs revision, communicate the interim expectation clearly while the review takes place. Do not ask employees to choose between conflicting instructions without guidance. A short team briefing, updated checklist, or written clarification may prevent repeated individual conversations.
Managers should also apply the clarified standard consistently. If one employee is criticized for using a shortcut while others are allowed to use it, the issue becomes one of fairness and credibility. Consistency does not require identical treatment in every circumstance, but differences should be based on relevant facts rather than favoritism or convenience.
Closing Thoughts
Dealing with an employee not following procedures requires more judgment than simply repeating a rule or issuing a reprimand. Establish the facts, assess the risk, speak privately, understand the reason for the departure, and make the expected behavior specific. Provide reasonable support, then follow up and respond consistently if the pattern continues. This approach protects the work, treats the employee fairly, and helps distinguish a training or process problem from a genuine accountability issue.