A consistent file name can save time when you return to a report months later or need to send the correct version to someone else. A useful system is simple enough to apply every time and descriptive enough to distinguish files at a glance.
Choose a predictable pattern
A practical pattern is date, subject, document type, and version. For example: 2026-11-15-project-report-draft-02.pdf. Put dates in year-month-day order so files sort chronologically. Use short words separated by hyphens or underscores, and avoid relying on labels such as “final-final-new.”

Separate source files from exports
Keep originals in a folder such as Source and place edited or combined copies in a separate Output folder. This makes it easier to identify which file came from a scanner or another person and which one was produced by a later workflow. Avoid overwriting an original when rotating, merging, numbering, or converting a PDF.
Use versions with care
- Use “draft” while a document is still being reviewed.
- Use a short version number when several revisions are expected, such as v01 or v02.
- Mark a copy “approved” only after the responsible person has actually approved it.
- Archive older versions when you need a history, but keep only the current version in a folder meant for everyday use.
Prepare a set of files for merging
If you plan to combine multiple PDFs, label copies with a two-digit sequence such as 01-cover, 02-report, and 03-appendix. Then open the Merge PDF tool, arrange the files, and check the exported page order. The filenames help you plan; they do not replace reviewing the final PDF.
Avoid putting sensitive details in names
File names can appear in downloads, email attachments, shared folders, and device histories. Do not put full account numbers, medical details, passwords, or other sensitive information in a filename. Use a neutral project label or a reference code when appropriate.
A five-minute folder cleanup
- Create a Source folder for originals and an Output folder for changed copies.
- Rename unclear files using one consistent pattern.
- Move duplicates into an archive folder only if your retention rules allow it.
- Open the newest file and confirm it is the version you intended to keep.
A good naming system is one you can follow consistently. Start with a small set of folders and add complexity only when the work requires it.
A note on file handling: Keep a backup of each source document, and inspect any downloaded result before sharing it.