Protocol

Name files for identity and state, not for your desktop history

A file name should help the receiver choose the right artifact without opening every version.

Work through the ideaIllustrative example

“Final again” is your history, not the file's identity.

A colleague needs to locate the room plan and understand whether it is ready for review.

Blank cream letter sheets and a dark binder clip in a mustard envelopeA draft you can inspect

The name records your revisions.

It does not tell the next person the object's purpose or state.

new_final_again.pdf

Use this one.
What should replace a string of “final” suffixes?

A consistent purpose, identity and state convention, or the relevant system-of-record link.

A filename is a label, not proof of content identity or approval. Do not expose confidential identifiers in it.

VedokrokKeep the idea. Try the next move.

Before you use it

Use when
  • Attachments arrive as final.xlsx, final2.xlsx or screenshot.png.

Keep this limit in mind

  • Do not expose confidential identifiers in filenames that may leave the protected system.

Why it matters

Include the artifact purpose, relevant object or date and version/state where needed. Use one stable convention. If a system of record exists, link it instead of creating another detached copy.

Steps

  1. A receiver can identify the likely correct artifact from the name and message context.

An example

'BP_order-block_2026-09-19_to-import.xlsx' is clearer than 'New final 3.xlsx.'

Check your result

A receiver can identify the likely correct artifact from the name and message context.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading
Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingName files for identity and state, not for your desktop history

Evidence and sources
Supports

ONS content guidance recommends frontloading important information because readers often scan for task-relevant material rather than reading linearly.

The guidance is for web content and is applied here by analogy to async work communication.

Writing and editing: Structuring content · Frontload your content and descriptive headings

Supports

ONS guidance recommends writing around user needs, removing content that does not serve those needs, and using concise task-focused headings.

Regulated or audit-heavy work may require context that feels redundant to the immediate reader.

Writing and editing: Plain language · Put users' needs first; titles and headings; be concise

All sources (2)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details