---

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 (PMO-04.02.05), Schedule (PMO-04.03.08), Cost (PMO-04.04.04)
• Optional / Contextual:
  • Risk Register (PMO-04.08.02)
  • Stakeholder Engagement Plan (PMO-04.10.01)

2. Downstream Dependents

• Mandatory:
  • Project Status Report (PMO-06.01)
  • 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