Weekly Status Report

Weekly Status Report

Week of [dates] | [Your name], [Role]

---

HIGHLIGHTS

• Billing service migrated to the new queue. All 3 consumers are cut over and the error rate stayed flat.

EU invoice email incident fixed the same day. EU customers' invoice emails ran about 40 min late. The cause was the queue consumer autoscaling minimum being set to 0 in eu-west. The fix went out the same day. The postmortem is started but not finished.

Onboarding revamp has a clear problem to solve. Support (Ravi) says the top complaint is

confusion during SSO setup. I drafted a 1-page problem statement around it.

PROGRESS

Onboarding revamp (Jen wants it scoped by end of month)

• Problem statement drafted (1 page)
• Scoping doc started, about 40% done
• Activation funnel numbers are still missing; they need warehouse access (see blockers)

Incident follow-up: EU invoice email delay

• Postmortem started. Still needs the timeline section and action items. Aiming to finish Monday.

Queue / billing

• Migration done (see highlights)
• Paired with new hire Tom for 2 hrs on the queue codebase

BLOCKERS & RISKS

NEXT WEEK

• Finish the postmortem (Monday)
• Finish the onboarding scoping doc, adding funnel data if access comes through
• Get warehouse access. Escalate DATA-412.
• Prep for Q4 planning on the 15th

NOTES / FYI

• 4 code reviews: auth refactor, two dependabot bumps, one typo fix

---

Before you send it:

Check the two severities. Your notes don't rate either blocker, so I proposed them. I picked Medium for DATA-412 because it threatens the end-of-month deadline but isn't urgent yet. If it's already putting that deadline at risk, raise it to High.
2. Your manager will likely ask whether the incident is linked to the migration. The migration finished Monday and a queue consumer setting caused Tuesday's incident. Your notes don't say whether that eu-west setting came from the cutover. Add a line either way, or I'll leave it as is.
3.

"Escalate?" I wrote it as a request to your manager for help. If you'd rather escalate yourself, change that cell to "Escalating Mon."
4. Fill in the dates, your name and your role in the header.

Left out: nothing. The code reviews and the pairing session are in Notes and Progress rather than Highlights, because your notes don't describe an outcome for them.

Metrics: the only numbers in the report come straight from your notes: 3 consumers, about 40 min, about 40%, 2 hrs and 4 reviews. Two numbers would make it stronger if you have them: how many EU customers or emails were affected, and the error rate itself, not just "flat."

I can also write a 3-bullet version for your skip-level, or a version with more detail for your team.