Sample deliverable · Delivery and governance
Sample weekly status report
The one-page report you receive every week: status, progress, risks, decisions needed and next steps.
Sample / template. Fictional systems, names and dates that show the format and depth of what you receive. Not a client deliverable.
Engagement (fictional): EKS platform upgrade and observability · Week 3 of 8 · Report date: [date]
| Area | Status | Comment |
|---|---|---|
| Overall | Green | On plan for the week 5 production upgrade |
| Scope | Green | No change requests open |
| Schedule | Amber | Staging upgrade moved two days for a vendor add-on fix; milestone date unchanged |
| Fee | Green | Within the fixed fee; no change requests pending |
| Risks | Amber | One high risk open (R4); mitigation under way |
Done this week
- Deprecated API scan complete: 14 manifests updated, merged through pull requests
- Staging cluster upgraded from 1.30 to 1.31; smoke tests passed
- OpenTelemetry collector deployed to staging; traces visible for two services
Planned next week
- Staging upgrade from 1.31 to 1.32; node group rotation rehearsal with timings
- Draft production runbook and rollback for review
- Dashboard and alert review with the on-call team
Risks and issues
| ID | Description | Rating | Owner | Action |
|---|---|---|---|---|
| R4 | Ingress controller version incompatible with 1.32 | High | SRASH | Upgrade controller in staging first; tested rollback |
| I2 | Read-only role missing on the logging account | Medium | Customer | Access request raised |
Decisions needed
- Approve the week 5 production window (Saturday 06:00–10:00 Pacific). Needed by Thursday.
Milestones
| Milestone | Planned | Forecast |
|---|---|---|
| Staging on 1.32 | Week 4 | Week 4 |
| Production upgrade | Week 5 | Week 5 |
| Observability live in production | Week 7 | Week 7 |
| Hand-over | Week 8 | Week 8 |
More delivery and governance samples
Sample contract document
Sample statement of work outline
The sections, acceptance criteria and change control in a typical fixed-fee statement of work. Fees are stated in each real SOW, not here.Sample deliverableSample architecture decision record (ADR)
How we record a significant technical decision: context, options considered, the decision and its consequences.Sample deliverableSample RAID log: risks, assumptions, issues and dependencies
The register we keep from day one and review with you weekly, with owners, ratings and mitigations.Want to see how this would look for your project?
On the free 30-minute review a senior engineer will walk you through how we would plan, report and govern your work.