ASSUMPTION LOG

سجل الافتراضات

tasleemat asset PMO-03.03 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 03: Initiating

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

Template Markdown (Bilingual)

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

Section Instructions:
*   **ID:** Unique identifier for the assumption or constraint.
*   **Type:** Specify whether this entry is an "Assumption" or a "Constraint".
*   **Category:** The category of the assumption or constraint (e.g., Technical, Financial, Schedule, Resource).
*   **Description:** A clear, detailed description of the assumption or constraint.
*   **Impact if invalid:** The potential risk or impact to the project (e.g., cost, schedule, scope) if the assumption proves false or the constraint is breached.
*   **Responsible party:** The person who is tasked with following up on the assumption to validate if it is true or not.
*   **Due date:** The date by which the assumption needs to be validated.
*   **Actions:** Specific actions that need to be taken to validate the assumption or monitor the constraint.
*   **Status:** The current status of the assumption (e.g., active, transferred, or closed).
*   **Comments:** Any additional information, context, or updates.
-->

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

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

---

## Assumption Log Entries
<!-- 
Please provide a comprehensive log of all assumptions and constraints for the project. For each entry, ensure you populate the following columns in the table below:
- **ID:** Unique identifier for the assumption or constraint.
- **Type:** Specify whether this entry is an "Assumption" or a "Constraint".
- **Category:** The category of the assumption or constraint (e.g., Technical, Financial, Schedule, Resource).
- **Description:** A clear, detailed description of the assumption or constraint.
- **Impact if invalid:** The potential risk or impact to the project (e.g., cost, schedule, scope) if the assumption proves false or the constraint is breached.
- **Responsible party:** The person who is tasked with following up on the assumption to validate if it is true or not.
- **Due date:** The date by which the assumption needs to be validated.
- **Actions:** Specific actions that need to be taken to validate the assumption or monitor the constraint.
- **Status:** The current status of the assumption (e.g., active, transferred, or closed).
- **Comments:** Any additional information, context, or updates.
-->
| ID | Type | Category | Description | Impact if invalid | Responsible party | Due date | Actions | Status | 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... ] | [ 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}} | _______________________ | [ .... - .... - .... ] |
| **PMO Lead** | {{PMO_Lead_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> ASSUMPTION LOG | <strong>Ref:</strong> PMO-03.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: Assumption Log

Document Reference: PMO-03.03

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

1. What?

A dedicated register capturing all operational, technical, and environmental assumptions and constraints.

2. Why?

Unverified assumptions and untracked constraints are leading causes of project risk and schedule slippage.

3. When?

Initiated during project initiation and continuously updated through execution and monitoring.

4. Who?

Maintained by the Project Manager with input from the project team and stakeholders.

Tailoring Tips

Review and validate assumptions at every milestone gate.
Convert invalid assumptions immediately into risk register entries or issue log items.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Project Charter (PMO-03.01)
- Business Case (PMO-01.01)
Optional / Contextual:
- Feasibility Studies
- Contractual SOW (PMO-04.09.04)

2. Downstream Dependents

Mandatory:
- Risk Register (PMO-04.08.02)
- Project Scope Statement (PMO-04.02.05)
- Cost Estimates (PMO-04.04.02)
Optional / Contextual:
- Duration Estimates (PMO-04.03.06)
- Decision Log (PMO-05.02)

5. How?

To accurately and professionally complete the Assumption 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 assumption or constraint entry.
Type: Specify whether this entry is an 'Assumption' or a 'Constraint'.
Category: The category of the assumption or constraint (e.g., Technical, Financial, Schedule, Resource).
Description: A clear, detailed description of the assumption or constraint.
Impact if invalid: The potential risk or impact to the project if the assumption proves false or the constraint is breached.
Responsible party: The person or role tasked with following up on the assumption to validate its accuracy.
Due date: The target date by which the assumption needs to be validated or reviewed.
Actions: Specific actions required to validate the assumption or monitor the constraint.
Status: The current status of the assumption (e.g., active, validated, closed).
Comments: Any additional information, operational context, or status updates.

6. Reference Example

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

📖 Completed Example: 03_03_Assumption_Log_Example.md

LLM Generation Prompt & Agent Instructions

Assumption Log - Generation Prompt

System Instructions: This document contains instructions for generating the «Assumption 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 document used to record all assumptions and constraints throughout the project lifecycle.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Project Charter (PMO-03.01), Business Case (PMO-01.01) * Optional: Feasibility Studies, Contractual SOW (PMO-04.09.04) * Downstream Dependents: * Mandatory: Risk Register (PMO-04.08.02), Project Scope Statement (PMO-04.02.05), Cost Estimates (PMO-04.04.02) * Optional: Duration Estimates (PMO-04.03.06), Decision Log (PMO-05.02)