The first two weeks of a client project generate more adjustment data than any other period. The communication channel you set up might not match how the client actually works. The pace you estimated might feel too fast or too slow. Something in the brief may have shifted. An assumption you both made at kickoff may already be proving false.
Most of this feedback sits quietly in the client’s head because they don’t want to seem difficult this early. They decided to trust the process and wait. By Week 4, the quiet dissatisfaction has either resolved itself or compounded into a real problem. Either way, you didn’t know it existed.
The Day 14 check-in is a structured invitation for the client to tell you what’s not working before they’ve had time to build a case. It’s fast. It’s specific. And every client appreciates being asked before they’ve had to bring something up themselves.
Why Day 14, Specifically
Day 7 is too early. The client is still in the honeymoon period and doesn’t have enough experience to give useful feedback. Many first-week issues resolve themselves before you’d even ask about them.
Day 30 is too late. By the end of Month 1, patterns have formed. The communication norms you established have been reinforced for four weeks. A client who’s been getting responses slower than they expected has already calibrated their behavior around that, they’ve started following up more aggressively or have stopped flagging issues because they expect a delay.
Day 14 is the right moment because it’s long enough for patterns to emerge and short enough for them to change.
Schedule the Day 14 check-in during kickoff. Put it in both calendars with a note: “2-week pulse check-in, 15 minutes.” When you schedule it at kickoff, it becomes routine, not remedial.
The 5-Question Script
Run this as a call, not an email survey. A call produces honest answers because the client can hear that you’re asking in good faith. Email produces polished answers that are easier to soften.
The framing to open with: “This is a quick 2-week pulse I do on every project, it usually takes 12-15 minutes. I want to make sure how we’re working together is actually working. I’m going to ask you five questions and I want completely honest answers, because the goal is to catch anything small while it’s easy to adjust.”
Question 1: “Are the communication channels working for you?”
This covers: which tool you’re using, how fast you respond, when they hear from you, and whether they feel informed.
What to listen for:
- “It’s fine”, accept at face value, but follow up with “is there anything that would make it even easier?”
- “I’m not sure which channel to use for what”, they need clarity on routing: urgent things go here, regular updates go there, file sharing goes there
- “I wish responses were faster”, be honest about your capacity and agree on a specific window that works for both
- “I feel like I’m out of the loop”, add a mid-week async update (a one-sentence Slack message: “Day X progress: [status]”) to the operating rhythm
Communication friction is the most common Week 1-2 complaint and the easiest to fix. A single operational change, adding a Slack channel, switching from email to voice notes, moving to same-day replies before 5pm, can eliminate the friction entirely. You can’t make that change if you don’t ask the question.
Question 2: “Is the pace right?”
This covers: how fast deliverables are moving, whether deadlines feel reasonable, and whether the overall timeline is right.
What to listen for:
- “It feels fast”, this is a warning. Either they’re overwhelmed with review requests or they feel like they don’t have time to give good feedback. Either way, slow down the review cadence and give them more processing time.
- “It feels slow”, find out why they perceive it as slow. Is their actual deadline earlier than what you planned for? Did something change? Or are they just impatient by temperament? The answer determines the response.
- “The pace is fine, but [specific thing] is taking longer than expected”, this is useful feedback. Identify the bottleneck and adjust the project plan around it.
Question 3: “Has anything surprised you?”
This is the question that catches the things they were going to bring up eventually. Surprises can be positive or negative, both are worth knowing.
What to listen for:
- A process surprise: “I didn’t realize revisions worked that way”, clarify and confirm the agreement
- A scope surprise: “I thought [X] was included”, either confirm it’s included (if it is) or have the scope conversation now (if it isn’t)
- A resource surprise: “I didn’t realize I’d need to be so involved”, this is important. Either the brief underestimated their involvement, or they underestimated what the project required. Name it and set the right expectation for Month 2.
- A positive surprise: “I didn’t realize you’d [do something they valued]”, note this for your case studies and future positioning
Question 4: “Do you have everything you need from me to feel confident in how this is going?”
This is an inverse accountability question. You’re not asking if you’re doing well, you’re asking if they have what they need to trust the process.
What to listen for:
- “Yes, your updates are clear”, good. Stay the course.
- “I’d love to see more of the process/thinking behind decisions”, add brief rationale to your deliverables. One sentence: “I took approach X because Y.”
- “I’m not sure what stage we’re at”, send a visual of the project plan with the current week highlighted. Make progress visible.
- “I feel like I’m not sure what’s expected of me”, this means your briefing of their role wasn’t clear. Revisit the roles matrix and confirm what you need from them and when.
Question 5: “Is there anything you’d set up differently if we were starting over?”
This is the question that gets to the truth. By framing it as hypothetical (“if we were starting over”), you give the client permission to express a preference without it sounding like a complaint.
What to listen for:
- “The kickoff was a bit fast, I would have liked more time on [X]”, schedule a 20-minute follow-up to complete that conversation
- “I’d want to involve [Person] earlier”, make that happen now: “Let’s do that in Week 3. Can you make an intro?”
- “I’d have set up [different tool/process]”, assess whether the switch is worth making now. Minor process changes at Day 14 are low-cost. The same change at Day 60 carries switching costs.
- “Honestly, nothing, this is working well”, document it and use it in the renewal conversation at Month 3
Response Protocol After the Call
Within 2 hours of the Day 14 call, send a summary email:
Subject: Day 14 Pulse, Summary + Adjustments
Hi [Name],
Thank you for the 15 minutes today. Here’s what I took away and what I’m adjusting:
Communication: [Specific adjustment or “no change needed, current setup is working”]
Pace: [Specific adjustment or “staying on current milestone schedule”]
Open item from surprises: [Specific action or clarification]
One change I’m making based on your feedback: [Be specific, even if it’s small. “I’ll add a brief rationale note to each deliverable so the thinking is visible.”]
Week 3 plan: [Two sentences on what’s happening next week]
Anything I missed or want to add?
[Your name]
The most important line is “one change I’m making.” Even if everything was largely positive, identify something you’re improving. This signals that you listen and act, not just that you asked politely. The specific adjustment is worth more than the entire conversation.
What Changes After the Day 14 Check-In
Clients who go through a Day 14 check-in and receive a follow-up summary with an actionable adjustment know two things about you: you solicit honest feedback, and you act on it. That combination is rare enough that clients notice and remember it.
This changes how they communicate for the rest of the engagement. They’re more likely to flag small issues early because they’ve seen that flagging produces a response rather than defensiveness. They’re more likely to give candid feedback on deliverables because you established a norm of directness in Week 2.
The check-in is a 15-minute investment that pays dividends for the remaining weeks or months of the project. Build it into your kickoff as a standard calendar event. Never skip it.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
