Disclosure LibraryPractitioner guidance for every reporting disclosure
Home Disclosure Library GRI GRI 2 GRI 2-7
GRI 2: General Disclosures
Disclosure GRI 2-7

Employees

Practical guidance for preparing this disclosure. Use this card to identify datapoints, verify claims and organise supporting evidence. For exact requirements, always refer to the official GRI source.

Dr Ross Kurinko, GRI Certified Trainer
Reviewed by Dr Ross Kurinko · GRI Certified Trainer LRA educational guidance · Not issued or endorsed by GRI
To prepare this disclosure
Disclosure focus

This disclosure asks an organisation to explain how many people it employs, and to do so in a way that gives a clear picture of its workforce rather than just a headline total. The emphasis is on employees, not contractors or other workers, and on presenting the information in a way that is understandable and comparable across the reporting period.

In practice, the focus is usually on whether the figures cover the organisation’s full operations, including different sites, countries or business units, rather than only its largest or most visible locations. The key question is whether the reported employee numbers reflect the whole employed workforce and are explained clearly enough for a reader to understand the scope and basis of the count.

This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official GRI source.

Before you start

A quick mental checklist before you prepare this disclosure — tick each as you settle it.

Preparation

Key datapoints to prepare

Datapoint What to capture Evidence hint Owner
Total workforce The overall employee count for the reporting period, using the organisation’s chosen counting basis. HRIS headcount extract, payroll summary, or workforce report; reconcile to the source used for the disclosed methodology. HR / People Operations
Workforce by gender Employee numbers split by gender for the reporting period, using the organisation’s defined gender categories. HRIS demographic report and the organisation’s gender classification rules; check the split ties to the total workforce count. HR / People Operations
Workforce by region Employee numbers split by geographic region for the reporting period, using the organisation’s regional grouping. HRIS location report, legal-entity mapping, or regional workforce dashboard; confirm each employee is assigned to one region only. HR / People Operations
Permanent staff total The overall count of employees on ongoing contracts for the reporting period. HRIS contract-type report and payroll records; reconcile the permanent category to the organisation’s employment-status definitions. HR / People Operations
Permanent staff by gender Employees on ongoing contracts split by gender for the reporting period. HRIS contract-type and demographic extract; verify the permanent subset is the same population used for the gender split. HR / People Operations
Permanent staff by region Employees on ongoing contracts split by geographic region for the reporting period. HRIS contract-type, location, and regional mapping report; check the permanent subset is assigned consistently across regions. HR / People Operations
Temporary staff total The overall count of employees on temporary contracts for the reporting period. HRIS contract-type report, agency worker listing if applicable, and payroll records; reconcile to the organisation’s temporary-worker definition. HR / People Operations
Temporary staff by gender Employees on temporary contracts split by gender for the reporting period. HRIS contract-type and demographic extract; confirm the temporary subset is the same one used for the gender analysis. HR / People Operations
Temporary staff by region Employees on temporary contracts split by geographic region for the reporting period. HRIS contract-type and regional location report; verify temporary workers are assigned to the same region logic as the total. HR / People Operations
Zero-hours staff total The overall count of employees with no guaranteed hours for the reporting period. HRIS contract-type report and payroll roster for casual or variable-hours staff; reconcile to the organisation’s no-guarantee-hours definition. HR / People Operations
Zero-hours staff by gender Employees with no guaranteed hours split by gender for the reporting period. HRIS contract-type and demographic extract; check the no-guaranteed-hours subset is complete before the gender split is calculated. HR / People Operations
Zero-hours staff by region Employees with no guaranteed hours split by geographic region for the reporting period. HRIS contract-type and regional assignment report; confirm all no-guaranteed-hours workers are mapped to one region. HR / People Operations
Full-time staff total The overall count of employees working full-time for the reporting period. HRIS working-pattern report and payroll records; reconcile the full-time category to the organisation’s working-hours definition. HR / People Operations
Full-time staff by gender Employees working full-time split by gender for the reporting period. HRIS working-pattern and demographic extract; verify the full-time subset is the same population used for the gender split. HR / People Operations
Full-time staff by region Employees working full-time split by geographic region for the reporting period. HRIS working-pattern and regional location report; check the full-time subset is assigned consistently across regions. HR / People Operations
Part-time staff total The overall count of employees working part-time for the reporting period. HRIS working-pattern report and payroll records; reconcile the part-time category to the organisation’s hours-based definition. HR / People Operations
Part-time staff by gender Employees working part-time split by gender for the reporting period. HRIS working-pattern and demographic extract; confirm the part-time subset is complete before the gender split is produced. HR / People Operations
Part-time staff by region Employees working part-time split by geographic region for the reporting period. HRIS working-pattern and regional assignment report; verify the same region logic is used for both the total and the breakdown. HR / People Operations
Counting method A plain explanation of how the workforce figures were built, including whether they are based on individual people, FTE, or another counting basis. Disclosure methodology note, HR reporting policy, and the source report definitions; keep the basis consistent across all workforce tables. HR / People Operations
Timing basis A plain explanation of whether the workforce figures reflect the period-end position, an average over the period, or another timing basis. Disclosure methodology note and reporting calendar; confirm the same timing basis is used throughout the workforce disclosure. HR / People Operations
Workforce context Any background needed to make the workforce figures understandable, such as organisational changes, scope boundaries, or classification rules affecting the reported numbers. Management commentary, HR reporting notes, and scope mapping; include only context that helps explain the reported workforce data. HR / People Operations
Workforce movements A clear explanation of any major rises or falls in employee numbers during the period and compared with prior periods. Month-by-month HRIS trend, restructuring records, and joiner/leaver analysis; tie the explanation to the reported workforce totals. HR / People Operations
+ Show GRI 2-7 sub-elements (LRA working checklist)

How to prepare it

1Set the reporting boundary first: decide which workforce population you are counting and make sure the same scope is used across the whole disclosure, so the totals and splits all relate to the same employee base.
2Define the categories you will use before you start counting. Separate the workforce into the required employment types, then sort each group by gender and by region, so every figure can be placed in the right bucket.
3Choose and record the counting method up front. Confirm whether you are using individual people, full-time equivalent measures, or another approach, and note whether the figures reflect the period-end position, an average over the period, or a different timing basis.
4Gather the source records and build the numbers from them. Use payroll, HR or equivalent internal records to compile the totals for each employment type and the related gender and regional splits, checking that the figures are complete and internally consistent.
5Add the explanatory context needed to make the data understandable. Include any notes that help a reader interpret the figures, and explain any material movement in employee numbers during the period and compared with the prior period.
6Document any exclusions, changes in method, or other assumptions, then compare the draft against the official source to confirm every required total, split and narrative point is covered and nothing has been omitted or mis-stated.
Request the data

Request the workforce headcount and mix data

Translate the disclosure into an internal business question — then adapt it to your organisation's own language.

What is the workforce count and how is it split across contract type, gender and region for the reporting period, with the method and any notable movements explained?

Use your organisation’s own workforce labels first (for example, staff, colleagues, workers, contingent labour, fixed-term, casual, bank, agency, or similar), then map them to the reporting categories needed for sign-off. Keep the request in business language that your team already uses, and only translate into the reporting view at the end.

Weak request

Please provide the GRI 2-7 employee disclosure data, including the required breakdowns and methodology.

Why it fails: This uses framework wording that may not match how the business stores or talks about the data, so the owner may not know which report, system, or internal categories to pull. It also leaves out the practical details needed to reconcile the numbers, such as the period, boundary, basis, and explanation of movements.

Better request

Please send the workforce headcount pack for [period] covering [scope]. Use your normal internal labels for staff groups, gender and region, and include totals, the counting basis, whether the figures are at period end or averaged, the source system, assumptions, and any material changes this period.

Formal email template
Subject: Request for workforce headcount and mix data for [reporting period]

Dear [name/team],

Please could you share the workforce data pack for [reporting period] for the entities/sites in scope for [reporting boundary].

For the pack, please use the organisation’s own workforce labels first, then map them to the reporting view. I need the following:
- total workforce count
- split by contract type used internally
- split by gender using the labels in your system
- split by region / geography used in the business
- the counting basis used (for example, headcount or FTE)
- whether the figures are taken at period end, averaged over the period, or calculated another way
- any context needed to explain the numbers
- any notable changes during the period and compared with the prior period

Please also include the source system, extraction date, and any assumptions or exclusions.

A possible LRA training template only — please adapt this to your organisation and check the official source before sign-off.

Many thanks,
[preparer name]
[team]
[contact details]
Short Teams / Slack version
Hi [name], could you send over the workforce pack for [period] for [scope]? Please use your usual internal labels first, then map them for reporting. I need totals plus splits by contract type, gender and region, along with the counting basis, timing basis, source system, assumptions, and any big changes this period. Thanks — [name]
Industry examples
Retail

Context. A chain with stores, head office, and seasonal staff across several countries.

Adapted request. Please provide the workforce pack for [period] covering stores, distribution centres, and head office in scope. Use our usual labels for permanent staff, fixed-term staff, seasonal staff, and part-time staff, then map them to the reporting view. Include totals, splits by gender and region, the counting basis, timing basis, source system, and any seasonal peaks or store closures that affected the numbers.

Example response. Returned table shows permanent, fixed-term, seasonal, and part-time staff by gender and region, plus a note that December trading drove a temporary increase in seasonal staff in two regions.

Manufacturing

Context. A multi-site business with shift workers, agency labour, and a central payroll system.

Adapted request. Please send the workforce data pack for [period] for all plants and the central office in scope. Use the site’s own worker labels first, then map them for reporting. Include totals, splits by gender and region, and separate lines for permanent, temporary, agency, and part-time staff, together with the counting basis, whether the figures are period-end or average, and any plant shutdowns or ramp-ups that explain changes.

Example response. Returned table shows headcount by worker group, gender, and region, with a note that one plant shutdown reduced temporary staff in the final quarter and a new line start-up increased permanent hires in another region.

Draft your disclosure

Notes that turn data into a disclosure

LRA training templates — adapt them to your organisation, and check the official source before sign-off.

Method note

State how you counted people for the reporting period, including what you treated as each employment category and how you assigned gender and region for the breakdowns.

Context note

Explain that the figures describe the size and make-up of the workforce at the reporting date, and that the splits help readers understand how employment is distributed across contract type, gender and location.

Fluctuation statement

If the numbers moved materially, note the main operational reasons, such as hiring, departures, contract changes or shifts between regions, and say whether the change was temporary or expected to continue.

Content index entry
GRI 2-7 Employees — [location / page] / [notes]
Download Centre

Preparation tools & forms

Professional preparation tools for GRI 2-7 — free with an LRA Community membership. Register once (it's free) and every download unlocks, together with the Disclosure Library, templates and the LRA AI-assistant.

Free · Community members
Assurance readiness

For each claim, check the evidence

ClaimRiskEvidence to check
The information reported for this disclosure reconciles to the underlying source records.What is reported cannot be traced back to the systems or documents it was drawn from, or does not tie out to them.calculation_workbook reconciling the reported value to source_system_export
The information reported for this disclosure is current as at the reporting date.The disclosure reflects a different period, a cut-off before the reporting date, or stale data carried over from a prior period.approval_record showing the data cut-off date and the period covered
The scope behind the information reported for this disclosure is applied consistently.Parts of the organisation are silently in or out of scope, or the scope differs from the prior period without that change being explained.methodology defining the scope and a site_register of what it covers
Everything in scope is included in the information reported for this disclosure — nothing material is left out.Parts of the population that should be reported are omitted, understating or overstating the disclosure.site_register of the full population vs the calculation_workbook of what was actually included

Evidence pack to prepare

Common reporting gaps

The information is presented without a date or as-at point.The scope or boundary of the statement is left undefined.Key terms are used inconsistently across the report.Material changes since the previous period are not disclosed.Assertions are made without supporting detail or a source record.Boilerplate is used that does not actually answer what is asked.
Common gaps

Mistakes to avoid when collecting the data

Wrong data owner
Chasing the wrong team for the headcount file leaves HR, payroll, and local managers each assuming someone else has the source numbers.
Framework language in the request
Asking for the figures using disclosure jargon instead of the business’s own labels makes the data owner map the request to the wrong report or field.
No clear scope or boundary
Failing to state which entities, sites, or worker groups are in scope leads to some people being counted twice and others not at all.
+ Show 5 more

Where judgement is often needed

Set the group boundary after deals and closures
Explain which employing entities are included after acquisitions, disposals or other structural changes, and keep the same cut-off logic clear across the totals and each split.
Choose one people-count basis and stick to it
State whether you used a simple person count, a full-time equivalent approach, or another internal method, and apply that basis consistently across all employee categories.
Fix the timing rule for the numbers
Say whether the figures reflect the position at period-end, an average over the year, or another timing basis, and use that same timing for every table line.
+ Show 6 more
Examples

Illustrative examples

Synthetic, written by LRA — not from a company report, not text from any standard.

Illustrative (synthetic) example — Food manufacturing

: we set out our workforce headcount by contract type, gender and region, and also show the split between full-time and other working patterns. The figures below are internally consistent and are for training purposes only.

This example shows how a company can present a single workforce snapshot with separate views by contract status, gender and geography, while keeping the totals aligned across each breakdown.

Illustrative workforce snapshot (people)
All staff420380
Permanent staff300260
Temporary staff8070
Non-guaranteed hours staff4050
Full-time staff260240
Part-time staff160140
Illustrative (synthetic) example — Logistics and distribution

: we present our workforce counts by employment status, with matching splits by gender and region, plus a separate view of full-time and other working patterns. All numbers are made up for educational use and reconcile within each line.

This example demonstrates a second way to organise the same workforce information, using regional groupings alongside contract type and gender so the reader can see how the totals are built up.

Illustrative workforce snapshot (people)
All staff220180100
Permanent staff15012070
Temporary staff403020
Non-guaranteed hours staff303010
Full-time staff18014080
Part-time staff404020
Company reportsReal published reports
Compare side by side →Get it free

How companies report GRI 2-7

Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Aena S.M.E., S.A.
Air Transportation — Airport Services · Spain · 2025
Open report →
Aena S.M.E., S.A.'s 2025 sustainability report provides detailed data on employees by contract type and gender, showing a total workforce of 11,053 with 4,222 females and 6,831 males (p.213). The report also includes employee distribution by gender, age, region, and professional category for Spain and the United Kingdom (p.291), as well as figures on permanent, temporary, and part-time employees by gender and region for 2024 and 2025 (p.292). However, the report lacks clear narrative or methodological explanations for these data points, and several expected disclosures are not found or remain unclear.
Firstsource Solutions Limited
Professional Services · India · 2025
Open report →
Firstsource Solutions Limited’s ESG Report FY 2024-25 provides detailed headcount data by age group and management level, showing numbers of permanent employees across categories such as top, middle, junior, and non-management on pages 124 and 125. The report also includes gender distribution within employee categories on page 90, with specific figures for male, female, and others. However, there is no clear evidence on methodology or narrative explanations for these data points, and several expected narrative items are not found or remain unclear in the report.
Taiwan Cooperative Financial Holding Co., Ltd.
Banks / Diverse Financials / Insurance · Taiwan · 2024
Open report →
Taiwan Cooperative Financial Holding Co., Ltd.'s 2024 ESG Report provides detailed gender and diversity statistics for employees from 2022 to 2024, including percentages of total employees by gender (p.175) and specific numbers of male and female employees in senior management and management roles (p.176). The report also includes data on new hires and employee transfers or promotions by gender for 2022 to 2024 (p.177). However, the report lacks clear narrative or methodological explanations for these figures, and several expected narrative items related to diversity disclosure are not found or unclear in the report.
✓ LRA AI Assistant · Human-in-the-loop
Dr Ross Kurinko
Ask Study Studio AI assistant about this disclosure
Get practical answers for your reporting context. Your first two answers are free — join LRA Community for free to continue without a limit.
TryHow do I prepare GRI 2-7?What data do I need to collect?Where can I see a real-report example?What mistakes should I avoid?
2 free answers
Check your understanding

Scenarios to work through

A group HR report shows 420 people on the payroll at year-end, but the payroll team also has 35 agency workers and 18 contractors on site. The draft note currently mixes all three groups together in one table.

QHow should you decide which people to include in the employee figures, and what extra detail needs to sit alongside the numbers?
Reveal model answer →

A business has 260 permanent staff, 90 temporary staff, 40 people on zero-hours arrangements, 120 full-time staff and 170 part-time staff. The regional team has only prepared a single overall headcount and says the split by gender can be added later if time allows.

QWhat should you check before sign-off for this disclosure?
Reveal model answer →

The HR system records 310 employees at the end of the year, but the sustainability team has used an average monthly figure of 298 for the narrative. The draft note does not say which approach was used for the employee tables.

QWhat needs to be clarified so the reader understands the figures correctly?
Reveal model answer →

Employee numbers fell from 540 last year to 470 this year after a site closure, while a new shared-service centre added 60 staff in another region. The draft only shows the current-year totals and gives no explanation for the movement.

QWhat should the preparer add to help users understand the change in the workforce figures?
Reveal model answer →
Framework references

Related framework references

How this disclosure maps across the major reporting frameworks.

GRI
GRI 2-7
within GRI 2: General Disclosures
Open official source →
Primary
Related & explore
FAQ

Questions this page answers

How do I prepare a GRI 2-7 Employees disclosure?+
What employee data do I need to collect for GRI 2-7?+
How should I define the reporting boundary for employee data?+
Should I report GRI 2-7 using headcount, FTE, period-end or average figures?+
How do I split employees by gender, region and employment type?+
How should I report the different employment categories (permanent and temporary contracts, full-time and part-time staff)?+
Who in the organisation should provide, check and approve GRI 2-7 data?+
What evidence do I need for assurance or pre-audit review of GRI 2-7?+
How can I use the GRI 2-7 workbook to collect data and build an evidence pack?+
What checks should I run before publishing GRI 2-7?+
How should I explain major changes in employee numbers during the reporting period?+
What are the most common mistakes when reporting GRI 2-7?+
More questions this page can help with