File hygiene · one spreadsheet

File Naming & Organization Engine

Check every filename against a four-token naming convention, get the corrected name for each file, and catch the rename that would collide with another file — before you run it.

Per file you get one of three verdicts: CONFORMS (leave it), RENAME (here's the fixed name), or COLLISION (two files would become the same name — fix first).

instant download · .xlsx · yours to keep

The problem

A messy folder is annoying. A bad rename loses a file.

Nobody can find anything

Inconsistent names mean every search is a hunt, and the right version is anyone's guess.

The rename that overwrites

Two files cleaned up to the same name — and, depending on the rename tool, the second replaces the first or the batch stops partway. The fix caused the problem.

Doing it by hand drifts

Renaming a hundred files by hand is slow and inconsistent. A rule applies the same way every time.

What's inside

One spreadsheet that checks names and catches clashes.

A four-token naming convention (date, client, type, version) with your own allowed document types and separator
A live per-file check grid — every token tested, the proposed name assembled
A collision gate that flags any two files that would become the same name
Editable allowed document types and separator
A worked 6-file example and 200 rows ready for your own batch (fill down to 1,000)

The standard

A collision outranks a clean name — because the rename is what can lose data.

Deterministic

Every check is a fixed string rule against the four-token convention — no model, no invented confidence. The same batch always gives the same verdicts.

Collision-safe

Two files that would become one name are both flagged COLLISION regardless of how well-formed each is. You disambiguate before renaming.

Honest about bad fields

A token that fails its check shows as FIXME-<token>, never a bad value smuggled into a 'conforming' name. A name that still shows a FIXME is not ready to apply: fix the field and it resolves.

How it works

Try it — fix a bad date, or disambiguate a collision, and watch the verdicts move.

Check a batch of files · live · deterministic
as of 2026-06-22
Convention: {date}_{client}_{doctype}_{version}.ext
2026-04-20_acme_invoice_v2.pdfCONFORMS
→(already conforms)
Northwind Report FINAL.docxRENAME
→2026-05-03_northwind_report_v1.docx
contract draft.pdfRENAME
→FIXME-date_globex-corp_contract_v3.pdf
invoice_copy_A.pdfCOLLISION
→2026-03-01_initech_invoice_v1.pdfshared by 2
invoice_copy_B.pdfCOLLISION
→2026-03-01_initech_invoice_v1.pdfshared by 2
proposal_umbrella.pdfRENAME
→2026-06-10_umbrella_proposal_v1.pdf
Batch verdict
COLLISIONS FOUND

1 conform · 3 to rename · 2 collision. A collision must be fixed before renaming. 1 proposed name still shows a FIXME: fix that field before you rename.

Conformance
17%
context only — the gate decides

Mixed batch (collisions found): One already-correct file, three to rename (incl. a bad date flagged FIXME), and two different files that normalize to the same name — a collision.

Every check is a fixed string rule against the four-token convention — a token that fails its check shows as FIXME and never leaks a bad value into a name. The workbook produces these exact verdicts.

This is the live engine. The full .xlsx with your own allowed types and separator Live per-file checks, proposed names, and the collision gate A worked 6-file example and 200 rows ready for your own batch

Get the kit — $49
Diagram of the File Naming & Organization Engine: filenames graded against a naming convention and rolled up worst-not-average, a collision gate, and the batch reading COLLISIONS FOUND on two files that would rename to the same thing.
Shareable diagram

How the gate works, in one image

How the File Naming & Organization Engine grades filenames against a four-token naming convention and flags COLLISIONS FOUND when two files would rename to the same thing — the same math the demo runs, as a diagram you can share or embed anywhere.

View & embed the full diagram

What you'll see

A proposed name for every file, and a clear stop on the dangerous ones.

CONFORMS

The name already matches the convention. Nothing to do.

RENAME

The name doesn't match yet. Rename to the proposed name once it shows no FIXME; a FIXME means fix that field first.

COLLISION

Two files would become the same name. Add a disambiguating token first.

Who it's for

Anyone with a folder of files that should follow one naming rule.

Built for
  • Ops and admins standardizing a shared drive
  • Bookkeepers naming invoices, receipts, and contracts
  • Anyone migrating files into a new convention
  • Teams who want a safe-rename check before a bulk move
Not for
  • Actually moving or renaming files on disk (it tells you the names; you apply them)
  • Classifying document content (that's a routing tool)
  • Scoring or ranking people

FAQ

Straight answers before you buy.

It checks each file against a four-token naming convention — date, client, document type, version — each with a format rule. For every file you enter the current name, the extension, and the four field values; it checks each token, assembles the corrected name, and returns one of three verdicts: CONFORMS (the name already matches, leave it), RENAME (the name doesn't match yet; here's the corrected name, ready to apply once it shows no FIXME), or COLLISION (renaming would clash with another file in your list — fix first). It's a single .xlsx, so it tells you the names to use; you apply them. It never touches your disk and never moves or renames a file.

Start here

New to the document-ops line? Run the Document Processing Pipeline Diagnostic first — it scores your workflow across six stages and, where a stage is short, routes you to the exact drop that fixes your bottleneck.

Get the kit

Rename with confidence.

  • One .xlsx — Start Here, Dashboard, Naming Checker.
  • Four fixed tokens, your allowed types, your separator.
  • A worked example and 200 rows ready for your batch.
$49

one-time

Buy the Kit

Checks your own filenames against a four-token naming convention. It does not score or rank people, and it is not legal advice.

← Browse all Quick Kits