CHANGE LOG

سجل التغييرات

tasleemat asset PMO-05.04 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.04 ./completed_data.json

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Populate the Change Log based on the project context. Note: This log must output an array of objects matching the flat table headers. -->

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

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

---

## Change Log Entries

| ID | Category | Description | Requestor | Submission Date | Status | Disposition | Cost/Schedule Impact | Type (Mandatory/Discretionary) | Configurable Items Impacted |
| :---: | :--- | :--- | :--- | :---: | :---: | :--- | :--- | :--- | :--- |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |

---

### Sign-off and Approvals

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

Document Reference: PMO-05.04

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

1. What?

A master tracking ledger documenting change requests, review status, CCB approvals, and impact.

2. Why?

Provides full traceability and auditability for project changes and baseline amendments.

3. When?

Maintained continuously throughout the project lifecycle.

4. Who?

Maintained by the Project Manager with oversight from the Change Control Board (CCB).

Tailoring Tips

Track total cumulative cost and schedule variance resulting from all approved changes.
Communicate change dispositions promptly to affected project teams.

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 Log, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

ID: Unique identifier for the change request (e.g., CR-01).
Category: Change category (Scope, Schedule, Cost, Quality, Resource).
Description: Summary description of the proposed change.
Requestor: Name or department submitting the change request.
Submission Date: Date the change request was formally submitted.
Status: Current lifecycle state of the request (Submitted, Under Review, Approved, Rejected).
Disposition: Decision made by the Change Control Board (CCB).
Cost/Schedule Impact: Estimated financial and timeline impact of the change.
Type (Mandatory/Discretionary): Whether the change is legally mandatory or discretionary.
Configurable Items Impacted: Configuration items, baselines, or specifications affected.

6. Reference Example

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

📖 Completed Example: 05_04_Change_Log_Example.md

LLM Generation Prompt & Agent Instructions

Change Log - Generation Prompt

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

Context and Definition: A comprehensive register recording all change requests submitted during the project lifecycle and their disposition.

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)