Skip to content
EMPOBase
en

Which HR numbers an NGO leader should watch

By the EMPOBase team · · 4 min read

Short answer

An NGO leader needs a short list of HR numbers, reviewed monthly: headcount by office and contract type, staff turnover, open vacancies and time to fill, leave balances, contracts ending in the next 90 days, training and declaration completion, and staff survey results. Pick the few that guide decisions, define each one in writing, and read the trend, not a single month.

Key points

  • Choose five to eight measures, and define each one in writing so everyone counts the same way.
  • Read trends over several months. One month alone can mislead.
  • Contracts ending soon and overdue declarations are early warnings, not history.
  • Small groups need care: a percentage from five people is not a pattern.
  • A number is a prompt for a question, not an answer.

Why does a leader need HR numbers?

People are usually the biggest cost in an NGO and the thing donors, boards and staff care about most. Yet HR often reaches leadership as a story: “morale is low” or “we are short of staff.” A few clear numbers turn those stories into questions you can check and act on.

The aim is not a big dashboard. It is a short list you can read in ten minutes each month.

Which numbers are worth watching?

Here are seven that suit most NGOs. Define each one in writing.

MeasureWhat it tells youA question it prompts
Headcount by office and contract typeWho you employ and how stable it isIs too much of our work on short contracts?
Staff turnoverHow many leave over timeAre we losing people in one team or grade?
Open vacancies and time to fillHow long gaps lastWhich gaps slow program delivery?
Leave balancesUnused leave and burnout riskWho has not taken a break in a year?
Contracts ending in the next 90 daysNear-term decisionsWhich renewals do we need to decide now?
Training and declaration completionWhether required steps are doneWho has not signed the conduct declaration?
Staff survey resultsHow people feelWhat are the three lowest scores?

You may add measures for your context, but add one only if you can say what decision it supports.

How should you define each measure?

A number is useful only if everyone counts the same way. For each measure, write:

  1. What is counted. For headcount: do you include part-time, casual and volunteer roles?
  2. The period. End of month, or average over the quarter?
  3. The source. Which record the number comes from.
  4. The owner. Who prepares it.

For turnover, decide how to treat staff whose contract ended as planned at the end of a project. Counting them hides real turnover. Excluding them hides pressure on funding. Many NGOs show both.

How do you read the numbers?

Look at trends across several months, not one month. A spike in exits in December might be a normal end of project. A steady rise over six months is a signal.

Also compare groups carefully. A percentage from a team of four people can swing wildly if one person leaves. When a group is small, show the count, not a percentage, and avoid any figure that reveals one person’s details. A common safeguard is to hide any group of fewer than five people.

What are the early warnings?

Some measures look forward, not back. These matter most to a leader:

  • Contracts ending soon. A list of renewals due in 90 days gives you time to decide, fund and tell people with care.
  • Overdue declarations. Unsigned conduct or safeguarding declarations are a compliance gap you can fix now.
  • Unused leave. High balances often mean heavy workload, and sometimes a payout cost later.
  • Vacancies in key posts. A gap in finance or program management can delay a donor report.

See also which numbers show you are keeping good staff and tracking contract renewals.

How do you present them?

Use one page. Put the seven measures in a table with this month, last month and the same month last year. Write one sentence under each number that moved: what changed and what you will do. Review the page at a regular leadership meeting, and record any action in the minutes.

What should you avoid?

Three traps are common. First, tracking a number because it is easy to collect, not because it helps a decision. Second, comparing offices without allowing for size and context: a field base on short project contracts will always show higher turnover than a head office on open-ended contracts. Third, using a number to judge a person. Staff turnover in a team may say more about funding or workload than about the manager.

Also be careful with personal data. A leadership report should show counts and rates, not names. Where one person could be identified from a figure, such as the only woman in a senior grade, leave the figure out.

A good test is to ask of every number: “If this moves by a quarter next month, what would we do?” If the answer is “nothing”, drop it from the leadership page.

Where EMPOBase fits

People & HR holds the records these numbers come from: the staff directory with contract type and end dates, leave, training, declarations and surveys. The HR analytics view shows only figures verified against the records of the organization that owns the data, so a number can be traced to its source. EMPOBase does not set your definitions, so decide them first. See the documentation for the full list of People & HR areas.

Questions people ask

What is staff turnover and how do you calculate it?

Turnover is the number of staff who left in a period, divided by the average number of staff in that period, usually shown as a percentage. Decide whether you count end-of-contract exits, because in project-funded NGOs they change the picture.

How many HR numbers is too many?

More than eight or ten for a leadership meeting. A long list hides the few that need action. Keep the longer list for HR and use the short list for leaders.

Where should the numbers come from?

From the same staff records that HR uses every day. If you build a separate spreadsheet by hand each month, the numbers will drift and nobody will trust them.