Send a weekly client status email that states progress, the decision needed, and the deadline, with a versioned status report attached. Copy the email and report templates below, replace the placeholders with checked project details, and include an escalation contact so the client knows how to resolve anything holding up delivery.
What subject line and body should I send right now?
Send a short client email that names the delivery status, completed outcome, and approval needed. Attach the matching report version and state who will handle an unresolved decision. Keep the request in the email body so the sponsor can respond without opening the attachment, while retaining evidence in the report.
Copy this email into your usual email tool. Complete the reporting-period date separately from the decision deadline. Use the same decision deadline in the subject, request, escalation sentence, and pre-send checklist.
Subject: [ProjectKey] weekly status update (week ending [YYYY-MM-DD]), status: [STATUS] | Escalation by: [Decision deadline]
Report version: v[NN]
Hi [Sponsor name],
Summary: [ProjectKey] is [status]. We completed [outcome], which means [effect on the agreed milestone].
Decision required: [Decision reference] | [Question]
Options: [Options and their delivery implications]
Recommendation: [Recommended option and reason]
Please respond by [Decision deadline].
Escalation contact: [Name, role, email, phone].
If the decision remains unresolved by [Decision deadline], I will contact [Escalation contact] to agree how to address [delivery impact].
Next actions:
- [Action], Owner: [Name], Due: [Due date]
- [Action], Owner: [Name], Due: [Due date]
Please confirm your decision using the wording below, request changes, or nominate an alternate decision owner by [Decision deadline].
Suggested approval reply:
I approve [Decision reference] to proceed with [description], subject to [conditions or none].
Attached: [ProjectKey]_WeeklyStatus_[YYYY-MM-DD]_v[NN].pdf
Supporting evidence: [Evidence location]
Thanks,
[Your name], [Role]
If no approval is needed, replace the decision and escalation lines with: No client decision is needed for the next agreed work. Please flag any change to [assumption or dependency].
Pre-send checklist:
- The email and attachment show the same status and version.
- Evidence references open to the claimed work and are accessible to the client.
- Actions have owners and due dates.
- The decision reference matches the project decision record.
- The escalation contact and [Decision deadline] are included and consistent.
- The attached filename is [ProjectKey]WeeklyStatus[YYYY-MM-DD]_v[NN].pdf.
- The sent email and attachment will be retained in the agreed project folder.
What should the attached status report contain?
The attached status report should explain progress against the agreed milestone, show evidence for completed work, and identify the next actions. Include decisions, blockers, scope changes, and a checked commercial summary where relevant. Give each unresolved item an owner and needed-by date so the client knows what requires attention.
Copy the block into your document editor and replace the placeholders. Keep supporting detail in the existing project records rather than repeating task histories. For a layout reference, Corcava provides a one-page report template with completed work, baseline, next actions, blockers, decisions, and commercial fields.
PROJECT: [ProjectKey] | CLIENT: [Client name]
PERIOD: Week ending [YYYY-MM-DD]
PREPARED BY: [Name] | VERSION: v[NN]
SUMMARY
[What changed, current status, and effect on the milestone]
CURRENT BASELINE
Milestone: [Agreed deliverable and date]
Schedule assessment: [Status and supporting reason]
Scope changes: [Approved changes or none]
COMPLETED SINCE LAST UPDATE
[Outcome] | Evidence: [Evidence reference]
NEXT ACTIONS
[Action] | Owner: [Name] | Due: [Due date]
Completion check: [Acceptance evidence]
BLOCKERS AND DECISIONS
Decision reference: [Decision reference]
Question: [Question]
Options: [Options and implications]
Recommendation: [Recommendation and reason]
Needed from: [Name] | By: [Decision deadline]
Delivery impact if unresolved: [Impact]
Escalation contact: [Name and role]
COMMERCIAL SUMMARY
Approved baseline: [Verified baseline]
Current position: [Verified position and reporting cutoff]
Pending change: [Change awaiting approval or none]
RISK
[Risk] | Response: [Action] | Owner: [Name]
SUPPORTING RECORDS
Project board: [Board reference]
Deliverable evidence: [Evidence reference]
Decision record: [Decision record reference]
NEXT UPDATE: [Date] | SENDER: [Name]
If commercial information is still being checked, write Awaiting verification by [Owner] rather than presenting an estimate as confirmed.
What does a worked, copy-paste report example look like?
A worked report should connect completed work to the milestone and explain exactly what the client needs to decide. Use the wording model below to turn your verified project details into sentences. The bracketed fields deliberately remain unfilled: the example illustrates phrasing, rather than claiming a completed client engagement or result.
Copy this model when you need more help with wording than the blank template provides. Replace each field and remove any sentence that your evidence does not support.
PROJECT: [ProjectKey] | CLIENT: [Client name]
PERIOD: Week ending [YYYY-MM-DD]
PREPARED BY: [Name] | VERSION: v[NN]
SUMMARY
[Deliverable] has completed [review stage], with the result recorded in [evidence reference]. The effect on [milestone] is [verified effect].
Approval of [scope question] is still needed before [dependent work] can proceed.
COMPLETED SINCE LAST UPDATE
[Deliverable] met [acceptance criterion]. Evidence: [Evidence reference].
[Client reviewer] confirmed [review outcome]. Evidence: [Feedback reference].
NEXT ACTIONS
[Owner] will complete [action] by [due date]. Completion will be checked against [acceptance criterion].
After approval, [Owner] will begin [dependent work] against [agreed scope].
DECISION NEEDED
[Decision reference]: Please confirm [question] by [Decision deadline].
The available options are [options and implications].
We recommend [option] because [reason supported by evidence].
If the decision remains unresolved, [delivery impact].
Escalation contact: [Name and role].
COMMERCIAL SUMMARY
Against [approved baseline], the verified position is [current position] as of [reporting cutoff]. [Pending change] remains separate until approved.
RISK
[Dependency] may affect [milestone]. [Owner] will take [mitigation action] and review the position at [review point].
SUPPORTING RECORDS: [Evidence and decision record references]
NEXT UPDATE: [Date] | SENDER: [Name]
How do I export and name the PDF so the archive is consistent?
Export the checked report as a PDF if your document editor supports that format, then use a consistent project, period, and version filename. Open the exported file before attaching it. Retain the sent version in the agreed project folder so later edits remain distinguishable from the report the client received.
Use this filename pattern:
[ProjectKey]_WeeklyStatus_[YYYY-MM-DD]_v[NN].pdf
- Paste the chosen template into your existing document editor.
- Replace the placeholders and check that the report remains readable after export.
- Use the available PDF export or save option.
- Open the PDF and check headings, page breaks, evidence references, and version.
- Save the file in the client-approved project folder and attach that version.
- Save a copy of the sent email alongside the attachment.
When a correction is needed, retain the earlier file, change the version token, and explain the correction in the replacement email. Follow the client's agreed storage and retention rules; a filename alone does not establish an approval record.
Should I attach the PDF or share a report link?
Attach a versioned PDF when the client asks for a fixed report to retain or review for sign-off. Share a report link when the client prefers navigating to supporting work. Agree which version the client is reviewing, check access, and identify the attachment as the record of the sent update.
Prefer a shared report link when the aim is to avoid copying different versions into email and chat, an approach recommended by Superthread.
For an attachment-based workflow, use the compact report above and agree the sign-off process with the client. Corcava supplies a printable PDF and worked report example; that format does not by itself establish your sponsor's approval requirements.
If you provide an attachment and access to supporting records, explain their roles:
The attached [filename] records the status sent for [reporting period]. Supporting work is available in [approved project location]. Please refer to [version] when giving feedback or approval.
How should I set the cadence and sponsor meeting agenda?
Agree a regular update time with the client and make decision deadlines explicit rather than waiting for the next status email. Use the sponsor meeting to resolve choices, review feedback, and confirm next steps. Send the relevant evidence beforehand and close the meeting by checking who owns each agreed action.
Keep the send time predictable, consistent with the timing guidance described in Client Work Hub's template.
Use this wording to agree the arrangement:
I will send the status email and report every [weekday] at [time and time zone]. Please suggest an alternative if needed. When a decision cannot wait for that update, I will contact [decision owner] with the question, evidence, and deadline.
Copy this sponsor meeting agenda:
- Confirm the status and what changed against the agreed milestone.
- Review [decision reference], the available options, and the recommendation.
- Resolve feedback on [deliverable] and confirm any approval conditions.
- Agree the response to [risk or blocker].
- Confirm actions, owners, due dates, and the next review point.
Finish by reading back the decision and next step. Record unresolved questions with the person responsible for resolving them.
How do I capture approvals and record decisions?
Ask the sponsor to identify the decision, approved scope, and any conditions in their reply, then preserve that reply with the project record. Use the client's agreed sign-off process where required. Suggested wording can help clarify approval, but check the actual response before recording a decision as approved.
Offer this reply wording:
I approve [Decision reference] to proceed with [description], subject to [conditions or none].
Name: [Sponsor name]
Date: [Approval date]
- Check that the reply comes from the agreed decision owner.
- Confirm what was approved and whether conditions change the next action.
- Ask for clarification if the reply leaves scope or conditions unclear.
- Save the original response in the approved project location.
- Update the existing decision record with the outcome, date, conditions, and evidence reference.
- Update the affected work and report version where needed, retaining the report originally sent.
A natural-language reply can be clear enough for your agreed process. Request clarification when necessary rather than asking the sponsor to repeat an unambiguous response solely to match the template.
What should I check before sending?
Before sending the client update, check that the email, report, and supporting records describe the same delivery position. Confirm the decision owner, deadline, and escalation contact, then inspect the attachment and access permissions. Use the pre-send checklist above and resolve discrepancies before asking the sponsor to review or approve work.
For several concurrent engagements, review each update against its own client and project records:
- Confirm that the recipient list, attachment, and project folder belong to the intended client.
- Check that completed work is supported by evidence, not just an activity update.
- Distinguish work ready for review from work already accepted.
- Confirm that pending scope changes remain separate from approved commitments.
- Check that workstream detail agrees with the overall status.
- Remove internal commentary or commercial details the recipients should not receive.
If a reported fact is still uncertain, name what needs checking and who will confirm it. Keep the rest of the update useful rather than holding back verified progress.
How should I write clear action items, escalation language, and decision wording?
Write action items that name the work, owner, due date, and completion evidence. Phrase escalation as a request for help with a delivery consequence, not a warning. Give the sponsor the question, options, and recommendation so the response can become a recorded decision and a clear next step for the team.
Copy and adapt these lines:
Action: [Action]
Owner: [Name] | Due: [Due date]
Complete when: [Acceptance criterion]
Evidence: [Evidence reference]
We need [decision or help] by [Decision deadline] to proceed with [dependent work]. If you cannot respond by then, please nominate an alternate decision owner. I will contact [Escalation contact] at the deadline to agree how to address [delivery impact].
Decision reference: [Decision reference]
Question: [Question]
Options: [Options and implications]
Recommendation: [Recommended option and reason]
Owner: [Name] | Needed by: [Decision deadline]
Next step after approval: [Action and owner]
Before sending an escalation, check that the deadline still reflects the work dependency and that the contact can help resolve the issue. After the sponsor responds, update the affected action and tell the team what to do next.
Template references used:
- Corcava: report structure, PDF format, and worked example.
- Superthread: shared report links rather than copied versions.
- Client Work Hub: predictable update timing.