The hidden cost of post-send review (and where a pre-send check fits)

Most communication-compliance budgets are spent on a queue. Messages are captured, a detection engine flags a subset, and a human reviews each flag: clears the benign ones, escalates the real ones, documents the decision. The archive is mandated and the review is mandated, so the queue is treated as a fixed cost of doing business. It is not fixed, and it is larger than it looks.

The cost is in the inflow

The expensive part of supervision is not storage, it is human review. Every flagged item consumes an analyst’s attention, and most flags are benign, which means most of the cost buys a “no issue” decision. The volume of flags is driven by one thing the queue cannot control: how much risky language gets sent in the first place.

A rough way to size your own cost:

Monthly review cost = messages sent × % flagged × minutes per review × loaded cost per minute

Put illustrative numbers against it. A team where staff send 200,000 messages a month, 3% are flagged for review, each flag takes 4 minutes, at a loaded analyst cost of €0.75 per minute:

200,000 × 0.03 × 4 × €0.75 = €18,000 per month, roughly €216,000 a year, before any remediation or fine.

The figures will differ for every firm, but the shape holds: the bill scales with inflow, and the inflow is the volume of risky messages that left the building.

Where a pre-send check changes the equation

Post-send tooling acts on the queue after it forms. A pre-send check acts on the inflow that feeds it. It reduces the equation in two places at once:

• Fewer flags (the percentage-flagged term): the guaranteed-returns line is corrected before send, so it never becomes a queue item.
• Lower severity (the remediation and fine you avoid): the worst lines, the admissions and the cartel invitations, never reach the record at all.

This is why the cost case is different from most compliance purchases. You are not asking a team to pay to prevent a hypothetical. You are reducing a queue they already staff and a budget they already defend, which is a number they can measure.

The honest scope

A pre-send check lowers the inflow of accidental and careless risk; it does not eliminate the queue, and it does not remove the obligation to capture and review. The archive stays, the supervision function stays, and a determined insider still gets recorded for the post-send layer to catch. The change is in the proportion of the queue that should never have existed. Compliance teams can quantify this against their own audit data.

The takeaway

The cheapest review is the one you never have to do. Measure your real review cost with the formula above, then estimate how much of your flagged inflow is the kind of accidental, well-meaning risk a pre-send check removes before it is sent. That delta is the business case.