DECISION LOG

سجل القرارات

tasleemat asset PMO-05.02 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 05: Executing

Sizing Tier Requirements

Tier 1

Validation Contract

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

tasleemat validate PMO-05.02 ./completed_data.json

Template Markdown (Bilingual)

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

Section-by-Section Instructions:
- Decision Log: Record all project decisions. Include the category, the decision itself, impacts on objectives, affected stakeholders, the responsible party, the date, and any comments (such as alternatives considered or reasoning). -->

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

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

---

## Decision Log Entries

| ID | Category | Decision | Impacts on Deliverables/Objectives | Impacted Stakeholders | Responsible Party | Date | Comments |
| :---: | :--- | :--- | :--- | :--- | :--- | :---: | :--- |
| [ 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 |
| :--- | :--- | :---: | :---: |
| **Decision Maker / PM** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Key Stakeholder Representative** | {{Stakeholder_Representative_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Sponsor** | {{Project_Sponsor_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> DECISION LOG | <strong>Ref:</strong> PMO-05.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: Decision Log

Document Reference: PMO-05.02

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

1. What?

A persistent audit record documenting major decisions made during the project lifecycle.

2. Why?

Prevents relitigating settled decisions and provides clear traceability for project direction and governance.

3. When?

Maintained continuously from kickoff through final delivery.

4. Who?

Documented by the Project Manager in consultation with technical leads and business decision makers.

Tailoring Tips

Include trade-offs and rejected alternatives to explain why the decision was taken.
Link decisions directly to change requests or risk register mitigations.

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 Decision 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 decision (e.g., DEC-01).
Category: Category of the decision (e.g., Scope, Architecture, Vendor, Process).
Decision: The specific decision made and its underlying rationale.
Impacts on Deliverables/Objectives: Anticipated impacts on deliverables, budget, schedule, or architecture.
Impacted Stakeholders: Stakeholders affected by this decision.
Responsible Party: The person or entity responsible for making and enforcing the decision.
Date: The date on which the decision was officially agreed or approved.
Comments: Alternatives considered, trade-offs, and supporting references.

6. Reference Example

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

📖 Completed Example: 05_02_Decision_Log_Example.md

LLM Generation Prompt & Agent Instructions

Decision Log - Generation Prompt

System Instructions: This document contains instructions for generating the «Decision 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 project management artifact that captures key architectural, technical, operational, and managerial decisions.

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)