The report is one page. It answers three questions: what is still usable, what is not, and why.
See a sample reportWant a diagnosis on your own list? Email caseylangness@gmail.com.
List name, source, date, record count, and the date of the last touch if the export has it. The sample uses synthetic data, so no client records appear in it. The header is there so you can tell which export the report belongs to without opening the file again.
The date matters because a list that was dormant six months ago is a different list today. The source matters because a list from a webinar and a list from a purchased file are not the same asset, even when the columns look identical.
How many rows the file contained, how many records were stitched from those rows, and how many were quarantined. A row count is not a record count. The report makes the difference visible.
An ordered list of the records worth re-engaging. Each one carries a score and the evidence behind it: a business domain, a named contact, a note with context, and the recency of the last touch. The order is the point. It tells you where to start.
The score is a way to order the work, not a promise that the person will buy. Read the reason, not just the number. A high score with a thin reason is a warning, not a green light.
The records that cannot be used safely, each with a reason: no email, malformed address, duplicate, missing company, no usable context, suppression match. A quarantine reason is not a judgment about the person. It is a note about what the record can support.
A reason like "no email" is actionable. A reason like "no usable context" tells you the record needs enrichment before it can be worked. The report does not hide the bad records in a count.
The input count equals the recoverable count plus the quarantined count plus the suppressed count. Every difference is accounted for. This is the part most tools skip. It is the part that lets you trust the report.
If the file has 1,000 rows and the stitcher produces 960 records, the report shows how the 40-row difference was handled, then how the 960 records split between recoverable, quarantined, and suppressed. No line goes missing between the input and the output.
No revenue forecast. No prediction of who will buy. No email copy. No CRM connection. No credentials. The report is a diagnosis, not a campaign.
It also does not clean the list, buy enrichment data, or send anything. If the export needs enrichment, the report names the records that need it. The next step is yours to choose.
Start at the top of the recoverable list. Read the reason for the first ten records. If the reasons make sense, the rest of the list is probably useful. If the reasons are thin, the export needs enrichment before a campaign. The report is a map. It does not walk the route for you.
Start with twenty records, not the whole list. If the first twenty reasons hold up, keep going. If they do not, fix the export before you spend time on the rest.
The one-page rule is deliberate. A longer report looks thorough, but it hides the decision. The page should let you start the work, not admire the analysis.
A CSV export. The more context it carries, the better: company, name, email, last touch, notes, source, consent. If the export has no context, the report will say so. That is still a useful answer.