RISK REGISTER

سجل المخاطر

tasleemat asset PMO-04.08.02 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 04: Planning

Sizing Tier Requirements

Tier 1 Tier 2 Tier 3

Validation Contract

This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.

tasleemat validate PMO-04.08.02 ./completed_data.json

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.

Section Instructions:
- Identified Risk Details: Provide comprehensive project data for all required fields in this section.
- Risk Analysis and Exposure Rating: Provide comprehensive project data for all required fields in this section.
- Planned Risk Response and Owner: Provide comprehensive project data for all required fields in this section.
-->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">RISK REGISTER</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |

---

## 1. Identified Risk Details

**Risk Identifier and Category:**
[ Add details... ]

**Risk Event Narrative and Root Cause:**
[ Add details... ]

**Risk Trigger and Symptoms:**
[ Add details... ]

---

## 2. Risk Analysis and Exposure Rating

**Assessed Probability and Impact Scores:**
[ Add details... ]

**Calculated Risk Exposure Rating:**
[ Add details... ]

---

## 3. Planned Risk Response and Owner

**Risk Response Strategy:**
[ Add details... ]

**Action Plan and Contingency Plan:**
[ Add details... ]

**Assigned Risk Owner and Status:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Risk Manager / Officer** | {{Risk_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **PMO Lead** | {{PMO_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> RISK REGISTER | <strong>Ref:</strong> PMO-04.08.02 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

User Guide & Practitioner Instructions

Tasleemat Forms Guide

Project Artifact: Risk Register

Document Reference: PMO-04.08.02

This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Risk Register in alignment with the Tasleemat framework.

1. What?

A master log recording risk IDs, descriptions, triggers, probabilities, impacts, exposure, and response actions.

2. Why?

Provides a single source of truth for managing uncertainties and tracking mitigation actions across the project.

3. When?

Initiated in planning and continuously updated throughout project execution and closing.

4. Who?

Maintained by Risk Manager and Project Manager, actions executed by Risk Owners.

Tailoring Tips

Integrate as a prioritized risk backlog within agile standups and sprint planning.
Include quantitative monetary impact valuations for formal commercial contracts.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Project Charter (PMO-03.01)
- Assumption Log (PMO-03.03)
- Project Baselines (Scope/Schedule/Cost)
Optional / Contextual:
- AI Governance Plan (PMO-02.02)
- Procurement Strategy (PMO-04.09.02)

2. Downstream Dependents

Mandatory:
- Risk Register (PMO-04.08.02)
- Risk Reports (PMO-04.08.06)
- Risk Audits (PMO-06.06)
Optional / Contextual:
- Risk Mitigation Action Plan (PMO-04.08.07)
- Decision Log (PMO-05.02)

5. How?

To accurately and professionally complete the Risk Register, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

Risk Identifier and Category: Unique risk tracking code (e.g., RSK-01) and assigned RBS category.
Risk Event Narrative and Root Cause: Clear risk statement describing event cause, uncertain occurrence, and potential outcome.
Risk Trigger and Symptoms: Observable early warning signs and conditions indicating risk materialization.
Assessed Probability and Impact Scores: Quantitative probability rating and multidimensional impact score.
Calculated Risk Exposure Rating: Composite risk severity score (Probability x Impact) and overall priority ranking.
Risk Response Strategy: Selected treatment strategy (Avoid, Mitigate, Transfer, Accept, Exploit, Enhance, Share).
Action Plan and Contingency Plan: Specific preventive mitigation steps and secondary fallback contingency plan.
Assigned Risk Owner and Status: Designated individual accountable for managing the risk and current lifecycle status.

6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

📖 Completed Example: 04_08_02_Risk_Register_Example.md

LLM Generation Prompt & Agent Instructions

Risk Register - Generation Prompt

System Instructions: This document contains instructions for generating the «Risk Register». When asked to fill this template, follow the section-by-section instructions below. Refer to parameters.md for project variables.

Context and Definition: A central project repository capturing identified individual project risks, analysis results, response strategies, and assigned risk owners.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Project Charter (PMO-03.01), Assumption Log (PMO-03.03), Project Baselines (Scope/Schedule/Cost) * Optional: AI Governance Plan (PMO-02.02), Procurement Strategy (PMO-04.09.02) * Downstream Dependents: * Mandatory: Risk Register (PMO-04.08.02), Risk Reports (PMO-04.08.06), Risk Audits (PMO-06.06) * Optional: Risk Mitigation Action Plan (PMO-04.08.07), Decision Log (PMO-05.02)