Toward more scrutiny of the substance and less tolerance for the adjective. The direction of travel in US corporate diversity reporting over recent years has been away from narrative pages in a glossy report and toward two harder questions: what did you actually do, and can you show the records. That shift comes from several directions at once, and they do not all push the same way.
For an ERG lead, the practical translation is short. Stop optimizing for the annual publication and start keeping a clean evidence file: dated activity, named budget lines, aggregated participation, and documented eligibility criteria. That file is useful whether the pressure arrives as a disclosure request, a regulator's audit, a shareholder proposal or a plaintiff's discovery request. It is the one asset that holds up regardless of which way requirements move.
Here is what to keep, why, and what to ask your general counsel before the next reporting cycle.
The current landscape: EEO-1, federal contractor rules and voluntary disclosure
Three separate regimes get blended together in conversation. They are worth untangling because they place very different obligations on you.
The EEO-1 Component 1 report is filed with the Equal Employment Opportunity Commission by private employers of 100 or more employees, and by certain federal contractors at lower thresholds. It is a headcount of employees by job category, sex and race or ethnicity. It is a workforce demographic filing. It says nothing about ERGs and your ERG data does not feed it.
Federal contractor obligations sit with the Office of Federal Contract Compliance Programs and rest on affirmative action program requirements for covered contractors, including recordkeeping and audit response. This landscape has been actively contested and revised, so the single most important thing to know is who at your company tracks it, and to ask them each year rather than assuming last year's answer still stands.
Voluntary and semi-voluntary disclosure is where ERG content usually appears: the annual sustainability or corporate responsibility report, the proxy statement's human capital section, customer diligence questionnaires, and supplier RFP responses. This is the least regulated category and the one most likely to be quoted back at you.
Keep reading: What actually happens in the two weeks before an ERG annual impact report goes to the board?
Why ERG activity shows up in human capital reporting
Because it is one of the few things a company can point to that is concrete, dated and countable. Representation numbers move slowly and are largely outside a single year's control. Programs, events, mentoring cohorts and budget are within it.
That is why the ERG paragraph tends to get drafted last and reviewed hardest. Someone in investor relations or corporate communications needs a sentence with a number in it. If your records cannot support the number, either a weaker sentence goes in or, worse, a stronger one goes in based on a figure nobody can reproduce six months later.
Treat every number you hand to that team as one you may have to substantiate under oath. In practice this means: know the source system, know the date range, know the definition, and be able to produce all three on request.
What counts as a company record and how long it must be kept
Most ERG leads assume their materials are informal. They usually are not. If the activity is company-sponsored, funded from a company budget and run on company systems, the artifacts are company records subject to your organization's retention schedule and to litigation hold if one is issued.
Under EEOC recordkeeping rules, employers are generally required to preserve personnel and employment records for a defined period, and to preserve all relevant records once a charge of discrimination has been filed until final disposition. Your retention schedule is set by counsel, not by you. Your job is to know which of your artifacts fall inside it.
Practically, treat these as records:
- Event invitations, agendas, attendance lists and post-event summaries
- Budget requests, approvals, purchase orders, invoices and reimbursements
- Eligibility and membership criteria, and any version history of them
- Selection criteria for mentoring, sponsorship or development cohorts
- Survey instruments, the raw response file and the reported summary
- Leadership term records, chapter charters and sponsor assignments
And treat these as risky places to keep them: a personal drive, a departing lead's laptop, a group chat, a shared inbox nobody administers. When a hold lands, records in those places are still discoverable and much harder to produce cleanly.
Aggregation thresholds that protect individual employees
The single most common self-inflicted problem in ERG reporting is publishing a cell small enough to identify one person. If your Denver chapter has nine members and you report satisfaction by chapter and by level, someone will work out who said what.
Set a minimum group size before you report anything, and apply it without exception. Many organizations use a threshold in the range of five to ten responses; pick one with your privacy or employment counsel and write it into your reporting standard. Then apply two rules alongside it:
- Suppress the small cell, and suppress a second cell too. If one region is hidden and the total is shown, the hidden value can be derived by subtraction. Suppress the next smallest as well.
- Do not cross-tabulate to the point of identification. Chapter by level by tenure will identify people in almost any mid-size company. Report one dimension at a time.
Say the threshold out loud in your report. A line reading that groups under the threshold are not shown separately is a credibility signal, not an apology.
Keep reading: How do I write an ERG charter that HR and legal will actually approve the first time?
Self-identification data and who is allowed to see it
Self-identification data, whether gender, race, disability status, veteran status or LGBTQ identity, is voluntary, is collected for specified purposes, and is generally held by HR under access restrictions. ERG leads are usually volunteers, not HR staff, and typically should not hold the identified file at all.
The workable arrangement is that HR runs the join and holds the identity data, and the ERG receives aggregate counts above the threshold. You get to say how many people in a population participated. You do not get a list.
Two specific cautions. Disability-related information collected under the Americans with Disabilities Act carries confidentiality obligations and is kept in separate confidential files. And membership in a women's network is not itself a lawful proxy for gender in any employment decision, so a roster should never travel into a talent review, a promotion slate or a layoff selection file.
Program versus preference: how legal reviews eligibility criteria
This is the question counsel is actually worried about, and it is worth understanding rather than being surprised by.
The core concern under Title VII is that a company-sponsored program should not restrict a term, condition or privilege of employment on a protected basis. Legal teams therefore look hard at whether an ERG is an open community or a closed benefit.
The distinctions that tend to matter in review:
| Reviewed favorably | Reviewed with concern |
|---|---|
| Membership open to all employees, with a stated focus | Membership limited by a protected characteristic |
| Allies explicitly welcome at events | Events where attendance is screened by identity |
| Development open to any employee meeting neutral criteria | Sponsorship or promotion pipelines limited by group |
| Named business purpose in the charter | Charter that reads purely as an affinity social club |
| Consistent criteria applied and documented | Criteria applied informally by the lead |
Nothing here is legal advice, and the analysis is fact-specific and jurisdiction-specific. The takeaway is procedural: write your criteria down, keep the version history, and have counsel review them once a year. An undocumented practice is harder to defend than a documented one, even when the practice itself was fine.
See how ERGCircle handles this for employee resource group programs
Building an annual evidence file you can hand to counsel
One folder, one owner, refreshed each year, structured the way a reviewer reads. A workable structure:
- Charter and criteria. Current charter, eligibility language, dated versions of both, and the date of the last legal review.
- Activity log. Every event with date, format, host, location or time zone, topic, and attendance count.
- Budget. Approved amount, actual spend by category, and the reconciliation to finance's ledger.
- Participation. Distinct participants, aggregated only, with the suppression threshold stated.
- Listening. Survey instruments, response counts, response rates and reported summaries.
- Published claims. Every external or internal statement made about the ERG that year, with the source figure behind each one.
Item six is the one people skip and the one counsel wants most. If a claim appears in the annual report, the recruiting site and a customer questionnaire with three slightly different numbers, that inconsistency is the finding, not the underlying program.
Questions to ask your general counsel this quarter
- Is our company a covered federal contractor, and does that change our recordkeeping obligations this year?
- What is our retention period for ERG event, budget and survey records, and where must they be stored?
- What minimum group size should we apply before reporting any breakdown?
- Who may hold membership data containing self-identified characteristics, and in which system?
- Have you reviewed our current eligibility language, and when was that review dated?
- Which of our published ERG claims would you want substantiated before the next filing?
- If a litigation hold were issued tomorrow, would our ERG materials be captured by it automatically?
Start with the file, not the forecast
You cannot control which way disclosure expectations move next. You can control whether, on any given Tuesday, you can produce a dated activity log, a reconciled budget, an aggregated participation count and a version-controlled charter within an hour.
That is the whole discipline, and it is a systems problem rather than a willpower problem. ERGCircle keeps the event log, the budget reconciliation, the aggregated survey results and the annual impact record in one place, with the dates and definitions attached, so the evidence file assembles itself as the year runs instead of being reconstructed after the request arrives.
