Measuring Past The Mandate Turns Hiring and Promotion Guesswork Into Visible Patterns

The federal EEO-1 requirement may be on its way out, and for many organizations, the instinct will be relief: one less administrative lift to tackle. But treating workforce demographic data as a compliance chore misreads what it actually is. The reporting obligation was never the point. The visibility was. An organization that stops collecting the moment it's no longer forced to is choosing to operate with less information about its own people at a time when that data is more valuable than ever.

Carlyne Ervin, Vice President of Human Resources at Chrysalis, has been watching HR leaders split into two camps as the vote approaches: those relieved to let go of the reporting burden, and those who understand that the burden was carrying something valuable. She sits firmly in the second group. With more than 20 years in human resources and a career spanning organizational change management, labor law compliance, and employee engagement, the MBA and dual SHRM-CP and PHR credential-holder has spent decades treating workforce data as a management instrument rather than a filing obligation. She's direct about why the distinction matters.

"When you measure your workforce data, it creates awareness. What awareness does is it allows you to see patterns in your organization. It helps you ask better questions." Everything about how she runs data at Chrysalis follows from this perspective.

What organizations are letting go

Ervin doesn't pretend the EEO-1 reporting is painless. She grants that it's a heavy lift, and that plenty of organizations will read a repeal as permission to walk away. Her objection is to what walking away costs. In her framing, a company already measures the things it takes seriously, and workforce data belongs on that list rather than in a separate category labeled 'government paperwork.'

"We measure profit, we measure loss, we measure client satisfaction and customer satisfaction. We should be, and should want to be, measuring our workforce data," she says. The comparison is deliberate. Nobody argues a company should stop tracking revenue because no regulator demands a particular format. Ervin extends the same logic to the workforce. The value of the measurement is internal, and it exists whether or not anyone external is asking for it.

That's why her advice to organizations facing a repeal isn't to stop, but to convert. Keep the discipline, drop the mandated shape. "You don't have to do the EEO-1 report, but certainly produce data by departments. Break down your data," she advises. Reframed that way, the reporting stops being something imposed from outside and becomes an instrument the organization built for itself, which changes how it feels to complete.

What the data actually shows

Aggregated year over year, Ervin says the same demographic data the EEO-1 captures becomes a map of how an organization actually behaves over time. "I'm measuring turnover trends from this data. You can go from year to year when you're aggregating the data by category and by race and gender," she says. "I'm also able to see promotion patterns. This data helps you understand how many leaders are in this role that are females. I'm able to see leadership gaps and recruiting effectiveness from year to year."

Those are four distinct management questions: who's leaving, who's advancing, where the leadership pipeline thins out, and whether recruiting is reaching the right people. They're all answered by one dataset most companies were treating as a filing obligation. At Chrysalis, which has five main center locations plus an additional partner service site, Ervin also uses it for workforce planning as the organization grows. The pattern only becomes visible in the aggregate, which is exactly what gets lost when a company stops collecting the year the mandate lifts.

The privacy objection, answered

Any conversation about collecting demographic data today runs straight into employee wariness about how personal information gets used. Ervin takes the concern seriously, and her answer to it rests on how the data is handled. Because it's aggregated, no individual is exposed. "You're not using names, you're categorizing this data. This is how many Latina females we have in this location in manager-level positions. This is how many in entry-level positions. No one's privacy is divulged when you're producing this data."

The distinction she's drawing is between surveillance and pattern-recognition. The organization isn't learning things about a named person, but about itself. In Ervin's experience, that framing is also what makes the collection sustainable internally because it holds up when employees ask what the data is for. Rather than employees resisting collection, at Chrysalis, Ervin describes them requesting it because the organization connected the data to something they wanted to see. "They want to see themselves being promoted and they want to understand where the gaps are," she shares. "They champion for us to collect this data because they want to see certain groups advance and be considered and be mentored and be promoted into certain roles." That's a meaningfully different posture than a workforce that merely tolerates data collection.

Ervin's closing counsel is deliberately low-barrier, aimed at organizations that might otherwise treat the whole thing as all-or-nothing: start small. "However you measure, just measure. Start somewhere. You can start measuring small, but those measurements help us make more informed decisions." The vote on the EEO-1 requirement will resolve one way or another, and her point survives either outcome. The visibility to see turnover, promotion, and leadership patterns before they harden into problems is worth keeping on its own terms, by whatever name an organization chooses to give it.