Reports and Export

Reports summarize a completed task; exports turn the selected records into a handoff artifact. Keep those two goals separate: a report explains the list, while a result export carries record-level data.

Review the report

Open a completed task and review:

• total and completed records;
• valid, invalid, risky, and unknown distribution;
• list-quality score;
• frequent reasons and risk signals;
• domain or other available breakdowns;
• task method, timing, and operating context.

The list-quality score is an aggregate comparison aid, not a delivery forecast. See Results and risk scores.

Build an export subset

1. Open the task results.
2. Apply status, score, reason, domain, or available advanced filters.
3. Inspect a sample of the filtered records.
4. Choose the supported result-export format.
5. Save to a controlled location.
6. Record the task, method, filter, and export time in the handoff process.

Examples:

• valid records for a conservative downstream audience;
• risky records for manual or policy review;
• unknown records for a targeted retry;
• invalid records for source-quality feedback and suppression.

Preserve context

Include status, risk, reason, and risk details when the downstream process can retain them. Exporting only the address discards the evidence needed to explain a decision.

Protect exported data

Exports can contain personal data and assessment results:

• restrict access and retention;
• avoid public or shared temporary folders;
• encrypt or use an approved transfer method when handing off;
• delete redundant exports according to your data policy;
• never send a complete list to support unless an approved process requires it.

RS Email Verifier does not automatically import exports into RSender. Review the file and map its fields in the destination application.