Operations template

Weekly team update

Pull the week's progress from your project tools and team notes into a short update for leadership, with wins, risks and next week's focus.

Use this templateUsed by 6,200 teams
Operations

What you fill inPreview

Team
Platform engineering
Sources
Linear project, #platform channel, standup notes
Audience
Leadership team

Example output

Generated by Pilot

Platform engineering: week of November 2

Status: on track. Two of three milestones for the database migration are done, one day ahead of plan.

Shipped this week

  • Read replicas are live in the EU region. Report pages load 40% faster for European customers.
  • The old job scheduler is switched off. All 62 scheduled jobs now run on the new queue, with no failures since Tuesday.
  • On-call handbook updated with the new escalation path and runbooks for the queue.

In progress

  • Moving the last two services to the new database. Billing goes first, on Wednesday, during the low-traffic window.
  • Load testing for the December traffic peak. First results are due Friday.

Risks

  • Billing migration depends on the finance team’s freeze calendar. If the month-end freeze starts early, the migration moves to November 18. Iris is confirming with finance by Monday.
  • One engineer on leave next week. Load testing may slip by two days. No customer impact expected.

Numbers

Metric This week Last week
Uptime 99.98% 99.95%
Pages to on-call 3 7
Median API response 142 ms 168 ms

Next week

  1. Migrate the billing service.
  2. Share load test results and a capacity plan.
  3. Start retiring the old database, beginning with read-only tables.

Drafted by Autopilot from 41 Linear updates, 5 standups and 128 messages in #platform. Reviewed by Iris Calder.

All templates

Your next draft is already started

Join 14,000 teams that research, write and ship with Pilot.