Reply to a Follow-Up When Work Is Still in Progress

Answer the status question first, distinguish completed work from remaining work, and explain any dependency. Include a delivery date or next update only when you can actually confirm it.

By MailCat · Published 9 October 2026

Give a status the recipient can use

A follow-up often asks more than “Did you see this?” The sender may need to decide whether to wait, move a meeting, or supply something you need. A useful response states what is complete, what remains, and what action would move the work forward.

Do not confuse an acknowledgment with a progress report. “Thanks for checking in” is courteous, but it cannot replace the answer. Equally, “almost done” is hard to use unless you explain the remaining work and know what that means for timing.

Worked example: progress known, completion uncertain

Known facts: Ellis has revised the introduction and navigation instructions. The new access steps have not been incorporated because the team has not supplied its final process. The guide is not ready to circulate. Ellis cannot confirm tomorrow's delivery or a reliable update time.

The response does not turn partial progress into a complete deliverable. It also names the missing input instead of saying “waiting on your side,” which may sound accusatory without helping the sender act.

A reusable status map

1. Complete: identify the actual finished work, not your general effort.
2. Remaining: state the specific unfinished step.
3. Dependency: name the input or decision required, and its owner if known.
4. Timing: give a verified commitment, a conditional estimate, or an explicit unknown.
5. Next action: tell the recipient whether to review, wait, send an input, or choose an option.

Keep these facts separate before drafting. If you do not know whether a requested change is complete, inspect your work rather than guessing from an earlier plan. Avoid presenting a target date as a promise just because the sender hoped for it.

Alternative: progress and delivery are both confirmed

Known facts: in this separate scenario, Ellis has received and added the final access steps. Only proofreading remains. Ellis has checked the remaining work and chosen to commit to Thursday at 2 PM UTC.

This version earns its confident wording from the supplied facts. Reusing it when you only hope to finish Thursday would change its meaning.

Alternative: an unresolved decision blocks progress

Known facts: the account-approval owner affects the instructions. Ellis can organize the existing material, but cannot finish that section correctly until the team chooses an owner.

Review the tone without hiding the status

Acknowledge a missed commitment directly if one exists: name the agreed date and give the true current position. Do not invent an apology for a delay that has not occurred. Avoid “rest assured” or “everything is on track” when the evidence is a blocked task.

In MailCat, supply your progress, remaining task, and timing decision before compiling a reply. Check that the preview has not introduced a checkpoint or completion claim. You review, explicitly insert, and send the reply yourself. See professional client reply examples for structure.

• Does the first substantive sentence answer the status question?
• Are completed and pending tasks separated?
• Are dates supported by your actual decision?
• Is the missing input specific enough to provide?
• Would the sender know whether this version is ready to use?

For mixed known and unknown answers, see replying with unanswered questions. Before sending an assisted draft, use the draft-review checklist.