Cadence & Status Templates

The weekly rhythm

If a deployment is healthy, this rhythm runs without effort. If it isn't, the rhythm is the first thing to slip. Treat consistency as the leading indicator of deployment health.

Monday sync agenda

30 minutes. Same agenda every week so attendees know what to expect. Goal: reset focus for the week.

# [Customer] Monday Sync — YYYY-MM-DD
30 min · customer data lead + FDE + analysts (as needed)

## 1. Last week (5 min)
- What we said we'd do
- What actually shipped
- Anything we didn't get to

## 2. SLA / quality check (5 min)
- Extraction accuracy by class (link to dashboard)
- HITL queue health
- Anything trending toward the line

## 3. This week's targets (10 min)
- 2–3 concrete deliverables
- Who owns each
- Anything blocking

## 4. Blockers & risks (5 min)
- Open access tickets, integration gating, IT approvals
- Anything that should escalate

## 5. Customer questions (5 min)
- Their floor — anything they want to flag

Action items captured in shared doc; updated within 2 hours of meeting.

The discipline

• Send the agenda in the calendar invite. Don't make people remember it.
• Start exactly on time. End exactly on time.
• One person takes notes. Action items in writing; circulated within 2 hours.
• If the meeting starts running long, cut sections 1 and 4 first; sections 2 and 3 are the load-bearing ones.
• If the meeting becomes a status reading, it's lost its purpose. The status doc covers status; the sync covers decisions.

Friday status doc

The most important artifact in the deployment. Five sections, one screen, ships by noon customer time every Friday — even when the week was rough, especially when the week was rough.

# [Customer] Status — Week of YYYY-MM-DD

## 1. Shipped this week
- [Concrete artifact with a number or link]
- [Another concrete artifact]
- [Third one if applicable]

## 2. In flight
- [Item, owner, expected date]
- [Item, owner, expected date]

## 3. I need from you
- [Specific ask, owner, by when]
- (Or "nothing this week" — say it explicitly)

## 4. I'm worried about
- [Honest risk, with what would help]
- (Or "nothing material" — but only if true)

## 5. Next week
- [Top 2–3 deliverables]

---
Questions? Reply to this email or grab me Monday.

The rules

• Concrete in section 1. "Made progress on extraction" is not concrete. "Extraction accuracy on supplier agreements moved from 78% to 91%" is.
• Real asks in section 3. "I need from you" is the part most candidates skip. It's the most valuable. If you have nothing, say "nothing this week" — don't fabricate.
• Honest in section 4. If the SLA is at risk, name it. If a customer-side blocker is undermining the timeline, name it. Friday-status hiding bad news is how deployments die.
• One screen. If it's longer than one screen, you're losing readers. Cut.
• Send to the working team plus the executive sponsor. The sponsor doesn't read every word; the doc is their tripwire when something's off.

Internal Thursday sync

30–45 minutes with your platform team — PM, engineering lead, sometimes AE. Goal: surface platform-blocking issues, share learnings, plan next week's customer asks.

# Internal — [Customer] Deployment Sync — YYYY-MM-DD
30 min · FDE + platform PM + eng lead

## 1. Deployment health
- Phase, milestone progress vs plan
- Any milestone at risk

## 2. Platform asks
- Bugs to file (with customer evidence)
- Feature requests (with customer rationale + urgency)
- Documentation gaps blocking work

## 3. Things to share back to platform
- Patterns we're seeing across customers
- Tooling that worked / didn't
- Learnings that should land in the next deployment's playbook

## 4. Commercial flags
- Any expansion signal (procurement asking about other BUs)
- Any churn risk
- Anything the AE should know

## 5. Help I need from leadership
- Decisions blocked above me
- Resource asks (more reviewer capacity, eng hours, etc.)

Section 3 is the most underrated. The platform team learns more from FDE-DE field reports than from any other source — write yours up.

Monthly leadership review

45 minutes. Customer sponsor + platform leadership. Goal: keep the strategic conversation aligned, surface risks early, set up expansion.

# [Customer] Monthly Review — YYYY-MM
45 min · Customer sponsor + platform leadership + FDE

## 1. Deployment status (10 min)
- Phase, milestones hit, milestones at risk
- Headline business outcomes to date

## 2. SLA & quality dashboard (10 min)
- Live walkthrough of customer-facing SLA dashboard
- Any class trending below; what we're doing

## 3. Wins (5 min)
- Specific customer artifacts that landed
- Quotes from end users if available

## 4. Risks (10 min)
- Honest enumeration
- For each: what we're doing, what would help

## 5. The conversation (10 min)
- Open Q&A
- Anything the sponsor wants to surface
- Expansion conversations as they come up

The discipline

• Walk the SLA dashboard live, not from a screenshot. Builds trust that it's real and current.
• Wins section uses end-user quotes where possible. "Sarah in Procurement said 'this saved me three hours of review last week'" is worth ten lines of metrics.
• Risks section is honest. The customer sponsor is paying for outcomes; they'd rather hear about a risk in month 2 than be surprised in month 4.

Cadence tips

Adjust to the customer, not the calendar

If the customer is in a freeze window (quarter-end close, board prep), reduce Monday syncs to biweekly. If they're in a critical phase, you may temporarily move to Tue/Thu sync. The goal is to match their attention, not to enforce your calendar.

The deployment without a sponsor showing up

If your executive sponsor has missed two consecutive monthly reviews, the deployment is in trouble whether you've noticed or not. Escalate to your AE before missing the third.

The "should we move to async?" question

Sometimes the customer's data lead is great over Slack and useless in meetings. Adapt. The Monday sync can become a Slack thread with a short structured update if both sides are healthy that way. Don't impose synchronous cadence as ceremony.

Customer goes dark

If you don't hear from the customer for 5+ business days during active deployment, that's a signal. Reach out specifically and personally. Don't just send the status doc and hope.

When status feels formulaic

The Friday status doc gets ignored when it becomes templated. Vary the section 4 ("I'm worried about") content — even on weeks when there's no worry, write a sentence about something you're watching. Reading the doc is the customer's tripwire; keeping it useful keeps them reading.

✓ Check yourself

Answer from memory before opening each one.

1. The Monday sync keeps running to 40 minutes. Which sections do you cut first, which do you protect, and why?

   Show answer

   Cut last week and blockers first; protect the SLA check and this week's targets. The sync exists for decisions, and the status doc already covers status, so a meeting that reads status aloud has lost its purpose. See Monday sync agenda.

2. On Friday, accuracy on a legacy supplier class has slipped two points over two weeks and the cause is unknown. Does it go in the status doc, and where?

   Show answer

   Yes, in the section on what you are worried about, with what would help and a date for the fix path. Raising a concern before the customer asks is the strongest trust signal in an embedded deployment. See the Friday status doc.

3. You have no asks of the customer this week. Why does the template have you write "nothing this week" rather than delete the section?

   Show answer

   An explicit "nothing" tells the reader the section was considered. An empty or missing one cannot be told apart from a forgotten one. Do not invent an ask to fill the space either. See the Friday status doc.

4. What goes in section 3 of the internal Thursday sync, and what is lost if you skip it?

   Show answer

   Patterns seen across customers, tooling that worked or failed, and learnings for the next deployment's playbook. The platform team learns more from field reports than from any other source, so skipping it means the same problems get rediscovered on the next deployment. See internal Thursday sync.

5. A customer is in quarter-end close and the data lead answers Slack within the hour but misses meetings. How do you adapt the cadence?

   Show answer

   Match their attention. Move the Monday sync to biweekly or to a short structured Slack update, and keep the Friday doc and the monthly review as they are. Watch for five business days of silence, which is a signal to reach out personally. See cadence tips.

6. Your sponsor has missed two monthly reviews and every Friday status is green. What do you do?

   Show answer

   Escalate to the AE before the sponsor misses a third, and look for a secondary sponsor. Two missed reviews mean the deployment is in trouble whether or not you have noticed. A green doc during that silence is the moment to check it against your own risks. See cadence tips.

Takeaway

• Consistency of the rhythm is the leading indicator of deployment health; when a deployment struggles, the rhythm slips first.
• The Monday sync is for decisions on a fixed agenda, and the status doc is for status.
• The Friday doc ships by noon customer time every week, and most of all in a rough week.
• Naming a risk in the status doc before the customer asks is the strongest trust signal you have.
• The Thursday internal sync turns field experience into platform fixes and the next deployment's playbook.
• The monthly review walks the live SLA dashboard, lists risks honestly and uses end-user quotes.
• Adjust the cadence to the customer's attention, and treat a sponsor who misses two reviews as an escalation.

The cadence will eventually surface an ask nobody can pin down, or a deployment that is not working, and the next chapter gives you the tools for both. → Scoping & Kill Criteria

Further reading

• Communication and Collaboration in SRE — Google SRE book, 2016. Covers production meetings and how teams share status; a model for the Monday and Thursday syncs.
• Monitoring Distributed Systems — Google SRE book, 2016. What to put on a dashboard and what to alert on, useful for the SLA view you walk each month.
• Service Level Objectives — Google SRE book, 2016. Why a dashboard should show the target and the measure side by side.
• Source freshness — dbt Labs documentation, accessed 2026. How to measure and surface data freshness, a common line on the SLA dashboard.