PMO-04.08.05 Phase 04: Planning

RISK DATA SHEET

ูˆุฑู‚ุฉ ุจูŠุงู†ุงุช ุงู„ู…ุฎุงุทุฑ
tasleemat asset PMO-04.08.05 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 04: Planning

Sizing Tier Requirements

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.05 ./completed_data.json

Template Markdown (Bilingual)

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

Section Instructions:
- Risk Identification and Event Narrative: Provide comprehensive project data for all required fields in this section.
- Qualitative and Quantitative Analysis: Provide comprehensive project data for all required fields in this section.
- Root Cause, Triggers, and Impacts: Provide comprehensive project data for all required fields in this section.
- Detailed Response Strategy and Action Plan: 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 DATA SHEET</h1>

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

---

## 1. Risk Identification and Event Narrative

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

**Risk Statement and Operational Context:**
[ Add details... ]

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

---

## 2. Qualitative and Quantitative Analysis

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

**Expected Monetary Value (EMV) Analysis:**
[ Add details... ]

**Schedule Delay and Critical Path Exposure:**
[ Add details... ]

---

## 3. Root Cause, Triggers, and Impacts

**Root Cause Analysis Details:**
[ Add details... ]

**Early Warning Triggers and Thresholds:**
[ Add details... ]

---

## 4. Detailed Response Strategy and Action Plan

**Primary Mitigation Action Plan:**
[ Add details... ]

**Contingency and Fallback Response Plan:**
[ Add details... ]

**Allocated Contingency Budget and Reserves:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Risk Owner** | {{Risk_Owner_Name}} | _______________________ | [ .... - .... - .... ] |
| **Risk Manager** | {{Risk_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_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 DATA SHEET | <strong>Ref:</strong> PMO-04.08.05 <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 Data Sheet

Document Reference: PMO-04.08.05

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


1. What?

A comprehensive single-risk dossier detailing root causes, triggers, EMV calculations, mitigation steps, and fallback responses.


2. Why?

Provides exhaustive operational and financial analysis to de-risk high-exposure threats to project success.


3. When?

Created when a risk is categorized as High or Critical in qualitative assessment.


4. Who?

Authored by Assigned Risk Owner with input from Lead Engineers and Risk Manager.


Tailoring Tips

  • Mandatory for any risk whose EMV exceeds contingency allocation thresholds.
  • Incorporate detailed technical simulation models for complex architecture and security risks.

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 Data Sheet, 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 Title: Unique identifier code and descriptive title for the specific high-impact risk.
  • Risk Statement and Operational Context: Comprehensive statement articulating cause, condition, and operational impact.
  • Assigned Risk Owner and Stakeholders: Designated risk owner, action lead, and impacted project stakeholders.
  • Assessed Probability and Impact Ratings: Detailed probability rating and impact breakdown across scope, schedule, and cost.
  • Expected Monetary Value (EMV) Analysis: Quantitative calculation of monetary impact (Probability x Financial Consequence).
  • Schedule Delay and Critical Path Exposure: Projected days of delay on critical path activities if the risk occurs.
  • Root Cause Analysis Details: Underlying systemic, technical, or environmental drivers causing the risk.
  • Early Warning Triggers and Thresholds: Identifiable metrics and operational thresholds that trigger risk activation.
  • Primary Mitigation Action Plan: Step-by-step preventive measures, action item owners, and completion deadlines.
  • Contingency and Fallback Response Plan: Secondary action plan implemented if primary mitigation fails or risk materializes.
  • Allocated Contingency Budget and Reserves: Specific financial reserve allocation assigned to execute this risk response.

6. Reference Example

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

๐Ÿ“– Completed Example: 04_08_05_Risk_Data_Sheet_Example.md

LLM Generation Prompt & Agent Instructions

Risk Data Sheet - Generation Prompt

System Instructions: This document contains instructions for generating the ยซRisk Data Sheetยป. When asked to fill this template, follow the section-by-section instructions below. Refer to parameters.md for project variables.

Context and Definition: A deep-dive analytical document prepared for major or high-exposure project risks requiring comprehensive individual analysis, quantitative modeling, and dedicated action plans.

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)


Risk Identification and Event Narrative

Risk Identifier and Title

Instruction: Unique identifier code and descriptive title for the specific high-impact risk.

Generated Value: [ Add details... ]

Risk Statement and Operational Context

Instruction: Comprehensive statement articulating cause, condition, and operational impact.

Generated Value: [ Add details... ]

Assigned Risk Owner and Stakeholders

Instruction: Designated risk owner, action lead, and impacted project stakeholders.

Generated Value: [ Add details... ]

Qualitative and Quantitative Analysis

Assessed Probability and Impact Ratings

Instruction: Detailed probability rating and impact breakdown across scope, schedule, and cost.

Generated Value: [ Add details... ]

Expected Monetary Value (EMV) Analysis

Instruction: Quantitative calculation of monetary impact (Probability x Financial Consequence).

Generated Value: [ Add details... ]

Schedule Delay and Critical Path Exposure

Instruction: Projected days of delay on critical path activities if the risk occurs.

Generated Value: [ Add details... ]

Root Cause, Triggers, and Impacts

Root Cause Analysis Details

Instruction: Underlying systemic, technical, or environmental drivers causing the risk.

Generated Value: [ Add details... ]

Early Warning Triggers and Thresholds

Instruction: Identifiable metrics and operational thresholds that trigger risk activation.

Generated Value: [ Add details... ]

Detailed Response Strategy and Action Plan

Primary Mitigation Action Plan

Instruction: Step-by-step preventive measures, action item owners, and completion deadlines.

Generated Value: [ Add details... ]

Contingency and Fallback Response Plan

Instruction: Secondary action plan implemented if primary mitigation fails or risk materializes.

Generated Value: [ Add details... ]

Allocated Contingency Budget and Reserves

Instruction: Specific financial reserve allocation assigned to execute this risk response.

Generated Value: [ Add details... ]


PMO-04.08.05 Phase 04: Planning Realistic Case Study Benchmark
Date Prepared
2026-03-15
Project Manager
Faisal Al-Harbi, PMP
Prepared By
Faisal Al-Harbi, PMP (Senior Project Manager)

Risk Data Sheet (Reference Example)

๐Ÿ† Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (PMO-04.08). All company names, project references, and figures are realistic fictional simulations.


Apex Global Solutions

Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01

RISK DATA SHEET


1. Risk Identification and Event Narrative

Risk Identifier and Title: Overall Project Risk Assessment: Overall risk is classified as 'Moderate-High' due to multi-system integration complexity and cross-departmental change impact. Key mitigation actions include dedicated middleware squads, a phased regional rollout strategy (Pilot first), a 10% contingency management reserve, and active weekly risk reviews with the executive steering board.

Risk Statement and Operational Context: Overall Project Risk Assessment: Overall risk is classified as 'Moderate-High' due to multi-system integration complexity and cross-departmental change impact. Key mitigation actions include dedicated middleware squads, a phased regional rollout strategy (Pilot first), a 10% contingency management reserve, and active weekly risk reviews with the executive steering board.

Assigned Risk Owner and Stakeholders: Overall Project Risk Assessment: Overall risk is classified as 'Moderate-High' due to multi-system integration complexity and cross-departmental change impact. Key mitigation actions include dedicated middleware squads, a phased regional rollout strategy (Pilot first), a 10% contingency management reserve, and active weekly risk reviews with the executive steering board.


2. Qualitative and Quantitative Analysis

Assessed Probability and Impact Ratings: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.

Expected Monetary Value (EMV) Analysis: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.

Schedule Delay and Critical Path Exposure: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.


3. Root Cause, Triggers, and Impacts

Root Cause Analysis Details: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.

Early Warning Triggers and Thresholds: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.


4. Detailed Response Strategy and Action Plan

Primary Mitigation Action Plan: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.

Contingency and Fallback Response Plan: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.

Allocated Contingency Budget and Reserves: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.


Sign-off and Approvals

Role Name Signature Date
Risk Owner Faisal Al-Harbi, PMP [Electronically Signed] 2026-03-18
Risk Manager Layla Al-Omari, PMI-RMP [Electronically Signed] 2026-03-18
Project Manager Faisal Al-Harbi, PMP [Electronically Signed] 2026-03-18
---
Template: RISK DATA SHEET | Ref: PMO-04.08.05
Generated on: 2026-03-15 10:00 UTC, by Tasleemat

Draft 2020-12 JSON Schema

Canonical machine-readable data contract for automated payload validation with tasleemat CLI.
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-04.08.05.schema.json",
  "title": "Completed RISK DATA SHEET Data Contract",
  "description": "Additive structural schema validating completed RISK DATA SHEET artifact data payloads (PMO-04.08.05).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-04.08.05"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "risk_identification_and_event_narrative": {
      "type": "object",
      "properties": {
        "risk_identifier_and_title": {
          "type": "string",
          "minLength": 1,
          "description": "Unique identifier code and descriptive title for the specific high-impact risk."
        },
        "risk_statement_and_operational_context": {
          "type": "string",
          "minLength": 1,
          "description": "Comprehensive statement articulating cause, condition, and operational impact."
        },
        "assigned_risk_owner_and_stakeholders": {
          "type": "string",
          "minLength": 1,
          "description": "Designated risk owner, action lead, and impacted project stakeholders."
        }
      },
      "required": [
        "risk_identifier_and_title",
        "risk_statement_and_operational_context",
        "assigned_risk_owner_and_stakeholders"
      ]
    },
    "qualitative_and_quantitative_analysis": {
      "type": "object",
      "properties": {
        "assessed_probability_and_impact_ratings": {
          "type": "string",
          "minLength": 1,
          "description": "Detailed probability rating and impact breakdown across scope, schedule, and cost."
        },
        "expected_monetary_value_emv_analysis": {
          "type": "string",
          "minLength": 1,
          "description": "Quantitative calculation of monetary impact (Probability x Financial Consequence)."
        },
        "schedule_delay_and_critical_path_exposure": {
          "type": "string",
          "minLength": 1,
          "description": "Projected days of delay on critical path activities if the risk occurs."
        }
      },
      "required": [
        "assessed_probability_and_impact_ratings",
        "expected_monetary_value_emv_analysis",
        "schedule_delay_and_critical_path_exposure"
      ]
    },
    "root_cause_triggers_and_impacts": {
      "type": "object",
      "properties": {
        "root_cause_analysis_details": {
          "type": "string",
          "minLength": 1,
          "description": "Underlying systemic, technical, or environmental drivers causing the risk."
        },
        "early_warning_triggers_and_thresholds": {
          "type": "string",
          "minLength": 1,
          "description": "Identifiable metrics and operational thresholds that trigger risk activation."
        }
      },
      "required": [
        "root_cause_analysis_details",
        "early_warning_triggers_and_thresholds"
      ]
    },
    "detailed_response_strategy_and_action_plan": {
      "type": "object",
      "properties": {
        "primary_mitigation_action_plan": {
          "type": "string",
          "minLength": 1,
          "description": "Step-by-step preventive measures, action item owners, and completion deadlines."
        },
        "contingency_and_fallback_response_plan": {
          "type": "string",
          "minLength": 1,
          "description": "Secondary action plan implemented if primary mitigation fails or risk materializes."
        },
        "allocated_contingency_budget_and_reserves": {
          "type": "string",
          "minLength": 1,
          "description": "Specific financial reserve allocation assigned to execute this risk response."
        }
      },
      "required": [
        "primary_mitigation_action_plan",
        "contingency_and_fallback_response_plan",
        "allocated_contingency_budget_and_reserves"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "risk_identification_and_event_narrative",
    "qualitative_and_quantitative_analysis",
    "root_cause_triggers_and_impacts",
    "detailed_response_strategy_and_action_plan"
  ]
}
๐Ÿ“‹ Form Field Definitions Dictionary (Legacy Specification)
{
  "form_name": "RISK DATA SHEET",
  "document_reference": "PMO-04.08.05",
  "_llm_instructions": "Populate the fields of 'RISK DATA SHEET' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.08.05.",
  "project_title": "",
  "date_prepared": "",
  "fields": {
    "f01_Risk_Identifier_and_Title": {
      "section": "Risk Identification and Event Narrative",
      "label": "Risk Identifier and Title",
      "guidance": "Unique identifier code and descriptive title for the specific high-impact risk.",
      "value": ""
    },
    "f02_Risk_Statement_and_Operational_Context": {
      "section": "Risk Identification and Event Narrative",
      "label": "Risk Statement and Operational Context",
      "guidance": "Comprehensive statement articulating cause, condition, and operational impact.",
      "value": ""
    },
    "f03_Assigned_Risk_Owner_and_Stakeholders": {
      "section": "Risk Identification and Event Narrative",
      "label": "Assigned Risk Owner and Stakeholders",
      "guidance": "Designated risk owner, action lead, and impacted project stakeholders.",
      "value": ""
    },
    "f04_Assessed_Probability_and_Impact_Ratings": {
      "section": "Qualitative and Quantitative Analysis",
      "label": "Assessed Probability and Impact Ratings",
      "guidance": "Detailed probability rating and impact breakdown across scope, schedule, and cost.",
      "value": ""
    },
    "f05_Expected_Monetary_Value_EMV_Analysis": {
      "section": "Qualitative and Quantitative Analysis",
      "label": "Expected Monetary Value (EMV) Analysis",
      "guidance": "Quantitative calculation of monetary impact (Probability x Financial Consequence).",
      "value": ""
    },
    "f06_Schedule_Delay_and_Critical_Path_Exposure": {
      "section": "Qualitative and Quantitative Analysis",
      "label": "Schedule Delay and Critical Path Exposure",
      "guidance": "Projected days of delay on critical path activities if the risk occurs.",
      "value": ""
    },
    "f07_Root_Cause_Analysis_Details": {
      "section": "Root Cause, Triggers, and Impacts",
      "label": "Root Cause Analysis Details",
      "guidance": "Underlying systemic, technical, or environmental drivers causing the risk.",
      "value": ""
    },
    "f08_Early_Warning_Triggers_and_Thresholds": {
      "section": "Root Cause, Triggers, and Impacts",
      "label": "Early Warning Triggers and Thresholds",
      "guidance": "Identifiable metrics and operational thresholds that trigger risk activation.",
      "value": ""
    },
    "f09_Primary_Mitigation_Action_Plan": {
      "section": "Detailed Response Strategy and Action Plan",
      "label": "Primary Mitigation Action Plan",
      "guidance": "Step-by-step preventive measures, action item owners, and completion deadlines.",
      "value": ""
    },
    "f10_Contingency_and_Fallback_Response_Plan": {
      "section": "Detailed Response Strategy and Action Plan",
      "label": "Contingency and Fallback Response Plan",
      "guidance": "Secondary action plan implemented if primary mitigation fails or risk materializes.",
      "value": ""
    },
    "f11_Allocated_Contingency_Budget_and_Reserves": {
      "section": "Detailed Response Strategy and Action Plan",
      "label": "Allocated Contingency Budget and Reserves",
      "guidance": "Specific financial reserve allocation assigned to execute this risk response.",
      "value": ""
    }
  }
}