Write an end-of-day status update people

Status updates people finish reading

A useful end-of-day note answers four questions: what finished, what is still open, what is blocked (with an owner), and what happens next. The before/after pair below is the whole standard. Formats and failure modes follow.

Before and after (start here)

Weak

Busy day. Lots of calls. Made progress on checkout. Will continue tomorrow.

Strong

Done
- PR #482 opened for checkout payment step (unit tests green)

Still open
- Preview deploy (~1 block after secret is set)

Blocked
- DevOps: preview webhook secret for payment callback (needed before tomorrow 14:00 UTC)

Tomorrow, first move
- After secret is set: redeploy, click success + failure once, comment on PR

People forgive slow days. They stop trusting vague days. Keep the update short enough to read on a phone. Day shape that makes updates easy: structure a remote workday. Sharper blockers: how to write a good blocker update.

Copyable core format

Paste this shell, or start from the end-of-day summary template / daily work summary builder.

Done
- …

Still open
- … (state + roughly how much left)

Blocked / need from others
- Who / what / by when

Tomorrow, first move
- One concrete action

Prefer outcomes and links over hours and vibes.

Freelancer to client

Clients skim. Put the ask where it cannot be missed.

Done
- FAQ sections 1 to 4 in shared doc (link)
- Staging screenshots for empty states (folder link)

Still open
- Section 5 (shipping) pending your policy answers

Needs from you
- Confirm whether international shipping FAQ stays or cuts (choose A or B in the doc comment)

Next checkpoint
- Thursday with section 5 drafted after your reply

Copy-paste shell: client status update template. A diary of your afternoon builds sympathy and hides the decision. One clear ask builds progress.

Internal teammate / overnight handoff

When another region continues, the note is the interface.

Done
- PR #482 opened; unit tests green

Open
- Preview deploy waiting on webhook secret

Blocked
- DevOps: preview webhook secret for the payment callback

Next for whoever continues
- Set secret, redeploy, click success + failure once, comment on PR

For overnight detail (environment, exact verify command, what not to redo), use the end-of-day handoff template and leave work in a state someone else can pick up.

Audience tradeoffs

Audience	Emphasize	Cut
Client	Deliverables, decisions needed, links	Branch names, debugging diary
Internal team	Handoffs, shared blockers, verify steps	Soft narrative
Both	Write internal first, then strip for client	Sending one blob to everyone

Do not send clients your debugging diary. Do not hide client decisions inside a long team note.

Timing and failure modes

Write the update before you shut down, not the next morning. Habit: shutdown routine for ending a remote workday. Draft during the last five minutes of the last focus block.

Common failure modes:

Listing every meeting as "done work"
Hiding blockers inside "still open"
Three next actions with no first move
Updates so long nobody reads the ask
Copying yesterday's open list without checking what changed

If the note takes more than two minutes, you are organizing history instead of reporting state. Cut to the four questions and stop.

When the day was messy, be blunt: "Primary slipped after an urgent support interrupt. Salvaged X. First move tomorrow is Y."

Open the workday dashboard, write Done / Open / Blocked while the day is still in memory, then paste the useful parts into chat or email.