You're working with a corporate client on the design of a new commercial building. Their internal approval process involves a board that meets once a month, on the first Tuesday.
This means project decisions don't always come back as quickly as your team might need them to. A question raised on the 4th of March, for example, may not be discussed until the board's next meeting on the 1st of April.
There's also a brand team that reviews the interiors towards the end of the design process. By then, the layout may already have been approved, and incorporating their feedback could mean revisiting earlier decisions. During the same project, a change in leasing requirements also meant adjusting the floor plate.
By the time the building was handed over, your team had worked through eleven revision cycles. The original proposal, however, had accounted for four.
Now the same client is back with a second building.
It's a good relationship. They pay on time, the first project has become a strong addition to your portfolio, and they've recommended your practice to others. Naturally, you'd be happy to work with them again.
But as you prepare the next proposal, there's something worth considering. Should the fee be based on the original estimate, or on what you learned from the first project?
The first building has given you a much better understanding of how this client works. You know how their internal approvals happen, when different teams get involved and how long certain decisions can take.
You also have a clearer picture of the work involved beyond the actual design and drawings. There are discussions to coordinate, feedback to incorporate and decisions that sometimes need to be revisited.
This is useful information, especially because many of these processes are likely to remain the same for the next building. The board will still meet monthly. The brand team may still prefer to review interiors towards the end. The leasing team will continue to have its own requirements.
The next project won't necessarily follow the exact same pattern, but you aren't starting from scratch either.
And that's an important distinction when preparing a fee.
With a new client, much of your estimate is based on experience with similar projects. With a returning client, you have something more specific to work with. You have already seen how their organisation approaches decisions and how that affects the time your team spends on a project.
Your next proposal should reflect that experience.
This doesn't mean simply adding a higher amount to the previous fee. It means understanding what the previous project involved and making sure the next fee accounts for a similar level of work.
For instance, you could explain that the previous building involved eleven revision cycles, while the original fee had accounted for four. Based on that experience, the new proposal includes a more realistic allowance for revisions and coordination.
You could also offer an alternative.
If the client is able to arrange key approvals within two weeks and involve the brand team during the concept stage, the project may require fewer rounds of changes. You could then propose a different fee based on that working arrangement.
This makes the conversation more useful for both sides. The client understands what influences the fee, and your practice has a clearer basis for planning the work. It also gives everyone an opportunity to discuss how the next project could run more smoothly.
But there's one thing you need before you can have this conversation confidently: a record of what happened during the first project.
And this is where many architecture practices struggle.
Changes on a commercial project don't always arrive as formal revision requests. A stakeholder might send an email with a new requirement. A discussion during a meeting might lead to an adjustment. The brand team might share feedback that changes something the design team had already considered final.
Your team handles these requests as they come in. Someone updates the drawings, another person informs the relevant consultant, and the project continues.
But how much of that information is actually recorded?
By the time the project is complete, you might remember that there were more changes than expected. You may even remember a few major instances that took considerable time. But putting together an accurate account of every change, when it happened and who requested it can be difficult.
There's a big difference between trying to reconstruct this information after a project and recording it while the work is happening.
A list prepared months later can feel like a summary of everything that took longer than expected. The same information, recorded as the project progresses, simply gives you a clearer picture of the work involved.
It doesn't need to be another complicated reporting exercise. Start with one line for every significant change. Record the date, what was requested and which team or stakeholder it came from.
You don't need to send this list to the client or turn every entry into a billing discussion. It's primarily a reference for your own practice.
Over time, these records can help you understand which projects require more coordination, where additional time tends to go and what needs to be considered when preparing future fees.
Keeping this information accessible throughout the project is important. Trying to piece everything together once the building is complete rarely gives you the full picture.
Projectsmate keeps project information and updates together as the work progresses, giving your team a reliable record to refer to when planning future projects and preparing proposals.
A returning client brings familiarity, trust and the possibility of more work. Your experience of working with them is valuable, too. Use it to understand the next project better, plan more accurately and prepare a fee that reflects the work involved.

