Version control and change history that is actually useful, traceability between documents, running a review that produces comments rather than approvals, and writing so a successor can take over.

For readers whose documentation now has to hold up over time, through reviews, changes and people leaving the project.

You can maintain documentation that stays accurate through change, run a review that finds problems instead of collecting signatures, and hand over work to someone who was not there.

Documentation that satisfies an auditor without becoming unusable, requirements as contractual obligations, recording decisions and who made them, and specifying what will not be delivered.

Written for people documenting work subject to audit, regulation or contract, where the document is itself the evidence.

You can produce documentation that satisfies an audit and remains usable day to day, record a decision so it can be defended later, and write down what is out of scope as carefully as what is in it.

Setting documentation standards across a programme, the real cost of maintaining a document, why standards are ignored, and choosing what not to write down.

The most difficult level, concerned with how much documentation is worth producing and how to make that judgement defensible.

By the end of this level you can set a documentation standard people follow without enforcement, judge what a document is worth against what it costs to keep current, and decide deliberately to leave something undocumented.