Generate Comprehensive Risk Register Templates

This skill builds comprehensive risk registers and risk-management frameworks, aligned to ISO 31000, PMI, and PRINCE2, that capture, assess, and track risks through a project lifecycle. The essential-fields structure covers Risk ID, Risk Title, Risk Description, Risk Category, Risk Owner, Probability (1-5 or percentage), Impact (1-5 or monetary), Risk Score (Probability times Impact), Response Strategy (Avoid, Mitigate, Transfer, or Accept), Action Plan, Target Date, Current Status, and Review Date. A standard risk-categorization framework organizes coded risks across five categories - Technical (T01-T04: technology obsolescence, integration complexity, performance, security), Operational (O01-O04), Financial (F01-F04), Regulatory (R01-R04), and External (E01-E04).

The Excel template structure defines a 15-column layout (Risk_ID through Comments) with dropdown validation for category, response strategy, and status, plus formula-driven fields:

Days Until Review:
=IF(N2="","",N2-TODAY())

Risk Age (Days):
=IF(M2="Closed","",TODAY()-[Creation_Date])

Action Overdue:
=IF(AND(L2<TODAY(),M2<>"Closed"),"OVERDUE","On Track")

Risk level is derived from score via conditional formatting (1-4 green/Low, 5-12 yellow/Medium, 15-25 red/High) mapped onto a 5x5 probability-impact grid. Industry-specific customization guidance covers IT projects (system dependencies, data migration, cybersecurity), construction (weather, safety, permits, materials), healthcare (patient safety, regulatory compliance, data privacy), and financial services (market, credit, operational, reputational risk). Stakeholder communication is tailored by audience - an executive dashboard (high-risk items scored 15+, trend charts, top-10 risks, overdue-actions summary), a project-manager view (all active risks, action plans, owner assignments, status), and a risk-committee report (heat map, new/closed risks, risk-appetite compliance). Review cycles are risk-scaled - weekly for high risks, bi-weekly for medium, monthly for low, quarterly verification for closed - with an automatic-review-date formula adding 7, 14, or 30 days by risk level. Best practices call for specific measurable risk descriptions (avoiding vague terms like "may cause issues"), single-person accountability rather than team ownership, and defined closure criteria, while flagging anti-patterns like "zombie risks" left open indefinitely and generic descriptions reused across projects.

Use it when building or maintaining a project risk register - defining fields and categories, setting up the Excel formulas and conditional formatting, tailoring stakeholder views, or setting review cadences. It is not a general project-status or issue-tracking template - it is scoped specifically to structured risk identification, scoring, and tracking.

Given a project and its risk landscape, it produces a structured risk-register field set, a categorized risk taxonomy, an Excel template with scoring formulas and conditional formatting, and stakeholder-specific reporting views.

Designed for Excel (formula-driven Risk_Score, Risk_Level, and overdue tracking) and for SharePoint list integration (a Choice field for risk category and a Calculated field computing [Probability]*[Impact]).

Project managers, PMOs, and risk owners building and maintaining a structured risk register across a project lifecycle.