File-naming convention: agree what each part of a name means

Naming an individual file is different from choosing the folder that groups it with other files. Neither decision settles who owns the work, may read it, or has approved it. Discuss those questions separately rather than encoding an assumed agreement in a filename.

Worked example: a puppet-show poster

In this fictional example, a parent and teen are making a poster for a neighborhood puppet show. They have three drawings and two text layouts. “Poster,” “new poster,” and “final poster” leave them asking which drawing goes with which layout.

They propose names containing the project, item, and stage: “Puppet show - doorway poster - drawing B - for discussion.” The name describes the item without saying that anyone has chosen drawing B. A different file is labeled “Puppet show - handout text - agreed wording.” They use that label only after the people responsible have actually agreed on the wording.

A grandparent preparing a printed sample asks which file to use. The teen points to one exact filename and says it is a sample, not an instruction to print every version. They keep a short note of that choice rather than expecting the name to communicate the entire conversation.

Make a small naming key

Project or collection:
Parts we want in each name, in order:
What each part means:
One example using an ordinary item:
Words we will use for stages:
Who can confirm that a stage has changed:
What a date means, if we include one:
What we will do when two items have the same name:
Where to ask about an unclear name:

Try the pattern on a few disposable examples before changing a collection. Keep the actual file type and any unfamiliar technical requirements outside this naming exercise; it is not a procedure for changing extensions or repairing files. Do not reorganize another person's files without discussing the proposed changes.

Check the meaning, not just the pattern

If you include a date, say whether it means the event date, when someone made the item, or when the group checked it. Choose one meaning for that part of the pattern. “Final” should not quietly become shorthand for “the most recent file I happened to open.”

Use descriptions people involved can understand. A child can name their own drawings without becoming responsible for maintaining the adults' collection. A partner can ask for a shorter name or fewer stages. Personal explanations, health information, and private disagreements do not belong in our sample labels.

Leave room for exceptions

Write down an exception instead of forcing a misleading name. If an item arrives from someone else, keep their instructions and ask before renaming their working material. Revisit the pattern when the people using it cannot explain what a label means. The convention serves this particular collection; following it is not a judgment about someone's organization.

Related guides

• Organization

  : distinguish the naming rule from the wider arrangement.

• Task ownership

  : say who has accepted responsibility for an item.

• Collaboration

  : agree on changes with the people doing the work.

• Personal privacy

  : choose which details belong in labels.