Document Lifecycle Management: Six Stages, One Owner Each

Document lifecycle management is the practice of treating a document as something with a beginning, a working life and an end, rather than as a file that appears somewhere and stays there. The lifecycle itself is not a product. It is a map, and its value is that it shows where responsibility changes hands.

Most document problems are handover problems. The draft is fine, the approval is fine, the archive is fine, and the document falls between two of them.

The six stages

1. Creation

A document comes into existence, from a template or from nothing. The decision that matters here is whether it is born inside the system or outside it. A document created on somebody's desktop and uploaded later starts its life with no author trail and often no category.

2. Collaboration and review

People edit, comment and disagree. This is the stage with the most activity and the least ceremony, and the only thing the system must guarantee is that there is one current copy.

3. Approval

Somebody with authority says yes. This is the sharpest transition in the whole lifecycle: before it the document is an opinion, after it the document is a commitment. The approval has to attach to a specific version, not to a file name.

4. Publication and use

The document does its job: it is signed, sent, followed, or referred to. Access rules usually change here, often widening to people who had no reason to see the drafts.

5. Retention

Active use ends and the document becomes a record. Here the clock starts: a term, a case, a rule it belongs to. Nothing visible happens on the day this stage begins, which is exactly why it gets skipped.

6. Disposition

The term expires and the document is destroyed with a report, or transferred to a permanent archive. This is the stage nobody designs, and the one every audit asks about.

Where the handovers break

• Between approval and use. The approved version is stored somewhere different from where people go looking, so the organisation works from the draft.
• Between use and retention. No event marks the end of active life, so the document sits in the working system forever and its term never starts.
• Between retention and disposition. The term expires and nothing happens, because nobody is named as the person who signs.

Notice that all three are organisational before they are technical. Software cannot decide who signs a disposal report; it can only refuse to let the step be skipped silently.

Lifecycle is not the same as workflow

A workflow is a route through one stage: this approval, these three people, in this order. A lifecycle spans all six stages and usually several systems. Organisations that automate workflows without mapping the lifecycle end up with very efficient stage three and nothing at all after stage four.

The reverse is also common and less harmful: a mapped lifecycle with manual steps works, slowly. A fast workflow that loses documents at the end does not.

How to map it without a six-month project

Take one document type that somebody already owns, a contract or a personnel order. Write down, for each of the six stages, two things: which system holds the document, and which role is accountable. One page.

The gaps are visible immediately, and they are almost always at stages five and six, where the column is empty. That empty column is the project. Filling it is usually less work than the mapping was, because by then the argument about who decides has already happened on paper rather than during an inspection.

Where this sits in our products

Stages one to four live in a document management system: in Microsoft 365 that is our document management for Microsoft 365, on the classic platform it is document management software. Stages five and six live in the archive: document archiving software for the storage, and records management software for the terms, the file plan and the disposal evidence.

FAQ

How many stages does a document lifecycle have? Different models count between four and eight, and the number matters less than the handovers. Six works because it separates approval from publication and retention from disposition, which are the four places things actually get lost.

Is document lifecycle management a product you buy? No. It is a map you draw, implemented by whatever combination of systems you already have. Anyone selling it as a single product is selling you one or two stages and calling it all six.

When does a document become a record? When active use ends and the organisation keeps it as evidence. In practice you have to name the event that marks it, such as a contract expiring or a case closing, otherwise the transition never happens and the term never starts.

Do all documents need the full lifecycle? No, and pretending otherwise is why these projects stall. Routine correspondence can go from creation to disposal with nothing in between. Reserve the full treatment for the types where somebody will one day have to prove what happened.

Related reading. version control rules, how to write a retention policy, what document archiving is.

Map it on your own document types. Talk to us and we will walk one type through all six stages and show where your column is empty.