How to Ask for a Progress Update: Email and Reply Examples Before and After a Deadline

A progress check is a request for facts that support a decision, not simply a reminder to work faster. State the deliverable, what you need to know, and when you need the reply. Asking about remaining work, forecast conditions, and support makes the answer more useful than a general “How is it going?”

Ask for the current state and the decision you need

Ask for a decision-ready state, not just whether someone expects to finish. Identify the deliverable and agreed completion criteria, then ask what meets those criteria, what remains, and what could change the forecast. Understanding a blocker can help you offer support without demanding a lengthy explanation of everything that happened.

For three banners, “produced” might mean files have been exported or that all checks and approval are complete. Ask how many have passed mandatory-text and size checks and received owner approval. Both parties can then use the same basis.

• Object: which assignment or deliverable are you checking?
• Facts: what meets the completion criteria now?
• Remaining work: what needs revision or approval, and by whom?
• Forecast: when is delivery expected, subject to what conditions?
• Decision: what support, priority, or downstream adjustment is needed?

An unknown is a valid response when paired with who will confirm it and when the record will be updated. Pressing for an unsupported number or guarantee can produce a confident answer that is unsuitable for planning.

Agree on check-in dates and reply times around downstream work

Agree on check-in dates and reply times by working backward from revision, approval, and downstream needs. Do not apply a universal number of days before delivery. Account for the recipient’s availability and explain why the information is needed.

The examples below concern a fictional three-banner assignment. D3 and D5 stand for dates in an agreed schedule; all times are Japan Standard Time, JST. Use full calendar dates in real messages. The three scenarios are alternatives, not one continuous actual history.

D3 is selected for this example’s revision needs. It is not a standard check-in interval. If the reply time is impractical, agree on an interim response with known information or involve a designated backup.

Adapt your email for before, on, and after the deadline

Before the deadline: a request and reply on D3

Subject: Progress check for three banners due D5 — reply by D3, 15:00 JST

Could you update us on the three banners due D5 at 17:00 JST? We need to reserve revision time on D4. Please reply by D3 at 15:00 with the number approved, remaining work, and the expected D5 delivery time and its assumptions. If you need help obtaining copy approval, coordinator B can assist.

Reply example: One banner has passed mandatory-text and size checks and received approval. The other two are waiting for copy confirmation. If A finalizes the copy by 17:00 today, we expect to complete production, checks, and approval for delivery by D5 at 17:00. Could B coordinate confirmation with A? If the copy is not finalized, we will update the forecast then.

On the deadline day: a request sent at 10:00 on D5

Subject: Status of three banners due today at 17:00 JST

To coordinate tomorrow’s D6 submission preparations, could you update us by 11:00 on the three banners due today, D5, at 17:00? Please include the number approved, remaining work, and forecast delivery including final checks. B can help arrange approval availability if needed.

Reply example: Two banners are checked and approved; the third needs a size adjustment. We will submit the revision by 12:00. If approver C can review it by 13:00, we expect delivery at 15:00, including any necessary corrections and rechecking. Could you arrange C’s review slot? If review runs beyond 13:00, we will reassess the remaining work and update the delivery forecast.

After the deadline: a request sent at 09:00 on D6

Subject: Missed delivery deadline — current status and forecast for three banners

The agreed delivery deadline of D5 at 17:00 has passed. We need to decide how to handle the D6 submission. Please reply by 10:00 today with the number complete, remaining work, and a revised delivery forecast and its assumptions. Contact B if you need support or coordination with the submission owner.

Reply example, D6 at 09:30: Two banners are checked and approved. We are correcting mandatory text on the third and will submit the revision at 11:00. If C reviews it by 12:00, we expect delivery at 14:00 after corrections and rechecking. Please help confirm C’s availability and the impact with the submission owner. The effect on D6 submission is still unconfirmed. Our next update will be at 12:30.

These forecasts depend on review availability and feasible remaining work. Replace the details with actual facts; do not turn a conditional example into an unconditional promise.

Offer a concise reply format

A concise response format helps collect relevant information without requiring a long narrative. Select fields needed for the present decision instead of making every field mandatory in every exchange.

A simple count does not represent comparable progress if the deliverables differ substantially. Explain what is ready for acceptance and what remains difficult. The aim is a reply that is both easy to provide and accurate enough for the decision.

Respond to delays and silence with support and escalation

When a delay emerges, establish remaining work and possible effects on downstream activities. Check reviewer availability, what can be substituted, and who may change the release plan. A detailed retrospective can wait, but actionable information about the current blocker is needed now.

The UK Government’s project delivery standard covers reporting, risk and issue handling, and communication suited to stakeholders. It is a reference for connecting facts with decisions, not a universal rule for email etiquette. See GovS 002 on project delivery.

If no reply arrives, verify the agreed response time and contact route, then restate the decision deadline. For an urgent issue, use the agreed urgent channel and contact a designated backup or decision-maker. Automatically copying everyone or duplicating reminders across channels can make response ownership less clear.

An escalation should state verified facts, unknowns, and the decision required. Separate a request for support from assigning accountability, and send the information to someone able to act.

Record the agreement and the next update location

After receiving the answer, record conditions and decisions. A forecast delivery time, a newly agreed deadline, and a submission owner’s decision are different pieces of information. Do not silently convert the forecast into a commitment.

Agree on a location that relevant people can access, such as the reply thread or assignment record. Keep decisions traceable so separate places do not carry conflicting dates. The check is complete when the information supports a clear next action and owner, not merely when someone has replied.

Related reading

• What Does Shinchoku Mean? Business Progress and Status Update Examples
• Weekly Campaign Progress Template: Filled Examples and Review Rules
• Marketing Team Task Management: Ownership, Backup, Approval, and WIP Examples

References (checked October 10, 2026)

• UK Government: GovS 002 Project Delivery