A useful set of claim records makes it possible to trace each answer back to its source. It does not need to contain every screenshot, email, and download you have ever saved. Begin with the instructions for the actual process, identify the facts they ask you to document, and build an organized collection around those questions. Keep the original files available even when you create a shorter working summary.

This checklist is an organizational aid. DigitalAssetSettlement.com is an independent educational site, not a law firm or settlement administrator, and does not receive claim documents. The applicable court orders, court-approved notice, and official claim instructions determine what a particular process requires. This article cannot establish eligibility or whether a document will be accepted.

Start with a request-to-record map

Read the official instructions before gathering material. On a private worksheet, give each requested fact its own row. Add columns for the relevant document, its location, the period it covers, and any uncertainty. This creates a direct relationship between a question and the material you plan to use when answering it.

For context, the CFPB's complaint preparation guidance asks consumers to explain important facts clearly and provide supporting records such as account statements and communications. A CFPB complaint is a separate agency process, not a settlement claim. Its emphasis on a concise factual account is useful as a general organizational principle; its requirements and procedures should not be imported into a court settlement.

Use the claim preparation checklist alongside your worksheet. Treat any category absent from the official instructions as something to evaluate, rather than automatically collect or disclose.

Establish which account and records you are reviewing

Write down the account or service name as it appears in the records. Preserve relevant account identifiers privately, and use a shortened label in working filenames. If the account changed names, record the relationship only to the extent your documents establish it. Avoid guessing that two similar names represent the same account.

Keep separate folders for different account owners. A personal account, a jointly held account, and an account connected to an organization should not be merged merely because you accessed all three. If the official instructions raise a question about who may submit information, note that question for the verified administrator or an appropriately qualified adviser.

Where your records show different email addresses or mailing addresses over time, make a simple history with supporting references. This can help explain why a notice or statement uses an older detail without altering the original document.

Gather transaction records with enough context

Start with exports or statements already available through account channels you independently know to be legitimate. Keep the file as received. If several formats are available, retain the version that preserves the fields relevant to the official questions, then make a working copy for sorting or analysis.

Review the transaction identifiers, dates, asset names, quantities, and account labels actually present. Where a record identifies a network or transaction hash, preserve that value accurately. Do not shorten a value in the source file to make a worksheet easier to read. Use a separate display column if you need an abbreviated reference.

Explain the boundaries of each file

Write a brief coverage note: which account the file concerns, which dates it includes, whether it contains all activity or a filtered selection, and when you obtained it. If you cannot establish one of those details, say so. A clear limit is more informative than an unsupported assertion that the file is complete.

Keep quantities, prices, and currencies distinct

When making a summary, give asset quantity and money value separate columns. Preserve the currency attached to a monetary amount. Do not add figures with different units simply because they appear in the same export. Label any calculation you perform as your working calculation and retain the inputs needed to reproduce it.

If the official instructions require a particular valuation method, identify that instruction before calculating. A number displayed in an account, a transaction amount, and a later estimate are different descriptions in your records. Copy the description alongside the value so a reviewer can understand what you recorded.

When two files disagree, preserve both and record the difference. Do not silently choose the larger amount or revise an original statement to match your worksheet. A discrepancy is a question to resolve using the applicable instructions and reliable source records.

Preserve correspondence and its sequence

Collect communications that help explain the specific facts under review. Examples could include an account statement notification, a support exchange about access to records, or a confirmation related to a transaction. These are categories to consider, not a universal list of required claim evidence.

Arrange relevant messages chronologically and retain enough of each exchange to make the sequence understandable. A single reply can be confusing when the question it answers is missing. Record whether an attachment was included, but avoid opening unknown files merely because a message mentions a settlement.

Before treating a new notice as part of your record set, follow the settlement notice verification workflow. Keep unverified communications separate from material obtained through independently established account or official channels.

Protect originals and identify working copies

Create one folder for original files and another for material you prepare. Give working files descriptive names that avoid exposing full account numbers. A short index can list the filename, document type, period covered, and purpose. File naming should help you find a record; it should not become a second location for sensitive details.

Annotate a copy when you need to highlight a row or explain a calculation. Keep your notes visually distinct from the underlying record. If you convert a file into another format for convenience, retain the original and note the conversion. Open the converted version to check that pages, columns, and text remain readable.

For a paper record, review any scan for missing edges, reversed pages, and unreadable text. An index entry should state if the scan is only part of a longer document. Keep the physical original where you can retrieve it.

Make missing records visible

A gap log prevents an unanswered question from disappearing into a tidy folder. State the missing item, why it might matter under the instructions, where you have looked, and what response you received from an independently verified record holder. Keep a record of requests without treating a request as proof that the document exists.

If an old account is inaccessible, preserve existing statements and relevant messages. Use independently verified support channels to ask what records remain available. Do not give account access or wallet credentials to someone offering to reconstruct a claim for you.

Avoid filling gaps with invented dates or estimated quantities presented as facts. If the instructions permit estimates or explanations, follow their wording and label your work accordingly. When the instructions are unclear, write a focused question about the missing category.

Review the set before any authorized submission

Compare the assembled material against the current official instructions one more time. Confirm that each proposed attachment serves an identified purpose. Review whether the destination, format, and file size requirements match the instructions. Preserve an unchanged copy of what you intend to submit through the verified official process.

Keep unrelated private information out of working summaries. Before redacting a document intended for submission, check the instructions so you do not remove required information. Never include a wallet recovery phrase, private key, password, or authentication code in a claim records collection.

After any submission you choose to make, retain the confirmation and an exact inventory of the transmitted files. For help organizing dates and follow-up questions, read the guide to claim, opt-out, and objection deadlines.

Conclusion: make every answer traceable

A strong records workflow connects each requested fact to an identifiable source, preserves originals, and exposes uncertainty. It does not turn a general checklist into a promise of acceptance or payment. Keep the collection proportionate to the official instructions, protect sensitive material, and use our educational resources to prepare better questions when the process requires clarification.