> For the complete documentation index, see [llms.txt](https://framework.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.aic.io/company-operating-manual/delivery-governance/reporting-and-progress-tracking.md).

# Reporting and Progress Tracking

### Purpose

Reporting must support decision-making without creating unnecessary overhead.

Good reporting shows progress, risk, blockers, decisions, and next steps.

### Weekly Delivery Report

The weekly delivery report should include:

* overall status
* progress this period
* planned work next period
* milestone status
* risks
* issues
* dependencies
* decisions required
* change requests
* commercial or acceptance matters
* support required from customer

### Status Definitions

### Green

Delivery is on track.

No material intervention required.

### Amber

Delivery is at risk.

Management action or customer decision may be required.

### Red

Delivery is materially off track.

Immediate escalation required.

### Progress Measures

Use a balanced view of progress:

* completed deliverables
* accepted milestones
* backlog movement
* user research findings
* technical progress
* risk reduction
* test evidence
* defect trends
* readiness indicators