Weekly Status Report Template Confluence

Standard Operating Procedure: Weekly Status Reporting (WSR)

Document Control Block

• Document ID: SOP-OPS-001-WSR
• Effective Date: 2023-10-27
• Version: 2.1.0
• Review Cadence: Quarterly

1. Executive Summary & Purpose

The purpose of this SOP is to standardize the generation and archival of Weekly Status Reports (WSR) within the Confluence ecosystem. This protocol ensures cross-departmental alignment, identifies systemic blockers, and facilitates executive-level visibility into project health, resource utilization, and milestone progression.

2. Scope & Prerequisites

• Scope: All project teams, engineering squads, and product units reporting to the Template Registry PMO.
• Prerequisites:
  • Active Atlassian Confluence Cloud credentials.
  • Read/Write access to the department-specific "Status Reports" page tree.
  • Integration with Jira Software (for automated ticket/burn-down pulling).

3. Roles & Responsibilities (RACI Matrix)

4. Step-by-Step Procedure

Phase 1: Preparation (Friday 09:00 - 13:00)

• Locate the "WSR Master Template" in the Shared Space.
• Create a child page for the current week (Format: YYYY-MM-DD | [Project Name] | WSR).
• Apply the "Status Report" template macro to the new page.

Phase 2: Data Aggregation (Friday 13:00 - 15:00)

• Jira Integration: Update the "Jira Filter Results" macro to reflect the last 7 days of completed tasks.
• KPI Logging: Manually input data for "Velocity," "Risk Level (Red/Amber/Green)," and "Budget Burn."
• Blockers: Explicitly list blockers requiring external intervention with assigned owners.

Phase 3: Review and Publication (Friday 15:00 - 17:00)

• Conduct a peer-review check for tone, grammatical precision, and metric accuracy.
• Tag relevant department heads in the comments section for sign-off.
• Click "Publish" and set page permissions to "View: All Staff."

5. Quality Assurance & Pro-Tips

Quality Assurance (QA) Metrics

• Timeliness: Must be published no later than Friday, 17:00 local time.
• Completeness: All Jira macros must return data; no "null" or "TBD" fields permitted in sections 1-4.
• Accuracy: Discrepancies between Jira burn-down charts and manual reports must be < 5%.

Pro-Tips

• Macro Automation: Use the Content Report Table macro on the parent index page to automatically roll up status signals into a dashboard.
• Brevity: If a section exceeds 300 words, provide an executive summary followed by a link to a detailed sub-page.
• Link Hygiene: Always link to the specific Jira Epic or Board in the "Scope" section.

6. Frequently Asked Questions

Q: What should I do if a Jira macro is returning a 'Permissions' error? A: Verify that your Jira project board is set to 'Public' within the Confluence workspace scope. If the error persists, contact the internal SysAdmin for JQL access privileges.

Q: How do I handle status reports during leave or vacation? A: You must designate a 'Proxy Owner' in the RACI matrix at least 24 hours prior to the reporting window. The proxy is responsible for the submission.

Q: Are attachments allowed within the WSR? A: No. Upload all documentation (PDFs, spreadsheets) to the project repository and embed the link. Direct uploads clutter the Confluence space and inhibit searchability.