IT Project Weekly Status Report Template

Standard Operating Procedure: IT Project Weekly Status Report Generation & Distribution

Document ID: SOP-TR-PM-042
Effective Date: October 24, 2023
Version: 3.1.0
Review Cadence: Semi-Annual
Author: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional requirements for authoring, validating, and distributing IT Project Weekly Status Reports across all engineering and infrastructure divisions at Template Registry. The purpose of this procedure is to eliminate variance in project tracking, enforce objective metric reporting, surface systemic bottlenecks to executive stakeholders, and maintain an immutable audit trail of project health indicators.

---

2. Scope & Prerequisites

2.1 Scope

This SOP applies to all Project Managers (PMs), Scrum Masters, Tech Leads, and Engineering Directors responsible for delivering software, infrastructure, and architectural initiatives within Template Registry.

2.2 Prerequisites & Tooling Access

• Jira Data Center / Cloud: Administrative or Project Lead access for metric extraction.
• Confluence Enterprise: Designated repository for published reports.
• Microsoft Power BI: Access to the Template Registry Executive Portfolio Dashboard.
• Corporate Enterprise Mail System: Access to designated distribution lists.
• Hardware: Standard corporate workstation with verified VPN connectivity.

---

3. Roles & Responsibilities (RACI Matrix)

• Responsible (R): Drafts, verifies, and publishes the weekly status report.
• Accountable (A): Reviews and signs off on project health indicators and variance justifications.
• Consulted (C): Provides technical blockers, velocity metrics, and scope adjustments.
• Informed (I): Receives finalized status report notifications.

---

4. Step-by-Step Procedure

Phase 1: Data Extraction and Metric Compilation

• Access Jira and navigate to the target project workspace.
• Export completed story points, opened/closed defects, and current sprint burndown metrics for the active reporting period (Monday 00:00 to Friday 17:00 UTC).
• Query the CI/CD pipeline telemetry (GitLab/GitHub Actions) to record deployment frequency, change failure rate, and mean time to recovery (MTTR).
• Cross-reference financial tracking logs in the Enterprise Resource Planning (ERP) system to capture actual versus budgeted capital/operational expenditures (CapEx/OpEx).

Phase 2: Report Drafting & Health Assessment

• Open the standardized Confluence Weekly Status Report template (TR-SOP-042-TPL).
• Populate the Executive Summary section using a maximum of three concise sentences detailing overall progress, major milestones achieved, and critical path items.
• Assign an objective Traffic Light Health Indicator (Green, Amber, Red) based on the following strict criteria:
  • Green: On schedule, within budget ($\pm 5%$), zero critical blockers.
  • Amber: Minor schedule slippage ($< 10%$), budget variance ($5% - 15%$), manageable blockers with mitigation plans.
  • Red: Major schedule slippage ($\ge 10%$), budget overrun ($> 15%$), unmitigated critical path blockers, or security/compliance breaches.
• Complete the Milestone Tracking Table indicating baseline dates, forecasted dates, and variance status.

Phase 3: Risk, Issue, and Action Item (RIA) Documentation

• Update the Risk Register log, ensuring every active risk has a calculated Risk Exposure Score (Probability $\times$ Impact) and a designated owner.
• Document all active blockers (Issues) requiring intervention outside the project team's direct authority, including the date identified and escalation path.
• Review pending Action Items from the previous reporting cycle; close completed items and rollover uncompleted items with updated due dates and root-cause annotations.

Phase 4: Quality Assurance & Executive Review

• Execute the internal validation check: verify that all numerical metrics match underlying Jira and ERP data sources.
• Submit the draft report to the Engineering Director for review no later than Fridays at 14:00 UTC.
• Incorporate required adjustments resulting from the Engineering Director's review.

Phase 5: Publication and Archival

• Export the validated Confluence report to PDF format and attach it to the permanent project audit repository.
• Publish the live Confluence page and dispatch the automated notification summary to the project distribution list via the enterprise communication gateway by Fridays at 17:00 UTC.
• Archive raw telemetry JSON and CSV data extracts in the project's secure data lake bucket for retrospective analysis.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• Objective Narrative: Never use subjective adjectives ("going well," "almost done") without corresponding empirical data (e.g., "82% of acceptance criteria verified").
• Forward-Looking Bias: Allocate 70% of the report's real estate to forward-looking risk mitigation and upcoming milestones rather than historical recounts of completed tasks.
• Naming Conventions: Enforce strict file and page naming conventions: [Project-Code]_Weekly-Status_[YYYY-MM-DD].

5.2 Common Pitfalls to Avoid

• The "Evergreen Green" Fallacy: Marking a troubled project as Green to avoid difficult conversations. PMs found falsifying health metrics will be subject to PMO audit.
• Data Silos: Manually transcribing metrics without verifying against single-source-of-truth platforms (Jira/ERP).
• Blob Reporting: Submitting excessively long narrative blocks instead of structured bullet points and data tables.

5.3 Metric Thresholds

• Schedule Variance (SV): $\text{SV} < -10% \implies$ Mandatory Amber/Red declaration.
• Cost Variance (CV): $\text{CV} < -10% \implies$ Mandatory budget review meeting with Finance.

---

6. Frequently Asked Questions (FAQ)

Q1: What is the mandatory cutoff time for submitting the weekly status report?
A1: All reports must be published and distributed no later than Fridays at 17:00 UTC. Late submissions trigger an automated flag in the PMO compliance dashboard.

Q2: How should a project status be handled if a critical blocker is resolved on Friday afternoon after the draft has been reviewed?
A2: Update the Executive Summary and Issue log prior to the final 17:00 UTC distribution, and add an inline annotation noting the time of resolution to maintain transparency.

Q3: Can project managers modify the structure of the Confluence report template?
A3: No. The structural integrity of template TR-SOP-042-TPL is locked at the administrative level to ensure cross-project data parsing for automated executive dashboards. Feature requests for template modifications must be submitted to the Chief Architect via the internal tooling portal.