PDF naming for ISO 9001 document control

Document control rarely fails on concept and usually fails in everyday practice: a procedure gets revised, exported as PDF, and named QM_Handbuch_v4.pdf while v4_final still sits in the folder next to it. From that moment nobody can say with confidence which version applies. ISO 9001 requires the valid version to be identifiable. A naming scheme that is actually kept is the simplest contribution to that, and it needs no large project to introduce.

Download for free

Before & After

QM_Handbuch_v4.pdf 2024-06_QM-Handbuch_Rev04_Freigabe-GF.pdf

Control means every version is identifiable

The requirement is that documents are identifiable, current and available at the point of use, and that obsolete versions are not used by accident. For filing that means concretely: the filename should show which document this is, which revision state it carries, and from when it applies. A pattern of revision date, document identifier, revision number and approval covers that in a single line anyone can read. What remains is the discipline not to append extras such as final, new or copy, which soften the scheme again within weeks. Keep that rule and the valid state is visible in the file list alone.

What is in the document and what is not

This is the most important limitation of the approach. Filery recognises what is actually present in the PDF: title, date, document type, subject, and in many cases a document number printed in the header or footer. An approval status or a valid-from date, by contrast, is often nowhere in the document and lives only in the approval workflow, the minutes, or people's heads. No analysis can guess such fields. You add them in the suggestion list before confirming the run, or you make sure your templates print those details in future.

Set up once: fix the pattern and the identifiers

Before renaming, settle two things. First the pattern, for example revision date in YYYY-MM form, then identifier, then document type, then revision number. Second the identifiers themselves: procedures, work instructions, forms and records should stay distinguishable, and the abbreviations for them belong in a short list that becomes part of your control rules. Deciding both cleanly once is worth more than half a year of patching, because changing the scheme later affects every reference to a filename sitting in training material, process descriptions and notices. Also settle who maintains the pattern in future and where it can be looked up.

The workflow at a revision

A revision runs in a fixed order: revise, review, approve, export as PDF, name, move into the folder of valid documents, and move the previous version into the archive. Filery sits at the second-to-last position and names the newly exported files according to your pattern. For a single revision that is a minute of work; for an annual review covering thirty documents it is a batch run with a preview. The order stays important: renaming happens after approval and not before, otherwise drafts circulate under the name of a valid version.

Where control stays with the QM system

Filery does not replace document control. It knows no approval workflows, no distribution lists, no validity periods and no obsolete-copy markings, and it does not move files into the archive folder either. Those steps stay with your QM system or your written rules. On data handling: the PDF is read on your computer and its content transmitted encrypted for AI analysis; the recognised metadata come back, the renaming then happens again in the file system, and the documents are not stored permanently. For your own keys there is the Custom plan with your own API keys.

FAQ

Only if it is printed in the document, for example in the header or footer. If it is visible nowhere, the analysis cannot supply it, because it works exclusively with the content of the PDF. You then add the field in the suggestion list before confirming.

No. Approvals, distribution, validity and records stay with your QM system or your written rules. Filery makes sure the exported PDFs are named consistently, which makes it a building block of control rather than control itself. Without regulated approvals, even the best naming scheme will not help.

Yes. Procedure, work instruction, form and record can appear as their own abbreviations in the pattern. Keep the list short and fix it in your control rules so that everyone involved uses the same abbreviations and the sorting stays stable.

Filery does not move them, because the app only renames. Clearing them into an archive stays a separate manual step in your process. A scheme carrying revision date and number does, however, make it visible at a glance which file is the older one.

Related topics

Prepare PDFs for DMS and ECM
Create GoBD-compliant PDF filenames automatically
Prepare PDF files for DATEV import

Download Now

Choose your platform and start with automatic document renaming

macOS

Universal (Apple Silicon & Intel)

Download (DMG)

Windows

Windows 10 & 11

Download (EXE)

We are currently working on official code signing for Windows. The download is already available – Windows Defender or SmartScreen may show a warning because the app is not yet certified. Choose “More info” → “Run anyway” to install.

System requirements: macOS 10.14+, Windows 10/11

All downloads are transmitted securely via HTTPS.