From review to control: What closing the marketing compliance gap actually looks like

From review to control: What closing the marketing compliance gap actually looks like

To close the marketing compliance gap, should review occur earlier in the workflow?

To close the marketing compliance gap, should review occur earlier in the workflow?

by Prakash Kakarla

In my earlier article for Corporate Compliance Insights, I wrote about why marketing compliance reviews often happen too late to materially influence the outcome. The harder question comes next: what does closing that gap actually look like when compliance is built into the work rather than added at the end?

Marketing compliance is often described as a review function. That is accurate, but it can also be misleading.

A review suggests that the business has already decided what it wants to say and compliance is there to determine whether it can be said. In practice, some of the most useful compliance work happens well before that stage. When I think about the marketing compliance work I have done across consumer banking, the difference is not simply whether compliance sees a piece of content early or late. It is whether compliance can influence the thinking behind it while there is still room to change it.

The control has to enter before the copy is finished

A marketing request rarely arrives as a compliance question. It usually starts with a business objective. There is a product to promote, a customer segment to reach, a feature to explain, or a message to communicate. As the message takes shape, Marketing is thinking about how to make it compelling, Product is confirming what the offering actually does, and Compliance is thinking about what the customer is ultimately being asked to take away from it.

By the time a completed communication arrives with Compliance, many of those decisions may already be settled. That is where the timing problem begins.

Bringing Compliance into the process earlier does not mean having a compliance reviewer involved in every conversation from the beginning. It means identifying where compliance judgment can materially change the outcome and placing the control there while the message is still being developed.

That can start with a few basic questions before the wording becomes fixed. What exactly are we asking the customer to understand? What claim is being made? What supports it? What qualification sits behind it? Does the communication leave the customer with the same understanding the business intends to create?

Sometimes the answers are straightforward and the review moves on. In other cases, they expose something that needs more attention. A claim may depend on evidence that is not yet clear, a qualification may not fully resolve the customer takeaway, or the product terms and proposed marketing language may not be lining up as cleanly as they first appeared.

Those are much easier issues to address while the message is still being shaped. Once the copy is considered finished, every change can feel like a change to someone's deliverable, especially when a launch date is already in place. Earlier involvement changes the conversation from “Can we approve this?” to “What do we need to get right before this reaches approval?”

Start with the message, not the sentence

One of the things I have learned from marketing compliance is that the most important question is not always whether an individual sentence is technically supportable. The harder question is what the communication is actually telling the customer when everything is considered together.

A statement can be accurate in isolation and still create a misleading overall impression when it is combined with the headline, imagery, placement, qualifications or surrounding copy. That is where regulatory interpretation starts becoming operational judgment.

The review is not just about finding a prohibited phrase or checking whether a disclosure exists. It is about understanding the communication as a customer would encounter it and whether the overall message remains consistent with the product, evidence and regulatory expectation.

That is also where the different perspectives in a review start to matter. Marketing may be focused on whether the message is compelling enough to work. Product may be focused on whether it accurately describes what the product does. Compliance may be focused on whether the customer takeaway is consistent with the underlying terms and expectations. Those perspectives can sound different, but they do not necessarily represent competing objectives.

That is why I do not see good marketing compliance as making communications more conservative by default. The objective is to help the business communicate what it wants without creating avoidable risk for the institution or the customer. Sometimes that means changing wording, strengthening the evidence, clarifying a qualification or reconsidering the proposed message. The important point is asking the question early enough for the answer to matter.

Not every question needs an escalation. Some do.

The other side of an embedded control is knowing when a normal review has stopped being a normal review.

Some reviews are straightforward. The question is clear, the supporting information is available, and there is little reason to take the discussion further. The more difficult reviews often begin the same way. A question may start with copy, but once you work through the product, customer interpretation and supporting evidence, the issue can become broader than the wording itself.

If the customer interpretation is unclear, the supporting evidence is not strong enough, or the product terms and marketing language are not lining up cleanly, treating the matter as another copy edit does not solve the problem. The question is no longer simply what wording works. It is whether the communication is sound and whether the right people need to be involved.

“Something similar was approved before” can be useful context, but it is not automatically the answer. The product, audience, claim, channel or surrounding context may have changed enough to make the question different.

Once that happens, the discussion needs to widen and the right stakeholders need to become part of it.

The review is rarely owned by one team

Marketing compliance sits in the middle of several objectives, particularly when a review moves beyond straightforward wording.

Marketing understands the communication objective. Product understands the underlying offering. Compliance interprets and applies regulatory expectations. Legal may become involved when broader legal interpretation is required, while business or product leadership may ultimately decide how the offering or communication moves forward.

What matters is getting the right people around the same question at the right point. An issue that looks like a wording problem may turn out to be a product or process question. A regulatory concern may be understood clearly by the business but still be difficult to implement within an existing campaign. A proposed change may address one part of the concern while creating another problem elsewhere in the communication.

The compliance professional has to explain why the issue matters, distinguish the regulatory concern from a preferred drafting approach, and help stakeholders understand what needs to change. Compliance is not simply there to say yes or no. It has to explain the risk clearly enough that the business can make an informed decision about how to proceed. The aim is to get the right people around the same problem while there is still time to resolve it.

A decision is not finished until you can explain it later

Once the question has been worked through and a decision has been reached, there is another part of the workflow that is easy to underestimate: the evidence behind that decision.

A compliance decision can make perfect sense to the people involved at the time. Six months later, it may not. People move teams, campaigns change, earlier versions become harder to locate, and someone reviewing an issue later may see only the final communication and approval status.

The objective is not to create documentation for its own sake. It is to leave enough of a trail that someone outside the original discussion can understand what was questioned, what supported the conclusion, whether anything changed, whether the issue was escalated and why the final approach was acceptable.

A useful audit trail should do more than demonstrate that someone approved the final version. It should provide enough context to understand how the decision was reached.

That makes documentation part of the control rather than something recreated later at an auditor, regulator or internal reviewer's request.

Let technology handle repetition. Keep judgment where it belongs.

Once that process is working, technology has a practical role to play, particularly in the repetitive, rules-based parts of the review, especially when teams are dealing with large volumes of communications.

A system can identify content requiring review, apply consistent checks, route it to the appropriate reviewer and preserve the version history and decision trail.

The value is therefore not just speed. It is consistency. Applying the same rule each time reduces reliance on manual checks.

But that does not mean every compliance decision should be automated.

Some questions require the reviewer to understand the product, customer proposition and context. A system may be able to flag a claim or identify language that warrants attention, but that is different from determining whether the overall communication creates the customer understanding the business intends.

That distinction becomes even more important as AI enters regulatory and compliance workflows. AI can support identifying patterns, surfacing potentially problematic language or helping a reviewer work through large volumes of information. But the control cannot simply become “the AI checked it.” There needs to be clarity around what the tool is being used for, how its output is validated, when human review is required and what evidence is retained.

Technology should take repetition out of the process where it can. It should not take accountability out of it.

Related article: Ready for AI marketing compliance?

The real test comes when the deadline is tomorrow

The strength of a marketing compliance control is rarely tested when everyone has enough time.

It is tested when the communication is close to launch, stakeholders are aligned around an outcome and somebody wants a decision quickly. That is when even a well-designed process can be pushed back toward the old way of working. A compliance question becomes a last-minute issue, a change is viewed as a delay, a previous approval is brought forward as precedent, or a disclosure is added because there is no time to revisit the broader communication.

The temptation in that situation is to solve the immediate problem and move on. That is precisely why the control has to exist earlier.

When the process has been designed well, the important questions have already been raised while the message was still being shaped. The supporting evidence is easier to locate, the points requiring escalation have been identified, and the final review is confirming a path that has been considered rather than redesigning the communication at the last moment.

Stakeholders will still have different priorities and deadlines will still be deadlines. The difference is that the difficult conversation happens at the right point, rather than when the only option is to negotiate over wording everyone has already become attached to.

Closing the gap means changing where compliance does its work

For me, that is the real shift from a compliance review to a compliance control.

It is not about adding another checkpoint at the end of the marketing process. It is about moving compliance judgment closer to the point where the underlying decision is being made, while there is still enough flexibility to act on that judgment.

Related article: The great compliance shift

That means understanding the business objective early enough to challenge it constructively, looking at the customer takeaway rather than only the wording, recognizing when a routine question needs escalation, and bringing the right people into the discussion before the communication is finished.

It also means being able to explain the decision afterwards, not simply prove that an approval happened. And where technology can apply a repeatable check consistently, it should do so, leaving the compliance professional more time to focus on the parts of the review that genuinely require judgment.

The control is no longer something that happens at the end to determine whether the business can proceed. It becomes part of how the business gets to the answer in the first place.

Prakash Chakravarthy Kakarla is a senior compliance professional with nearly 10 years of experience in marketing compliance, regulatory risk and financial promotions oversight within global financial institutions. His work has focused on translating complex regulatory expectations into practical controls, stronger review processes and clearer governance across business teams.

Team Haast