Cover & Version Control

Professional cover sheet and full version history. Tracks who changed what and when, with reasons for each revision.

AI in this module

How AI suggestions work

The reason for each version is drafted automatically whenever the DRP is generated — the AI compares this version's module content against the previous version's and writes a short, factual summary of what actually changed. You can't generate a new version at all if nothing has changed since the last one — Requio blocks generation outright in that case, rather than the AI ever needing to write a "no changes" reason. This happens as part of generation, not by clicking "Get AI Suggestions" here.

This module uses a stricter, fixed prompt than every other module: it is only ever allowed to describe version numbers, dates, authors, and reasons that genuinely exist in the DRP's real version history — never invented ones. If you click "Get AI Suggestions" directly on this page it follows the same rule, but in practice you'll rarely need to.

Quality checks

What "Check Quality" looks for here

Specific, factual reasons. Vague reasons like "various updates" get flagged — keeps the audit trail actually useful to a reviewer comparing versions.

What it captures

The DRP's cover sheet — title, project, and dates — plus a live revision history table: every generated version, who generated it, and why it changed.

Using this module

Unlike every other module, most of this one is automatic. Each time the DRP is generated as a .docx, a new row is added to the Revision History table with the version number, date, who generated it, and a reason for the change — sourced directly from the DRP's real version records, never a separate copy that can drift out of sync.

  1. 1You don't write the revision history by hand — it's populated automatically every time the DRP is generated.
  2. 2Click "Edit" next to a reason if you want to word it differently — this is the one thing in the table you can change directly.
  3. 3Past rows are never rewritten by a later generation — each version keeps the reason that was true for it at the time.
  4. 4A DRP uploaded as a custom document (rather than generated by Requio) is marked "(custom upload)" and defaults to the reason "Manual upload".

Review and approval — permanently exempt

This module sits outside the review workflow entirely, and always will. It has no review level, no reviewers and no approver, and it never appears as something outstanding on the Review & Approval module, on the DRP-generation gate, or on the version-approval gate.

The reason is that none of its content is independently authored. The revision history is read directly from the DRP's real version records — who generated each version, when, and why. Asking someone to review that would mean reviewing a read-out of what has already happened, and approving it could not change anything.

  • 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.

Review & Approval is the only other permanently exempt module. See the Review & Approval Workflow guide topic for how sign-off works for everything else.

Tips

  • Keep an edited reason short but specific ("added acceptance criteria to REQ-014") — it's what a reviewer sees when comparing versions later.
  • This module needs nothing from you day-to-day; it stays accurate automatically as long as you generate the DRP normally rather than editing version history by hand elsewhere.