Turn a reassuring monthly number into a clear view of unfinished work, uncertainty, and the choice your board needs to make.
By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.
AI-generated illustration: fictional nonprofit colleagues discuss a printed dashboard. This is not a photograph of an FWF meeting.
A small nonprofit board receives a report with a large green number: “80% completion.” The arithmetic has been checked. The team has worked hard. Yet several routine jobs have been waiting for weeks, and the unfinished list is longer than it was last month. Nobody has falsified a number. The report has simply answered a different question from the one the board needed to ask.
A useful dashboard should help readers distinguish activity from the condition of the work, and both from a decision. For people preparing monthly reports, the challenge is not to fit more indicators onto a page. It is to show what changed, what remains uncertain, and whether somebody needs to choose a different course. A short, well-explained report can do this without specialist software.
First, identify the question the headline actually answers
Consider a fictional teaching example: a community nonprofit coordinates non-emergency maintenance for shared meeting spaces. These figures are invented for learning, not reported FWF results. At the start of a month, six requests remain open. Twenty new requests arrive. The team closes sixteen requests during the month. There are no cancellations, duplicate removals, or reopened requests in this simplified example.
The tempting calculation is sixteen divided by twenty, or 80%. That is a ratio of monthly closures to monthly arrivals. It is not necessarily the percentage of this month’s new requests that were resolved. Some closures may concern work carried over from the previous month. To calculate the latter percentage, the report must identify which of the twenty new requests were closed by the cutoff date.
Now reconcile the workload: six open at the start, plus twenty received, minus sixteen closed, equals ten open at the end. The team completed sixteen jobs, but the backlog grew by four. Both statements are true. A dashboard that celebrates the first and omits the second leaves readers without the information needed to judge whether the workload is becoming manageable.
In a real register, show cancellations, reopened cases, and duplicate corrections separately when they affect that reconciliation. Otherwise an apparent improvement may reflect a changed definition rather than completed work. Give the headline a plain label such as “16 requests closed during September,” and place the opening and closing backlog beside it.
Count what is waiting, then ask what the wait means
A closing backlog of ten still does not explain the whole situation. Suppose five of those requests have been open for more than fourteen days. In this fictional organization, fourteen days is a locally chosen review point, not a legal requirement or a universal maintenance standard. The report should say so. Urgent hazards belong in an immediate safety response, not in a queue waiting for a monthly board meeting.
The next question is why the older requests remain open. Perhaps access to a room has not been arranged, a replacement part has not arrived, or a specialist is unavailable. These are hypotheses until the underlying records and staff explanations support them. Adding volunteer hours would not necessarily solve a supplier delay. Counting age helps locate a question; it does not establish its cause.
Use enough detail to make the issue intelligible without turning the board pack into a case-management system. A brief explanation of the main documented delay reasons may be more useful than a long list of names and addresses. Keep personal or sensitive details out of routine reporting unless the recipient genuinely needs them. The purpose is to improve the system, not expose the people using it.
Make uncertainty part of the report
The UK Government’s Government Data Quality Framework distinguishes completeness, accuracy, and timeliness. A complete record can still contain an incorrect value; a correct value can arrive too late for the intended decision. Although developed for government, these distinctions offer a practical way to examine a small organization’s own reporting.
Suppose two request records lack a reliable opening date. Do not silently classify them as recent, remove them from the count, or describe their age as zero. Show the total open count and explain how many records cannot yet be assigned an age. Keep the uncertainty beside the aging figure, where it affects interpretation, and name who will check it and when.
Also distinguish a reporting cutoff from the date somebody last edited the dashboard. “Position at September 30; checked October 3” tells a different story from an unexplained “updated today.” If a definition or correction changes a previous figure, preserve a short revision note. Readers should not have to guess whether performance changed or the measurement changed.
The Office for Statistics Regulation’s dashboard principles, published August 21, 2025 for producers of official statistics, call for prominent limitations, source information, update details, and information about corrections. These are useful reporting principles to borrow, not a claim that a nonprofit’s internal dashboard is an official statistic.
Replace “for information” with a precise decision request
The report can now move from a headline to a choice. In the fictional example, the question might be: “Should we change how routine maintenance requests are triaged before considering additional capacity?” That question is narrower and more useful than “How are operations going?” It also leaves room for the evidence to show that the proposed change is unnecessary.
A compact decision card can be written as one connected paragraph: “The open list increased from six to ten this month; five are beyond our fourteen-day review point. We have not yet confirmed the main causes of delay. Management proposes a two-week review of the older requests and will return with delay reasons and costed options. The board is asked whether this evidence is sufficient before considering a capacity change.” The exact authority and next step should fit the organization’s own arrangements.
That card separates observation, uncertainty, proposal, and request. It does not use a green indicator as a substitute for a recommendation. Nor does it invite board members to assign individual repair jobs. Management can retain responsibility for operations while the board receives the evidence relevant to its oversight and any decisions reserved to it.
There is a tradeoff. Waiting for better information can avoid an unnecessary commitment, but delay also has consequences. If waiting will worsen a material problem, state that risk and explain the limited action proposed in the meantime. A good report does not demand perfect data before every choice; it makes clear what can responsibly be decided with the evidence available.
Test whether someone can use the page
Give the report to a colleague who did not prepare it. Ask them to explain what the percentage measures, whether unfinished work increased, what remains unknown, and what response is requested. If they need the author’s spoken explanation for every answer, revise the page before adding another chart.
The Government Analysis Function’s dashboard design and accessibility guidance recommends plain language, explained visuals, logical organization, and alternative access to chart information. For a board pack, put the key numbers and their meaning into readable text or a simple table. Labels such as “review needed” carry meaning that a colored dot alone cannot provide.
Test the version people will actually receive. A page that works on a large monitor may become unreadable when printed or viewed on a phone. Avoid forcing readers to infer important distinctions from tiny legends. Keep a stable definition for each measure so that comparisons over time remain understandable, and explain any necessary change.
Improve one report before rebuilding the dashboard
Before the next meeting, choose one headline number from an existing report. Write the question it answers, the period and population it covers, and the unfinished work it leaves out. Then add one sentence stating the decision, investigation, or continued monitoring it should support. If there is no clear use, consider whether the number belongs on the main page.
This emphasis on understandable evidence and practical institutional capacity connects with FWF’s Leadership, Institutions & Implementation Capacity pathway. To share a question or explore a relevant conversation, use the foundation’s contact page. Start with one report that helps people see the work honestly, including the part that is still waiting.
Explore Resources for Your Next Step
A clearer report begins with a better question, not necessarily a new purchase. If your next step does involve comparing tools, services, or learning resources, the optional links below are a starting point for your own review. Check current terms, suitability, accessibility, and costs directly with each provider.
This section contains affiliate and referral links. Qualifying purchases or sign-ups may generate a commission. Arbab Naseebullah Kasi will donate all commissions he receives through these links to Feel Worldwide Foundation Inc. to support its programs and operations.
ElevenLabs · Synthesia · Pictory · Bookshop · beehiiv
Zoho · SiteGround · Fiverr · Expedia · Viator
Use only what fits a genuine need and your available resources. No purchase or sign-up is necessary to apply the reporting exercise in this article.
