---
name: weekly-leadership-report
description: Produces a weekly leadership report from team updates and operating metrics, showing progress against targets, material exceptions, risks, dependencies, decisions required, and changes since the prior week. Use for weekly leadership report, evidence review, management reporting, and decision support.
license: Apache-2.0
metadata:
  adlass.categories: "executive-strategy/reporting-reviews"
  adlass.industries: ""
  adlass.tags: "weekly-report,leadership,kpi,risks,decisions,targets,updates"
  adlass.adaptation: "reference-doc"
  adlass.source: "original"
  adlass.version: "1"
---

# Weekly leadership report

## Purpose

Produces a weekly leadership report from team updates and operating metrics, showing progress against targets, material exceptions, risks, dependencies, decisions required, and changes since the prior week.

## Scope

Cover one completed reporting week and compare it with the prior week, target, or forecast named in the reporting template. Include KPI movement, team commitments, delivery status, risks, dependencies, and decisions required. **Excluded:** inventing an update for a silent team, changing a KPI definition, or closing a risk without evidence.

## Data basis

- Weekly team updates with owner, status, accomplishment, blocker, and next-step fields.
- KPI table with metric, week, actual, target, prior_week, unit, and source row.
- Risk and dependency register with severity, due date, mitigation, and status.
- Prior leadership report and approved reporting template.

## Result

Produce the weekly report plus a KPI and risk appendix: headline changes, progress by team, red or amber items, decision requests, and explicit source citations.

## Quality criteria

- Every KPI shows actual, comparator, unit, direction, and source row.
- Each team has present, missing, or stale update status; silence is never progress.
- Risk color follows the supplied severity rule and cites the risk-register row.
- Decision requests state the decision, consequence of delay, and evidence, not an assumed approval.
- Headline numbers equal appendix totals and prior-week deltas.

## Instructions

Use reporting-template targets and escalation definitions. Calculate deltas from the KPI table rather than copying prose. Preserve exact owners and due dates from updates and registers. A stale update is outside the configured freshness window; do not invent that window. Keep accomplishments, risks, and requests separate, moving supporting rows to the appendix.

## Adapt before use

- Add the reporting template, KPI dictionary, target definitions, prior report, and risk register.
- Define week boundary, freshness window, target variance threshold, color labels, and report length.
- Specify audience, decision-owner vocabulary, and treatment of confidential team updates.