Engineering · Weekly report

Weekly Engineering Status

A concise view of delivery confidence, engineering health and decisions.
REPORTING PERIOD[Start date – End date]
Team / Product
[Team name]
Product or service
Accountable leader
[Engineering Manager]
Report owner
Overall status
Amber
Illustrative status
Next milestone
[Milestone]
[Target date]
Overall confidence
Amber
Delivery outlook
01

Executive summary

What changed, what matters, and whether the team is on track.

Most important outcome delivered[Outcome]
Biggest change since last report[Change]
Primary concern[Risk or blocker]
Overall confidenceAmber [Rationale]
02

Delivery and commitments

Milestones, scope, dependencies and near-term priorities.

MeasureCurrent position
Key milestones[Status and forecast]
Scope changes[What changed and why]
Dependencies[Owner and expected resolution]
Next week’s priorities[Top three outcomes]
03

Engineering health

Status should be supported by current evidence.

DimensionStatus / trendEvidence
Quality and testingAmber[Pipeline / defects]
SecurityGreen[Findings / exceptions]
ReliabilityAmber[SLO / incidents]
Delivery flowAmber[Lead time / blocked work]
Lifecycle practicesGreen[Control evidence / gaps]
04

Top risks and mitigations

The risk, response and accountable owner.

[Risk description and impact]
Mitigation
[Action and contingency]
Owner
[Name or role]
Target date
[Date]
05

Decisions and support required

Items that need action beyond the team.

Decision / supportRequired fromNeeded by
[Decision][Leader / team][Date]
06

Improvement actions

Track actions through to completion.

ActionOwner / dueStatus
[Action][Owner]
[Due date]
In progress
i

Reporting note

Keep the report evidence-led.

Replace placeholders with current facts. Use Green, Amber or Red consistently, call out material changes, and assign an owner and target date to every significant risk or action. Missing or stale evidence should not silently default to Green.