How often do sequence enrollments lack documented approval?

Question and scope

This brief asks a narrow question: in one defined enrollment population and one observation window, how many enrollments can be tied to a named approver before the first send? It does not estimate whether the sequence was well written or whether the contact was a good fit.

The decision the result should inform is where to place the approval control. If most gaps sit in imported lists, the intake check is the place to fix. If they sit in manual enrollments, the send permission is the place.

Population and case key

Define one case as one contact enrolled in one sequence version during the window. Decide before collection whether a re-enrollment after a pause is a new case or a continuation, and apply the rule consistently.

Use the enrollment id as the case key and carry it into the approval log and the send log. If the platform lacks an id, create one at export time and record the export date, filter, and row count.

Evidence standard

An approval is documented only when the approval event names the approver, the time, the sequence version, and the contact or segment. A chat message without those fields is a lead, not evidence.

Treat missing, unavailable, and confirmed negative as three states. An enrollment with no approval record is not the same as an enrollment explicitly rejected. Collapsing them hides the difference between a gap and a decision.

Sampling and collection

If the population is small, report every case and say the sample is exhaustive. If it is large, use consecutive enrollments and stratify by source list so the sample is not only the manually reviewed work.

Include adverse cases: a late approval, a disputed approver, and an enrollment that was paused before send. These are where the definition is tested and where a clean-looking rate usually breaks.

Limits and reporting

Report the eligible count, the sampled count, the exclusions, and the number of cases that could not be classified. A rate without those numbers is not reproducible.

The cited public sources frame recordkeeping and control practice; they do not supply a result for this population. Any change to the sequence tool, the approval rule, or the source list during the window should be recorded as a limit.

Sources

1. Federal Trade Commission, CAN-SPAM Act compliance guide
2. NIST Privacy Framework
3. NIST, Security and Privacy Controls for Information Systems and Organizations

Apply the operating question

Use the finding to define one source, output, review owner, and exception path inside a real workflow.