A recap of the September 24 call, for anyone who could not attend.
A recap of the tenth live discussion, on managing change. The hour covered the gray zone between a request and a change, what to say first, what a small free change really costs, and how to raise changes early without harming the relationship. This summary carries the substance of the full call.
Meeting RecordingFull September 24 discussion · about 75 minWhere the Room Started
PMs often ask for help with change. In practice, it is also the topic most easily set aside. Large changes are obvious to everyone. The small request that doesn’t feel major in the moment is the one that gets let go.
5 themes came from the feedback.
There are 2 sides. Early in the project, set the table: change is normal, and you will handle it openly. When a change comes, use a plan for the conversation. The words help only when the PM already believes the extra work deserves to be raised.
The Gray Zone
The scenario: the CD phase just started. A repeat client asks to reopen a major layout decision made early in DD. You start to discuss it, and the client says, “Just start. You know how we work.” Is it a change?
Clients rarely say “revisit a major layout decision.” They say, “There was that second option we ruled out. I’d like to look at it again.” The room gave 4 answers.
The phase closed and the work goes backward, often through the consultants too. One exception raised: a request during the owner review period of the last phase.
Use it to explain why the team chose the current layout, and that changing it now is a change to the project.
Know what the contract says before you push for an additional service. The terms assume both sides mean the same thing, so talk through what they mean with the client.
For example: “We have worked 3 weeks and about 80 hours in this direction. Changing it means going back and starting a new path.” Clients respond better when they see a number.
The room also raised the hard case: inherited relationships. Some long term clients, including some public agencies, don’t accept design phase changes as additional services. That pattern was learned over many projects and may not be fixable. It can be prevented on the next new client by setting expectations early.
The First Words
The pressure in the moment is to commit or to push back hard. A third option is almost always open: look at the request first, then answer.
“Thanks for asking us to look at that. Before we do, I’d like to see what it involves and talk with the principal on the project. Then I’ll come back to you.” It treats the request as a normal part of the work. The answer can come the same day or the next.
PMs don’t decide these alone. The principal in charge can guide the approach, contact the client, or decide to do the work at no charge.
A client exploring options is different from a client giving direction. A 15 minute sketch on trace paper in the meeting can answer the question. Rebuilding that part of the Revit model takes 8 hours.
A layout change can reach structural, civil, food service, and every other discipline. On a school, the opening date doesn’t move.
If the change adds area or cost, link the fee adjustment to that increase. The reverse also happens: a free rework that reduces the project also reduces the fee.
One more option from the room: an hourly, not to exceed additional service. It shows good faith while the team studies the request. If the request grows, a full additional service with consultant fees follows.
Where Is The Threshold?
Most PMs size up a request and weigh the effort against the risk of a hard conversation. Where does the line sit? One answer in the chat was 1 day. Others said it depends on the client, the relationship, the history, and how much rework is involved. One participant couldn’t name a single line.
A survey answer put the line at 1 day: “If it can be done in a day or less, I don’t typically ask for it.” The arithmetic on that day:
Free work is paid from the profit of another project. When a PM skips the conversation, another PM has to run a project profitably enough to cover it. Few PMs would give away a $5,000 change. Asking for $880 is easier.
Language In Your Back Pocket
“This is a creative process. You may like something now and want to reopen it later. If it is a change, we’ll tell you right away and work out together how to handle it.”
“Thanks for bringing this up. It’s small, and we’ll take care of it. We’ll add it to the list we track. If the list gets large enough, we’ll talk about it then.”
“We’d love to help. This is an hourly additional service. Give us approval by email and we’ll start, or we can pause and send you a written proposal.”
If the team does the work without a word, the client never sees the full facts. They may not know it was a change, and they may expect it every time. Part of the job is to show the client the effect of the decision, including the cost.
Death By A Thousand Cuts
The scenario: a new client, first month of the project. Each request took under 2 hours, but this is the 4th, and together they total a day. Nothing was said about the first 3.
Do We Work For Free?
A question from the room went to the core: if Grace values its work, why is free work even on the table? One answer: nobody in the industry works for free. Consultants and clients don’t either. How much depends on the effort, 1 hour or 8.
Lean toward naming changes and getting credit for them. A client can’t thank you for a favor they don’t know about.
Grace’s position lets it be realistic about cost and still flexible with the key clients that built the firm.
A small favor to a client who gives repeat work, year after year, can cost less than chasing a new client. That is a business decision for a few clients. It is not the default.
If PMs tell clients more often that a request is extra, even when the answer is “we’ll do it,” that is progress.
Track It, Then Decide
One participant, working as a consultant, listed every task on each monthly statement, including items marked no charge. The architect passed it to the client. The client saw the work, and the no charge items built goodwill.
A team of about 5 ran CA on 45 buildings at once, with requests from many client project managers. Every request was logged with the email, the date, the time, and who asked. Near the end, that record supported the conversation about additional services and what it cost to finish.
Take It With You
The tools
The Change Log Template records each request as it comes in. The Quick Reference Guide has the four part conversation and the two path script word for word.
What they cover
The Takeaway