PROJECT STATUS REPORT

تقرير حالة المشروع

tasleemat asset PMO-06.01 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 06: Monitoring and Controlling

Sizing Tier Requirements

Tier 1 Tier 2 Tier 3

Validation Contract

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

tasleemat validate PMO-06.01 ./completed_data.json

Template Markdown (Bilingual)

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

Section-by-Section Instructions:
- Report Information: Provide the reporting period dates, the name of the project manager preparing the document, and the sponsor name.
- Schedule Performance (Current Period): List accomplishments, incomplete work, root causes of schedule variances, impacts to milestones, and corrective actions.
- Cost Performance (Current Period): Detail funds spent, root causes of cost variances, impacts to the overall budget, and corrective actions.
- Planning for Next Period: Outline the accomplishments and costs planned for the upcoming reporting period.
- Risks, Issues, and Escalations: Log new risks, issues, and any matters requiring escalation to sponsors or program managers.
- Project Knowledge and Decisions: Document decisions made, summarize change requests, and record lessons learned for organizational knowledge transfer.
- Comments: Document any comments that add relevance to this report. -->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">PROJECT STATUS REPORT</h1>

| **Date Prepared:** {{Current_Date}} | **Reporting Period:** [ Reporting Period Start Date ] to [ Reporting Period End Date ] |
| :--- | :--- |
| **Project Manager:** [ Prepared By (Project Manager) ] | **Sponsor:** [ Sponsor Name ] |

---

## 1. Schedule Performance (Current Period)

**Accomplishments for this reporting period:**
1. [ Add details... ]
2. [ Add details... ]
3. [ Add details... ]

**Accomplishments planned but not completed this reporting period:**
1. [ Add details... ]
2. [ Add details... ]
3. [ Add details... ]

**Root cause of schedule variances:**
[ Add details... ]

**Impact to upcoming milestones or project due date:**
[ Add details... ]

**Planned corrective or preventive action (Schedule):**
[ Add details... ]

---

## 2. Cost Performance (Current Period)

**Funds spent this reporting period:**
[ Add details... ]

**Root cause of cost variances:**
[ Add details... ]

**Impact to overall budget or contingency funds:**
[ Add details... ]

**Planned corrective or preventive action (Cost):**
[ Add details... ]

---

## 3. Planning for Next Period

**Accomplishments planned for next reporting period:**
1. [ Add details... ]
2. [ Add details... ]
3. [ Add details... ]

**Costs planned for next reporting period:**
[ Add details... ]

---

## 4. Risks, Issues, and Escalations

**New risks identified:**
[ Add details... ]

**New issues identified:**
[ Add details... ]

**Escalations:**
[ Add details... ]

---

## 5. Project Knowledge and Decisions

**Decisions made:**
[ Add details... ]

**Change requests submitted this period:**
[ Add details... ]

**Lessons learned and knowledge transfer:**
[ Add details... ]

---

## 6. Comments
[ 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> PROJECT STATUS REPORT | <strong>Ref:</strong> PMO-06.01 <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: Project Status Report

Document Reference: PMO-06.01

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

1. What?

A formal executive artifact presenting regular performance metrics, milestones, risks, and forecasts across the project.

2. Why?

Enables executive sponsors and PMO leaders to make informed governance decisions and authorize necessary interventions.

3. When?

Prepared on a recurring cycle (weekly or monthly) throughout executing, monitoring, and controlling phases.

4. Who?

Authored by the Project Manager and distributed to Project Sponsors, PMO Director, and Steering Committees.

Tailoring Tips

Adjust reporting frequency and level of detail based on project scale, risk rating, and stakeholder governance needs.
Emphasize variance root causes and corrective action plans rather than raw descriptive status.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Approved Project Baselines (PMO-04.01.01)
- Work Performance Data & Logs (PMO-05.01 - 05.12)
Optional / Contextual:
- Risk Register (PMO-04.08.02)
- Vendor Agreements (PMO-04.09.04)

2. Downstream Dependents

Mandatory:
- Change Requests (PMO-05.03)
- Project / Phase Closeout (PMO-07.03)
- Lessons Learned Summary (PMO-07.01)
Optional / Contextual:
- Transition to Operations Checklist (PMO-07.04)
- Value Realization Register (PMO-01.03)

5. How?

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

Accomplishments for this reporting period: Key milestones, deliverables, and tasks completed during this period.
Accomplishments planned but not completed this reporting period: Activities that were scheduled for completion but remain in progress or delayed.
Root cause of schedule variances: Underlying causes and contributing factors for any schedule delays or slippages.
Impact to upcoming milestones or project due date: Expected effects of current schedule performance on future critical path milestones.
Planned corrective or preventive action (Schedule): Specific recovery actions planned to bring the schedule back in alignment with baseline.
Funds spent this reporting period: Total expenditures and actual costs incurred during the current reporting period.
Root cause of cost variances: Reasons for any cost overruns or underruns compared against the cost baseline.
Impact to overall budget or contingency funds: Projected impact of current spending trends on total project budget and reserves.
Planned corrective or preventive action (Cost): Corrective steps designed to control project expenditure within approved budget limits.
Accomplishments planned for next reporting period: Key objectives, tasks, and deliverables scheduled for execution in the next cycle.
Costs planned for next reporting period: Anticipated financial expenditures and commitments for the upcoming period.
New risks identified: Newly discovered risks requiring qualitative or quantitative analysis and response planning.
New issues identified: Newly materialized issues requiring immediate tracking and resolution.
Escalations: Matters requiring immediate intervention or decision-making from executive sponsors.
Decisions made: Significant architectural, operational, or management decisions ratified during this period.
Change requests submitted this period: Summary of formal change requests submitted, evaluated, or approved this period.
Lessons learned and knowledge transfer: Insights and practical lessons captured to enhance ongoing and future project performance.
Comments: Additional explanatory notes, contextual remarks, or qualitative updates.

6. Reference Example

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

📖 Completed Example: 06_01_Project_Status_Report_Example.md

LLM Generation Prompt & Agent Instructions

Project Status Report - Generation Prompt

System Instructions: This document contains instructions for generating the «Project Status Report». 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 periodic report conveying project health, progress against baselines, variances, upcoming plans, and critical issues.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Approved Project Baselines (PMO-04.01.01), Work Performance Data & Logs (PMO-05.01 - 05.12) * Optional: Risk Register (PMO-04.08.02), Vendor Agreements (PMO-04.09.04) * Downstream Dependents: * Mandatory: Change Requests (PMO-05.03), Project / Phase Closeout (PMO-07.03), Lessons Learned Summary (PMO-07.01) * Optional: Transition to Operations Checklist (PMO-07.04), Value Realization Register (PMO-01.03)