Account First Aid
Identity & Paper Trails 2026-10-11 12:14 2 reads

How to Build an Evidence File a Bank, Regulator, or Police Officer Can Actually Use

How to Build an Evidence File a Bank, Regulator, or Police Officer Can Actually Use

A practical system for building an identity-theft or fraud evidence file that banks, regulators, and police can actually use, centered on one folder, a master index, and the five-minute test.

A pile of screenshots is not a file.
A file that a bank fraud investigator, a CFPB analyst, or a police officer can open and understand in under five minutes is a different object.

This article describes a simple evidence-file system I use after account takeovers, unauthorized transfers, and identity-theft incidents. It is deliberately low-tech so it works on a phone, a laptop, or a printed binder.

I started building files this way after a bank representative asked me for “the timeline and the reference numbers” and I spent twenty minutes scrolling through camera rolls and email. The representative was patient; the next one might not be. A five-minute file respects both your time and theirs.

The same structure works whether the incident is a single unauthorized Zelle payment or a broader identity-theft case involving multiple accounts. Scale the volume of evidence; keep the organization principles the same.

The One-Folder Rule

Create one folder (digital or physical) named with the incident type and the start date, for example:

2026-09-28-unauthorized-transfer-MainStreetBank

Everything related to that incident goes in that folder. Nothing else does. When a new related problem appears—say a second bank is affected—either expand the folder name carefully or create a clearly linked second folder and note the link in both places.

Handwritten one-folder rule for incident evidence

What Goes Inside

Organize with consistent file names and a short master index.

Master index (one text file or sheet of paper)

  • Incident summary in five sentences or fewer

  • Key dates (discovery, first freeze, first report, FTC report, etc.)

  • List of institutions contacted and their reference numbers

  • Current status of each claim or recovery path

Evidence items

  • Screenshots and photos of transactions, lockout messages, and alerts

  • Call logs with date, time, representative ID, and reference number

  • Letters or emails from banks, bureaus, or platforms

  • FTC Identity Theft Report PDF and recovery plan

  • Police report number if one was filed

  • Timeline of actions you took

Name files so the date and content are obvious:
2026-09-28-screenshot-unauthorized-zelle.png
2026-09-28-call-log-MainStreetBank.txt

If you are helping a parent or an older relative, keep the language in the master index plain enough that they can read it themselves. Avoid internal shorthand. The file may need to travel without you.

The Five-Minute Test

Before you share the file with anyone, open it as if you were a stranger. Can you answer these questions in five minutes?

  • What happened?

  • When was it discovered?

  • What has already been reported and to whom?

  • What reference numbers exist?

  • What is still open?

If the answers are buried, rewrite the master index until they are not. The five-minute test is also a kindness to your future self. Months later, when a follow-up letter arrives, you will not remember the details as clearly as you do today. The index is the memory.

Section

Purpose

Keep it to

Master index

Fast orientation

1 page

Timeline

Sequence of events and actions

1–2 pages

Institution log

Who was called, when, reference #s

Table or list

Raw evidence

Screenshots, PDFs, photos

Clearly named files

Correspondence

Letters and emails received

Chronological

Five-minute test questions for an evidence file

Digital vs. Paper

Digital folders are searchable and easy to share as a zip file. Paper binders are useful when a police desk or an older relative needs something they can hold. Many families keep both: a digital master and a printed core set of the index, timeline, and key confirmations.

Whatever format you choose, back it up. An evidence file that lives only on a compromised phone is a risk, not an asset.

For digital files, prefer a cloud account that was not involved in the incident, or an external drive kept offline. For paper, store the binder somewhere other than the bag that holds the compromised device. Physical separation is a form of security that does not require technical skill.

Sharing the File Without Losing Control

When a bank or regulator asks for documentation, send only what is needed for that request, not the entire life history of every password you have ever used. Keep a log of what you sent, to whom, and when. That log belongs in the same folder.

If you are asked to upload documents to a portal, take a screenshot of the successful upload confirmation and add it to the folder. Portals change; confirmations disappear. Your folder should still show what was provided and when.

Common Failure Modes

  • Scattering evidence across email, camera roll, and random notes apps

  • Using vague file names like “screenshot1.png”

  • Updating the master index only in your head

  • Sending the entire folder when only one statement was requested

Avoiding these keeps the file usable months later when a follow-up question arrives.

Stop the damage. Save the proof. Take the next step.

A usable evidence file does not win every case. It does make every conversation shorter, clearer, and less dependent on memory under stress. That alone is worth the hour it takes to set up. Build it once, then keep it current as new confirmations arrive. The habit of adding each new reference number the same day you receive it is what keeps the file trustworthy.

Last updated — 2026-10-11 12:14
Comments [ 0 ]

No comments yet.

Leave a comment