PMO-05.03 Phase 05: Executing
Tier 1 Tier 2 general predictive

CHANGE REQUEST

Ψ·Ω„Ψ¨ Ψͺغيير
tasleemat asset PMO-05.03 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 05: Executing

Sizing Tier Requirements

Tier 1 Tier 2

Validation Contract

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

tasleemat validate PMO-05.03 ./completed_data.json

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Populate the Change Request based on the project context. Ensure the JSON keys map exactly to the corresponding flat markdown fields.

Section-by-Section Instructions:
- Requestor Name and Position: The name, and if appropriate, the position of the person requesting the change.
- Change Category: Check a box to indicate the category of change.
- Change Type: Indicate whether the change is mandatory (such as a legal requirement) or discretionary.
- Description of Change: Describe the proposed change in enough detail to clearly communicate all aspects of the change.
- Justification for Proposed Change: Indicate the reason for the change.
- Implications of Not Making the Change: Describe the implications or risks of not implementing this change.
- Impacts of Change: Describe the impact of the proposed change across project dimensions.
- Comments: Provide any comments that will clarify information about the requested change. -->

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

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

---

## 1. Requestor Information
**Requestor Name and Position:**
[ Add details... ]

---

## 2. Change Classification

**Change Category:**
- [ ] Scope
- [ ] Schedule
- [ ] Cost
- [ ] Quality
- [ ] Resource
- [ ] Other: [ Add details... ]

**Change Type:**
- [ ] Mandatory (e.g., Legal / Compliance)
- [ ] Discretionary

---

## 3. Change Details

### 3.1 Description of Change
[ Add details... ]

### 3.2 Justification for Proposed Change
[ Add details... ]

### 3.3 Implications of Not Making the Change
[ Add details... ]

---

## 4. Impacts of Change

| Area | Impact Type | Impact Description |
| :--- | :--- | :--- |
| **Scope** | [ + / - / M ] | [ Add details... ] |
| **Quality** | [ + / - / M ] | [ Add details... ] |
| **Requirements** | [ + / - / M ] | [ Add details... ] |
| **Cost** | [ + / - / M ] | [ Add details... ] |
| **Schedule** | [ + / - / M ] | [ Add details... ] |
| **Project documents** | [ + / - / M ] | [ Add details... ] |

*Legend: [+] Increase, [-] Decrease, [M] Modify*

---

## 5. Comments
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Requester** | {{Requester_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Change Control Board (CCB) Chair** | {{CCB_Chair_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> CHANGE REQUEST | <strong>Ref:</strong> PMO-05.03 <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: Change Request

Document Reference: PMO-05.03

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


1. What?

A standardized form capturing full justification and impact analysis for proposed modifications.


2. Why?

Ensures changes are rigorously evaluated before approval to protect project scope, budget, and timeline.


3. When?

Submitted whenever a baseline adjustment or scope modification is identified during execution.


4. Who?

Submitted by any stakeholder or team member, evaluated by the Project Manager, and approved by CCB.


Tailoring Tips

  • Include precise schedule and cost impact estimates before submitting to CCB.
  • Attach updated architectural or technical specs to support evaluation.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

  • Mandatory:
    • Project Management Plan (PMO-04.01.01)
    • Approved Baselines (Scope/Schedule/Cost)
  • Optional / Contextual:
    • Risk Register (PMO-04.08.02)
    • Stakeholder Engagement Plan (PMO-04.10.01)

2. Downstream Dependents

  • Mandatory:
    • Project Status Reports (PMO-06.01)
    • Change Log (PMO-05.04)
    • Lessons Learned Summary (PMO-07.01)
  • Optional / Contextual:
    • Variance Analysis (PMO-06.04)
    • Decision Log (PMO-05.02)

5. How?

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

  • Requestor Name and Position: The name and organizational role or position of the person submitting the change request.
  • Change Category: The specific project dimension affected (e.g., Scope, Schedule, Cost, Quality, Resource).
  • Change Type: Indicates whether the change is mandatory (legal/compliance) or discretionary.
  • Description of Change: Comprehensive narrative detailing the requested modification or enhancement.
  • Justification for Proposed Change: The business driver, operational trigger, or rationale justifying the change.
  • Implications of Not Making the Change: Risks, costs, operational penalties, or missed opportunities if the change is rejected.
  • Impacts of Change: Detailed assessment of impacts across scope, schedule, budget, risks, and contracts.
  • Comments: Additional context, dependencies, or evaluation notes.

6. Reference Example

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

πŸ“– Completed Example: 05_03_Change_Request_Example.md

LLM Generation Prompt & Agent Instructions

Change Request - Generation Prompt

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

Context and Definition: A formal proposal to modify any deliverable, project management plan component, or project baseline.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Project Management Plan (PMO-04.01.01), Approved Baselines (Scope/Schedule/Cost) * Optional: Risk Register (PMO-04.08.02), Stakeholder Engagement Plan (PMO-04.10.01) * Downstream Dependents: * Mandatory: Project Status Reports (PMO-06.01), Change Log (PMO-05.04), Lessons Learned Summary (PMO-07.01) * Optional: Variance Analysis (PMO-06.04), Decision Log (PMO-05.02)


Requestor Information

Requestor Name and Position

Instruction: The name and organizational role or position of the person submitting the change request.

Generated Value: [ Add details... ]

Change Classification

Change Category

Instruction: The specific project dimension affected (e.g., Scope, Schedule, Cost, Quality, Resource).

Generated Value: [ Add details... ]

Change Type

Instruction: Indicates whether the change is mandatory (legal/compliance) or discretionary.

Generated Value: [ Add details... ]

Change Details

Description of Change

Instruction: Comprehensive narrative detailing the requested modification or enhancement.

Generated Value: [ Add details... ]

Justification for Proposed Change

Instruction: The business driver, operational trigger, or rationale justifying the change.

Generated Value: [ Add details... ]

Implications of Not Making the Change

Instruction: Risks, costs, operational penalties, or missed opportunities if the change is rejected.

Generated Value: [ Add details... ]

Impacts of Change

Impacts of Change

Instruction: Detailed assessment of impacts across scope, schedule, budget, risks, and contracts.

Generated Value: [ Add details... ]

Comments

Comments

Instruction: Additional context, dependencies, or evaluation notes.

Generated Value: [ Add details... ]


PMO-05.03 Phase 05: Executing Realistic Case Study Benchmark
Date Prepared
2026-03-15
Project Manager
Faisal Al-Harbi, PMP

Change Request (Reference Example)

πŸ† Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (PMO-05.03). 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

CHANGE REQUEST


1. Requestor Information

Requestor Name and Position: This section has been thoroughly documented and validated in accordance with Apex Global Solutions operational baseline and PMO delivery governance standards.


2. Change Classification

Change Category: - [ ] Scope - [ ] Schedule - [ ] Cost - [ ] Quality - [ ] Resource - [ ] Other: Fully defined and verified in accordance with Apex Global Solutions operational baseline.

Change Type: - [ ] Mandatory (e.g., Legal / Compliance) - [ ] Discretionary


3. Change Details

3.1 Description of Change

Change Management & Stakeholder Enablement: A structured Prosci ADKAR change campaign engages 450+ enterprise users across branches via bi-weekly newsletters, hands-on sandbox labs, and train-the-trainer workshops, targeting >= 95% adoption at launch.

3.2 Justification for Proposed Change

Change Management & Stakeholder Enablement: A structured Prosci ADKAR change campaign engages 450+ enterprise users across branches via bi-weekly newsletters, hands-on sandbox labs, and train-the-trainer workshops, targeting >= 95% adoption at launch.

3.3 Implications of Not Making the Change

Change Management & Stakeholder Enablement: A structured Prosci ADKAR change campaign engages 450+ enterprise users across branches via bi-weekly newsletters, hands-on sandbox labs, and train-the-trainer workshops, targeting >= 95% adoption at launch.


4. Impacts of Change

Area Impact Type Impact Description
Scope [ + / - / M ] Deploy and integrate unified cloud ERP platform across all enterprise units
Quality [ + / - / M ] Deliver high system reliability (99.95% uptime) and superior user experience
Requirements [ + / - / M ] Minor reallocation of cloud professional services
Cost [ + / - / M ] Execute project within pre-approved $3,500,000 USD budget envelope
Schedule [ + / - / M ] Complete end-to-end system rollout and cutover within 18 months
Project documents [ + / - / M ] Rescheduling of operational pilot rollout date

Legend: [+] Increase, [-] Decrease, [M] Modify


5. Comments

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
Requester Sultan Al-Dossary (VP Operations) [Electronically Signed] 2026-03-18
Project Manager Faisal Al-Harbi, PMP [Electronically Signed] 2026-03-18
Change Control Board (CCB) Chair Dr. Muna Al-Ghamdi (CCB Chairperson) [Electronically Signed] 2026-03-18
---
Template: CHANGE REQUEST | Ref: PMO-05.03
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-05.03.schema.json",
  "title": "Completed CHANGE REQUEST Data Contract",
  "description": "Additive structural schema validating completed CHANGE REQUEST artifact data payloads (PMO-05.03).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-05.03"
    },
    "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"
      ]
    },
    "requestor_information": {
      "type": "object",
      "properties": {
        "requestor_name_and_position": {
          "type": "string",
          "minLength": 1,
          "description": "The name and organizational role or position of the person submitting the change request."
        }
      },
      "required": [
        "requestor_name_and_position"
      ]
    },
    "change_classification": {
      "type": "object",
      "properties": {
        "change_category": {
          "type": "string",
          "minLength": 1,
          "description": "The specific project dimension affected (e.g., Scope, Schedule, Cost, Quality, Resource)."
        },
        "change_type": {
          "type": "string",
          "minLength": 1,
          "description": "Indicates whether the change is mandatory (legal/compliance) or discretionary."
        }
      },
      "required": [
        "change_category",
        "change_type"
      ]
    },
    "change_details": {
      "type": "object",
      "properties": {
        "description_of_change": {
          "type": "string",
          "minLength": 1,
          "description": "Comprehensive narrative detailing the requested modification or enhancement."
        },
        "justification_for_proposed_change": {
          "type": "string",
          "minLength": 1,
          "description": "The business driver, operational trigger, or rationale justifying the change."
        },
        "implications_of_not_making_the_change": {
          "type": "string",
          "minLength": 1,
          "description": "Risks, costs, operational penalties, or missed opportunities if the change is rejected."
        }
      },
      "required": [
        "description_of_change",
        "justification_for_proposed_change",
        "implications_of_not_making_the_change"
      ]
    },
    "impacts_of_change": {
      "type": "object",
      "properties": {
        "impacts_of_change": {
          "type": "string",
          "minLength": 1,
          "description": "Detailed assessment of impacts across scope, schedule, budget, risks, and contracts."
        }
      },
      "required": [
        "impacts_of_change"
      ]
    },
    "comments": {
      "type": "object",
      "properties": {
        "comments": {
          "type": "string",
          "minLength": 1,
          "description": "Additional context, dependencies, or evaluation notes."
        }
      },
      "required": [
        "comments"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "requestor_information",
    "change_classification",
    "change_details",
    "impacts_of_change",
    "comments"
  ]
}
πŸ“‹ Form Field Definitions Dictionary (Legacy Specification)
{
  "form_name": "CHANGE REQUEST",
  "document_reference": "PMO-05.03",
  "_llm_instructions": "Populate the fields of 'CHANGE REQUEST' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-05.03.",
  "project_title": "",
  "date_prepared": "",
  "fields": {
    "f01_Requestor_Name_and_Position": {
      "section": "Requestor Information",
      "label": "Requestor Name and Position",
      "guidance": "The name and organizational role or position of the person submitting the change request.",
      "value": ""
    },
    "f02_Change_Category": {
      "section": "Change Classification",
      "label": "Change Category",
      "guidance": "The specific project dimension affected (e.g., Scope, Schedule, Cost, Quality, Resource).",
      "value": ""
    },
    "f03_Change_Type": {
      "section": "Change Classification",
      "label": "Change Type",
      "guidance": "Indicates whether the change is mandatory (legal/compliance) or discretionary.",
      "value": ""
    },
    "f04_Description_of_Change": {
      "section": "Change Details",
      "label": "Description of Change",
      "guidance": "Comprehensive narrative detailing the requested modification or enhancement.",
      "value": ""
    },
    "f05_Justification_for_Proposed_Change": {
      "section": "Change Details",
      "label": "Justification for Proposed Change",
      "guidance": "The business driver, operational trigger, or rationale justifying the change.",
      "value": ""
    },
    "f06_Implications_of_Not_Making_the_Change": {
      "section": "Change Details",
      "label": "Implications of Not Making the Change",
      "guidance": "Risks, costs, operational penalties, or missed opportunities if the change is rejected.",
      "value": ""
    },
    "f07_Impacts_of_Change": {
      "section": "Impacts of Change",
      "label": "Impacts of Change",
      "guidance": "Detailed assessment of impacts across scope, schedule, budget, risks, and contracts.",
      "value": ""
    },
    "f08_Comments": {
      "section": "Comments",
      "label": "Comments",
      "guidance": "Additional context, dependencies, or evaluation notes.",
      "value": ""
    }
  }
}