File-name builder

How to use the builder

1. Choose the date that the file was created, approved, or published. Use one rule consistently across the project.
2. Enter a short project name without client secrets or personal information.
3. Select a document type that explains the file’s purpose, such as report, checklist, notes, or invoice.
4. Add a version only when the file changes through controlled drafts. Use final labels only when your team defines what final means.

Review the generated name before copying it. Your workplace may require a department code, retention label, ticket number, or another approved naming element.

Example

2026-08-03_client-onboarding_checklist_v03.docx sorts by date and still explains the project, file type, and revision when it is downloaded or moved to another folder.

Why the pattern works

Beginning with an ISO date keeps chronological sorting reliable. Project, document type, and version make the file understandable outside its original folder. Lowercase words and hyphens also reduce problems when files move between operating systems or cloud platforms.

Common mistakes to avoid

• Using names such as document1, new final, or latest without context.
• Putting passwords, personal data, medical details, or confidential client information in a filename.
• Creating several “final” versions instead of following an agreed version rule.
• Changing the order of filename parts from one file to the next.

For a complete folder and naming workflow, continue with the shared cloud folder structure guide.