# How Consultants Keep Client Projects Moving - Published: 2026-10-19 - Author: [Consultant Magazine](https://consultantmagazine.co/author/consultantmagazine-co.md) - Topics: [Q&A](https://consultantmagazine.co/qa.md) - Source: https://consultantmagazine.co/qa/how-consultants-keep-client-projects-moving/ - Publisher: Consultant Magazine ### Clarify Dependencies and Ease Responses When a project stalls because we are waiting on a client, I try not to make the conversation about blame. Usually there is a reason something has not moved, even if it is simply that the client has ten other priorities competing for attention. My first step is to make the dependency very clear. Instead of saying "we are still waiting for this," I explain exactly what we need, why we need it, and what it is currently blocking. That makes the consequence visible without making the message confrontational. At spectup, this matters because a fundraising or advisory process can have several moving pieces that depend on information arriving at the right time. I also try to make the request as easy as possible to action. If I can reduce a long list of questions to a few specific items, I will. Sometimes the best approach is simply giving the client a clear choice rather than sending another open ended request. I have found that people respond faster when they understand what decision they actually need to make. If something is genuinely urgent, I will say so, but I try not to manufacture urgency. The relationship is more important than winning one email exchange. One thing I have learned is that repeated reminders usually become less effective when they contain no new information. A better follow up explains what has changed and what will happen once the missing piece arrives. That keeps the conversation focused on progress rather than frustration. In the end, I want the client to feel that we are helping them move the project forward, not chasing them for paperwork. That small difference in tone can make a surprisingly big difference. --- ### Park Blockers With Preset Paths 1\. Stop chasing and re-sequence trading forex VPS broker migration. The number of dependencies for broker migration for our clients can reach 40. However, even one client-dependent step such as server credentials or cutover approval can block the whole team. In such a case, I simply park the step and direct the rest of the team to work that does not depend on that step. Blocked steps and the reasons for them are then logged with the timestamp. What people hate is nagging them until they respond. Logging the blocker is far better than chasing after the same person. 2\. Default decisions. This is a message I send to clients: "Provisioning to trade in Frankfurt on the standard trading config unless I hear otherwise by Wednesday 5pm". Clients prefer to make a choice over having one made for them and so most respond within hours. Where there are things that I cannot make a default decision on regarding a client, then I contact the person who actually signed off the compliance document (not the day-to-day contact of mine who merely forwards on emails relating to the document). In all cases though I try to keep it very short: 3 lines or so - one question, one issue, one deadline. That gets far better results than a lengthy and polite email that will likely get skimmed and then shelved whilst something is grabbed from between other meetings on a phone. --- ### Use Color Codes to Unblock Care I was tired of our projects stalling because we were waiting on one signature or one document. I tried something different, a quick email update with colors. Red meant we were blocked, yellow meant waiting, and green meant we were good to go. I just asked how I could help unblock them. It kept everyone in the loop and focused us on what actually matters. Keeping patients safe. --- ### Offer Launch Alternatives, Not Open Requests A branded-residence client in Dubai sat on a floor plan approval for three weeks last year while our launch campaign was ready to go. Every day we waited, the ad spend we had already booked for the launch window got less effective, and the frustration on our side started leaking into emails that read as pressure rather than partnership. What changed the dynamic was replacing open-ended check-ins with a specific choice. Instead of "any update on the approval," we sent "we can launch Tuesday with floor plan A or wait until the 15th for the final version, which do you prefer." Giving the client a decision to make, rather than a task to complete, moved things in two days after three weeks of silence. The approach holds up because it respects why clients stall: they are usually avoiding a decision, not ignoring us. A forced-choice question removes the ambiguity that let the delay drag on, and it reads as helpful rather than as a complaint about their timeline. --- ### Escalate Through Shared Support Escalation should feel like support for the relationship, not punishment for a missed reply. I first give the day-to-day contact a private, practical route to resolve the delay, including a draft they can forward internally and a suggested decision date. That protects their credibility and often unlocks movement quickly. If broader involvement is needed, communicate it as a joint effort to protect the shared plan. Include the original contact, summarize the facts without judgment, and ask for help confirming ownership and timing. Leaders usually respond well when escalation is precise and solution-oriented. The goal is never to create discomfort. It is to restore a dependable decision rhythm that allows both organizations to execute with confidence. --- ### Quantify Lost Traffic and Present Options At Backlinker AI, when clients take forever to respond, I learned to stop saying "we're waiting on you" and instead show them exactly what traffic they're losing each day. That gets their attention fast. We had projects sitting dead for weeks until I started giving them three options: shrink the project, push the deadline, or pay for more help. People like having choices. Now I just lay out the numbers and let them decide what to do next. --- ### Map Risks and Bridge Internal Roadblocks Restoring momentum without creating resentment requires shifting the narrative from a request for information to a shared assessment of project risk. Resentment builds when a consultant treats a client like a delinquent student; instead, frame missing approvals as critical dependencies that directly impact success metrics or go-live dates. In enterprise delivery, a vague "just checking in" email is less effective than a concise Impact Analysis that illustrates how a two-day delay in a signature translates into a two-week delay for the final rollout due to lost resource windows or scheduling conflicts. Stalls often happen because a client contact is facing internal friction, such as a pending legal review or a security compliance hurdle they do not know how to navigate. Rather than repeating the request, offer to act as a bridge by joining a brief call with their internal teams to address specific technical questions directly. This transforms the consultant from a persistent solicitor into a proactive problem-solver, allowing the client to save face while providing them with the tools to unblock the project. Maintaining the relationship requires transparency without blame, which is best achieved through a live Roadblock Log visible to all stakeholders. Documenting the status of every dependency in a shared environment makes the stall a neutral data point rather than a personal failure. This creates a culture of accountability where the focus remains on the finish line, helping the client navigate their own internal landscape to reclaim the project's original vision. --- ### Trim Requests Before Seasonal Closures A founder we work with went quiet for 5 weeks in the middle of building his data room. He was not avoiding us. Indian companies more or less disappear into year-end closing every February and March. Nobody on our side had planned for it. Our IB team prepares fundraising material for early-stage founders. Chasing founders harder rarely works for us because the founder is usually behind on 10 things that feel more urgent than a cap table. What works is shrinking what you ask for to 3 items with a date beside each, with everything we can fill in already filled in. One of our senior analysts books the April catch-up call before the quiet even starts. --- ### Send Brief, Direct Notes When work gets stuck I don't send people full memo style instructions anymore. Instead, I keep it quick and simple (e.g., "can you send the two assets and we start on Monday?") and close with, "call me if this is unclear." It's quicker for everyone to respond, it doesn't seem like you're pushing them and work gets done, even if late. --- ### Convene Signatories for a Quick Call When a client stops answering emails about approvals, I don't keep sending them. It never works. I just set up a 15-minute meeting with everyone who has to give the okay. After watching a few big repair projects stall, this is the only thing that reliably gets things moving. I'll start the call by saying we all want the same thing here, so let's find out what's blocking us. --- ### Resequence Tasks Around Absent Inputs In my agency days, when a project stalled because the client had not supplied an approval or key information, I tried to make the dependency visible without making the client feel blamed for it. I would show what we had completed, exactly what was blocked, what we needed from them, and what work could still move forward in parallel. The approach that worked best was re-sequencing the project rather than letting one missing input freeze everything. Giving the client one clear decision or action, along with the impact of waiting, usually got a faster response and kept the relationship constructive. Do not let one blocked input stop every useful piece of work. --- ### Establish Response Norms at Kickoff My AI projects kept getting stuck waiting for client feedback. It was frustrating. Now, I use a simple dashboard that shows every deadline and sends a reminder when one's coming up. It keeps everyone on the same page. The real trick, though, is talking about how fast they can respond before we even start. Then those reminders just feel like a team nudge, not me chasing them down. --- ### Hold Bottleneck Huddles to Reset Roles At Patron Accounting LLP, I've learned to be direct. I tell clients that a delayed ITR filing means penalties, or a stuck payroll setup means they can't hire. When something goes wrong, we get on a quick bottleneck huddle with the client. We walk through the process together, find where the approval is stuck, and reset who owns what. That way we solve it as a team, not by pointing fingers. --- ### Reveal Schedule Domino Effects When clients go silent on SEO projects, I send a simple email showing exactly what's done, what's waiting on them, and concrete date impacts. Last month, a client hadn't approved meta descriptions for three weeks. I showed them how their launch would slip to Q4, and they responded within hours. It's not about pressure - it's about clarity. They see the domino effect of their delays, and suddenly they're part of the solution, not the bottleneck. --- ### Define Delay Costs at Onset Client delays on approvals are usually a signal they don't understand what happens if they don't move, not that they don't care. We had a project where Pageloot was integrating QR scanning into a client's workflow and the approval chain broke at their CMO for three weeks. The work was ready, the team was waiting, and resentment was building internally. Instead of sending a status update email (which just adds to their inbox noise), we called and said: "We're blocked on your sign-off, which means our team is either sitting idle or jumping to another client's work. If you jump us back of queue, that's fine, but we need to know now so we can plan." We gave them a choice with real consequences attached, not a guilt trip. They approved in two days. The difference was specificity. "We need your feedback" is abstract. "If we don't hear by Friday, the earliest we can ship this is three weeks from now" is concrete enough that they feel the cost of delay, not just the weight of a decision. The harder move is earlier: at kickoff, you have to establish what blocks actually look like and what the cost of delay is in terms they care about. "If approvals take longer than two weeks, here's how the timeline shifts." Most consultants skip this because it feels transactional. It's not. It's the conversation that keeps resentment from building in the first place, because they chose the terms when they were paying attention. --- ### Assign Gatekeepers and Reassess Priority When a project stalls waiting for client approval, another "just checking in" email rarely helps. I try to make the decision easier instead. I'll send a short message explaining exactly what's needed, what I recommend, and which part of the project is affected if the decision gets delayed. It gives the client something specific to respond to rather than another reminder sitting in their inbox. At Stride, we also agree on one person responsible for approvals during onboarding. We use a shared Slack channel for feedback and a short weekly call to resolve anything that needs discussion. If something still isn't moving, I'd rather ask whether the priority has changed than make someone feel they're holding everything up. That usually opens a much more constructive conversation. --- ### Automate Prompts Through Team Portals At my aesthetics academy, approvals would get stuck and information would go missing. During a big training session last month, we were drowning in follow-up emails. So we tried a shared portal that pings everyone with their next task. No more chasing people down. The key is telling everyone upfront when you need their stuff. Then the reminders actually help instead of adding stress. --- ### Frame Disclosures as Compliance Paths Having led legal and compliance teams and now advising General Counsel at Rule Ltd, I frequently navigate complex due diligence engagements that stall waiting on client disclosures or sign-offs. I restore momentum by replacing open-ended document requests with structured decision rules, asking only for targeted proof like beneficial ownership declarations rather than broad file dumps. When approvals bottleneck during counterparty reviews, I present the delay as an objective governance choice--such as proceeding within existing risk thresholds, applying mitigations, or escalating to enhanced due diligence. Framing the required response around regulatory defensibility and clear escalation paths removes personal friction and enables the client to act with confidence. --- ### Specify Choice, Impact, and Ownership I've spent 20+ years scaling healthcare technologies, and at CortiCare delays usually involve busy hospital teams, approvals, IT/security, staffing, or clinical workflow. My first rule is to make the stall about the work, not the person. What works best for me is a "decision, impact, owner" message: "We need one decision on EEG coverage workflow; without it, ICU go-live planning and local team staffing stay unresolved; is this owned by neuro, IT, or operations?" It keeps the conversation factual and gives the client a clean way to re-engage. A lesson from neurodiagnostics: when call burden was crushing staff, vague complaints went nowhere, but specific patterns changed the discussion. Instead of "we're getting called too much," I'd show what calls were happening, why they were happening, and where the routine EEG-to-continuous EEG handoff was creating avoidable friction. The tone I use is: "I'm trying to protect your team and your timeline." People respond better when they feel you are reducing chaos, not assigning blame. --- ### Divide Approvals Into Tiny Steps When a project stalls on the client's side, it is rarely due to reluctance. Often, the request is too complex to address quickly. For example, "We need your approval on the design package" may remain unanswered for weeks, while a specific question like "Do you want the railing in option A or option B, so we can submit for permits?" receives a prompt response. When momentum slows, I break down pending items into the smallest actionable decisions to move the project forward. I also connect each decision to the client's objectives rather than our internal schedule. In bridge construction, delayed approvals can result in missing permitting cycles or seasonal work windows in sensitive environments. Clarifying that their opening date depends on a timely decision is not pressure; it provides essential information. My preferred approach is to jump in before any delays occur. On day one, we outline every decision the client will make and identify when each becomes critical, allowing them to track their responsibilities alongside ours. This way, follow-ups reference a shared plan rather than appear as reminders. If progress stalls, I call instead of sending repeated emails. A brief conversation often reveals the true obstacle, such as an unexpected stakeholder needing approval, and resolves the issue efficiently and respectfully. --- ### Ask Clients to Pick a Day I stop asking when the client can send it and ask them to pick the day. A vague request leaves the client with nothing to do today, so it slides. I name the exact item, say what it unblocks, and ask which day they'll send it. A 2006 meta-analysis by Gollwitzer and Sheeran covering 94 tests found that plans naming when and where someone will act had a medium-to-large effect on follow-through. Then I make yes easy. One link, a short list of what's still missing, and a reminder the day before their date. If the date passes, I follow up on what the delay is holding up, not on the person. "The kickoff moves until this arrives" is a fact, so nobody has to feel blamed. I ran a content design practice that onboarded clients through Google Sheets, DocuSign and email, which is how I learned how much of the chasing is avoidable. --- ### State Stakes and Simplify Actions I've spent over 25 years litigating personal injury cases, and 100% of my practice is litigation, so stalled information is something I deal with constantly. Clients, doctors, insurers, courts, and opposing counsel all create bottlenecks if you let the file drift. The communication that works best is: "Here is the decision I need, here is the consequence if it waits, and here is the smallest next action." In a Michigan no-fault/PIP case, I won't say "please send everything"; I'll say, "I need the therapy bills from March and April or those dates may become unrecoverable under the one-year-back rule." I also try to remove shame from the delay. Many injured clients are overwhelmed, so I frame it as, "You focus on healing; I'll organize this, but I need this one item from you today." For approvals, I send a short "approve / revise / call me" message with the exact deadline and what happens next. People respond faster when they are not being blamed and do not have to decode what you actually need. --- ### Set Communication Rules Upfront I always start projects by sorting out who decides what, how we'll talk, and how fast we need responses. When people are juggling multiple tech projects, it's easy to lose track. Setting these rules upfront means nobody gets surprised when things need to move up the chain. A quick email has saved us days of confusion before, and clients like knowing what to expect without all the back-and-forth. --- ### Test Alternatives When Plans Change If a project goes quiet, I just ask if their priorities changed. A client was stuck waiting on branding assets, so I suggested we test the first piece of automation while we waited. It kept us from losing steam and took the pressure off. They replied way faster, too. Basically, stay flexible and let them feel in control. It keeps things moving. --- ### Offer a Timed Default Most stalls happen because the client has twelve other things on their plate and my request looks like work. So I make the next step smaller than whatever is sitting ahead of it in their inbox. I send one email with one question, and I attach a default with a date: "Quick one on \[project\]: do you want the reporting to cover A or B? If I don't hear by Thursday, I'll go with A so we stay on schedule. You can change it later." Three things make this work. It asks for a decision, not a document. It is answerable in ten seconds from a phone. And the default puts the cost of silence on the calendar instead of on the person, so nobody has to feel chased. If a second nudge is needed, I change the channel instead of repeating the email. A two-line message or a five-minute call usually clears in a day what three emails did not. --- ### Related Articles - Turn Silent Client Stakeholders Into Decisive Partners in Consulting Projects - Unlock Stalled Client Decisions in Consulting Projects Without Escalation - Turning Consulting Buy-In Into Action: Follow-Through Habits That Drive Implementation