Freeze a representative sample.
Capture the exact input set, source context and evaluation time so later comparisons do not drift underneath you.
INPUT CONTROLSwitch verification engines without switching off your judgment.
A credible migration should compare evidence, disagreement patterns and operational behavior — not just whether two vendors print the same final label. Clean’s evaluation playbook keeps the decision trail visible.
SIX-PHASE RUNBOOK
Evaluate the operating model, not the marketing claim.
Use a representative sample and keep your incumbent in place while you inspect where the systems agree, disagree and remain uncertain.
Run both systems independently.
Do not translate one system’s labels into the other before the evidence exists. Preserve each system’s native output first.
INDEPENDENT OBSERVATIONBucket the disagreements.
Separate syntax, routing, role/disposable risk, mailbox evidence and temporary uncertainty instead of treating every mismatch as one category.
DISAGREEMENT ANATOMYInspect Clean receipts.
Use the evidence, confidence, policy result and immutable receipt to understand why Clean reached each decision.
EXPLAINABILITYStage the integration path.
Move from operator checks to Bulk Clean or the versioned API only after your team accepts the vocabulary and decision boundaries.
CONTROLLED CUTOVERKeep a rollback boundary.
Preserve the previous provider path until production behavior and downstream suppression/review rules are understood.
REVERSIBILITYDISAGREEMENT REVIEW
The interesting rows are the ones that disagree.
Clean is designed to make those rows inspectable. A disagreement becomes a question about evidence and policy instead of a blind vendor popularity contest.
PatternReviewClean lens
Valid vs reviewRole/disposable/provider evidenceKeep uncertainty visible
Invalid vs unresolvedTemporary provider/routing conditionDo not force certainty
Different correction adviceOriginal input + typo advisoryNo silent rewrite
Same label, different evidenceReceipt detail and provenanceInspect the path, not only label
CUTOVER CHECKLIST
Know what “ready” means before traffic moves.
Downstream teams understand safe, review, suppress and unresolved.
Suppression and review behavior is explicit rather than buried in an integration.
API credentials, scopes, tenancy and revocation are assigned deliberately.
The previous path remains available until the new operating model is accepted.
Evaluation boundary
This playbook does not claim a specific competitor behaves in any particular way. It gives your team a method for comparing whatever systems you actually use.