The Art of Following Up Without Becoming “That Compliance Person”
Following up is one of those parts of compliance work that sounds simple until you actually have to do it every day. A policy acknowledgment is still pending. Evidence for a control has not been uploaded. A corrective action has been sitting open for two weeks.
Someone involved in an incident has not responded to a request for information. A department owner promised an update on Friday, and it is now Tuesday.
So compliance follows up. Then follows up again.
After a few reminders, the interaction can start to feel uncomfortable. The compliance professional worries about sounding repetitive or overly aggressive. The person receiving the messages begins to feel chased. What started as a straightforward request slowly turns into friction between compliance and the business.
This is where follow-up becomes a skill rather than an administrative task.
Good compliance professionals know how to maintain accountability without making every interaction feel like enforcement. They understand when to remind, when to ask questions, when to change the communication channel, and when an issue genuinely needs escalation. Most importantly, they understand that getting the task completed is only part of the job. Preserving the relationship matters too.
Highlights
Why Compliance Follow-Ups Feel Different
Almost every department follows up on something. Finance asks for purchase approvals. HR follows up on employee documentation. Project managers ask for status updates. IT reminds people to complete system changes. Yet compliance requests often feel different to the person receiving them.
There is usually an added sense of consequence.
A message from compliance asking for documentation can immediately make someone wonder whether something has gone wrong. A request for clarification during an investigation may cause an employee to become defensive before the conversation even begins. A reminder about an overdue control may be interpreted as criticism rather than a routine workflow notification.
Compliance teams therefore need to be especially conscious of how their communication is perceived. A message that feels completely neutral to the sender may sound serious to the recipient simply because it came from the compliance department.
That does not mean compliance should soften every message until the urgency disappears. It means the tone should match the situation. A routine evidence request should sound routine. A serious unresolved compliance issue should sound serious. When every message carries the same formal or urgent tone, people eventually struggle to distinguish what genuinely requires immediate attention.
Most Follow-Up Problems Start With the Original Request
When people consistently fail to respond to compliance requests, the natural reaction is often to focus on the reminder process. Maybe reminders need to go out earlier. Perhaps the wording needs to be stronger. Maybe managers should be copied sooner.
Sometimes the problem started much earlier. The original request may not have been clear enough.
Imagine receiving an email that says, “Please provide evidence for the quarterly access review.”
Someone working in compliance probably understands exactly what that means. The employee receiving it may have several questions. Which system does this relate to? What qualifies as evidence? Is a screenshot sufficient? Does a manager need to approve it? Where should the document be uploaded? Is someone else on the team already responsible for this?
If people have to figure out what compliance wants before they can complete the request, the chances of delay increase significantly.
Strong follow-up begins with a strong initial assignment. The recipient should understand what needs to be completed, why it matters, who owns the responsibility, where the information should be submitted, and when it is due.
The clearer those expectations are at the beginning, the less chasing compliance will have to do later.
Explain Why the Request Matters
Compliance professionals spend their days thinking about controls, regulations, audits, investigations, policy requirements, and risk. Other employees do not. A request that feels obviously important to the compliance team may look like another administrative task to someone in operations, finance, IT, HR, or another department. This is why a small amount of context can make a significant difference.
Consider a request to complete a vendor assessment. A simple reminder saying, “The vendor assessment is due Friday,” provides a deadline but very little motivation. Explaining that the assessment needs to be completed before a vendor renewal can be approved gives the recipient a clear reason to prioritize it.
The same principle applies to corrective actions. Instead of repeatedly saying that an action is overdue, explain that its status needs to be reviewed before an upcoming audit, committee meeting, or regulatory deadline.
Context helps people understand that compliance is not asking for documentation simply because compliance likes documentation. The task supports something larger.
When people understand the consequence of a request, they are more likely to treat it as meaningful work rather than another box to check.
Make the First Follow-Up Feel Helpful
The first follow-up rarely needs to sound like a warning.
In many situations, the best approach is simply to check whether something is preventing progress.
A message such as, “Checking in on the access review that was due yesterday. Let me know if you are waiting on anything from our side,” accomplishes several things at once. It reminds the person about the task, acknowledges that it is overdue, and gives them an opportunity to explain a blocker.
That last part matters.
Sometimes someone has not completed a task because they are waiting for a report from another department. Perhaps they no longer have access to the system required to complete the work. Maybe responsibility has shifted to another employee. They might simply be unclear about what documentation is needed.
Sending another automated overdue message will not fix any of those problems.
A helpful first follow-up allows compliance to understand the reason behind the delay before assuming that the person is ignoring the request.
That does not remove accountability. It makes the next step more informed.
Not Every Overdue Item Deserves the Same Level of Pressure
One of the easiest ways to create reminder fatigue is to treat every compliance task as equally urgent.
A policy acknowledgment that is two days late does not necessarily deserve the same response as evidence required for an upcoming regulatory examination. A routine annual certification should not be communicated with the same urgency as a corrective action addressing a serious control failure.
When everything is marked urgent, nothing feels urgent.
Compliance teams should consider the risk, deadline, and potential consequence attached to the task before deciding how aggressively to follow up.
Routine requirements usually need a reasonable reminder cadence. Higher-risk items may justify more frequent communication and faster escalation. Critical items connected to regulatory deadlines, significant incidents, or serious audit findings may require active management rather than relying on email reminders at all.
This distinction also builds credibility.
If employees know that compliance only uses urgent language when something truly requires immediate attention, they are more likely to react when they receive that message.
Do Not Turn Every Reminder Into an Escalation
There is a difference between reminding someone that something needs to be completed and making them feel as though they are already in trouble.
Compliance communication can sometimes become unnecessarily formal very quickly. Phrases about failure to comply, escalation to management, or further action may be appropriate eventually, but using them too early can damage cooperation.
A better approach is to allow the tone to become progressively firmer as the situation develops.
The first message may simply check the status. The next reminder can restate the deadline and explain what is being held up. If the item remains unresolved, compliance can communicate what the next escalation step will be.
This gives the recipient a clear opportunity to act before management becomes involved.
More importantly, escalation becomes predictable rather than emotional.
The goal is not to make every late task feel like a disciplinary issue. The goal is to communicate that accountability increases when deadlines continue to be missed.
That distinction can preserve relationships while still keeping the compliance program moving.
Know When Email Has Stopped Working
One of the most common patterns in compliance is the endless reminder email.
The first email receives no response. A second message is sent. Then a third. Eventually the same request is buried inside a long email thread with increasingly urgent subject lines.
At some point, another email is unlikely to solve the problem.
Changing the communication channel can be surprisingly effective.
A short message through Teams or Slack may get an immediate response. A quick conversation during an existing meeting may resolve the issue in minutes. A phone call may reveal that the person has been waiting for information from somebody else. Speaking to the department manager may confirm that ownership changed several weeks ago.
People communicate differently. Some employees carefully manage every email. Others work primarily through collaboration tools or meetings and may receive hundreds of emails every day.
The objective is not to prove that compliance sent enough reminders.
The objective is to get the requirement completed.
If the current communication method is clearly not working, change it.
Separate the Person From the Compliance Problem
Repeated delays can become frustrating.
When the same department misses multiple deadlines or one employee regularly requires reminders, it becomes easy to form judgments. Compliance professionals may start thinking that a team is careless, that an employee does not respect the process, or that someone simply refuses to cooperate.
Those assumptions can quickly affect the tone of communication.
Instead of focusing on the individual, focus on the unresolved requirement.
Rather than saying, “You still have not provided the documentation we requested,” the conversation can be framed around the outstanding evidence and what needs to happen to close the requirement.
This approach is particularly important during incidents and investigations.
People may already feel uncomfortable when compliance asks questions about an event, complaint, or potential policy violation. Language that appears accusatory can cause them to become more defensive and less willing to communicate openly.
Neutrality is valuable.
The strongest compliance professionals can be persistent without making the conversation personal. They focus on facts, deadlines, actions, and outcomes.
The issue is the missing evidence, unresolved action, or unanswered question. The person is someone compliance needs to work with to resolve it.
Ask What Is Causing the Delay
When a compliance task becomes overdue, the easiest question to ask is, “Why has this not been completed?”
A better question may be, “What is preventing this from being completed?”
The difference is subtle, but the conversation it creates can be very different.
Compliance delays often have underlying causes.
The assigned employee may not understand the requirement. The wrong person may own the task. The process could require too many manual steps. A manager may need to approve something before it can move forward. The employee may be managing multiple priorities with competing deadlines.
Sometimes the issue really is a lack of attention or accountability. That should be addressed.
But compliance cannot know that until it understands the situation.
If the same task repeatedly becomes overdue across different teams, that may indicate a process problem rather than a people problem.
Perhaps the request is too complicated. Maybe the deadlines are unrealistic. The organization might lack a central location for submitting evidence. Ownership may not be updated when employees change roles.
Repeated follow-ups can sometimes reveal weaknesses in the compliance process itself.
Build Relationships Before Something Becomes Urgent
It is much harder to ask someone for an urgent response when the only communication they have ever received from compliance has been about overdue work.
Relationships matter.
Compliance teams that interact with departments outside of enforcement situations tend to have easier conversations when difficult issues arise.
That does not require endless meetings or forced relationship-building exercises. It can be as simple as understanding how another department works, learning when their busiest periods occur, explaining upcoming requirements ahead of time, and asking whether the compliance process creates unnecessary friction.
Small positive interactions build familiarity.
When an urgent evidence request eventually arrives, the person receiving it recognizes the compliance professional as someone they have worked with before rather than an unfamiliar name appearing in their inbox with a deadline.
This becomes even more important in incident and case management.
People are far more likely to share information openly when they trust that compliance will listen, remain fair, and handle the issue professionally.
Trust cannot be created at the moment an investigation begins. It is built through every interaction that happened before it.
Use Automation Without Creating Reminder Fatigue
Automation can solve a large part of the follow-up problem, but only when it is used carefully.
Compliance teams often manage dozens or hundreds of recurring obligations, evidence requests, policy acknowledgments, investigations, corrective actions, and approvals. Manually remembering when every person needs a reminder is neither efficient nor reliable.
Automated workflows can notify owners before deadlines, flag overdue responsibilities, alert managers when something remains unresolved, and give compliance teams a central view of pending work.
The danger is over-automation.
If employees receive constant automated compliance notifications, the messages eventually become background noise. People learn to ignore them.
The purpose of automation should not be to send more reminders. It should be to send fewer, better reminders at the right moments.
A thoughtful workflow might provide an early reminder before the deadline, another notification when the due date approaches, and an escalation only after the item becomes meaningfully overdue.
The specific cadence will depend on the risk and the type of obligation.
What matters is that every notification serves a purpose.
Automation should remove repetitive chasing from the compliance team’s workload, not create automated nagging for everyone else.
Make Accountability Visible
Compliance teams often spend large amounts of time chasing work because responsibility is hidden inside emails, spreadsheets, and individual conversations.
The compliance officer knows who owns a task. The employee knows they received the request. Their manager may or may not know that it is overdue.
That lack of visibility creates unnecessary follow-up.
When responsibilities, deadlines, and status are visible, accountability changes.
A department leader who can see that three corrective actions are overdue across their team may address the issue without compliance sending individual escalation emails. A control owner who sees that evidence is still missing can act before someone has to remind them. Compliance leadership can identify patterns across departments instead of manually collecting status updates.
Visibility turns compliance from a private conversation between one compliance professional and one employee into a shared operating process.
This is one of the most effective ways to reduce the perception that compliance is constantly chasing people.
The system shows the status.
Compliance no longer has to be the messenger every time.
Create Predictable Escalation Paths
There will always be situations where reminders are not enough.
A regulatory deadline may be approaching. A significant corrective action may remain unresolved. A department may repeatedly fail to provide required evidence. An investigation may depend on information that someone has not supplied.
At that point, escalation is necessary.
The important thing is to make escalation consistent and predictable.
People should understand what happens when deadlines are missed. They should know when a manager becomes involved, when compliance leadership needs to review an issue, and when an overdue requirement becomes a formal exception or finding.
When those rules are clear, escalation feels less personal.
Compliance is not deciding to involve someone’s manager because it has become frustrated. The process requires escalation because the task has remained unresolved beyond an agreed point.
That distinction protects both the relationship and the integrity of the compliance program.
Escalation should be a defined part of the workflow, not an emotional response to unanswered emails.
Remember to Close the Loop
Following up should not end the moment the requested document appears.
Acknowledging completion is a small habit that can have a large impact.
A short response such as, “Thanks, we have everything we need and this item is now closed,” gives the person confidence that their work was received and that no further action is required.
It also changes the tone of the relationship.
Without that acknowledgment, interactions with compliance can begin to feel like a continuous stream of demands. A request arrives, the employee completes it, and the next interaction is another reminder about something else.
Closing the loop adds a positive end to the process.
Recognition does not need to be elaborate.
A simple thank you communicates that the person’s time and cooperation were noticed.
Start your 21-day free trial and experience how VComply helps you with your policy management and compliance maturity.
Look for Patterns Behind Repeated Follow-Ups
Sometimes repeated chasing is not a communication problem at all.
It is a sign that the compliance process needs improvement.
If compliance professionals spend hours every week checking spreadsheets, searching through email threads, reminding task owners, and manually determining what is overdue, the organization may have outgrown the process it is using.
Repeated delays can reveal structural issues.
Ownership may not be clearly assigned. Deadlines may live in different systems. Evidence may be stored across shared drives and inboxes. Employees may have no easy way to see all of their compliance responsibilities. Managers may have no visibility into what their teams owe.
When this happens, improving the wording of reminder emails will only provide temporary relief.
The better solution is to improve the process.
Centralized responsibilities, clear ownership, automated reminders, shared dashboards, documented escalation rules, and consistent workflows can reduce the amount of manual follow-up required in the first place.
The best compliance teams do not simply become excellent at chasing people.
They build systems that require less chasing.
Following Up Is Part of Building a Strong Compliance Culture
Compliance professionals will always need to follow up.
There will always be deadlines, evidence requests, investigations, approvals, corrective actions, and people who need an occasional reminder.
The goal is not to eliminate those conversations.
The goal is to make them better.
When compliance communicates clearly from the beginning, explains why requests matter, understands the reasons behind delays, and escalates consistently, follow-up becomes part of normal organizational accountability rather than a source of tension.
People stop seeing compliance as the department that appears only when something is late.
Instead, compliance becomes the function that helps keep responsibilities clear, issues moving, and commitments visible.
The most effective compliance professionals are not necessarily the people who send the most reminders or write the strongest escalation emails.
They are the people who know when to be patient, when to ask questions, when to be firm, and when the underlying process needs to change.
Because the real art of following up is not getting someone to respond after the fifth email.
It is building a compliance environment where the fifth email is rarely necessary.
Frequently Asked Questions
