ICIMS EEO reporting setup comes down to four things: voluntary self-identification questions in the application, an EEO category on every job, an EEO tab on the Person profile that only the right user groups can open, and two reports in the Reporting Center that pull it all together. Get those four right and your EEO-1, VETS-4212, and applicant recordkeeping work becomes a report you run, not a spreadsheet you rebuild.
Most instances we audit have the questions turned on and nothing else finished. The category field is blank on half the requisitions, hiring managers can open the EEO tab, and whoever files the reports exports the whole database and filters it by hand. That is the gap this guide closes.
How EEO data flows through ICIMS
During the application, candidates are asked a set of voluntary self-identification questions covering gender, race, disability, and veteran status. Each question includes an opt-out option, so a candidate can decline any single question. The answers store on the candidate’s Person profile under the EEO tab, according to the ICIMS Community article on EEO reports.
That is the whole data model. Person profile holds the answers. Job profile holds the EEO category. The Recruiting Workflow connects the two, so a report can show which candidates applied to which jobs and where they ended up. If you are new to how those three objects relate, our explainer on ICIMS data structure for non-technical teams is the place to start.
Three practical consequences follow. First, EEO data is only as complete as the questions you present, so an application with the questions turned off for a portal produces a report with blanks. Second, the EEO Report aggregates by job category, so a blank category on a job drops those candidates out of the rollup. Third, the EEO tab is a tab like any other, which means its visibility is governed by user group, and that is where most instances are too open.
What changed in 2026 (and what did not)
A lot of ICIMS instances were configured around federal contractor rules that are now being retired, and the configuration has not caught up. Here is the short version of the regulatory picture as of September 2026, drawn from OFCCP’s August 21, 2026 final rules.
The pattern to notice: the reports most companies actually file (EEO-1 and, for contractors, VETS-4212) did not change. What changed is the disability self-identification requirement and the race and sex plan framework for contractors. So the right response is not to rip the questions out. It is to review each question against a current obligation, keep what still has one, and make sure whatever you keep is voluntary, restricted, and reportable.
ICIMS EEO reporting setup in six steps
This is the sequence we run on every engagement. It is deliberately ordered: the obligations come first because they decide everything downstream.
Confirm which obligations apply
Sit down with HR, the compliance owner, and counsel and write a one-page list: which reports you file, which entity files them, what the reporting period is, and which demographic fields each one needs. This list becomes the spec for every step below. Do not configure from memory of what the last company did.
Review the voluntary questions in the application
Apply to one of your own jobs on every career portal you run and read the self-identification step as a candidate would. Check three things: every question is presented as voluntary, every question has an opt-out choice, and the categories match what your filings need. Multi-portal instances often have one portal configured differently from the rest, which is why we test each one rather than trusting the template.
If you are also reworking the application itself, our ICIMS career portals setup guide covers the portal-level settings that decide which steps a candidate sees.
Populate the Job EEO Category on every job
The EEO Report in ICIMS aggregates self-identification data per job category, so the category field on the Job profile is what makes the rollup work. Put it on your job templates so new requisitions inherit it, and run a Job search for open and recently filled jobs where the field is empty, then fix them in bulk before your reporting window.
Map each category to the EEO-1 job category your filing uses. The person who files EEO-1 should own that mapping, not the recruiter opening the requisition.
Restrict the EEO tab by user group
ICIMS restricts access to profiles, tabs, and fields by user group, per the Community article on the Person profile. Use that. The EEO tab should be visible to the compliance or HR role that files the reports and, if you choose, a system administrator. It should not be visible to recruiters, hiring managers, or interviewers who make selection decisions.
Check the search and report side too. A user who cannot open the EEO tab should not be able to add EEO columns to a Recruiting Workflow search. Our ICIMS login groups setup guide walks through how tab and field permissions are layered, which is the model you need here.
Run and save the two Reporting Center EEO reports
Go to Report, then Reporting Center, then the EEO Reports panel. Run the EEO Recruiting Workflow Report and the EEO Report, adjust the date filter to your reporting period, and save the versions your team will reuse. The next section explains what each one is for.
Document the process and put it on a calendar
Write down who runs which report, when, which filters they use, and who receives the export. Then add a review to the calendar for every regulatory change and every workflow change. A new Hired status that is not flagged as hired, for example, will quietly drop those hires out of your hired-candidate analysis. We cover this ownership question in depth in our post on the signs an ICIMS system audit is overdue.
Not sure who can see your EEO data today?
We audit application questions, job categories, user group visibility, and the Reporting Center setup, then hand you a documented process. Flat monthly pricing, no surprises.
Book an ICIMS discovery callThe two built-in EEO reports, and how to use each
ICIMS ships two EEO reports. Both live in the EEO Reports panel of the Reporting Center, and both are also available as search templates under Search, then Recruiting Workflow, from the Search Template dropdown. Same data, two doors.
EEO Recruiting Workflow Report
This is the row-level report. It displays candidates’ EEO data alongside the jobs they applied to. Use it when you need applicant-level detail for a recordkeeping request, an internal analysis, or a reconciliation against your HRIS. Because it is a Recruiting Workflow search under the hood, you can group it by Job Title and filter by status, which is exactly how the Community article builds its two sample analyses.
EEO Report
This is the aggregate report. It rolls EEO data up per job category, which is the shape your EEO-1 preparation wants. Its default filter shows all candidates with an Application Date of This Year. Change that before you export. Your filing has its own snapshot or period rules, and “this year” from the day you run it is rarely what the form asks for.
Two searches worth saving
The ICIMS Community article gives two recipes we recommend saving as named searches so nobody rebuilds them each quarter.
Once those exist, the reporting owner can subscribe to them or run them on a schedule the same way you would any other search. If your team is still deciding what leadership should see from the system, our guide to building ICIMS recruiting reports leadership will use pairs well with this one, with one caveat: EEO searches should never be shared to the same audience as pipeline dashboards.
Five configuration mistakes we see most often
Where FlowFam fits
ICIMS Professional Services builds the instance. We help your team run it, and EEO reporting is one of the areas where a second set of eyes pays off fastest because the cost of getting it wrong is a compliance problem, not a productivity one. Our ICIMS consulting services include a configuration review that covers the application questions, job categories, user group visibility, and Reporting Center setup described above, and a full ICIMS system audit when you want the whole instance checked at once.
The outcome we aim for is simple. When the reporting window opens, the owner logs in, runs two saved reports, and sends the export. No spreadsheet surgery, no scramble to find out who can see what.
Frequently asked questions
Make EEO reporting a two-report job
Tell us how your instance is configured today and we will show you what to tighten before the next reporting window.
Book an ICIMS discovery call
