# Progress Report Template

Use this concise report after a work package or phase. Progress means verified output, not time spent or optimistic percentages.

[Team README](README.md) · [Roles](Team%20Roles.md) · [Workflow](Team%20Workflow.md) · [Master Team Prompt](Master%20Team%20Prompt.md) · [Quality Checklist](Team%20Quality%20Checklist.md)

~~~markdown
# Team Progress Report

## Report ID and Context Version
[ID / VERSION]
## Phase and Overall Status
[PHASE] — [On Track / At Risk / Blocked / Needs Approval]
## Completed Since Last Report
| Task | Owner | Output | Evidence |
| --- | --- | --- | --- |
| [ID] | [AGENT] | [ARTIFACT] | [TEST/REVIEW] |
## Active Tasks
| Task | Owner | Dependency | Expected Handoff |
| --- | --- | --- | --- |
| [ID] | [AGENT] | [DEPENDENCY] | [OUTPUT/DATE] |
## Failures and Defects
[DEFECT ID / SEVERITY / OWNER / RETEST]
## Decisions and Assumptions Changed
[CHANGE + EVIDENCE]
## Risks and Blockers
[RISK/BLOCKER + IMPACT + ACTION]
## Pending Human Approvals
[EXACT DECISION + CONSEQUENCE]
## Next Three Actions
1. [OWNER + ACTION]
2. [OWNER + ACTION]
3. [OWNER + ACTION]
~~~

## Reporting Rules

- Do not count a task complete until its acceptance evidence exists.
- State failed and unrun checks explicitly.
- Highlight changes affecting communicate the offer within ten seconds, reach primary content in two navigation decisions, submit a contact request with verified confirmation, pass responsive, accessibility, SEO, and performance gates.
- Escalate immediately when unclear positioning, broken mobile navigation, silent form failure threatens a critical criterion.
- Keep updates concise by linking artifacts and shared context instead of repeating them.