The lifecycle of a business document

Talking about the lifecycle of a document is not about theorising a DMS. It is about recognising that a file sitting “somewhere” is not being managed. This satellite complements the guide to business document management by detailing the operational stages — distinct from the contract lifecycle, which has its own deadlines.

Why map the journey

Without a map, every department invents its own storage. Versions multiply, access rights diverge, and nobody knows whether the document is still active. Mapping is about assigning responsibilities, not adding bureaucracy.

Five stages to make visible

1. Capture

E-mail, scan, web upload, mobile photo: every channel must lead to the same repository. As long as intake is scattered, the rest of the lifecycle stays fragile.

2. Identification

Type, parties, dates, status: document metadata turns a file into a document you can find.

3. Use and decision

Consultation, validation, controlled sharing. If a business decision depends on the document, the process must leave a trail — without confusing it with a dedicated contract workflow.

4. Reference version

Only one version is authoritative. Drafts can live elsewhere. See the reference version of a document.

5. Retention or disposal

Useful archiving or destruction according to the retention policy. An archive is not a dumping ground: it is the ability to prove something or to delete it cleanly.

Signs that the lifecycle is broken

• Nobody can say within five minutes where the official version is
• Several “final” folders for the same document
• New starters who do not know where to look
• Audits that rebuild the history from e-mails

Fix one critical flow end to end, then expand. The document management guide describes how to scale up.