Predictable updates reduce anxiety on both sides and prevent scope-by-DM.
Weekly email template
Status - week of [date]
Done
- [item]
- [item]
In progress
- [item] - on track for [date]
Blocked (need you)
- [item] - waiting on [approval / file / login]
Next week
- [priority 1]
- [priority 2]
Hours: [X] of [cap] used
Send Friday their morning or your Friday 4pm.
Daily Slack (busy retainer)
EOD [date] Done: [1-3 bullets] Tomorrow: [top task] Blocked: [none / item]
Keep under 5 lines. Phone readable.
PULSE format
- Progress (what shipped)
- Upcoming (next)
- Limits (hours cap warning if 80%+ used)
- Stakeholder (if new voice appeared, note for primary contact)
- Escalation (payment or scope flag calmly)
When updates prevent scope creep
Client asks random tasks in DM. You reply:
Logging this for Monday priority list. Current cap focused on [in-scope A, B]. Confirm if [new ask] replaces one or needs change order.
Update becomes boundary tool.
Common mistakes
| Mistake | Fix |
|---|---|
| Novel every week | Same headings |
| Only good news | List blocks early |
| No hour visibility | Show cap usage |
| Updates only when they chase | Proactive rhythm |
How Salag helps
- Agreement Builder: put update rhythm in scope.
- Rate Calculator: cap hours to report against.
- Scope Creep Detector: flag DM tasks outside scope.
Move safer. Not faster.
In short
Clients panic when they do not hear from you. Status updates fix that.
Same day each week. Same format: Done, Doing, Blocked, Need from you. Ten minutes to write. Hours of "just checking in" DMs saved.
Common questions
Clients panic when they do not hear from you. Status updates fix that. Same day each week. Same format: Done, Doing, Blocked, Need from you. Ten minutes to write. Hours of "just checking in" DMs saved.
Pick a rhythm (weekly Friday, daily Slack). Same format every time so client knows what to expect.
Short English, bullet points, mobile-friendly. Done / doing / blocked / need from you.
Put "weekly written update" in scope for retainers. Sets norm early.
Explain updates save them from asking "any update?" ten times a week.
Progress, Upcoming, Limits, Stakeholder asks, Escalation needs. Five lines max each.
When blocked items sit 5+ days with no client reply. Note in update then follow up.
Yes. Updates prove work done if payment or scope disputed later.
Templates and scope tools tie updates to agreed tasks.
Email template, Notion page, Loom for demos, calendar reminder.
Ten to fifteen minutes weekly if you track as you go.
Retainers: weekly rhythm. Projects: milestone updates at gates.
Still send updates. They protect you. Scope confirm is separate.
