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.
instant download · .xlsx · yours to keep
The problem
A messy folder is annoying. A bad rename loses a file.
Inconsistent names mean every search is a hunt, and the right version is anyone's guess.
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.
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.
The standard
A collision outranks a clean name — because the rename is what can lose data.
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.
Two files that would become one name are both flagged COLLISION regardless of how well-formed each is. You disambiguate before renaming.
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.
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.
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

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 diagramWhat you'll see
A proposed name for every file, and a clear stop on the dangerous ones.
The name already matches the convention. Nothing to do.
The name doesn't match yet. Rename to the proposed name once it shows no FIXME; a FIXME means fix that field first.
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.
- 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
- 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.
It's the honesty core of the kit. If two distinct files would normalize to the same conforming name, both are flagged COLLISION regardless of how well-formed each one is individually — because the rename itself is what can lose data. Clean two files up to the same name and, depending on your rename tool, the second overwrites the first or the batch stops partway, so the cleanup causes the problem. The gate makes that impossible to do blind: it stops you before the rename and tells you which files would clash, so you add a disambiguating token first. It compares the files you list in the sheet; a file you leave off the list is not checked.
RENAME means the current name doesn't match the convention yet and no other listed file wants the proposed name. If the proposed name shows no FIXME, apply it and you're done; if it shows a FIXME, fix that field first, and the Dashboard counts the rows that still show one. COLLISION is a stop: two different files would become the same name, so renaming either one risks overwriting the other. RENAME is 'go ahead once the name is complete'; COLLISION is 'resolve this before you rename anything.' A conformance percentage is shown for context, but it never decides the verdict — the gate does.
A token that fails its check is written as FIXME-<token> instead of leaking a bad value into the name — so a date like 05/14/2026 becomes FIXME-date rather than smuggling a slash into the filename, and a date that isn't on the calendar (2026-02-30) fails the same way. The proposed name points at exactly the field to fix, and it isn't ready to apply until the FIXME is gone. Only a few things are auto-corrected: in a client name, capitals are lowercased and spaces, underscores, and periods become hyphens, with none left at either end ('Globex Corp' becomes 'globex-corp', 'Acme Inc.' becomes 'acme-inc'), and a document type or version typed in capitals is lowercased. A client with any other character ('Smith & Sons'), or with a doubled, leading, or trailing hyphen you typed, is flagged FIXME-client, not guessed. The file extension is carried over as you typed it.
Partly. The list of allowed document types and the separator (underscore, hyphen, or period) are editable cells on the Naming Checker tab, so the kit checks against the document types your team actually uses. The four tokens and their order — date, client, document type, version — are fixed, and so is the format rule for each. The verdict logic and the collision gate stay fixed and deterministic: the same batch of files always produces the same verdicts and the same proposed names, every time.
Different surface. The Document Classify & Route Kit reads a document's content and decides which queue the whole document belongs in (route it to AP, Legal, Recruiting). This kit works on the filename string and the destination name — it checks names against a convention and catches the rename that would clobber a file. One asks 'where does this document go?'; this asks 'what should this file be called, and will renaming it overwrite something?' They don't overlap, and both are deterministic.
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.
Checks your own filenames against a four-token naming convention. It does not score or rank people, and it is not legal advice.