The nonprofit version of this question is usually mis-stated, including by the people asking it. The need is rarely "we want to know if staff are working". It is "our funder requires us to show how staff time was spent across restricted grants, and we are reconstructing it from memory every quarter".
Those are different problems and they want different tools. Getting the distinction right saves money and avoids importing a surveillance culture into an organisation that cannot afford the goodwill.
The real requirement: allocation, not productivity
Grant funding is typically restricted. If a programme officer's salary is 40% funded by Grant A, 35% by Grant B and 25% from unrestricted income, the organisation has to be able to show that the work actually broke down that way — to funders, to auditors, and sometimes to a regulator.
In practice most organisations reconstruct this at quarter end from calendars and recollection. It is approximate, it absorbs management time, and it is the thing an auditor queries.
What solves it is time allocation by project or funding stream: a lightweight way for staff to attribute hours to grants, with enough record to survive an audit. That is a timesheet problem, and the products that solve it are time trackers and project accounting tools, not workforce analytics.
Our note on automatic versus manual time tracking covers the trade-off, and for grant reporting the answer leans manual more than it does elsewhere — an auditor wants an attribution a human stands behind, not an inference from application usage.
Why monitoring is a poor fit for the sector
Three reasons beyond cost.
Autonomy is part of the compensation. Nonprofit staff frequently accept materially below-market pay. Part of what they get in exchange is trust and latitude. Introducing activity surveillance withdraws some of that, which means it is not a neutral addition — it is a pay cut nobody costed. In a sector with recruitment difficulty, that matters.
The work resists activity measurement badly. Casework, advocacy, community organising, fundraising relationships — the valuable parts happen in conversations, in the field, and over timescales that activity data cannot see. A caseworker's good week may contain very little desk time.
There is usually no administrator. Enterprise tools assume someone configures rules and reviews output. In a twelve-person charity nobody has that time, so complex tools go unused while still being paid for. The small business guide covers the same constraint, and most of it transfers.
What is genuinely worth measuring
If there is budget and appetite for analytics beyond allocation, a few questions pay back in this sector specifically.
Administrative burden. Nonprofits run a lot of reporting — to funders, boards, regulators — and it tends to accrete. Quantifying how much of the week goes to reporting rather than programme delivery is a finding boards act on, because it translates directly into mission impact.
Systems friction. The sector runs donated, discounted and ageing software, often poorly integrated. Hours lost moving data between a CRM, a finance package and a grant management system is a real and recoverable cost, and it is the strongest case for an integration or replacement.
Workload concentration. Small teams with specialised roles concentrate risk on individuals. One person who knows the grant reporting process is a continuity problem, and it is visible in load distribution — see capacity planning.
Overwork. Mission-driven organisations have a well-documented tendency toward unsustainable hours, partly because staff believe in the work. After-hours and weekend patterns are the earliest reliable signal, and in this sector leadership frequently does not know the scale of it — the burnout signals piece covers reading them.
That last one is the use case I would actually argue for in a charity. Not productivity. Sustainability.
Volunteers: don't
Volunteers are generally not employees, which makes the lawful basis for monitoring them harder rather than easier, and the relationship is voluntary by definition.
Beyond the legal position, the reputational exposure is disproportionate. "Charity monitors its volunteers" is a story, and nothing you would learn justifies the risk. If you need to know volunteer hours for reporting, ask them to record hours — that is a self-report, which is both appropriate to the relationship and what funders generally expect anyway.
Compliance still applies
Nonprofit status changes nothing about data protection. A charity employing staff in the EU or UK is a controller with the same obligations, and the GDPR checklist applies in full. Smaller organisations are if anything more exposed, because there is rarely a data protection officer and the assessments do not get written.
The practical minimum: write down the purpose, keep the collection narrow, set a short retention, put a one-page notice in front of staff. The policy template is a reasonable starting point and takes an hour to adapt.
Where ProdView fits
ProdView is free for three seats permanently, and $4.99/user/month beyond that with no seat minimum, which makes a small-team deployment genuinely cheap. Activity and application metadata only, never screen content or keystrokes, screenshots off by default, useful on install with no rules to configure — which matters when nobody has administrator time. Staff see the same dashboard managers do. Ask us about nonprofit pricing; the answer is usually yes.
When not to pick us: your actual requirement is grant time allocation. We do not produce auditable timesheets attributed to funding streams, and that is the job — buy a time tracker or project accounting tool built for it. We would rather tell you that than sell you seats that do not solve the problem you have.
Try before you commit
Three seats are free forever with no card. If the question is whether staff are working unsustainable hours, that is enough to find out — and it is the question most worth answering in this sector.
General information as of October 2026, not legal advice.