How should a freelancer report project status to a client?

Report status in a short message at the same time every week. Lead with numbers, name the next date and say what you need from the client. Keep the long explanation for when someone asks. A client reading a status wants one answer above all, which is when it will be done.

In the video, Arjun, a freelance developer, answers Catalina’s questions with long replies late in the evening. They contain no numbers and no date. Catalina, his client, tells him what she needs. It is not an explanation. It is a date.

What does a good project status update contain?

A good status update has five parts. They are progress in numbers, the next date, risks, what you need from the client, and any change to scope. Keep each part to a line. If a part has nothing to report, write “none”, so the client knows you checked.

• Progress. A number, not an adjective. “Seven of twelve pages are done” beats “good progress.”
• Next date. The next milestone and the day it will be ready.
• Risks. Anything that could move the date, and how likely it is.
• What you need. Decisions, access or content, with a deadline for each.
• Changes. Anything that affects scope, budget or the date.

A full update can look like this.

Seven of twelve pages are done. Checkout is next, and it will be ready on Thursday 20 March. One risk remains, because I still have no payment test account. I need it by Monday. Scope and budget are unchanged.

Why do long replies fail as status updates?

A long reply answers the writer’s worry, not the reader’s question. It explains what was hard and why things took time. The client wanted to know where the project stands and when it will be done.

Length also hides the answer. If a date or a decision sits in the fourth paragraph, the client has to hunt for it, and may miss it. A long message sent late in the evening also signals that something is wrong, even when nothing is.

Numbers fix both problems. They are short, they can be compared from one week to the next, and they show that you are in control. When there is bad news, a number and a new date still serve the client better than three paragraphs of context.

How often should a freelancer send a status update?

Weekly is a good default for projects that run for several weeks. Send the update on the same day and at the same time, so the client knows when to expect it. Friday works well because it closes the week, and the client starts Monday with a clear picture.

For short projects, send an update at each milestone instead. For long ones, keep the weekly rhythm and add a deeper review every month.

A fixed rhythm also makes time zones easier. Agree one meeting time that works for both of you, and make the written status the default for everything else. When you are hours ahead of the client, send the status before their day starts, so it is waiting when they open their laptop.

How do you find out whether your communication is a problem?

Ask the client, and ask in the same way every time. You may feel you communicate a lot, while they feel they never know where things stand. Both can be true.

In Feedback Journey’s Service Delivery survey, Communication is one of four fixed categories. The question asks how satisfied the client is with your communication and availability throughout the project. Its guidance asks whether their questions were answered without waiting too long, and whether your promises were fulfilled.

In the video, Catalina gives Communication a 6. On Feedback Journey’s scale, a 6 reads as average, with room to improve. The score alone does not say what to change, but the message is clear enough. She needs to know when to expect answers.

How do you turn a low Communication score into a plan?

Set an improvement goal with a clear action, and track it in the next survey. In Feedback Journey, you create an improvement goal from a completed survey. You name the goal, choose the categories to improve, set an end date, describe the starting situation and write an execution plan.

Arjun names his goal “Friday status” and chooses Communication. His plan has two lines. One is a fixed meeting time. The other is a short status, with numbers, every Friday.

A goal runs in three phases. The first week is for planning. Then comes the execution phase, where you keep a journal and send new surveys to track progress in the categories you chose. The last week is for a conclusion, where you judge whether the goal succeeded. Because progress is continuous, even a small improvement counts as success.

In the video, the next survey shows Communication at 8. The new rhythm worked, and the numbers show it. A goal turns a wish to “communicate better” into a result you can point to. To see what makes clients go quiet in the first place, read why client silence is not a sign that everything is fine.

What should you avoid in a status update?

• Apologies and long backstories. State the fact and the new date.
• Vague words. “Almost done” and “going well” cannot be checked.
• Burying a problem. Put bad news in the first lines, together with what you are doing about it.
• Changing the format every week. A fixed structure lets the client scan for what changed.

What happens in the video?

The video is under a minute long. The text on screen tells the story, so it works without sound. The people in it are fictional, and the video is AI-generated. Here it is as text, in the order it plays.

1. Title card. “Is a long reply a good update?” Arjun, a freelance developer, and Catalina, his client, are introduced.
2. A long reply. On screen, “A long reply, late in the evening.” Arjun sits at his laptop and writes a long answer to Catalina.
3. No numbers, no date. On screen, “No numbers. No date.” Catalina reads the long reply. She says, “I don’t need an explanation. I need to know when it’s done.”
4. From long replies to a plan. An infographic shows three steps. A short survey after each milestone. Four questions from 0 to 10, plus a comment, on Expertise, Communication, Expectations and Quality. A goal in Communication, tracked in new surveys.
5. The score. On screen, “Communication gets a 6.” Arjun reads the result of the survey.
6. The goal. An example goal card, labelled “Example”, shows an improvement goal named “Friday status”, with the category Communication. The execution plan has two lines, “A fixed meeting time” and “Short status, with numbers, every Friday.”
7. The next survey. On screen, “Next survey: Communication 8.” Catalina reads a short status and smiles.
8. End card. “Set a goal, and track the progress.” The card shows feedbackjourney.com and the note “AI-generated. Fictional characters.”

Frequently asked questions

Try it with your next client

Create your first client survey in the Feedback Journey app, or read more guides on collecting honest feedback.

Create your first surveyMore guides