An implementation on hold letter for customer delays formally pauses the rollout. It names the customer-owned items still outstanding and the dates you followed up, and it states what happens to your team, the go-live date and billing during the pause. It also tells the sponsor which actions and decision will restart the work, and by when. Write it as a factual record, not an apology, and send it only after earlier follow-ups have gone unanswered.
The sections below follow the order you will work in: decide whether a pause is right, gather the evidence, settle the commercial terms, send the letter, and get a restart decision.
When should you send a pause notice instead of another follow-up?
Send a pause notice when work your team can do is finished, the next steps depend on items only the customer can provide, and earlier follow-ups and a warning have gone unanswered. If the team still has useful work it can do, keep chasing. A hold letter is for when progress has genuinely stopped.
Check these before you draft:
- Is the blocker really customer-owned? Look at the statement of work or project plan. The item (data, system access, an approval, a named decision-maker) should be listed as the customer's responsibility.
- Have you asked clearly, more than once? Your follow-ups should name the item, the owner and the date it was due, and say what it was holding up.
- Did the customer get a warning? The message before the pause should say that if the item does not arrive by [date], you will pause the implementation and reassign the team. That way the letter is the expected next step, not a surprise.
- Is your own side clean? If any open item is yours, close it or say so in the letter. A pause notice loses its force if the customer can point to something you owe.
If you have not yet escalated, start there. The usual sequence is follow-up, then escalation to the sponsor, then a warning, then the hold.
What should an implementation on hold letter include?
An implementation on hold letter should include the effective date of the pause, each outstanding customer-owned item with its due date and follow-up dates, and the contract terms the pause rests on. It should also explain what happens to staffing, go-live and fees, list the restart conditions, name the decision needed and give a deadline.
Work through it in this order:
- Subject line that says what this is: "Implementation on hold: [project name], effective [date]".
- One-sentence purpose: the implementation is paused from [date] because customer-owned dependencies are outstanding.
- Outstanding items table: item, customer owner, original due date, follow-up dates, what it blocks.
- Contract basis: the section of the agreement or statement of work that covers customer responsibilities and delays.
- What changes during the hold: team assignment, go-live date, fees and subscription.
- Restart conditions: the specific items and the decision that will restart work.
- Deadline and what happens after it: for example, a change order or a formal review of the engagement, as your contract allows.
- A named contact and an offer to talk.
How do you record the customer-side delays without blaming anyone?
Record customer-side delays as dated facts from the project record: what was requested, from whom, when it was due, and when you followed up. Leave out adjectives and motives. A plain list of dates and owners carries more weight than any wording about how frustrating the delay has been.
Build the evidence before you write a sentence:
- Pull every open dependency from your project plan or task tool.
- For each, note the customer owner, the original due date and each follow-up date with the channel used (email, meeting, ticket).
- Note the milestone each item blocks, and whether that milestone sits on the path to go-live.
- Ask your delivery lead to confirm the list so nothing in it can be disputed.
Wording to use: "[Item] was due from [customer owner] on [date]. We followed up on [date] and [date], and raised it with [sponsor name] on [date]. It is required before [milestone] can start."
Wording to avoid: "despite repeated requests", "your team has failed to", "as we have said many times". The dates already say this.
What happens to the team, go-live date and billing during the hold?
During a hold, your contract decides billing and fees, and your letter should restate those terms rather than invent new ones. In most cases the team is reassigned, the original go-live date is withdrawn, and a new date is set only once work restarts, based on when your team is next available.
What to state, and what to check first:
- Team assignment. Say plainly that the assigned consultants will move to other work from [date] and that restart depends on availability. Avoid promising the same people will return.
- Go-live date. Withdraw the current date rather than moving it. Say a new date will be agreed after restart.
- Fees and subscription. Read the agreement before you write this line. Contracts handle this in different ways. As an example, one sample clause on Law Insider provides that when the customer requests a delay past the Target Date, remaining implementation fees are due and monthly recurring Service Fees remain in effect, the remaining work may be rescheduled to the next available timeframe, and the vendor may apply additional implementation fees for rescheduling. Your contract may say something different, or nothing at all.
- If the contract is silent, do not assert billing consequences in the letter. Talk to your commercial or legal lead and, if needed, propose terms as a change order instead.
Check this section with whoever owns the commercial relationship (account executive, finance, legal) before sending.
Implementation on hold letter template
Copy this and replace every bracketed field. Remove any line your contract does not support.
Subject: Implementation on hold: [project name], effective [date]
Dear [sponsor name],
I am writing to confirm that the [project name] implementation is on hold from [effective date]. The next phase depends on items your team owns under [agreement or SOW section], and these are still outstanding.
Outstanding items
Item Owner Due Follow-ups Blocks [item] [customer owner] [date] [date], [date] [milestone] [item] [customer owner] [date] [date], [date] [milestone] We raised these with you on [date] and noted on [date] that we would pause the work if they were not resolved by [date].
What changes during the hold
- Our consultants assigned to [project name] will move to other work from [date]. Restart will depend on team availability at that point.
- The go-live date of [original date] no longer applies. We will agree a new date with you once work restarts.
- Under [contract section], [state the fee and subscription terms exactly as the contract does].
What will restart the work
- [Customer owner] provides [item].
- [Customer owner] provides [item].
- A decision from you on [decision, for example confirming the revised scope or a named owner for data migration].
Please confirm by [deadline] whether you would like to restart on these terms. If we have not heard by then, we will [next step your contract allows, for example propose a change order or arrange a review of the engagement].
I would value a short call before [date] to agree the way forward. [Delivery lead name] remains your contact at [email or phone].
Kind regards, [Your name] [Title], [Company]
How do you get the sponsor to decide on a restart?
Get a restart decision by asking the sponsor one specific question with a deadline, and making the answer easy to give. "Do you want to restart on these terms by [date]: yes, no, or let's talk?" gets a clearer reply than a request to "let us know how you'd like to proceed".
Steps that help:
- Send the letter to the sponsor, not only the day-to-day contact. Copy the contact so nothing is hidden.
- Offer a short call in the letter and in a follow-up a few days later.
- Follow up before the deadline, not after it. A reminder shortly before the deadline is normal practice and should repeat the question word for word.
- Record the answer in your project record and confirm it in writing, including any new due dates.
- Tell your team what the sponsor decided and what they will do next, so restart planning starts from the decision.
In Unblockd, asks to the sponsor by email with one-tap answers (no account), or answered by replying to the email, are how a sponsor responds.
What mistakes make a pause letter damage the account?
A pause letter damages the account when it surprises the sponsor, apologizes for a delay you did not cause, or threatens consequences the contract does not support. It keeps the relationship intact when it arrives after a warning, sticks to dated facts and offers a clear way back.
Common mistakes and fixes:
- Using an apology template. Delay templates such as Text Blaze's advise taking responsibility and offering compensation, which suits delays you caused. For a customer-caused pause, thank the sponsor for their attention and keep the letter factual.
- Offering concessions. Discounts or free extensions signal that the delay was yours.
- Vague restart terms. "Once things settle" invites drift. List the exact items and the decision.
- No warning beforehand. If the customer is surprised, send the warning first and hold the letter.
- Leaving out your own open items. Name them and their dates.
What should you do after the letter goes out?
After the letter goes out, keep the record current and the door open. Log the send date, reassign the team as stated, follow up before the deadline, and when the sponsor answers, confirm the restart terms in writing and replan with your team from that decision.
If the deadline passes without a reply, take the next step you named in the letter, and only that step. Consistency between what you said and what you do is what keeps a firm letter credible.