How often should I send project updates?

Weekly is a good default for active projects. Increase the cadence when risk is high or a decision deadline is close.

Should I include every task?

No. Include only the progress, risk, or decision that changes stakeholder understanding. Link to the task tracker for detail.

What should the subject line say?

Use the project name and status. For example: 'Checkout redesign update - on track for June 20.'

How to write a project update email

Updated June 11, 2026 · ~1 min read · Ilura Technology

DIRECT ANSWERWrite a project update email with a headline status, progress since the last update, open risks, decisions needed, and next milestones. Put the status in the first line. Stakeholders should not have to read the whole email to know whether the project is healthy.

Want this written for you? ILURA drafts it in your voice on your iPhone — free, no account. Get ILURA — free

A project update email is not a status meeting in paragraph form. It is a decision and alignment tool.

The reader should understand the state of the project before they finish the first screen.

What does a weak project update look like?

Hi all,

We had a busy week on the checkout redesign. Design made progress, Engineering started implementation, and we are continuing to work through open questions. More soon.

This is positive but not useful. Is the project on track? What changed? What decision is needed?

What does a strong project update look like?

Subject: Checkout redesign update - at risk for June 20

Status: at risk. Design is complete, but Engineering found a payment edge case that adds two days.

Progress: new mobile layout approved; copy and empty states are final.

Risk: payment validation may push QA from Wednesday to Friday.

Decision needed: keep June 20 and cut saved cards, or move launch to June 24 with full scope.

This update creates alignment because it makes the tradeoff visible.

The five-part format

Headline status. On track, at risk, blocked, launched.
Progress. What changed since last time?
Risks. What could change the plan?
Decisions. What do stakeholders need to choose?
Next milestones. What happens next and when?

What if there are no risks?

Say so.

Risk: none currently. Next risk review is after QA starts Wednesday.

Silence around risk can look like you forgot to check.

Save this as a playbook

Project update voice is highly reusable. ILURA can keep your stakeholder update format consistent: short, honest, and focused on decisions rather than activity.

Message → rule → agent

Turn this message into an agent rule

Do not treat the answer as a one-off rewrite. Save the repeatable behavior behind it so your ILURA agent can apply the same judgment next time.

What situation triggered the message?
What tone, boundary or decision should repeat?
What should the agent avoid doing again?

Problems this guide helps with

The same rule appears in real user searches.

Manager Agent

I need to write a project update

write project update email

Manager Agent

I need to turn a chat thread into an update

turn Slack thread into update

Do it now

Draft this in ILURA right now.

Open ILURA, paste your message, and get help with "write project update email" — in your voice, on device, free. It quietly saves the rule (Progress, risk, blocker, owner, next milestone.), so the next time is one tap.

Free to start · No account · Data Not Collected

Download ILURA Open the pain point

Quick answers

How often should I send project updates?: Weekly is a good default for active projects. Increase the cadence when risk is high or a decision deadline is close.
Should I include every task?: No. Include only the progress, risk, or decision that changes stakeholder understanding. Link to the task tracker for detail.
What should the subject line say?: Use the project name and status. For example: 'Checkout redesign update - on track for June 20.'

ILURA does this on your iPhone — on device, private. Get ILURA — free, no account