ForceVue

Risk Register

Record delivery risks and stated expectations in a structured form, then generate a register that keeps the gap between expectations and support visible.

A Risk Register makes the gap between what leadership expects and what delivery can support visible, with the receipts attached. It works in two steps: you record risks and expectations as structured context, then ForceVue generates the register from what is actually recorded.

Record an entry

  1. Open an initiative and go to the Context tab.
  2. Click Add Context and pick the Risk label.
  3. The content is pre-filled with a short skeleton. Fill in each field:
    • Risk, the statement itself.
    • Impact, what it puts at stake.
    • Likelihood, as it was stated by whoever raised it.
    • Mitigation, what would reduce the risk, or what is being asked of leadership.
    • Revisit trigger, the signal that would warrant reopening it.
  4. Save. Owner and date are recorded automatically.

The owner and date are recorded automatically from who added the entry and when, never typed by hand. See Context items for the full label list.

You can also record a risk from chat: in an initiative-scoped Ask ForceVue conversation, say "Record a risk: ..." and confirm the proposed context item. The saved entry works exactly like one added from the Context tab.

Recorded, never forecast

The register keeps likelihood and confidence in the words they were stated in. ForceVue does not turn them into probabilities and does not predict outcomes. What you see is what was said, plus where it came from.

Generate the register

  1. Open the initiative and click Generate Document.
  2. Choose Risk Register.
  3. Click Generate.

ForceVue synthesises the initiative's recorded risk entries, decisions, goals, and context into five sections:

  • Summary, what the register covers and who relies on it.
  • Register Index, one line per entry: the entry's short title, date, owner, and stated likelihood.
  • Risks and Expectations, each entry expanded with its impact, mitigation or ask, and revisit trigger, naming the context item it draws from.
  • Evidence and KPIs, the delivery and operational signals from your goals and context that bear on the entries.
  • Revisit Watchlist, every revisit trigger gathered into one list.

The register only writes what your context supports. An initiative with no recorded entries gets a summary that says so, not invented risks. Generation spends one generation from your monthly quota, like any other document. See Generating documents.

Trace every entry

The generated register carries the Generation Sources panel at the top. Open Show Details to see exactly which entries, decisions, goals, and documents informed it, and click any source to preview the passage inline. See How generation works.

Export and share

The register exports like any other document: Export in the document header offers Export as Markdown and Export as PDF, and the PDF carries your workspace branding. See Exporting documents.

Where to go next

  • Context items to record risks and expectations.
  • Goals to add the delivery signals the register cites as evidence.
  • Document templates to adjust the register's sections for your workspace.