Priya ran a small DevOps consulting practice, and her favourite client was a logistics company with a tangled deployment process. After a long Tuesday workshop, she and the client’s engineering head, Daniel, shook hands on a plan. Priya believed she had agreed to map the release pipeline and recommend improvements. Daniel believed she had agreed to map it and also to carry out the first round of those improvements. Neither of them noticed the difference for five weeks.
When the gap surfaced, nobody was angry, but both were embarrassed, and the next month’s invoice turned into a long, careful conversation. The cost of that single missing paragraph was weeks of goodwill. Priya later said the fix was almost laughably small: a written follow-up note after every workshop. This article tells the story and then gives you a checklist for auditing your own notes, so you can find your Tuesday before it finds you.
What went wrong in the workshop
Looking back, the workshop had been productive. Whiteboards were full. People used the same words, such as “stabilise” and “improve”, for two different ideas. A mapping exercise and a hands-on change both fit under “improve the release pipeline”. In the room, each person filled in the blank with their own expectation, and the energy of the meeting covered the difference.
The deeper lesson is that agreement feels strongest at the moment it is least precise. Warm rooms produce vague yeses. The tool that converts a vague yes into a real one is a few lines of text sent the next morning.
What Priya sends now
After each session she writes a short message, usually five or six lines. It restates the outcome in the client’s words, lists what she will deliver, says what she will not do unless asked, gives the date, and ends by inviting corrections. When she first tried it, Daniel replied within the hour with one line: “Good, but please add that your team also owns the first fixes.” That correction took thirty seconds, and it would have taken thirty days to unravel later.
The audit: ten questions for your last three follow-ups
Pull up the last three messages you sent after client conversations. If you did not send any, that is your first finding. Otherwise, score each one against these ten questions.
- Does it name the outcome in the client’s own language? A reader outside your team should understand it without a glossary.
- Does it say what you will deliver? Look for nouns: a report, a pipeline diagram, a working script, a training session.
- Does the note spell out the exclusions? The most valuable sentence in the note is often the one that begins “this does not cover”.
- Is there a date? Phrases like “soon” and “next sprint” do not count.
- Is the pricing basis clear? You need not repeat figures, but the method should be written: fixed, time-based, or a staged mix.
- Does it say who does what on the client side? Engagements stall when access and approvals sit in someone’s head.
- Is the change rule written? What happens if the scope, timeline or priorities shift?
- Is there an invitation to correct? A closing line such as “tell me if I have misread anything” makes the note collaborative.
- Was it sent within a working day? Notes lose value quickly as memories blur.
- Is it findable? Check that it sits in a shared thread or project folder, not only in your sent items.
Seven or more yeses on each message is a healthy record. Fewer than five suggests a Tuesday is brewing. Mark the weakest question across all three and make that the one you strengthen first.
Reading the audit results
If the exclusions are missing
This is the most common gap, and the most expensive. Consulting scopes expand naturally, because clients and advisers both want to be helpful. Writing the boundary down is not unfriendly; it makes generosity a choice rather than an accident. The same reasoning appears in our look at how a consulting engagement moves from assessment to enablement, where each stage hands the client something concrete.
If dates are vague
Put a calendar date on the next visible step, even a small one. Large programmes such as the ones in our discussion of consulting support during a cloud move are made of hundreds of small commitments, and each one needs a date somebody can hold.
If the change rule is absent
Add a standing sentence to your template: “If priorities change, I will tell you the effect on time and cost before starting the new work.” Clients tend to welcome it because it promises no surprises in either direction.
Why the story keeps repeating
Priya’s experience is not unusual, and the pattern behind it is worth naming. Consulting conversations are generous by nature. The adviser wants to help, the client wants progress, and the shared enthusiasm quietly stretches the edges of what was promised. Nobody sets out to mislead anyone. The edges simply move a little each time somebody says, “while you are at it”, and the only fixed point in the whole process is whatever got written down.
There is also a human side that checklists do not capture. Writing the note is an act of respect: it says that the client’s priorities mattered enough to be recorded accurately. Clients notice. Several of Priya’s referrals came from people who said, in almost these words, that she was the first consultant who sent them a summary they could forward to their own manager without editing.
Handling the awkward replies
Sometimes the reply contradicts you, as Daniel’s did. Resist the urge to defend. Thank the client, adjust, and resend the corrected note, so the record shows one agreed version. Occasionally the correction reveals a bigger disagreement than a missing sentence. That is uncomfortable, but it is far better discovered in week one than week five.
Sometimes there is no reply at all. For anything involving cost or a hard dependency, follow up once with a gentle line: “Just checking this matches your understanding before I start.” Silence on a minor point can be treated as agreement; silence on a major one should not be.
Advisers beyond your own field
Consulting clients often ask about matters outside technology, such as how a new service contract should be treated in their books. You are not the right person to answer, and it is worth knowing where to point them. A searchable listing of chartered accountants by location, specialisation and consultation mode is one place a client can start looking. If you refer someone, suggest they send the same kind of written follow-up to whoever they speak with.
Where Priya’s practice stands now
A year on, Priya says the notes changed more than her disputes. They changed how she listens. Knowing she must write three precise sentences after the call, she asks sharper questions during it: “When you say improve, do you want a recommendation or the change itself?” Her workshops run slightly longer and her follow-up conversations run much shorter.
Daniel, for his part, adopted the habit inside his own team. His engineers now close planning meetings by agreeing who will send the confirming message, and the answer is written on the whiteboard before anyone leaves the room.
Your next step
Open your sent folder today and run the ten-question audit on the three most recent follow-ups. Circle the weakest question. Write one improved template line for it, and use it after your next client call. Then do the audit again in a month. The practice is small enough to feel trivial and powerful enough to prevent a very expensive Tuesday.
Best Cardiac Hospitals Near You
Discover top heart hospitals, cardiology centers & cardiac care services by city.
Advanced Heart Care • Trusted Hospitals • Expert Teams
View Best Hospitals