Most teams do not have a “document problem”.
They have a retrieval problem: people cannot predict what a file will be called, where it will be stored, or how it will be classified.
If you want a document system where retrieval is repeatable, start here:
Rule 1: keep naming conventions simple (and enforceable)
Avoid conventions that require perfect discipline.
A convention that works in real ops is short and composable:
[entity]_[identifier]_[topic]_[YYYY-MM-DD]_[vX].pdf
Examples:
PO_PO-00123_delivery-note_2026-03-15_v1.pdfinvoice_INV-8842_payment-proof_2026-03-20_v1.pdf
Rule 2: tags represent how people search
Naming conventions help when the searcher knows the identifier.
Tags help when the searcher only knows the reason:
evidencecomplianceexceptionapproveddraft
Tags should be shared vocabulary, not personal preference.
Rule 3: one document can have multiple tags
If tags are mutually exclusive, teams will avoid using them.
Example:
An invoice PDF can be tagged:
evidencepaymentexception(if it was disputed)
Recommended starting tag set (small on purpose)
Start with 8–12 tags total, then expand only when teams ask for a new retrieval rule.
Suggested tags for procurement + finance:
evidencecomplianceexceptionapprovalpaymentdeliverycontractvariation
Next steps
Tagging and naming conventions are most effective when your documents are first-class records (not just files in a folder):