November 5, 2026
Thank you to the follow participants for sharing the experiences and insights during our September Gathering Space that served as the foundation for this blog post: Claire Quimby, Dawn Coleman, Heather Britt, Hyemi Jacka, Katharina Kreutz, Nirmi Vitarana, Noah Goodman.
Every evaluation proposal starts with a budget, and every budget is a best guess of what it will take to fulfill the project’s work requirements. A recent Gathering Space explored the question: what principles should guide an evaluation consulting team’s proposal budget design and budget management, so the budget is fair for everyone on the team and the client?
The conversation centered on two common scenarios that put evaluation consulting firms’ or teams’ budgets under pressure. The same themes came up in both: be transparent, put things in writing, and plan for the unexpected.
Scenario 1: The client wants something different from what they said they needed
This can happen to anyone. Either as early as during the inception phase or at any point during a project, it becomes clear that what the client wants no longer matches what the original scope of work described. For the contracted evaluation team, that can mean that a different allocation of hours and sometimes a different set of skills are required. So, how can we address this?
Start with transparency, and start early. Be up front from the moment the budget is developed that it is a best estimate and may change. This applies to the client and to teammates alike. With a client, it is important to discuss and agree on budget implications associated with any change in the scope of work. If bringing together a team of independent or small firm consultants, team members may come in with their own budget expectations, and a budget that shrinks without warning can be a real hardship, making income unsteady. Telling teammates early about the possibility of change keeps it from becoming a surprise.
Use bigger umbrella topics. Grouping work under broader budget categories allows a project to be more iterative. It gives you room to negotiate where time is spent without reopening the whole budget each time something shifts.
Get the language right. Words mean different things to different people. An inception or kick off meeting is a good place to walk through the scope of work together, and put everything in agreed language that everyone understands, and then document it in an inception report. Addressing the language up front can prevent a lot of misunderstanding later.
For adaptive projects, name them as such in the scope of work. When the work is emergent and likely to change, include language about ways of working in the scope itself: hours are based on an estimate, they will be shared regularly, and invoicing will reflect hours actually used. Then the client knows when time (and/or budget) may need to be readjusted.
Don't rely on verbal agreements. When the work needs to adapt, revisit the agreed scope of work, rather than shifting course verbally. Documenting changes can help ensure shared understanding of both changes to the scope of work and the budget implications of those changes, protecting both client and consultant in the future. That said, not every change warrants a formal update. Whether a change is big or small matters, and revising the scope of work for every adjustment may not make sense.
Be professional, and be brave. When the budget needs to change, renegotiate it, rather than quietly compromising the quality or methods of the evaluation or taking on significantly more work than agreed. Evaluators need the courage to speak up. These conversations help clients understand what it takes to complete the desired work successfully.
Keep reserves. Because a changed budget can leave an evaluation consultant with less income than expected, and income isn't always steady, evaluators need their own financial cushion. The same advice applies to commissioners: in capacity-building work with evaluation commissioners working in complexity, setting aside contingency resources, both funds and time, is a standard recommendation.
Scenario 2: A teammate has an emergency and someone else has to cover
The second scenario is more personal. A teammate has an emergency and another teammate steps in. How does the budget hold up?
One story from the group shows how messy this can get. A team member left, and the lead decided to pay them anyway, given the personal emergency nature of their departure. The person never fully returned to the project, and the remaining evaluation consultant ended up finishing the work alone.
The group's suggestions:
Build in a contingency budget to cover unexpected, minor shifts in the work.
Be transparent about reallocating work between people, so no one is surprised.
The takeaway
A fair budget requires flexibility. It's one where everyone understands from the start that it might change, knows how changes will be handled, and can see the numbers as they move. Transparency, plain language, written agreements, careful time tracking, and a healthy reserve go a long way toward making that possible.
