Set a source file naming rule before the research folder migration

A naming rule that keeps research files findable when the team moves years of folders into a new structure.

Set a source file naming rule before the research folder migration

Inventory what the folder actually contains

Before writing a naming rule, export the file list with names, dates, sizes, and owners. Group the files by the decision they supported rather than by the year they were created. The inventory usually shows a long tail of one-off exports beside a smaller set of documents the team still opens. That smaller set should shape the rule, because it is the work the team actually reuses.

Open a sample from each group and note what the file name fails to say. Common gaps include the market, the source date, the version, and the person who approved the finding. Write those gaps down before proposing a format. A naming rule that fixes imaginary problems adds length without making search easier.

Note the tools that hold the files as well as the folders. A research library may span a shared drive, a document tool, and a chat archive. A naming rule that covers only one tool leaves the others inconsistent. List the tools in the inventory so the migration plan can address each one.

Put the decision in the file name

Start the name with the topic a future reader would search for. A name such as packaging-page-review is easier to find than a name built from the author's initials or the ticket number. Add the specific scope, such as region, segment, or competitor, after the topic. The first two or three words should distinguish the file from its neighbors.

Avoid names that describe the file type, such as notes, final, or draft. Those words appear in hundreds of files and tell a reader nothing. If a version matters, put a short marker at the end and keep the version history in one place. The goal is a name that a new analyst can search from memory without opening a folder tree.

Standardize the date and owner fields

Choose one date format and decide whether the date means created, observed, or reviewed. Write that definition in the naming guide, because a date without a meaning is easy to misread. Use the same format everywhere and put it in the same position in the name. A reader should be able to sort a folder and understand what the dates represent.

Record the owner in the file metadata or the folder record rather than in the name when possible. If the owner must appear in the name, use a short identifier that the team can map back to a person. Do not use a shared team name, because a team cannot answer a question about a file. An owner is the person who can confirm why the file exists and whether it is current.

Test the date field with a file that was created before it was reviewed. A creation date and a review date can be months apart, and the reader needs to know which one the name shows. If both dates matter, put one in the name and the other in the file properties. A single ambiguous date invites a wrong assumption about freshness.

Handle duplicates before the move

Duplicates are cheaper to resolve before a migration than after it. Compare files that share a topic and choose one canonical version with a named owner. Mark the others as superseded and move them to an archive folder that does not appear in normal search. A migration that carries three copies of the same claim into a new system simply hides the conflict in a new place.

Record why the superseded version was kept, such as a legal hold or a customer dispute. A retention reason is different from a habit of keeping everything. If no reason exists, remove the duplicate from the active set and keep a single archived copy. The migration should reduce the number of files a reader has to judge, not multiply it.

Test the rule on a sample of files

Rename a sample of twenty files using the proposed rule and ask two colleagues to find a specific document. Watch where they look first and how many attempts they need. If they search by topic but the rule leads with a source name, the rule is wrong for the team. Adjust the order of the fields before applying it to the whole folder.

Test names that are unusually long and unusually short. A long competitor name may need a standard abbreviation, while a short topic may need a scope word to be unique. Write the abbreviation list beside the rule so people use the same one. The test is finished when a colleague can find the sample file without asking where it lives.

Publish the rule where new files are created

Put the naming guide in the folder where new files are created, not in a separate policy library. Add a short checklist to the intake form or template so the name is correct before the file is saved. A rule that lives only in a training deck decays as soon as the next person joins. Keep the guide to one page and show real examples from the team.

Review the rule after the migration and again at the next quarterly cleanup. Look for names that had to be corrected and for topics that keep colliding. Change one field at a time so the team can see what improved. A naming rule is a small piece of infrastructure, and it stays useful only when someone owns its upkeep.

Add a short note to the migration announcement that explains the change and links to the guide. Tell people what to do with an old file they cannot rename, such as moving it to the archive. A rule without an exception path creates quiet workarounds. The exception path should be narrow and owned.

Related GTM guides