In practice, a multi-site evaluation looks at one initiative carried out in several places, such as programs, organizations, colleges, or communities, under a single design that every site shares and each site can adapt. The shared part is a set of evaluation questions, a short list of information collected the same way everywhere, common definitions and timing, and one set of procedures for consent and data handling. The local part is what each site adds because it fits its own participants, setting, and goals. The evaluator collects and analyzes information site by site, returns results to each site while there's still time to use them, and brings the sites together at agreed points to interpret what's happening across the initiative. The work runs alongside the initiative for its whole length, so each site and the funder or lead organization learn what's working, for whom, and under what conditions while the work is still underway.
Agree on the shared evaluation questions and the short list of common measures with the sites before data collection starts, and decide what each site may add.
Sites collect comparable information without giving up what's distinctive about their work, and the evaluator can report on each site and the whole initiative.
List the sites, what each one is doing, and what you'd most want to learn across them, and use that list to start the conversation with an evaluator.
Did participants at different sites have the same experience?
Lauren McClain, Ph.D., Grantibly
In a multi-site evaluation, the sites share the parts that make results comparable, and each site decides the parts that make results meaningful locally. The shared parts usually include:
Each site can then add questions that matter locally, choose methods that suit its participants, and schedule data collection around its own calendar. An evaluator who understands how a school, college, or community organization operates won't schedule a focus group during finals week or a survey during a site's busiest season.
A multi-site evaluation runs as a repeating cycle over the course of the initiative: collect information at each site, analyze it site by site, return results to each site, and bring the sites together to interpret what's happening across them. How often that cycle repeats depends on the length of the initiative and the decisions it informs.
For example, a made-up foundation funding mentoring programs at six community organizations might agree on three shared questions and two common measures, collected at the start and end of each program year. Each organization might also run its own focus groups with mentors. After each round, the evaluator would send each organization a short summary of its own results, then hold a session where all six compare what they're seeing and discuss why results differ. The funder would receive a cross-site synthesis built from the same information.
What does the evaluation process look like from kickoff to final report? describes the arc of a single evaluation engagement from start to finish.
Each site gets its own results during the initiative, along with a view of how its work compares with the other sites and what they're learning. A site can see what's working in its own program early enough to adjust it, and it can learn from sites that are solving a similar problem in a different way. That exchange is one of the main reasons to evaluate across sites instead of separately.
Sites also benefit when data collection is coordinated. A shared design means each site isn't building its own evaluation from scratch, and an evaluator working across all of them can keep the requests proportionate to what will be used. When a funder sponsors the evaluation, the purpose, who sees each site's results, and how they'll be used should be clear to every site from the start. What's the difference between grantee support and compliance monitoring? covers that line.
A multi-site evaluation is usually coordinated by an external evaluator working with the funder or lead organization and with a contact person at each site. The evaluator leads the design, keeps procedures consistent across sites, analyzes the information, and facilitates the cross-site conversations. The site contacts help schedule data collection, explain local context, and share results with their own teams. The funder or lead organization sets the purpose and decides how the results will inform its next steps.
On a larger initiative, the evaluation may be led by one firm with others contributing specialist work. Grantibly can serve as the lead external evaluation partner across sites or as a specialist within a larger project team.
Evaluation shouldn't operate on a separate track from the program. We believe in sharing useful findings while there's still time to act on them. Annual reports and final reports matter, but project teams shouldn't have to wait until the end of a grant to learn something important.
Projects are often eager to know whether their program worked. That's an important question, but it's difficult to interpret outcomes without understanding implementation: who participated, what changed along the way, what barriers emerged, and whether participants at different sites had the same experience.
A multi-site evaluation differs from evaluating each site separately because the sites share questions, measures, and procedures, so their results can be compared and combined. Separate evaluations can each be useful, but they rarely line up well enough to say what the initiative as a whole is accomplishing.
The sites in a multi-site evaluation don't have to run the same program, but they need enough in common for shared questions to make sense. Sites pursuing the same goal in different ways can be evaluated together, and the differences become part of what the evaluation explains.
Whether a multi-site evaluation needs IRB approval depends on the institutions involved, what information is collected, and how it will be used, and each site's institution may have its own requirements. Does my program evaluation need IRB approval? covers how to find out.
If a site drops out partway through a multi-site evaluation, the evaluator documents when and why, keeps its information separate in the analysis, and reports on the remaining sites without implying the site's results are complete.