Name and Route Files Without Creating a New Mess

“Final,” “final-new,” and “final-really-this-one” are a sign that the filing system depends on memory. An automation can rename those files quickly, but it cannot decide which version is approved unless you give it evidence. Start with a reviewable plan. Do not begin by moving your only copies.

Choose a naming rule people can read Example: P104_Measurements_2026-09-14_v01.pdf The parts are project ID, document type, agreed date, and version. Decide whether the date means created, received, or revised. Consistency matters more than the exact pattern. Keep private details out of filenames. Use the FTC’s privacy guidance when deciding what should be visible in notifications and shared links.

Preview every proposed change Create a list containing original location, proposed name, proposed destination, and reason. Test on a copied folder first using the practice-test approach. Example: an unlabeled receipt image should go to review if its project is unknown. The receipt-extraction guide explains why readable text is not always enough to establish a record’s meaning. If two files would receive the same name, flag the collision. Do not overwrite one. As with contact matching, a resemblance is a reason to inspect—not proof of identity.

Check access as well as location A file can move successfully into a folder that exposes it to the wrong people. Check the destination audience using Drive sharing documentation where applicable. Also test existing links, collaborator access, and the ability to find the approved version. Google’s version-history guidance covers document revisions; it should not be treated as a universal undo for every move or permission change.

Write the recovery plan Keep the old-to-new mapping. Record who approved the batch and how you will reverse it if the result is wrong. Use the approval process for bulk changes and the maintenance card for the pause procedure. Capture naming and review rules in a short operating procedure so a new teammate does not invent another convention.

Try a ten-file pilot Include a clear name, missing date, unusual character, duplicate candidate, and unknown project. Approve the preview, run the change on copies, and ask someone else to locate each result. A good filing workflow reduces searching without losing history or control. If a link breaks or a file lands in the wrong place, use the first-wrong-step walkthrough before trying another bulk run.