ALFA
Small impactBeginnerTask

Rename and file a folder of 70 client documents in one pass

Take a dump of badly named PDFs and phone photos and turn it into a folder where every file is named to your convention and sitting where it belongs.

Instead of opening every file to see what it is, an AI tool that can work on files in a folder reads each document, proposes a name and a destination that follow your firm's convention, and shows you the whole plan as a table before it touches anything. You approve the plan, it moves the files, and it hands you a list of anything it could not identify.

Time
Saves 10 to 30 min
About 40 min down to 8 min per folder of about 70 files
Who does it today
Admin staff, or the preparer when there is no admin
Practice area
Firm operations

Illustrative planning estimate, not a measured result. Assumes a mixed folder of about 70 files (statements, receipts, tax forms, correspondence) named things like scan_0042.pdf and IMG_3381.jpg. Traditional time is opening each file, deciding what it is, renaming, and dragging it into a subfolder. AI time is writing the instruction, reading the proposed plan, fixing a few rows, and approving it.

Traditional vs AI-native

Traditional

  1. 1Open each file
  2. 2Decide what it is
  3. 3Type a new name
  4. 4Drag to a subfolder
  5. 5Repeat 70 times

AI-native

  1. 1Point the tool at a copy of the folder
  2. 2AI reads and proposes names
  3. 3You review the plan table
  4. 4AI renames and files
  5. 5You check the leftovers

Where you sit

You set the convention and approve the plan. The tool does the opening, reading, typing, and dragging, and it never moves a file you have not seen in the plan.

The traditional way

  1. Download the client's upload or email attachments into a folder.
  2. Open each file to see what it is, because the file name says nothing.
  3. Rename it to the firm's convention (year, client, document type, issuer).
  4. Drag it into the right subfolder: income, deductions, correspondence, prior year.
  5. Keep a mental note of anything that looks incomplete or unreadable.

Where it hurts

  • Pure clerical time, often done by someone whose time is worth far more.
  • Naming conventions drift from person to person and client to client.
  • Unreadable or duplicate files are noticed late, during prep.

The AI-native way

  1. 1You

    Work on a copy

    Copy the client folder to a working location and point the AI tool at that copy only. If the plan goes wrong, the original is untouched and you start again.

  2. 2You

    Give it your convention

    Paste your naming convention and folder structure into the instruction, with two or three real examples of correctly named files. Examples teach the pattern faster than rules do.

  3. 3AI

    Read every file and propose a plan

    The tool opens each PDF and image, identifies the document type, issuer, tax year, and account (last four only), and writes a table: current name, proposed name, destination folder, and how sure it is. Nothing is renamed yet.

    Tools: Claude Cowork or Claude Code · Any AI tool that can read and act on files in a folder you choose

  4. 4You

    Review the plan, not the files

    You scan a 70-row table instead of opening 70 files. Correct the rows that are wrong, and tell it how to handle the low-confidence ones. Duplicates and unreadable images are listed separately.

  5. 5AI

    Execute and report

    On your approval it renames and moves the files, then writes a short log of what it did and a list of anything it left alone. The log is your record if someone asks where a file went.

What you need

  • An AI tool that can read and act on files in a folder you choose
  • Your naming convention written down, with two or three examples
  • A copy of the client folder to work on
  • A data decision: use an enterprise tool under a data agreement, or keep this to files without client identifiers

Copy the prompt

Rename-and-file instruction

You are organizing a client document folder for a CPA firm. The folder is a working copy.

Naming convention: YYYY_ClientLast_DocType_Issuer_Last4.pdf
Examples:
  2025_Nguyen_W-2_Acme Corp.pdf
  2025_Nguyen_1099-DIV_Fidelity_4821.pdf
  2025_Nguyen_PropertyTax_Fulton County.pdf

Folders: 01 Income, 02 Deductions, 03 Correspondence, 04 Prior Year, 99 Needs Review

Step 1. Read every file in the folder. Do not rename or move anything yet.
Step 2. Show me a table: current name, what the document is, proposed name, destination folder, confidence (high/medium/low), and a note if something looks incomplete, duplicated, or unreadable.
Step 3. Wait for my approval. I may correct rows.
Step 4. After approval, rename and move the files exactly as approved. Put low-confidence files in 99 Needs Review with their original names.
Step 5. Write a log file listing every change and every file you left alone.

Rules:
- Never delete a file.
- Use only the last four digits of any account number.
- If two files look like duplicates, keep both and flag them.

Example

Fictional data.

Folder as received (excerpt)

scan_0042.pdf
IMG_3381.jpg
Document (3).pdf
statement.pdf
statement(1).pdf
tax form.pdf

Proposed plan (excerpt)

scan_0042.pdf       2025_Nguyen_W-2_Acme Corp.pdf               01 Income      high
IMG_3381.jpg        2025_Nguyen_Receipt_Bright Horizons.jpg     02 Deductions  medium (photo, total legible)
Document (3).pdf    2025_Nguyen_1098_Rocket Mortgage_7710.pdf   02 Deductions  high
statement.pdf       2025_Nguyen_1099-DIV_Fidelity_4821.pdf      01 Income      high
statement(1).pdf    (same as statement.pdf)                     99 Needs Review  possible duplicate
tax form.pdf        2024_Nguyen_1040_Filed Return.pdf           04 Prior Year  high

Needs you: 1 possible duplicate, 0 unreadable. Nothing has been moved yet.

Guardrails

  • Always work on a copy of the folder, and never give the tool permission to delete.
  • Require a plan-then-approve step. The tool should not rename or move anything until you have seen the table.
  • Client documents carry taxpayer data. Use an enterprise AI tool under a data agreement, or anonymize before you start.

What can go wrong

Phone photos and faint scans get misidentified.

Low-confidence files go to a Needs Review folder with their original names instead of a guessed one.

The tool invents a tax year from the file date rather than the document.

The instruction says the year must come from the document itself, and the plan table shows where it read it.

Where this goes

Once the convention is written down, the same instruction runs on every client folder the day documents arrive, and it becomes the first step of a full intake pipeline.

Demo

Demo video coming soon

Until then, the steps and the example above are the walkthrough.

Want to implement this in your firm?

Bring it to the weekly call. Members work through builds like this one together, with accountants who are already doing it.

See membershipDoing this already? Tell us

Keep browsing