What Belongs in a Monthly Volunteer Summary

A program officer skims your monthly summary in about ninety seconds. If the total hours do not tie to a program, if the date range is fuzzy, or if it runs three pages, they stop reading and email you a question instead. That email costs you a week. A tight one-page summary answers the question before it gets asked.

Here is what to put in it, why each piece matters, and how to produce it without retyping numbers.

Report hours as a total per program, not one combined number

A single "412 volunteer hours this month" number tells a funder almost nothing. The grant that pays for your tutoring program does not care about the hours your food pantry crew logged. Break the total out by program so each line maps to something the reader funds.

Apply it with worker groups and tags. Put each volunteer in a group for their program (After-School, Pantry, Front Desk), and the summary splits cleanly by group. If one volunteer helps two programs, tag their time entries by activity so a shift in the kitchen does not count against the tutoring line. The output is one row per program with its own hours total, which is the number a grant report wants.

State an exact date range, down to the day

"April" is ambiguous. Does it include the weekend event on April 30 that ran past midnight? Does a shift that started April 30 and ended May 1 land in April or May? Write the range as literal dates: "April 1 through April 30" or whatever window the grant period uses. Funders often work on quarters or fiscal years that do not start on the first of the month, so match their calendar, not yours.

This matters more than it looks because of how open shifts get counted. A volunteer who forgets to clock out should not dump twelve phantom hours into your total. Kangaroo Clock handles that with auto-close for forgotten clock-outs, which closes a stale entry at its start time plus a cutoff rather than at the current time. A forgotten clock-out never inflates the hours you report, so the number inside your stated range stays honest.

Break out recurring volunteers from one-time helpers

Funders read retention as a sign the program is working. Fifty hours from one steady tutor who shows up every week reads very differently from fifty hours spread across thirty people who came once and never returned. Both can be fine, but the funder wants to see which one you have.

Show a distinct-volunteer count alongside total hours, and if you can, flag the people who logged time in more than one week. The monthly volunteer summary tool gives you the distinct-worker count directly, so you can write a line like "38 volunteers, 11 of them active every week this month" without counting names by hand. That one sentence answers the retention question most program officers are quietly asking.

Keep it to one page, and lead with the numbers

The summary is not a narrative. Put the program totals and the date range at the top where a skimming reader sees them first. A short paragraph of context underneath is fine. Anything longer belongs in a separate narrative report that you attach, not in the summary itself.

A workable layout fits on one page:

Three columns of numbers, one row per program, a clear date range in the header, and you are done. No one needs a pie chart to read that.

Pull the numbers from your clock data, not a spreadsheet you retype

The fastest way to introduce an error is to copy hours by hand from one place into another. If your volunteers already record time at sign-in, the summary should come straight from that record. Every entry is stored in UTC and shown in your local time, so a shift that crosses midnight lands in the right day without you doing math.

When a funder wants the underlying detail, hand them a CSV export of the raw entries. The column schema is stable and never breaks, so the file you send in April opens the same way as the one you send in October, and a program officer who imports it into their own system will not hit a surprise. If a volunteer also needs proof of their own hours, the volunteer hours certificate generator produces that from the same data.

Set the programs up as worker groups once, pick the exact date range each month, and the summary becomes a two-minute job instead of an evening with a calculator. Start a free workspace and run your first month before the next report is due.