How to prepare a document collection checklist for Consumer Protection Matters

A consumer-protection document collection checklist should connect each disputed practice to the people, systems, and historical records needed to evaluate it. Start with the alleged consumer journey, define campaign and transaction periods, and assign collection tasks with traceable source references. Separate receipt from verified coverage, and distinguish unavailable records from records not yet requested. The resulting deliverable is a counsel-controlled table showing approved scope, evidence received, verification performed, unresolved gaps, handling restrictions, and responsibility for each next action.

When to use this workflow

Use this workflow when a complaint, demand, discovery request, or internal escalation identifies allegedly misleading advertising, undisclosed charges, subscription enrollment, cancellation obstacles, refund practices, or complaint-handling failures. It serves outside counsel coordinating collection and in-house teams directing marketing, customer service, finance, IT, and vendors.

The task is collection planning and verification—not a complete preservation, discovery-response, or production process. Coordinate collection with preservation instructions; an initial collection boundary should not silently narrow those instructions.

The procedural baseline is US district-court litigation. Rule 26(b)(1) defines discovery scope through relevance, privilege, and proportionality; it does not prescribe a collection checklist or make all relevant material automatically discoverable. Federal Rule of Civil Procedure 26(b)(1). Confirm state, arbitral, or agency requirements separately. Use the actual claims, defenses, governing law, and orders to set priorities.

What you need

Assemble these inputs before assigning tasks:

• Matter definition: allegations, disputed practices, products, channels, locations, relevant periods, and known defenses.
• Consumer journey: advertisements, landing pages, enrollment screens, checkout, confirmations, billing, cancellation, refunds, and support pathways.
• Source inventory: custodians, advertising platforms, publishing systems, billing databases, complaint systems, call recordings, and vendor repositories.
• Historical context: campaign identifiers, version dates, device variants, experiments, archived terms, substantiation files, and policy changes.
• Collection constraints: preservation instructions, retention settings, access restrictions, migration history, missing attachments, and export documentation.
• Discovery boundaries: requests, orders, agreements, disputed scope, and counsel’s collection-sequencing decisions.

Interview system owners about actual recordkeeping. A department name is not a source location, and a current website capture does not establish what a historical campaign displayed.

Use the template

The Consumer Protection Matters — Document collection checklist is a working table, not a requirement to collect every category in every matter. You can copy this table into your working document or spreadsheet. Use one row per distinct source and task; split rows when owners, periods, or methods differ.

Use stable row IDs rather than changing spreadsheet positions. “Records / period” identifies the category and historical coverage. “Scope / method” records filters, account boundaries, collection technique, exclusions, and scope approval, or links to a collection note.

“Evidence / verification” identifies received files, extract rows, pages, screen numbers, or recording timestamps, plus checks performed. Before receipt, identify an expected source without inventing a document ID. Distinguish requested, received, verified within scope, unavailable, and awaiting decision. “Handling” flags restrictions without deciding disclosure. Every unfinished row needs an owner, next action, and internal follow-up date.

Step by step

1. Translate the disputed practice into collection questions

Break allegations into factual questions: What did consumers see? What supported the representation? What did they authorize? What were they charged? Could they cancel? What happened after they complained?

A disputed introductory price calls for the advertisement, contemporaneous disclosure, enrollment path, and billing records—not merely final terms. The FTC’s deception framework considers practices in context, including likely effects on reasonable consumers and materiality. It does not supply uniform elements for state-law claims. FTC Policy Statement on Deception.

Record: Create issue IDs and evidence categories for each question, including potentially contrary evidence. Separate allegations from counsel’s investigative hypotheses.

2. Set historical and proportional boundaries

Identify campaign, transaction, cancellation, and complaint periods separately. Advertising may end before associated recurring charges or refund requests do. A company-wide complaint archive may extend far beyond the disputed product.

Have counsel approve initial boundaries and any staged approach. For example, begin with identified campaigns and linked transactions, then assess whether gaps justify expansion. Document excluded channels and periods rather than letting technical filters silently determine scope. Separately identify records with short retention periods for prompt preservation coordination.

Record: Enter date ranges, product and geography filters, exclusions, approval references, and unresolved scope questions. A bounded collection is not proof that no other relevant records exist.

3. Map categories to actual custodians and systems

Trace marketing claims to campaign managers, agencies, publishing tools, and substantiation repositories. Trace charges to billing systems and payment-provider records. Trace cancellation and refunds to workflow systems, scripts, recordings, and transaction adjustments.

Identify who can explain historical configurations, account identifiers, and field definitions. Ask about former employees, migrated systems, agency portals, and vendor-held attachments. For external sources, counsel should determine access rights and the appropriate collection route; vendor possession does not establish that internal staff can retrieve the material.

Record: Identify the business custodian, technical contact, and source location in the row or linked note. Assign separate vendor and attachment tasks where dependencies differ.

4. Specify methods that preserve consumer context

Define what collectors must retain, not just search terms. For digital advertising, request historical creative, destination pages, disclosures, screen sequences, and available device or variant information. Include supporting configuration records where available. Label later reconstructions explicitly.

FTC staff guidance considers disclosure placement, proximity, prominence, distractions, duration, and understandable language. Contractual assent alone does not make a disclosure clear and conspicuous. These considerations explain why terms alone may be inadequate; the guidance is not a safe harbor or comprehensive statement of disclosure obligations. FTC .com Disclosures.

For structured records, request field definitions, filters, time-zone conventions, and identifiers connecting consumers, transactions, complaints, and refunds. Preserve received originals separately from analytical copies.

Record: Specify method, contextual files, linking fields, collection date, and limitations. Keep collection dates distinct from event dates.

5. Route sensitive and potentially privileged material

Identify payment details, contact information, credentials, and sensitive complaint narratives. Establish restricted review arrangements and avoid unnecessary personal information in the checklist.

Flag potentially protected communications for counsel review without assuming that copying a lawyer establishes privilege. Rule 26(b)(5)(A) requires express privilege or protection claims and descriptions permitting assessment without disclosing protected information; Rule 26(f)(3)(D) addresses planning for compliance timing and method. These provisions do not determine substantive privilege or mandate this table. Federal Rules of Civil Procedure 26(b)(5)(A) and 26(f)(3)(D).

Record: Add handling restrictions, reviewer assignments, and restricted-record references. Keep sensitive legal analysis out of broadly circulated instructions.

6. Verify receipts against assigned tasks

Do not close a row because a folder arrived. Compare receipts against periods, accounts, versions, attachments, and record types. Obtain explanations for empty results, failed searches, inaccessible archives, and export limitations.

Retain original complaint narratives and repeat contacts even if later analysis groups them. Check recordings for usability and account links. For billing extracts, sample links to underlying transactions and identify unmatched records. Document counts where available, without treating a matching count as proof of completeness.

Identify who can explain each item’s origin. In proceedings governed by the Federal Rules of Evidence, Rule 901 requires support that an item is what its proponent claims. A document ID alone does not establish authenticity, and authentication does not resolve every admissibility issue. Federal Rule of Evidence 901.

Record: Enter source pinpoints, verification performed, exceptions, and unresolved foundation questions.

7. Resolve gaps and hand off the checklist

Review gaps with counsel and source owners. Distinguish pending collection, technical failure, unknown existence, unavailable historical content, and approved scope exclusions. Investigate useful alternatives without assuming equivalent coverage.

Set an internal follow-up date for unresolved tasks. Keep collection completion separate from production readiness, and retain the basis for decisions not to pursue additional sources.

Record: Close rows only as verified within their stated scope. Leave unresolved work visibly assigned. Give reviewers source references, restrictions, and limitations so the handoff explains both available evidence and remaining uncertainty.

Worked example

Fictional scenario: Counsel represents Harbor Lantern Learning LLC in a dispute about an online course subscription. Consumers allege that a “first month for $12” campaign obscured subsequent $48 monthly charges and that cancellation requests did not stop billing. All parties, records, amounts, and facts below are fictional.

Counsel requests January–March campaign and enrollment records, with related billing, cancellation, complaint, and refund records through May, all within the same fictional year. The longer transaction window tests later charges without assuming every complaint concerns that campaign. Marketing supplies a desktop capture; support and finance supply exports. Refund records arrive without payment references linking them to the complaints.

The checklist changes three decisions. Counsel cannot assess mobile disclosures from desktop captures, confidently sequence cancellation and charging without time conventions, or connect refunds to complainants without linking evidence. Collection remains open on targeted tasks rather than expanding immediately to every marketing and support record. These gaps are not findings of deception, improper billing, or unpaid refunds.

Common mistakes

• Collecting current terms for historical advertising. Obtain campaign-specific versions and label reconstructions.
• Requesting entire departments’ records without source mapping. Assign systems, custodians, periods, and methods so omissions become visible.
• Treating exports as self-explanatory. Obtain field definitions, filters, time conventions, and linking identifiers.
• Deleting repeat complaints during collection. Preserve source contacts; document grouping rules in later analysis.
• Closing tasks on receipt alone. Verify coverage, usability, and attachments, then assign exceptions.

Final quality check

Before circulating the checklist, confirm:

• Each disputed practice maps to collection rows, including contrary evidence.
• Campaign, transaction, complaint, and collection dates remain distinguishable.
• Historical versions and consumer-facing context are identified or marked missing.
• Source IDs and pinpoints resolve to accessible records; verification is documented.
• Filters, exclusions, limitations, and approvals are recorded.
• Preservation coordination, handling restrictions, and privilege-review assignments are clear.
• Open issues have owners and follow-up dates; closed rows state their verification basis.
• Legal references fit the forum, governing requirements, and case-specific orders.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, and evidence analysis capabilities can support review after collection. Tabular review supports work across multiple documents; the chronology viewer can support examination of the resulting event record. Counsel retains responsibility for scope, source verification, privilege decisions, and gaps. To discuss this collection-to-review handoff, book a demo.

Frequently asked questions

Should counsel collect every consumer complaint?

Not by default. Define product, practice, channels, and period first. Record the boundary and reasons, then reassess if gaps or emerging patterns warrant expansion. Do not confuse collection sequencing with preservation scope.

What if historical website screens no longer exist?

Investigate campaign archives, agency files, version records, and contemporaneous captures. Label reconstructions and their limitations. Record unsuccessful inquiries rather than silently substituting today’s page.

Can one row cover billing, cancellation, and refunds?

Only when source, owner, period, and method genuinely coincide. Otherwise use separate rows and shared account or transaction identifiers. Separate tasks make incomplete dependencies easier to identify.

Is the collection checklist also a production log?

No. It records collection and verification. Responsiveness, objections, privilege, confidentiality, and release require separate decisions. Link production records where useful without treating collected material as production-ready.

Sources

• Federal Rules of Civil Procedure, Rules 26(b)(1), 26(b)(5)(A), and 26(f)(3)(D).
• Federal Rules of Evidence, Rule 901.
• FTC Policy Statement on Deception.
• FTC .com Disclosures.

Scope: General legal-workflow guidance for professional readers, not advice for a particular matter.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.