Verified mail production
Piece-Level Verified Mail Production
Most mail is checked by sampling: someone pulls a piece from a tray and looks at it. Piece-level verification means a camera reads every finished piece, matches it against the record it was built from, and diverts anything that does not agree. Plavidian produces verified mail in Vista, California for political, government, nonprofit and commercial mailings.
Sampling vs verification
- Sampling proves a piece was right
- Verification proves every piece was right
- Sampling finds a systemic error, eventually
- Verification finds the single wrong piece
- Only one of them produces a record
- Since 2008Producing print and mail in Vista, California
- USPS Full-ServiceCertified Mail Service Provider
- Piece-level verificationCamera-read, not spot-checked
- AAPC memberAmerican Association of Political Consultants
- PCC memberUSPS Postal Customer Council
What the camera reads
The barcode already on the piece
Every mailpiece carries an Intelligent Mail barcode encoding a mailer ID and a serial number unique to that record. The camera reads it at production speed. Nothing extra is printed and nothing is added to the piece to make it verifiable.
Matching
Against the record it came from
The serial read from the piece is matched back to the row in the production file. That answers a narrow but important question: is the piece in front of the camera the one this record was supposed to produce.
Exceptions
Diverted, not discovered later
A piece that does not match, or cannot be read, is diverted from the good stream automatically. It does not enter a tray, so it cannot become an unexplained shortfall at the postal counter.
Reconciliation
What you receive afterwards
At the end of the run the counts are reconciled: records submitted, records suppressed, pieces produced, pieces verified, exceptions and their disposition, pieces mailed. Tracking then runs against the same identifiers, so delivery is reported per record rather than in aggregate.
Where verification matters
The mailings where a wrong piece is expensive
- Political mail with multiple versions
- A contrast piece delivered to the wrong segment is not a printing error, it is a campaign story.
- Matched inserting
- Letter, reply device and personalized insert that must belong to the same record. Verification is what proves they did.
- Public and legal notices
- Where the deliverable is the evidence, not the envelope.
- Financial and benefit communications
- Statements, plan notices and anything where a mismatch is a privacy incident rather than a complaint.
- Bilingual runs
- A single run producing several languages, where the wrong language is invisible to a spot check.
The arithmetic
Why sampling cannot find what verification finds
Pull ten pieces from a 50,000-piece run and inspect them. If 50 pieces are wrong, the chance that a ten-piece sample contains one of them is under one percent. Sampling is good at finding systemic faults, where every piece is wrong the same way. It is close to useless at finding the fifty pieces where a merge collapsed, an inserter double-fed, or one record produced the wrong version. Reading every piece and matching it to its record is the only method that finds those, and it produces the record afterwards.
The read
What happens in the fraction of a second
The piece travels past a fixed camera at production speed. The camera captures the barcode region, decodes the Intelligent Mail barcode, and passes the serial to the matching logic. That serial was written into the barcode when the piece was composed, from the record it was composed from, so the read is not an inference about what the piece probably is: it is the identifier the piece was built with. Pieces that cannot be decoded — a fold across the barcode, a misfeed, ink coverage where it should not be — are treated exactly as mismatches, because a piece that cannot prove it is right has not proved it is right.
Reprints
Closing the loop on an exception
An exception is not just a diverted piece; it is a record that has not yet been satisfied. The reprint run is built from those records specifically, verified in the same way, and reconciled back against the original file. That is what allows the final count to be complete rather than merely large: 50,000 records in, 49,950 verified on the first pass, 50 reprinted and verified, 50,000 accounted for.
What this is not
Honest limits
Verification proves that the piece produced matches the record it came from. It does not prove the record was correct — if the wrong address is in your file, a verified piece will be verifiably wrong. That is what CASS, NCOALink and deduplication are for, upstream. It also does not prove delivery; USPS scans do that afterwards. The three answer different questions, and a mailing that needs certainty needs all three.
One connected workflow
Data to proof, inside one building
Most mailings cross three or four vendors. Every handoff is a place where a list changes, a piece goes missing, or nobody can say what actually happened. Plavidian keeps all six steps under one roof and one set of records.
- DataCASS, NCOA, dedupe, householding, presort
- PrintVariable production, matched inserting
- VerifyCamera reads every piece, diverts exceptions
- MailFull-Service preparation, eInduction, entry
- TrackUSPS scans piece by piece
- ProveReconciled report of what mailed
One provider. One connected workflow.
Questions
Frequently asked questions
What is piece-level mail verification?
Reading an identifier on every finished mailpiece and matching it against the record that piece was produced from, so that each piece is individually confirmed rather than a sample being inspected.
What does the camera actually read?
The Intelligent Mail barcode already printed on the piece, which contains a mailer ID and a serial number unique to that record.
What happens when a piece fails verification?
It is diverted out of the good stream automatically before it can enter a tray, and it is recorded as an exception against the record it belongs to.
How are failed pieces recovered?
The affected records are reprinted and verified again, and the reprint is tracked back to the original record so the final count reconciles.
What evidence does the customer receive?
A reconciled report: records submitted, suppressed, produced, verified, exceptions and disposition, and the USPS documentation for the mailing.
Does verification slow production down?
No. Reads happen at production speed; the camera is in line, not a separate step.
What if the barcode cannot be read?
The piece is treated as an exception and diverted, the same as a mismatch. An unreadable piece is not assumed to be correct.
Is this the same as USPS tracking?
No, and the distinction matters. USPS scans tell you where a piece went after you handed it over. Verification tells you the piece was correct before you handed it over. <a href="/plavidian-insight">Insight</a> does the first; Sentry does the second.
Can we get the verification data?
Yes. The reconciled record is part of the job, not an upgrade.
Postal terms on this page: Intelligent Mail barcode · Full-Service · Seamless Acceptance
Related
Where to look next
Camera Verification · Job Accuracy · Campaign Mail Assurance · Plavidian Insight · The Plavidian Standard
Your mailing should not become a black box
Plavidian keeps data preparation, production, verification, USPS preparation and tracking inside one accountable workflow, and returns a reconciled record of what actually mailed.