Clear Research Records Start with Better File Names

Files named final, final-new and final-approved create unnecessary uncertainty. A useful document system does not need to be complicated. It needs a convention that everyone understands and applies consistently.

Choose a few meaningful fields

A filename can contain a project identifier, document type, date and version. For example, PROJECT-A_report_2026-09-21_v01.pdf says more than report-final.pdf. This is an organisational example rather than a universal requirement. Follow existing institutional rules where they apply.

Separate originals and working copies

Keep received documents intact. Store annotations, extracted tables and draft summaries separately. If you rename an original file, retain a connection to the issuer’s document number and original filename.

Explain revisions

When a replacement arrives, record which document it supersedes and why, when that information is available. A later date does not tell you which sections changed. A short revision note can save reviewers from opening every version to find out.

Maintain a small index

List the identifier, filename, source, receipt date, version and review status. Keep the fields practical enough to maintain. Avoid putting sensitive details in filenames, which may be visible outside the document.

Design for another reader

Ask a colleague unfamiliar with the folder to find a document and its latest revision. Their questions reveal where the system depends on knowledge held only in your head. Address those gaps before the collection becomes larger.