To ask a client for feedback mid-project, send two short asks while the work can still change: one the day after the first deliverable, one halfway through the timeline. Each ask is a score from 0 to 10 and one open question, sent by the account lead. A low score gets a phone call, not a reply. Atwork's Client Feedback Tracker template sets all of it up.
Why ask for client feedback mid-project instead of at the end?
Ask mid-project because a low score is only useful while you can still act on it. At handover the project is finished and a 6 is a grade. After the first deliverable, the same 6 is a change you can make before the next one, and the next ask tells you whether it worked.
You may also not see the problem from your side. In Setup's 2023 Marketing Relationship Survey results, clients ranked dissatisfaction with delivery as their second-most-common reason for ending an agency relationship. Agencies ranked delivery ninth. Asking during the project surfaces that gap while you can still close it.
| Asked only at handover | Asked mid-project | |
|---|---|---|
| A score of 6 is | A grade on finished work | A fix you still have time to make |
| What you can change | The next project, if there is one | The next deliverable |
| What the next ask tells you | Nothing, until the next project | Whether the change worked |
When should you ask a client for feedback during a project?
Ask at three fixed points: the day after the first deliverable the client can react to, halfway through the timeline before the last big round of work, and in the week after handover. Put all three in the plan when the project starts, with a date and a sender, so the asks don't depend on anyone remembering.

The first ask catches a wrong assumption while one deliverable is affected, not five. The second catches what has drifted since kickoff, such as a new approver or a date that moved on their side. The handover ask is the one you compare against.
These asks are about working with you, not about a draft. Comments on a draft are a revision round, which why client approvals multiply revision rounds covers.
What one question should a mid-project ask contain?
A mid-project feedback ask is a score from 0 to 10 plus one open question that asks for something specific. The score lets you compare answers across milestones and clients. The open question tells you what to change. Two questions fit in one short email; a ten-question survey becomes a task the client puts off.
When Fred Reichheld and a Bain team tested questions against what customers actually did, likelihood to recommend came out on top. In 11 of the 14 industry case studies they compiled, no other question predicted behaviour as well. The number alone doesn't tell you what to do:
"Asking a customer to tell us in their own words why they gave a score is what helps us understand how we can take action and continuously improve." Bain & Company, The History of Net Promoter
Keep it to those two questions. In SurveyMonkey's analysis of 100,000 surveys, published in 2010, drop-off rose fastest with each question added, up to about 15 questions.
| Ask | When to send it | The question |
|---|---|---|
| First deliverable | The day after the first deliverable | From 0 to 10, how is it going so far, and what is one thing we should do differently on the next deliverable? |
| Mid-project | Halfway, before the last big round of work | From 0 to 10, how sure are you that this project ends where you want it? What would raise that by one point? |
| Handover | In the week after handover | From 0 to 10, how likely are you to recommend us to a peer? What would you tell them about working with us? |
The mid-project question asks about the outcome, not about you, which is easier to answer honestly while you still work together. "What would raise that by one point?" asks for one doable thing instead of a list.
How do you log client feedback so the team acts on it?
Log every client feedback answer as one row: the client's words, who answered, the score, a theme and a next step. The theme shows where you lose points across clients. The next step is a decision someone makes on each answer: follow up on a low score or a named problem, or note it and move on.

- What they said, in their words. "We just never know what is waiting on us" and "approvals feel rushed" are the same problem; a summary would hide that.
- Score and theme. Communication, Quality, Speed, Value, Team or Results. In the template's example data, seven answers average 8.4 and Communication sits lowest at 6.0.
- Next step. Follow up when the score is 6 or lower or the answer names a problem. Noted when nothing needs doing.
You don't have to pick the theme by hand. In Atwork, open the Theme column's header, choose Autofill, then AI, and let it read What they said: each new answer gets a theme when it arrives (how to fill a field automatically). The score and the next step stay with a person.
The log is for your team. What the client sees belongs in the monthly client report and, if you run one, your client portal.
What do you do with a low client feedback score?
When a client scores you 6 or lower, call within two working days instead of replying by email. Ask what happened, agree one change, and write it down where the team will see it. Then ask again at the next milestone: the next score tells you whether the change worked.
Bain's Rob Markey and Fred Reichheld describe Net Promoter leaders such as Charles Schwab and Apple's retail division working to contact every customer who gives a negative rating within 24 hours. That way, the disappointing event is still fresh in the customer's mind. Two working days is the agency version.
- Call, don't email. A written reply to a 6 reads as a defence.
- Ask what happened, then agree one change. "A fixed approval slot every Tuesday" is a change; "better communication" is not.
- Write it next to the answer, so the team sees it before the next deliverable.
- Ask again at the next milestone. A higher score means the change worked.
In the template's example data, Harbor Dental scored the first deliverable an 8 and added, "We just never know what is waiting on us." At mid-project it came back as a 6: "Approvals feel rushed." The account lead called the next day and agreed a fixed approval slot every Tuesday. Read the comment on an 8 as closely as a 6. And an ask nobody answers is a signal too: call before the next one goes out.
A run of low scores is also the material for a year-end client review, long before the renewal.
How do you set it up with the Client Feedback Tracker template?
Install Atwork's Client Feedback Tracker, add your clients, and create three asks per project with a due date and the person who sends each one. Every ask then lands in that person's My Tasks on the day it is due. Answers sent through the template's Client feedback form arrive as rows in Responses.
- Install Client Feedback Tracker.
- On Clients, add each client with the account lead and their main contact.
- On Asks, add the three asks for each project, with the send date as the due date and the sender as the assignee.
- Publish the Client feedback form (the Getting started page shows where) and send its link with each ask, worded as on the Ask scripts page.
- Mark an ask Done when it goes out, then set Reply to Answered or No reply.
- On each answer in Responses, link the client and the ask, set the Next step, and fill in What we change for every Follow up.
- Check the Average score by theme chart before each client's next milestone.
Frequently asked questions
How many feedback asks are too many?
Three across a project of a few months, one question each, is light. For a project shorter than a month, skip the mid-project ask. On a retainer, send the mid-project question once a quarter.
Who should send the ask, the account manager or the project manager?
The person who owns the relationship, usually the account lead, because they also make the call on a low score. Account manager vs project manager sets out who owns what.
Should you calculate an NPS from these answers?
Not with a handful of clients: with seven answers, one client changing their mind moves the score by 14 points or more. Read the answers and the average by theme instead.
Where should you start this week?
Pick one live project past its first deliverable and send its mid-project question this week. If the answer is a 6 or lower, book the call before you reply to anything else. When an answer is one you would like to quote, ask first: the template's Testimonials sheet keeps the client's yes on record.
Install Client Feedback Tracker, add one live project, and send its mid-project ask this week. Start free
