Every funder asks a fair question: what changed because of your work? For a small nonprofit, that question can feel built for a larger shop, one with a data team, paid software, and time to build charts. You need none of that to answer well. You need three numbers, collected the same way each time, tied to the change your program promises, and reported with their limits stated plainly. Three honest numbers, kept current, beat a long report that nobody can check.
Start with the change, not with the count
First, separate what you did from what changed. Guidance on grant writing puts the split in two short questions: outputs answer what did you do, while outcomes answer what difference the work made in people’s lives. A workshop held is an output. A skill gained, a habit changed, or a need met is an outcome. Both matter, but only the second one answers the funder’s question.
Candid tells funders to put outcomes over outputs when they judge a nonprofit, and gives a plain example: the count of textbooks delivered to a school is an output, while the share of students who reached the honor roll is an outcome. So before you pick any number, write one sentence that names the change you aim for, in words a new volunteer could repeat. Every number below should point back to that sentence. If a number does not, drop it.
The three numbers to track
A practical guide for small teams says measuring well usually means being able to show three things with reasonable confidence: what you delivered, who you reached, and what changed as a result. The three numbers here follow that shape, tightened into counts a two person team can keep in a single spreadsheet.
Number one: who you reached, and how many stayed. Count the people who took part, as single people, not visits. Then count how many finished, stayed to the end date, or came back a second time. Report both counts together, with the dates they cover. Reach without staying can hide a program people try once and leave. Staying is weak proof on its own, but paired with the next two numbers it tells a funder the work held people long enough for change to be possible.
Number two: what changed, before and after. Pick one change your program promises and ask about it at the start and again at the end, using the same short question and the same scale both times. A food program might ask how many days in the past week the household had enough to eat. A tutoring program might use the same short reading check on day one and on the last day. The small nonprofit guide gives the same method: a short question before and after, using the same scale, with a short comment from a person who took part to help explain the result. Report the starting point, the end point, and how many people answered both times.
Number three: what happened next. Choose one next step that fits your promise and count how many people took it within a set time you name in advance. Examples: a job class counts how many people sent a job application within thirty days. A health signup program counts how many people kept a first appointment. A youth program counts how many people signed up for the next term. This number is harder to collect than the first two, and a smaller count here is normal. It is also the number funders remember, because it shows the change lasted past your last session.
Collect the numbers inside work you already do
The system holds only if collecting adds almost no new work. Put the before question on the signup form or first session sheet you already use. Put the after question on the last session sheet, the closing form, or the follow up call you already make. Keep one spreadsheet with one row per person and one column per number, and give one named person the job of checking it each month for gaps and repeat rows.
Use the same words, the same scale, and the same time window every round. Most bad outcome numbers are not false. They are uneven: the question changed halfway through the year, the end count covers a longer period than the start count, or two staff counted the same person twice. A plain written rule for each number, kept at the top of the spreadsheet, prevents most of that. Write who counts, what counts, and what does not count, before the round starts.
Present the three numbers honestly
When you report, put each number next to its base. Write “of the people who started” or “of the people who answered both times,” and give the count behind every share. If people left before the end, say how many and say that your change number covers only the people you could measure twice. Name the dates the numbers cover. Add one short comment, with permission, from a person who took part, chosen because it is typical, not because it is the best story you have.
Also say what the numbers cannot show. A before and after gain does not prove your program alone caused it. Other help, time, and the person’s own effort all play a part. Saying that plainly does not weaken a report. It is what makes the rest of the report believable, and it matches what careful funders already know about small programs.
What not to do
Do not track twenty numbers in the hope that one will look good. Do not report visits as people, or signups as results. Do not change the question mid year and then join the two halves into one result. Do not round a count up, fill a gap with a guess, or leave out a weak round. Each of those choices trades a small short term gain for the one asset a small nonprofit cannot replace: a funder’s trust that your numbers mean what they say.
GrantTitan is built for this kind of plain reporting. Your verified profile is checked against IRS records, grants publish their rules in full, and check ins are set when an award is made, so the dates and the counts live with the grant instead of in one person’s memory. GrantTitan is in pilot, and seekers pay $0 to verify, post a need, or apply. It will not choose your three numbers for you. That choice belongs to your program. Pick them this week, write the counting rules down, and by the next report you will be able to answer the funder’s question with numbers you can stand behind.