When a Quick Question Becomes a Change Request
Photo: Glyn Baker, CC BY-SA 2.0, via Wikimedia Commons
Most project budgets do not fail in one dramatic meeting. They leak. A question here, a small tweak there, a WhatsApp message on a Friday afternoon asking whether the team could just move a wall, rename a report or check one more supplier. Each request looks tiny in isolation. Stack twenty of them across a six-week programme and you have quietly rebuilt the scope without rebuilding the fee.
I have seen this from both sides. As a client, it is easy to think you are only asking for clarity. As a project lead, it is easy to answer quickly because you want to be helpful and the clock is running. Both instincts are decent. The problem is neither comes with a time sheet.
The quick one usually arrives by the wrong channel
Email, WhatsApp and passing phone calls all blur the line between a conversation and a work instruction. The channel matters because it sets expectations. A call feels like a chat. An email feels like a task. WhatsApp feels like nothing at all until someone has spent two hours on it. If the answer is longer than a sentence, it deserves a home in the project record.
That is not about being officious. It is about making the work visible. A question that lives only in a phone log is almost impossible to price, review or learn from later.
A three-bucket triage
I use a simple traffic-light system. It is not perfect, but it is fast enough to use in the moment.
Green is a clarification. It interprets what was already agreed. Confirming a colour from the approved schedule, checking a deadline already in the plan, or asking who signs off a document all belong here. Answer within the normal rhythm. No change note is needed. Still log it if the same question keeps returning, because repetition often hides an ambiguity in the brief.
Amber is uncertain. It could be either, or it might be small enough to absorb. Timebox it to fifteen minutes. If it needs more than that, treat it as red until proven green. A useful reply is: I can answer the first part now. The second part looks like it may add work, so let me check the scope and come back by Thursday.
Red is a change. It adds a deliverable, alters a specification, shifts a date, creates rework, or requires input that was not in the plan. Do not absorb it silently. Price it, log it, and give the client a clear choice. The test is not whether the request is small. It is whether the request changes what was agreed. A five-minute change can still be a change.
Wording that keeps the relationship intact
The trick is to make the budget visible without making the client feel foolish. A few lines I have used or seen work:
Happy to pick this up. It looks like a change to the agreed deliverable rather than a clarification. I can send a short note with the time and cost impact, or we can log it for the next review. Which suits?
Quick answer on the current spec: it says X. If you want Y, that is a small piece of extra work. I will price it as a variation so you can decide with your eyes open.
Let us put this in the question log so it does not get lost. I will confirm by Monday whether it is covered by the current scope or needs a variation.
None of these are refusals. They are receipts. They tell the client you have heard the request, you are not being precious about it, and you are keeping the project honest.
Put a question log in place
A simple spreadsheet is enough. Columns: date, who asked, channel, question, triage colour, decision, owner, and time or cost impact. Review it in the weekly project meeting. The log does two jobs. It stops the same query being answered three times by three people, and it gives you evidence when the scope conversation gets fuzzy later.
It also changes behaviour. Once clients see their questions written down with a status, they tend to send fewer random ones and bundle the rest. That is not a bad outcome.
The awkward bit
Some clients will test the boundary. That is normal. The response is not to become formal and distant; it is to become consistent. Answer the clarification quickly. Flag the change politely. Do not let a red item sit in your inbox for a week and then arrive as a surprise invoice.
The aim is not to win the argument. It is to finish the project with the fee still attached to the work. A quick question is welcome. A quick question that quietly becomes a day of unpaid work is a budget problem wearing a friendly face.
