Source-backed review guide

Review Regulation F documents with a defensible process.

Use this six-step workflow to examine validation notices, collection letters, email templates, and SMS scripts against current CFPB Regulation F requirements—then preserve the evidence behind each decision.

This guide is educational and is not legal advice. Applicability and document conclusions depend on the facts, governing law, and current official interpretations.

Compliance review documents arranged around a dark analysis workspace

Communication review

validation-notice-review.pdf

Decision trail active

DOCUMENT_TYPE: VALIDATION_NOTICE

CHANNEL: WRITTEN_NOTICE

ANALYSIS: COMPLETE

RULE_REFERENCES: ATTACHED

Required disclosuresPass
Itemization dateReview
Source citationsCited
Primary CFPB sourcesExplicit review statesAudit-ready decision context

Quick answer

A six-step document review workflow.

A defensible review is more than a word search. Capture context, verify required information, test prohibited representations, apply channel rules, route legal issues, and retain the completed decision record.

12 CFR part 1006
01

Classify the communication

Record the document type, channel, recipient, debt context, lifecycle stage, and whether it is an initial or subsequent communication.

02

Verify required information

Confirm applicable disclosures and, for validation notices, the required debt, protection, and consumer-response information.

03

Test claims and actions

Look for inaccurate amounts, status, identity, authority, legal-process language, or threatened actions.

04

Apply channel rules

Review electronic opt-out, actual-notice, retainability, delivery, timing, and accepted-channel details.

05

Escalate fact-dependent issues

Route time-barred debt, state-law, furnishing, dispute, and other legal questions for specialist review.

06

Preserve the decision trail

Keep the reviewed version, cited rules, findings, reviewer decision, overrides, and timestamps together.

Review context

Start with scope, not the wording.

The correct rule set can change with the document’s purpose, channel, recipient, collection stage, and account history. Do not mark a document compliant when essential context is missing.

Blocked—missing information

Required review inputs

Capture before making a determination

Exact document or template version
Intended recipient and delivery channel
Current and original creditor information
Debt type, account identifier, and relevant dates
Initial or subsequent communication status
Known disputes, preferences, opt-outs, and inconvenient times or places
Delivery failures and accepted electronic channels
Intended follow-up action, including furnishing or litigation language

Rule checklist

Review the requirement and the evidence together.

Each module states what to inspect and links directly to the governing CFPB section. Treat the citations as the start of legal review—not a substitute for it.

01

Required communication disclosures

For an initial communication, verify the disclosure that the debt collector is attempting to collect a debt and that information obtained will be used for that purpose. For subsequent communications, verify that it states the communication is from a debt collector. Review translated disclosures when the communication uses more than one language.

02

Accuracy and non-deceptive presentation

Compare the document against authoritative account data. Review the debt’s character, amount, and legal status; the collector’s identity; references to attorneys, courts, government, or legal process; and any stated consequence. Flag actions that cannot legally be taken or are not intended. Confirm amounts are authorized by agreement or permitted by law.

03

Validation notice content and format

When § 1006.34 applies, verify timing, clear-and-conspicuous presentation, debt collector disclosure, information about the debt, consumer protections, and consumer-response information. Confirm the itemization date is permitted and used consistently. Model Form B-1 is optional; compliant use provides a safe harbor for specified content and format requirements.

04

Disputes and validation-period rights

Review validation-period communications for language or layout that could overshadow or conflict with dispute and original-creditor rights. If the file shows a timely written dispute or request, verify the appropriate collection hold and response workflow before further collection on the affected debt or portion.

05

Electronic communications and delivery

For email, SMS, and other electronic communications, verify a clear and conspicuous reasonable and simple opt-out method at the specific address or number. Review actual-notice and retainability requirements, delivery failures, E-SIGN requirements where applicable, opted-out destinations, employer-provided email restrictions, and public social-media restrictions.

06

Specialized legal and operational checks

Route time-barred debt, furnishing, state-law, licensing, venue, and litigation issues for focused review. Regulation F prohibits bringing or threatening legal action to collect a time-barred debt, subject to its bankruptcy provision, and requires specified action before furnishing information about a debt to a consumer reporting agency.

Decision quality

Use explicit review states instead of hiding uncertainty.

Pass

The reviewed evidence supports the requirement.

Review

A qualified reviewer must resolve a fact or interpretation.

Blocked

Required account, delivery, or workflow evidence is missing.

Not applicable

The reviewer recorded why the check does not apply.

Every non-pass status should stay connected to the source text, governing citation, owner, and resolution.

Archived compliance records connected by a traceability line

Document version retained

Source communication preserved

Reviewer decision recorded

Rationale and ownership attached

Audit record linked

History remains reconstructable

Record retention

Build the audit record with the review.

Section 1006.100 generally requires records evidencing compliance or noncompliance to be retained from the start of collection activity until three years after the last collection activity on the debt. Recorded calls, if made, must be retained for three years after each call.

Recommended operational record

  • Exact document or template version
  • Account and communication context
  • Rule references and source links
  • Findings, rationale, approvals, and overrides
  • Assignments, timestamps, replacements, and disposition

These are recommended review controls; the rule does not state that each field is independently required.

Common questions

Clarify the limits before relying on the checklist.

Is the CFPB model validation notice required?

No. Regulation F requires compliance with the validation-information content and format requirements. The model validation notice is one way to comply and provides a safe harbor for specified requirements when used in compliance with the rule.

Does a checklist prove a document complies with Regulation F?

No. A checklist improves consistency and traceability, but conclusions depend on facts, account data, delivery history, current law, official interpretations, and applicable state requirements.

What should happen when review context is missing?

Do not convert missing evidence into a pass. Block the review, identify the missing input, assign an owner, and preserve the resolution with the document.

How long should review evidence be retained?

Section 1006.100 generally uses a three-year period after the collector’s last collection activity on the debt. Recorded collection calls, if made, have a three-year retention period after the call. Other obligations may require longer retention.

Turn the checklist into a repeatable review system.

Connect document analysis, deterministic checks, cited findings, reviewer decisions, and audit-ready history in one workflow.

Request demo

Bring your Regulation F review process into one defensible system.

Show us how your team reviews communications today. We’ll walk through where document analysis, deterministic checks, audit history, and pricing fit.

Submissions are securely captured by Ploy and emailed through the site’s submission notifications.