The role that ended with the grant: HR for NGOs and social enterprises

A programme officer on a three-year project learnt that her role was ending six weeks before the project's close date. The close date had been fixed since the grant was signed. Her manager had known for a year that no follow-on funding had been secured, and had said nothing because the conversation was difficult and there was always a chance something would come through. She found other work, in another sector, and when asked about the organisation afterwards described it as one that would let you find out from a calendar. The organisation had not been careless with her. It had been avoiding a conversation it knew was coming.

Sector HR runs against a structural fact: roles exist for as long as a grant does, and much of what a commercial HR function takes for granted — a permanent role, a single cost centre, a workforce that is entirely paid — does not apply. What can be managed is whether the foreseeable is handled honestly, and most of it is foreseeable.

AT AWARD       role end-date recorded against the grant period,
               visible to the person and the manager
SIX MONTHS     funding position stated honestly: secured,
OUT            probable, or not; redeployment explored across
               other funded projects
THREE MONTHS   confirmed either way; notice given if ending;
OUT            handover of programme knowledge, community
               relationships and beneficiary records planned
AT CLOSE       donor reporting complete; records transferred;
               alumni and re-engagement list updated

The end-date is known at the start. Everything
after it is a choice about honesty.

Because the end-date is usually foreseeable, the avoidable failure is late notice, and the reason it happens is that managers postpone a hard conversation in the hope that funding will arrive. Six months' honest notice — 'the funding is not secured; here is what we are trying; here is when we will know' — is tolerated far better than six weeks' certainty, and it keeps people in the sector rather than driving them out of it. Redeployment across other funded projects is the primary retention mechanism the sector has, and it only works if someone holds a view of which roles end when and which projects need what. That view, and the conversation it enables, is the exit and offboarding process as it has to work here — starting at award, not at close.

Staff funded thirty per cent by one grant and seventy by another are common, and a system that cannot express cost allocation across projects and funding sources forces a parallel spreadsheet that becomes the real record. The HR system in this sector has one requirement most commercial systems do not: every person's cost must be attributable to one or more funded projects, including splits, and reportable to each donor in that donor's format. Where that is absent, donor reporting is assembled by hand every quarter and audit-readiness is a project rather than a state. The payroll process management discipline underneath is the same as anywhere — cut-off, owner, freeze — with the allocation added as a field that has to be right before the run, not reconstructed after it.

1. 1

   Record the allocation at joining, per person

   Project, funding source, percentage. Changed when the funding changes, in the system of record, not in a side sheet.

2. 2

   Distinguish core from project-funded roles

   Core functions — finance, HR, the people who keep the organisation running between grants — are funded from core, or they end with whichever grant was paying them.

3. 3

   Keep audit-ready documentation continuously

   Per project, as it is made. Assembling it during a donor audit is where sector organisations lose the most time and confidence.

4. 4

   Report in the donor's format from the record

   Not from a spreadsheet somebody rebuilds each quarter.

Sector organisations often assume that shared purpose covers engagement. It carries people for a while and then stops, usually presenting as sudden burnout rather than gradual disengagement, and the organisations that lose people this way are frequently the ones with the strongest sense of mission — because purpose was doing the work that workload management, honest funding communication and development should have been doing. Workload acknowledged rather than absorbed into commitment; field staff given the same attention as programme staff; psychological support where the work involves distress; career development discussed even where funding is uncertain; and above all, transparency about the funding position, which is the strongest engagement lever available. Staff who understand the position tolerate uncertainty far better than those who learn about it from a calendar.

Field staff work in remote locations, in security-sensitive contexts and in direct contact with people in distress, and both physical and psychological risk are real and routinely under-resourced. The practical items are a safety and security briefing before deployment, travel and communication protocols for remote work, lone-working arrangements, and — the most under-addressed wellbeing risk in the sector — vicarious trauma, which falls hardest on the most junior and most remote staff. Safeguarding induction is the one item that cannot be deferred to a quieter week: it is among the few in sector onboarding where the consequence of a gap falls on someone other than the employee, and it belongs before the first field deployment, recorded per person.

A workforce that is partly voluntary needs the two populations administered distinctly — different records, different obligations, different exits — and the relationship between them managed deliberately, because a volunteer doing a paid role's work, or a paid role treated as a volunteer's, is where both legal and morale problems start. The HR policies and governance work here is mostly the line: what volunteers do and do not do, how they are inducted and safeguarded, and how the organisation makes sure that the goodwill of volunteers is not used to fill gaps that funding should have covered.

Sector hiring has a specific timing problem: the grant is awarded, the project has to start, and the role has to be filled quickly for a term that is already fixed. Filling it quickly with someone who does not understand that the role is funded, and for how long, is how the opening story begins — the end-date is a surprise only if it was never discussed at joining. The recruitment process here states the funding position in the advert and at offer: the project, the term, the funding secured, what happens at the end. Candidates who accept on those terms tolerate the end far better than those who discover them. The other structural item is the core team: finance, HR and the people who keep the organisation running between grants are funded from core or they are funded from whichever project is paying them, and when that project ends the organisation loses its own administration.

• State the term and the funding position at offer, in writing, so the end is not a discovery.
• Fund core roles from core, or watch the finance officer leave with the project that was paying her.
• Keep an alumni and re-engagement list, because the next grant will need the people the last one trained.

List every funded role with its end-date and its funding status, and for each one ending inside a year, ask whether the person has been told. That list, and the conversations it prompts, is where HR for NGOs and social enterprises work begins, because it addresses the sector's most common and most avoidable loss. Then the allocation record, so the spreadsheet can retire. Then safeguarding, before the next deployment. The programme officer in the opening left the sector over a conversation postponed for a year; sector HR work exists to make that conversation ordinary, six months out, and honest.