EXAMPLE DELIVERABLES
Know what you’re asking for.
Explore the format of a contact dataset, a cleansing result and a findings report before discussing your own brief.
All examples on this page are fictional. They illustrate structure and reporting, not actual people, firms, market coverage or achieved results. Fields, checks and deliverables are agreed for each project.
02 / CLEANSING
See the changes. Keep the uncertainties.
Fictional before-and-after example| Before | After | Action and limit |
|---|
| “ Alex Example ” | “Alex Example” | Surrounding whitespace removed |
| alex@@example.invalid | Unchanged; issue flagged | Malformed email retained for review; no replacement invented |
| Two rows with the same email | Both retained; duplicate flagged | Review before merging; a shared address may represent different people |
| Role missing | Still missing | No reliable source found in this example; left unresolved |
A project can include a cleaned file, issue list and change summary. Standardisation and firm matching are distinct from verifying a named person or their email.
Discuss a cleansing project →03 / FINDINGS REPORT
A short report that explains the file.
LCI / FICTIONAL QUALITY REVIEWExample only · not market research
Brief: review a 100-row sample
Scope: standardise agreed fields, identify missing values and flag possible duplicates. No email-deliverability or current-employment verification included.
100input rows retained
12rows needing review
8rows standardised
Interpretation: counts describe separate checks and may overlap. They do not establish an overall accuracy percentage.
What needs attention?
- Resolve possible duplicates before merging records.
- Research missing or conflicting role details if included in the agreed scope.
- Check applicable use restrictions and source dates before release.
Delivery notes: record the source-file version, review date, fields checked, changes made, exclusions and outstanding work in the actual report.
Discuss your requirements ↗