The requirements for the content and structure of the work products to be produced are defined.
Quality criteria for the work products are identified.
Appropriate review and approval (Approval = Written statement that a deliverable is fit for its intended use, and compliant with the defined criteria.) criteria for the work products are defined.
Note 1: Possible sources of documentation requirements may be e.g., best practices or lessons learned from other projects, standards, organization requirements, customer requirements, etc. Note 2: There may be types of work products for which no review or approval (Approval = Written statement that a deliverable is fit for its intended use, and compliant with the defined criteria.) is required, thus then there would be no need to define the corresponding criteria.

Requirements for the storage and control of the work products are defined, including their identification and distribution.
Note 3: Possible sources for the identification of requirements for storage and control may be e.g., legal requirements, data policies, best practices from other projects, tool related requirements, etc.
Note 4: Examples for work product storage are files in a file system (System = A system consists of at least two elements which can be either a system or a component.), ticket in a tool, Wiki entry, paper documents etc.
Note 5: Where status of a work product is required in base practices, this should be managed via a defined status model.

The work products to be controlled are identified.
Change control is established for work products.
Versioning and baselining of the work products is performed in accordance with the requirements for storage and control of the work products.
The work products including the revision status are made available through appropriate mechanisms.

The work products are reviewed against the defined requirements and criteria.
Resolution of issues arising from work products reviews is ensured.