Stop Counting Grants. Start Mapping Community Change.

At the end of a funding cycle, most community investment teams can answer one question with total confidence: how many grants went out, and for how much. What's much harder to answer is where that funding actually went — which issue areas it reached, which populations it touched, whether this year's investment looks any different from last year's. Right now, most grant programs just aren't set up to show that.

In our recent webinar, Stop Counting Grants. Start Mapping Community Change., we walked through six fixes that turn a stack of individual applications into a real, structured picture of where community investment is going, and closed with a live, hands-on look at the applicant and judge experience inside Reviewr. If you missed it live, here's what we covered, and you can catch the full session on demand below.

The session was framed for United Way programs specifically, but everything in it applies just as directly to any grant, scholarship, or award program — the mechanics don't change based on who's running it.

The Count Was Always There. The Map Never Was.

Most community investment teams can say exactly how many grants went out and for how much. What they can't easily answer is where that funding actually went. Right now, most programs are set up to say "yes, we got this many applications" and stop there, instead of looking at what actually happened with them. The applications themselves usually hold that missing story — issue area, geography, population, real outcomes — they're just never captured or structured in a way that lets anyone actually see it once the cycle ends.

What We Covered

Six fixes were presented as a sequence — each one building on the last, from how a form gets built all the way through what happens to that data years later.

1. Build a Form That Asks the Right Questions: The session opened this fix by naming something admins resist almost every time: making real changes to an existing form feels daunting, even though it's the highest-leverage step in the whole process. The fix starts before the form itself, in a conversation about what the program's actual goals and values are for this specific year — not just its eligibility requirements — since those goals can and do shift year to year. Reviewr's flexibility is what makes that conversation actionable instead of theoretical: a form can be rebuilt around this year's priorities without starting from scratch. The goal isn't piling on more questions; it's finding the smaller set of good, intentional questions that actually predict a strong recipient. On the applicant side, that same rebuilt form pays off immediately — clean, easy-to-read questions, and a save-and-log-out feature so progress is never lost partway through.

2. Organize Investment the Way Your Community Breaks Down: This fix started with a foundational question: how should these grants actually be broken down to reach the whole audience a program is meant to serve? That means sitting down each cycle and asking what categories and groups worked in the past, and just as importantly, what the community needs right now that isn't being captured yet. Admins often hesitate here too, assuming that adding or retiring a category means rebuilding significant parts of the program. That concern was addressed directly: categories can be deleted while the past event stays fully on file for reference, and a new category can be built fast by copying an existing, similar question set and layering in conditional logic — flexible enough to make that call right up until a program goes live.

3. See the Patterns Without Building a Spreadsheet: The manual version of this step was described bluntly: clicking into last year's submissions one at a time, dissecting each answer, and hoping to remember or manually transcribe it into a spreadsheet just to have the information in one place. In Reviewr, reports are already built and downloadable at any point in the cycle — from the moment the first submission comes in through the end of review — so that information is available to analyze immediately instead of reconstructed after the fact. This was tied directly to something worth naming honestly: for most people in this audience, running the grant program isn't their main job. It's squeezed into lunch breaks and after-hours time on top of a full workload, which makes spending that limited time actually improving the program — instead of just hunting for the data to do it — the real point of this fix.

4. Keep the Story Going After the Award: This was the fix the session spent the most time on, framed as the one closest to the whole session's premise: don't just count your grants, map where they went. Impact tracking is something most programs simply aren't doing today, even though it's what turns "we gave them a grant and they were grateful" into real, usable evidence. A recipient will almost always say the grant was helpful when asked directly — that's not the same as knowing exactly where the money went or what would have happened without it. Reviewr's supplemental forms close that gap: once recipients are selected and funds are disbursed, an impact report — its own short, structured form connected to the original application — becomes available to them, with a reminder email prompting them to log back in and complete it. Three concrete reasons that data matters were covered: it sharpens the program itself cycle over cycle, it gives leadership and the board real evidence instead of a hallway anecdote when the conversation turns to budget, and — when those impact stories are shared publicly — it actively brings in more applicants and more volunteer judges. Splitting disbursement into two halves was also raised as an option worth considering: releasing the second half only once a recipient has reported on the impact of the first, building the follow-up into the structure of the award itself rather than hoping it happens informally.

5. Give Your Board a Real Map, Not a Tally: Building directly on the impact reports from Fix 4, this step is about what a foundation actually brings to its board or leadership. Reviewr can generate a single combined report pulling from both the original application and its linked impact report, so a board sees applicants, completed submissions, recipients, and real impact together, in one place. A concrete example made the stakes clear: a program can grow from 80 submissions to 100, or hand out five more grants than the year before, and those numbers sound like unambiguous wins — until you ask whether those submissions were complete, whether they were high quality, and whether anyone ever found out what that funding actually did. Growth in volume alone isn't the same thing as proof the program is working.

6. Watch the Picture Change Year Over Year: The final fix ties the first five together: using the same reporting to see, cycle over cycle, whether a program actually grew or stalled, and to pinpoint exactly where a disconnect happened rather than guessing. Most people on the call likely don't have this visibility today, which is less a criticism than an invitation — an honest look at how much of this is possible that simply isn't happening yet, and a starting point for deciding what to change.

Putting It Together: From a Grant Count to a Community Map

The fixes closed with a fast before-and-after recap. Before: a grant count with no real picture of where the money went; applications that were never structured to be compared against each other in the first place; a board asking "where did this go?" and getting a shrug, or a week of manually assembled spreadsheets, instead of an answer; and a grant's story ending the moment the check clears. After: structured data on issue area, geography, population, and outcomes captured from the very first form; reports and patterns generated automatically, with no export-and-pivot required; board-ready maps showing exactly where funding is concentrated and who it's reaching; and a grant's full story connected end to end, from intake through the outcomes reported well after the award.

What the Live Demo Showed

After walking through the six fixes, the session moved into a live look at Reviewr itself, covering the applicant, judge, and admin experience side by side:

• Account creation with save-and-resume for everyone. Every user — admin, applicant, and judge alike — creates an account, which is what unlocks automatic save behavior. Applicants can save progress mid-form and log back in later; automated reminder emails go out for incomplete submissions, and a confirmation email arrives on submit. Logging back in shows exactly where they left off, giving both the applicant and the admin real visibility into status without anyone having to ask.
• The same flexibility for judges. Judges follow an invitation link, create an account, and land in a judge portal showing everything assigned to them. Like applicants, they can save an in-progress evaluation and return later — useful for anyone stepping away mid-review rather than being forced to finish in one sitting.
• An eligibility and grant-matching tool. A short set of questions routes an applicant who doesn't qualify to an ineligibility page early, before they invest time in the rest of the form — sparing their time and sparing admins a submission that was never going to move forward. The same tool matches applicants to specific grants within a program that runs more than one at once: selecting only the grants that actually apply sends that applicant down only the relevant path, instead of the all-or-nothing pattern of skipping through irrelevant questions one by one, which is how most current processes handle it.
• A clean, flexible submission form with real security behind it. The demo covered Reviewr's range of available question types, noting that the same structure that makes a form easy and intuitive for applicants to complete is what also makes the resulting report clean and easy for admins, leadership, and the board to read. Uploads accept nearly any file type. Reviewr's SOC 2 compliance was specifically called out here — a feature many competing platforms don't offer — as directly relevant to grant applications, which routinely collect sensitive information like tax IDs and bank statements that have no business sitting in a PDF or a Google Form.
• A judge portal built to catch outliers, not just collect scores. Judges see every submission assigned to them alongside their own scores in one view, making it easy to notice — say, a submission scored a 19 next to another scored a 31 — whether that gap was intentional or a misclick. Where board members or other reviewers are likely to personally know applicants, Reviewr can redact identifying information — name, address, phone number — to remove that bias, and some admins use the same redaction simply to keep a long form from overwhelming a reviewer with information they don't need to score it.
• Everything a judge needs in one tab. The specific complaint Reviewr was built to solve here: judges in other systems juggling five open tabs, downloading four separate files, and digging through email just to evaluate one submission. In Reviewr, the submission, every response, every file upload, and any supplemental forms all sit together on one screen — no downloads required.
• A scorecard built to reduce subjectivity. Scorecards are built directly from the application's own questions, kept in the same order, so every criterion a judge scores traces back to an actual answer rather than a general impression. One deliberate design choice stood out: rating criteria in descriptive terms — poor through exemplary — instead of a plain 1–10 scale, because a numeric scale invites exactly the inconsistency a fair, high-stakes process can't afford (one version of a 7 isn't necessarily the same as another reviewer's version of a 7). The running total stays visible to the reviewer throughout, so they always know where an evaluation stands.

Closing

The session closed by returning to Reviewr's own track record: 15 years in, thousands of events run every year, and a platform that keeps expanding with new features and products built on that foundation — all in service of the same goal laid out at the start of the session, a process that works better for the admin, the applicant, and the judge all at once.

‍