“I’m Working on It” Isn’t a Status Update
“I’m working on it” answers one question: Have you started? It leaves the more useful questions hanging. What’s done? What’s left? Is anything in the way? When will someone hear from you again?
A better status update doesn’t need to be long. It needs to give the other person enough information to plan their next move: what has changed, what happens next, and whether you need anything from them.
Compare these two replies to “How’s the presentation coming?”
“I’m working on it.”
“The outline and first six slides are drafted. I’m checking the figures now and will send you a version to review Thursday afternoon.”
The second reply won’t win a poetry prize. It will, however, tell the reader what they came to find out.
Why the Usual Reply Falls Short
“I’m working on it” isn’t dishonest or impolite. Sometimes it’s exactly right—especially if someone asks five minutes after assigning you a task. But once people are waiting on your work, the phrase can become a conversational holding screen: reassuring in appearance, short on information.
The same goes for “Making progress,” “Nearly there,” and the suspiciously elastic “Should be done soon.” Soon might mean before lunch to the sender and next Tuesday to the recipient. Neither person knows they disagree until the deadline arrives wearing a tiny surprise hat.
This isn’t a call to report every keystroke. It’s a call to share the details that affect someone else’s decision. Project-management guides from Asana and Atlassian both emphasize progress, obstacles, and next steps in useful updates. You can borrow that structure without turning an ordinary email into a formal report.
Use the Done–Next–Need Formula
When you’re not sure what to say, try three small pieces of information:
- Done: What have you completed or confirmed?
- Next: What are you doing now, and when can the reader expect the next result or update?
- Need: Is there a decision, answer, or resource you need from someone else?
You won’t need all three every time. The point is to replace a statement about your effort with a statement about the work.
“I’ve checked the first two invoices. I’m reconciling the third this morning and expect to send the summary by 3 p.m. No action needed from you.”
That’s a complete update in three sentences. If the task is simpler, one will do:
“The revised invitation is drafted; I’ll send it for your approval by noon.”
Notice the word drafted. It’s more informative than “done” because it distinguishes work that exists from work that’s ready to use. “Sent,” “approved,” “tested,” and “published” each describe a different milestone. Choosing the right verb is a small way to avoid a large misunderstanding.
It also helps to lead with the point: put the information the reader needs first, then add context if it matters. Nobody should have to read a paragraph about your busy morning to discover that the draft is ready.
Give the Reader Something They Can Actually Plan Around
A useful update often answers a quiet question: When should I check back? “I’ll send an update tomorrow at 2 p.m.” is a commitment the reader can use. “I’ll keep you posted” is a pleasant intention with no calendar attached.
Choose the promise you can realistically make. If you can commit to a finished file, say so. If you can only commit to knowing more, promise an update, not a result:
“The supplier hasn’t confirmed the price yet. I’ll check again tomorrow morning and update you by 11 a.m., even if the quote is still pending.”
That final clause matters. It tells the reader they won’t have to chase you simply because the situation hasn’t changed.
Be equally careful with uncertainty. An estimate is fine when it’s labeled as one: “I expect to finish Friday, provided the figures arrive by Wednesday.” That’s clearer than either pretending Friday is guaranteed or refusing to offer any timing at all.
Say What’s Blocking You—Without Writing a Defense Speech
A blocker is something preventing the next step: missing feedback, an unanswered question, a technical problem, or a decision only someone else can make. Naming it is useful; cataloging every frustration it has caused usually isn’t.
Compare:
“There have been various issues with the file, so I’m still working on it.”
“I can’t finalize the handout until the event time is confirmed. Could you confirm whether it starts at 6 or 6:30? Once I have that, I can send the final version.”
The second version identifies the obstacle, makes a specific request, and shows what will happen afterward. It doesn’t imply the other person has failed a character test. It simply opens a route forward.
If a deadline is at risk, say so before it passes. Separate what you know from what you’re proposing:
“The interview notes are complete, but I need another day to verify the figures. I won’t have the final report by Thursday. Could I send the verified version Friday afternoon? I can share the draft today if that would help.”
An extension is a request, not a date you get to announce as settled. For more on making that request clearly, see how to ask for more time without sounding unprepared.
Match the Update to the Moment
Not every situation deserves the full Done–Next–Need treatment. The art is choosing the smallest update that answers the real question.
When You’ve Just Started
Don’t manufacture progress. Say what you’re starting with and when you’ll know more:
“I’ve started reviewing the applications. I’ll have an initial shortlist by Wednesday afternoon.”
When You’re Waiting on Someone Else
Avoid making “waiting” sound like the entire plan:
“The design is ready for approval. I’ve sent it to Maya and will follow up Thursday if I haven’t heard back. After approval, I can prepare the final files.”
When the Work Has Changed Direction
Explain the change, not merely the activity:
“The first draft included all five topics, but it was too long for the newsletter. I’m narrowing it to the three that answer readers’ main questions and will send the revised draft tomorrow.”
When Someone Needs to Act
Put the request where it cannot hide:
“I’ve finished the comparison. Could you choose option A or B by Tuesday at noon? I can then prepare the order for Wednesday.”
That is more helpful than ending with a vague “Let me know what you think.” The reader knows exactly what decision you need and when. A useful update should make the next action easy to spot, a principle also reflected in Atlassian’s guidance on project status reports.
Don’t Confuse Detail With Clarity
Once you start being specific, it’s tempting to include everything: the calls you made, the tabs you opened, the spreadsheet that briefly looked haunted. Resist. A status update is not a diary of your effort.
Before sending, ask:
- What’s different since my last update?
- Does the reader need to adjust a plan or make a decision?
- Have I said when they’ll hear from me again, if that matters?
If a detail changes none of those answers, you can probably leave it out. If the work involves several teams or a significant change, add more context or link to the relevant document. For an ordinary task, a few well-chosen sentences are often enough.
There’s also no need to ban “I’m working on it” from your vocabulary. In a quick conversation, it can be a perfectly friendly start. Just don’t let it be the whole update when someone is depending on what you do next.
The goal isn’t to sound busy, polished, or impressively managerial. It’s to make the state of the work visible. Tell people what’s done, what’s next, and what you need—and they can stop guessing and start planning.