If you are trying to create a maturity assessment for a nonprofit, the hard part is usually not finding a template. It is working out what the assessment should actually measure, how detailed it needs to be, and how to make sure the results are useful rather than just interesting.
That is where many nonprofit teams get stuck. They know they want a clearer picture of where they are today and what needs improving, but they are not always sure how to structure the assessment in a way that fits their organisation. The risk is ending up with something too broad to be practical, too vague to guide decisions, or too complicated for people to use properly.
A good maturity assessment should do something simpler than that. It should help you understand how developed a particular area of work is today, give you a shared language for discussing strengths and gaps, and make the next step clearer.
This guide walks through a practical way to create a maturity assessment for nonprofits, based on three core phases: design, build, and testing.
What is a maturity assessment?
A maturity assessment is a structured way to evaluate how developed a process, capability, or area of work is within your organisation. It is often used to understand current practice, identify strengths and gaps, and guide improvement over time.
For nonprofits, maturity assessments can be useful in areas such as impact measurement, data practices, fundraising systems, service delivery, volunteer management, or internal operations. Instead of asking whether something simply exists or does not, a maturity assessment helps you look at how well it is working and how consistently it is being applied.
Done well, it can help your team move beyond vague discussions like “we need to get better at this” and towards something more practical: what good looks like, where you are now, and what would need to change to move forward.
Why nonprofits use maturity assessments
Nonprofits often reach a point where the work is getting done, but it is harder than it should be. Processes may depend on staff memory, workarounds, and manual effort. Reporting may feel inconsistent. Different parts of the organisation may have very different views of how well something is working.
A maturity assessment can help make that visible. It gives you a more structured way to assess the current state of a process or capability, compare it against clearer criteria, and identify where improvement will have the most value.
That can be useful for internal planning, prioritising improvements, supporting strategy discussions, or creating a clearer baseline before investing in new tools, systems, or ways of working.
Step 1: Design the assessment before you write it
The design phase is where you decide what the assessment is for and who it is for. This matters more than many teams expect. If these decisions are fuzzy, the rest of the assessment often ends up fuzzy too.
Start with the audience. Who will complete the assessment, and who will use the results? In some cases, one person may be able to answer on behalf of a whole team. In others, you may need input from several people or functions to get an accurate picture.
Then clarify the purpose. Are you using the assessment to identify improvement opportunities, benchmark current practice, support planning, or create a shared understanding of what better looks like? Different goals may lead to different structures and levels of detail.
You also need to define the scope. A maturity assessment works best when it is focused enough to be meaningful. Trying to assess everything at once usually creates something too generic to guide action. It is often more useful to focus on one domain, process, or capability area first.
Finally, decide what success looks like for the assessment itself. A good maturity assessment should not just be theoretically sound. It should be understandable to the people using it and useful enough to support real decisions afterwards.
Step 2: Build the structure of the maturity assessment
Once the purpose and scope are clear, the next step is to build the assessment itself. This usually involves choosing the process areas to assess, defining the maturity levels, and writing clear descriptions for each level.
Choose the process areas carefully
Process areas are the parts of the organisation or capability you want to assess. These should reflect the focus of your assessment and the areas that matter most to the outcome you are trying to improve.
For example, if you were creating a maturity assessment for nonprofit impact measurement, your process areas might include data collection, outcome definition, reporting, staff capability, and use of insights in decision-making. If you were assessing fundraising operations, the areas would look different.
The key is to choose areas that are distinct enough to assess properly, but not so many that the assessment becomes difficult to complete or interpret. In practice, simpler and clearer usually works better than exhaustive.
Define the maturity levels
Maturity levels describe the progression from less developed to more developed practice. They give the assessment depth and help teams understand what movement or improvement actually looks like.
You might use a simple scale such as emerging, developing, established, and strong. Or you might choose something more tailored to the area you are assessing. The exact labels matter less than the logic behind them. Each level should represent a meaningful difference in practice, not just a different word.
Good maturity levels usually reflect a mix of structure, consistency, capability, and learning. In other words, they look not just at whether a process exists, but whether it is understood, embedded, supported, and improved over time.
Write clear descriptions for each level
This is the part that often makes or breaks the assessment. If the descriptions are vague, people will interpret them differently. If they are too abstract, users will struggle to see which level fits. If they are too long, the whole assessment becomes harder to use.
The best descriptions are specific enough to guide judgement, but simple enough to read quickly. They should make it easier for someone to recognise current practice honestly, not push them towards the “best” answer.
It can help to define the strongest and weakest ends of the scale first, then fill in the middle. It is also worth grounding the descriptions in real examples, observed practice, stakeholder feedback, or existing evidence where possible.
Step 3: Test the assessment before relying on it
Once the assessment is drafted, do not assume it is ready. Testing is a core part of creating a maturity assessment that people can actually use.
Start by asking a small group of likely users to complete it. Watch for where they hesitate, interpret questions differently, or struggle to distinguish between levels. Those points of friction are useful. They usually show where the wording needs refining or where the scale is not doing enough work.
It is also worth checking whether the results feel credible. If the assessment suggests that very different teams all land in exactly the same place, or if it produces results that do not match what people know from experience, something may need adjusting.
Testing helps you refine both the assessment structure and the language. It also improves confidence that the tool is measuring something meaningful rather than just producing a neat-looking score.
Common mistakes to avoid
One common mistake is trying to assess too much at once. When the scope is too broad, the criteria often become generic, and the results become less useful.
Another is making the levels too aspirational and not descriptive enough of real-world practice. People need to be able to recognise their current state honestly. If every description sounds idealised or overly polished, the assessment will be harder to use well.
A third mistake is skipping testing. Even a thoughtful draft can behave differently once real users start applying it. Testing often reveals unclear wording, duplicated ideas, or criteria that sound sensible but do not work well in practice.
And finally, it is easy to create an assessment that produces a score but not a next step. The most useful maturity assessments help teams see where to focus, what to improve first, and what progress could reasonably look like over time.
Keep the assessment practical
For most nonprofits, the goal is not to create the world’s most sophisticated maturity model. It is to create something practical enough to use, clear enough to support decisions, and focused enough to improve the work.
That usually means keeping the structure manageable, using plain language, and designing the assessment around real decisions your team needs to make. If it feels too academic or too disconnected from everyday work, it probably needs simplifying.
A useful maturity assessment should help your team understand where things stand today and make the next step clearer. It should not become another piece of complexity to maintain.
Download the full guide
If you want a more detailed walkthrough, you can download the full guide below. It covers the design, build, and testing phases in more depth, with examples to help nonprofits think through audience, purpose, scope, maturity levels, and validation.
If you are working through this and realising the bigger challenge is not just the assessment itself but the messy process behind it, that is usually a sign the setup needs attention too. Sometimes the most helpful next step is not adding more framework. It is simplifying the way the work is currently being held together.
If that sounds familiar, get in touch. We help small nonprofits make work easier to run, including the processes behind reporting, assessment and improvement.
If creating a maturity assessment from scratch feels like more work than your team has time for, our Automated Beneficiary Maturity Assessment services offer a more structured way forward. We help nonprofits assess beneficiary maturity in a practical way, without turning it into a big project.
