Review & Approval

A live, read-only summary of every module's reviewer, approver, and sign-off status, plus an optional commentary box for anything you want published alongside it.

The "Sign-off Summary" table is generated automatically from the real reviewer/approver assignments and sign-off actions happening on every other module in this DRP, the same way Cover & Version Control's revision history is built from real version records rather than typed in by hand. Nothing in the table can be typed.

It updates the moment reviewers or an approver are assigned to a module — whether that happens on this DRP's Review Assignments tab or is inherited from the project's Modules tab — and again the moment one of them actually acts. Every module that uses the review workflow appears the same way, Requirements included.

Below the table is a commentary box for anything you want to publish alongside the sign-off record — for example, a note that two sections were approved by override because the approver was on leave, and why.

This module has no review workflow of its own, and never will. It is the review workflow — a live summary of every other module's reviewers, approver and sign-off status. Reviewing the review log would be circular, and assigning a reviewer to it would not mean anything, so the option is not offered.

• Its Review level cannot be set — not on the project's Modules tab, not on a DRP's Review Assignments tab, and not on this page.
• Bulk actions such as "set every module to Module-level" deliberately skip it, so it stays exempt however the rest of the project is configured.
• It is still a normal module in every other way: it appears in the DRP, is included when the DRP is generated, and counts toward the content-completeness check that gates generation.

What the table shows depends on each module's own review level. A Module-level module shows its reviewers, approver and current status. A DRP-level module shows that it is signed off as part of the whole-DRP pass rather than on its own. A module set to Not required shows as such once complete, and an approved module reads simply as Approved.

• If a module shows "In progress", work has started on it but no review round is open — an Analyst or Lead Analyst submits it for review from the module's own page. "Not started" means nothing has been written in it yet.
• If a module shows no reviewers at all, assign them on this DRP's Review Assignments tab, or set them once for every DRP on the project's Modules tab.
• A DRP can't be generated until every required Module-level module here is Approved — DRP-level modules are signed off after generation, so they never block it.
• The table is read-only and updates on its own; only the commentary box beneath it is yours to write.