A method for testing whether an opt-out reaches every outbound system.
Research scope and unit
Measuring Suppression Propagation asks whether a suppression event is reflected in every sending system before the next send. The unit is one sales development record or event, not an individual performance rating. The method fixes the window, source, exclusions, and owner.
The output is a reproducible evidence register, not a benchmark for every outbound team. It does not establish causation or a universal quality score.
Population and evidence
Collect opt-out, systems, verification, and time for each sampled record. Include routine, returned, corrected, and unresolved cases. Preserve source, version, event time, and load time.
Mark missing or conflicting evidence explicitly. Do not merge records or backfill a field from a later state to make the sample cleaner.
Review method
Two reviewers classify a frozen sample independently and record reasons. Measure propagation coverage and agreement before concluding. Resolve disagreements against the written rule and revise ambiguous definitions before expanding.
Separate preparation from judgment. A reviewer can classify and route; the named owner decides the exception or control change.
Limitations and decision use
Report counts, denominators, missing-data rates, and limitations. A bounded sample cannot prove causation and a clean CRM state does not prove a customer or prospect outcome.
Give the owner a short result, population, one proposed control change, and a retest date. Change one control at a time.
Sources
Apply the operating question
Use the finding to define one source, output, review owner, and exception path inside a real workflow.
Discuss the workflow