Nonprofits and NGOs

A nonprofit's people are paid for by programmes, and every funder wants to know how much of your team's time its grant bought. PeopleMuster records that as it happens. Your staff log hours against each programme, with leave and attendance in the same system. Your grant report starts from logged hours instead of a guess.

A core team and the programmes around it

You probably run a small core team on office hours. Around it sit programme staff who join when a grant starts and leave when it ends. Some programmes run evening sessions or weekend events, and those people need a different window.

Each window is a named shift, assigned per person from a start date. A youth programme that meets from four until eight gets its own shift, and late minutes read against it rather than against the office day.

Fixed-term contracts are the part that moves. Your directory filters by employment type and department, so the fixed-term people on each team are one filter away.

Attendance at the office and at partner sites

Head office can run a ZKTeco fingerprint terminal on its own network. PeopleMuster connects to it by IP and pulls new punches every 30 minutes on weekdays. Fingerprints stay on the terminal, and PeopleMuster receives only who punched and when.

Programme staff working from a partner's premises use browser check-in instead. An admin switches it on, and each person's card opens inside a window around their assigned shift. Your admin sets how early it opens and how late it closes.

A missed window becomes a manual punch request that HR reviews. For an audit-minded funder, that's the point: every correction has a date, a reason and the name of whoever approved it.

The number funders ask for

Staff time by programme. How many of your people's hours each grant paid for, and how many went to core work nobody funds directly.

Set up each funded programme as a project, and core costs as projects of their own. Your team logs each day in the daily recap, split across the programmes they worked on, and a manager approves the week.

Utilisation reporting then shows hours by project, by department and week over week. When a grant period closes, that programme's logged hours are where your funder report begins. You can post the report to Slack for the finance lead the same day.

Every change to a logged hour is in the activity log with its before and after values. If a funder asks why March looks different from the last report, you'll see who edited what, and when.

Leave matters here too. Programme staff take leave against the same quotas as everyone else. Approved days come off the capacity grid, so nobody plans a session around someone who's away.

Which modules run here

Switched on

Daily recap
Hours per programme, logged by the person who did the work, with weekly approval.
Utilisation reporting
Programme hours by department and week, posted to Slack when the report is due.
Projects
Each funded programme, and each core cost, as a project of its own.
Checklists
One joining routine and one leaving routine, run for every fixed-term hire.
Devices
Laptops and phones issued to programme staff, recovered when the grant ends.
Policies
Your code of conduct and travel rules in one place, with an assistant that answers from them.
Feedback
Staff feedback with identities masked by default, revealed per item by an admin.
Activity log
Before and after values on every edit, for the day a funder asks.

Left off

Clients
Your donor records stay in your fundraising system.
Meetings
Programme sessions rarely produce a recorded call to file.

Questions people ask

Can we report staff hours by grant?

Yes. Make each grant-funded programme a project, and your team logs hours against it in the daily recap. Utilisation reporting then shows hours per programme, by department and week over week.

How do we handle staff whose contract ends with the grant?

Build a leaving checklist once, with handover, device return and access removal as its steps. Run it against each person as the end date nears, and you'll see its progress and assignee until every step is resolved.

What does it cost a nonprofit?

$3 per person per month, or $30 per person per year if you pay annually, which gives you two months free. Every module is included, there's no setup fee, and you can cancel any time.