Reporting to a US client: a weekly update format that builds trust

Your US client has not heard from you since Tuesday and has started to wonder, in a different time zone and with nobody to ask, whether the work is moving. A good weekly update answers that in four parts of plain English: what is done, what is next, what is blocked, and what decision you need from them. It fits on one screen and says the uncomfortable thing early. The client cannot see your team working, so the update is the main evidence that it is happening.

Why distance changes what a report must do

A client in the same city sees you. They notice the late night and the full desk. A client in Chicago sees nothing between messages, so silence reads as drift. The update fills that silence with facts, and it works best at a rhythm you have agreed with the client.

It also protects you. A short written record of what was reported, and what the client replied, can settle an argument about what was agreed.

The four-part format

Use the same four headings every time so the client knows where to look.

Subject: [Project name]: update for week of [date]

Done this week
 - [Result, in plain words, with a link if there is one]
 - [Result]

Next week
 - [What will happen, who does it, expected day]

Blocked
 - [What is stuck, why, what you need, from whom, by when]

Decision needed from you
 - [One question with your recommendation]

Anything else
 - [Only if needed]

Keep each bullet to a sentence or two. If a bullet needs a paragraph, it probably belongs in a call or an attachment.

How to fill each part well

Done. Write results, not activity. "Landing page is live and the contact form sends to your sales inbox" tells the client something. "Worked on landing page" tells them nothing.

Next. Name the day and the owner. "Draft of the email series, Anita, Thursday" can be checked. "Continue content work" cannot.

Blocked. Say what you are waiting for and who holds it. Do not soften it. If the blocker is the client, say so politely and say what happens to the date if it stays stuck.

Decision needed. Give a recommendation, not an open question. "Do you prefer A or B?" makes the client do the work. "We recommend A because X; please confirm by Wednesday" lets them reply in one word.

An invented example: a store-setup team in Indore

This team is made up. It is an Indore team that set up an online store for a US candle brand. Its early updates read "Store build in progress. Product upload started." The brand's founder asked on a call whether anything was behind. Nothing was, but nothing in writing showed it.

Here is the update after the team changed to the format above (details invented for illustration):

Done this week: 40 of 120 products uploaded with photos; checkout tested with a dummy card. Next week: remaining 80 products, Priya, by Wednesday; shipping rates, Arjun, Thursday. Blocked: we need your US shipping rate table. Without it, checkout shows a placeholder rate. Needed by Friday to keep the launch date. Decision needed: launch with flat-rate shipping for the first month? We recommend yes. Please reply by Thursday your time.

The founder replied "yes, flat rate, table coming Friday". The table actually arrived the following Monday, so the launch slipped by three days, but the slip was visible in writing from Thursday and nobody was surprised. The blocker had sat unnoticed for a week before. Giving it a heading where it could not be missed, with a recommended answer attached, is what changed.

When the news is bad

A late delivery is the same format with one change: the "Blocked" line leads the email, and the subject says so. Write what slipped, why in one sentence, the new date, and what you are doing to hold it. Do not bury it under the good news, and do not apologise in three paragraphs. A client who learns on Wednesday that Friday is at risk can plan. One who learns on Friday cannot.

Rules of tone

• Use plain words. Write "late" when you mean late.
• Use the client's calendar. Write dates with weekdays, and say whose time zone for times.
• Keep numbers consistent from week to week, so the client can compare.
• Attach nothing the client must open to understand the message.
• Acknowledge the client's answers, even if the reply is only "received".

Avoid performing busyness. A long list of small tasks suggests you cannot tell what matters. Three real results beat twelve minor ones.

What to leave out

Leave out hours worked, unless the contract bills by the hour. A client does not care that you spent nine hours on a page; they care that it works. Leave out tool names and internal jargon too. If your team calls a task "the sprint-three spillover", the client will not know whether to worry.

Leave out good news you have not yet checked. "Payment gateway working" should mean someone placed a test order. If it means "I think so", write "built, test order on Tuesday". Many clients forgive a late date more readily than a result that turns out untrue.

When to change the format

A weekly note suits live projects with steady movement. If the work is quiet for a stretch, say so in one line rather than skipping the update. For a long engagement, add a longer review a few times a year, covering results against the goals you set at the start.

A dashboard helps when the client wants numbers they can check any day (management dashboards and reporting covers that). Until the client asks a question the email cannot answer, the email is enough. For more on serving American clients from India, see the United States hub.

Send the first one in the new format

Open your last three messages to the client, rewrite the most recent one in the four-part format, and send the new version at the next update. Ask the client whether the headings suit them, and adjust once. For help setting up reporting for a client base, tell us what you need.