HR Management Solutions for NGOs and Social Enterprises

• Organisation structure
• Programme structure
• Reporting lines
• Governance and board interface
• Approval matrix
• Role clarity across programmes

The hardest HR conversation in this sector is the one nobody plans: what happens to a good field officer when the grant that funds the role ends.

• Role-to-grant mapping
• Contract tenure aligned to funding
• Extension and renewal process
• Communication of tenure at hiring
• Redeployment across programmes
• Notice and transition planning
• Retention of key staff between cycles
• Cost allocation across grants

• Volunteer register
• Role description for volunteers
• Induction and orientation
• Code of conduct acknowledgement
• Attendance and contribution records
• Supervision arrangements
• Recognition
• Exit and records retention
• Distinction from employment

• Mobile attendance
• Field reporting discipline
• Activity and beneficiary records
• Travel and allowance rules
• Leave approval in the field
• Missed reporting escalation
• Attendance for project reporting
• Attendance cut-off

• Code of conduct
• Safeguarding policy readiness
• Child protection awareness where relevant
• POSH framework readiness
• Background verification
• Reporting and escalation route
• Investigation process
• Training records
• Acknowledgement records

• Staff cost allocation by project
• Timesheet practice where required
• Attendance evidence
• Contract and appointment records
• Training records
• Policy acknowledgements
• Audit-ready employee files
• Record retention practice

• Headcount by programme
• Staff vs consultants vs volunteers
• Roles by funding source
• Contract end dates approaching
• Field attendance
• Attrition by programme
• Open positions
• Training and safeguarding completion
• Staff cost by project
• Record completeness

Most exits in the sector are not performance or resignation events. A project closes, its funding stops, and the roles it paid for end on a date everybody knew about in advance.

• Role end-dates tracked against grant and project timelines
• Early notice given as soon as the funding position is known
• Redeployment to other funded projects considered first
• Programme knowledge and community relationships documented
• Beneficiary records and case files transferred properly
• Donor reporting obligations completed before release
• Volunteer and field team transitions handled separately
• Alumni and re-engagement list maintained

Because the end-date is usually foreseeable, the avoidable failure is late notice. Staff told six weeks before a known project close, rather than six months, leave with a view of the organisation that follows them into the sector.

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.

• Workload honestly acknowledged rather than absorbed into commitment
• Project end-dates communicated early so people can plan
• Field staff given the same attention as programme staff
• Volunteer and paid staff relationships managed deliberately
• Psychological support where work involves distressing situations
• Career development discussed even where funding is uncertain
• Decision-making transparency, particularly about funding

Funding transparency is the strongest engagement lever available. Staff who understand the funding position tolerate uncertainty far better than those who learn about it when a role ends.

Career development in a funded organisation runs against a structural obstacle: roles exist for as long as a grant does, so long-term planning feels dishonest. It is still necessary, and can be done honestly.

• Progression criteria defined independently of any single project
• Redeployment across projects as the primary career mechanism
• Field to programme and programme to management routes
• Leadership succession mapped despite funding uncertainty
• Development funded from core rather than project budgets where possible
• Honest conversations about funding horizons
• Alumni relationships maintained for re-engagement

Funding development from core rather than project budgets is the structural decision that makes any of this possible, and it is worth arguing for with donors rather than treating as impossible.

Sector HR technology has a requirement most commercial systems do not: every person's cost must be attributable to one or more funded projects, and reportable to donors on their terms.

• Cost allocation by project and funding source, including splits
• Role end-dates tracked against grant periods
• Donor-format reporting supported from the record
• Volunteer records held distinctly from employees
• Field and programme staff on one employee master
• Multi-location and multi-project deployment tracking
• Audit-ready documentation retained per project

Split allocation is the capability most often missing. Staff funded thirty per cent by one grant and seventy by another are common, and a system that cannot express it forces a parallel spreadsheet.

Sector onboarding carries an unusual requirement: telling a new joiner honestly about the funding position and horizon of the role they have accepted.

• Funding source and project horizon explained at joining
• Programme and beneficiary context before field deployment
• Safeguarding and code of conduct induction
• Field safety and security briefing where relevant
• Donor reporting and documentation responsibilities
• Volunteer and community relationships explained
• Probation objectives set against programme deliverables
• Review at a stated date with a documented outcome

Safeguarding induction should not be deferred. It is among the few items in sector onboarding where the consequence of a gap falls on someone other than the employee.

Sector staff frequently work in remote locations, in security-sensitive contexts, and in direct contact with people in distress. Both physical and psychological risk are real and routinely under-resourced.

• Field safety and security briefing before deployment
• Travel, accommodation and communication protocols for remote work
• Lone working arrangements for field staff
• Vicarious trauma and distress exposure acknowledged and supported
• Confidential psychological support, genuinely confidential
• Safeguarding obligations understood by all staff
• Incident and security reporting route that works from the field
• Workload honestly managed rather than absorbed into mission

Vicarious trauma is the sector's most under-addressed wellbeing risk, and the staff most exposed are usually the most junior and most remote.

Sector HR operations carry an external reporting burden that commercial organisations do not. Several donors, each with their own formats, timelines and audit expectations.

• Cost allocation by project and funding source maintained continuously
• Donor reporting formats supported from the HR record
• Role end-dates tracked against grant periods
• Audit-ready documentation maintained per project, not assembled later
• Named ownership for each donor's requirements
• Volunteer and employee administration handled distinctly
• Multi-location and field administration
• Core versus project-funded costs distinguished clearly

Maintaining audit-ready documentation continuously is worth the discipline. Assembling it during a donor audit is where sector organisations lose the most time and the most confidence.

Sector recruitment carries a structural honesty requirement: the role is funded for a period and candidates deserve to know that before they accept, not after.

• Funding horizon stated honestly in the advertisement and at offer
• Requirement planned against grant timelines, not started at award
• Programme and field roles sourced through appropriate local channels
• Language, community and context requirements defined explicitly
• Safeguarding checks completed before deployment
• Mission fit assessed without being used to justify low pay
• Internal redeployment considered before external hiring
• Alumni and former staff re-engagement as a channel

Planning recruitment against the grant timeline rather than from the award date is what prevents the common pattern where a twelve-month project spends three months hiring.

Sector pay is constrained by grant budgets that were often set before the role was scoped, and split funding means one person's cost may be attributed across several projects.

• Salary structure defined independently of any single grant
• Cost allocation across projects and funding sources, including splits
• Donor salary caps and norms accounted for in structure design
• Core versus project-funded roles distinguished clearly
• Benefits designed within funding constraints
• Pay equity across projects maintained deliberately
• Increment policy stated despite funding uncertainty
• Payroll records supporting donor audit requirements

Pay equity across projects is the issue that most damages sector organisations internally - two people doing the same work on different grants at different rates, with no stated reason.

Sector retention runs against a structural constraint: roles end when grants do. What can be managed is whether people leave before they need to.

• Redeployment across projects planned before roles end
• Funding position communicated early and honestly
• Attrition separated into funded-end and voluntary exits
• Burnout risk monitored in field and frontline roles
• Development funded from core budgets where possible
• Pay equity across projects maintained
• Alumni relationships maintained for re-engagement
• Exit reasons captured and distinguished by cause

Separating funded-end exits from voluntary ones is essential here. A combined figure makes the organisation look unstable and hides the exits it could actually have prevented.

Sector organisations are shaped by funding as much as by design, which means the structure can drift into something nobody would have chosen - programme silos that duplicate functions and share nothing.

• Core versus project-funded roles distinguished in the structure
• Reporting lines where staff are split across projects
• Decision rights between programme and organisational leadership
• Shared functions protected from project funding cycles
• Field to head office reporting and accountability
• Board and executive interface defined
• Succession for programme and organisational leadership

Protecting shared functions from project funding cycles is the structural choice that most determines whether an organisation can operate between grants.

Sector workforce planning is inseparable from fundraising. Roles exist because grants do, and planning has to run on the funding pipeline rather than on a calendar year.

• Role requirements mapped to confirmed and pipeline funding
• Roles ending mapped against roles starting
• Redeployment planned before external recruitment
• Core roles protected from project funding cycles
• Lead times for specialist and field roles
• Scenario planning for funding outcomes
• Cost of core function coverage between grants
• Honest communication of the plan to staff

Mapping roles ending against roles starting is what converts an anxious organisation into a planned one, and it is usually possible several months earlier than it is done.

Sector development is constrained by the fact that donors fund programmes rather than staff development, so most learning has to be built from what the organisation already has.

• Development funded from core budgets where possible
• Donor-funded capacity building used deliberately where available
• Internal knowledge sharing between projects and field teams
• Safeguarding and code of conduct training as a non-negotiable base
• Field safety and security training before deployment
• Management capability for programme leads
• Peer learning and sector networks used as low-cost channels
• Development discussed despite funding uncertainty

Sharing knowledge between projects is the cheapest development available and the most commonly lost, because project teams operate as silos with separate reporting.