Pay fairness

Pay fairness investigation, built for defensibility.

here is a bidirectional, -grade for how your organization groups , runs controls, and explains what the data does — and does not — support. Consultant-assisted by design: expert judgment on cohorts, exclusions, and narrative stays in the loop; the platform makes that work faster, clearer, and more auditable.

Context

Pay fairness sits on legal continuity — not on political theater.

After 2025, many boards and leadership teams are cautious about messaging that ties pay analysis too closely to partisan flashpoints — while statutes, private actions, and workforce expectations still require serious answers about how pay is structured. The defensible stance is investigative: precise about methods, restrained about headlines, and explicit about what the evidence does and does not establish.

Executive teams and regulators care whether comparisons use the right , legitimate controls, and stable . — looking at how unexplained gaps run after controls, without assuming one direction is the entire story — is the posture that survives expert review once real data is heterogeneous and real organizations resegment over time.

Tools that summarize pay into a lone “risk score” or compliance widget often crumble when counsel asks simpler questions: which cohort definition? which freeze date? what changed between last quarter and this rerun? Investigation-grade workpapers are not an add-on luxury; they are how serious organizations avoid buying software that collapses the first time someone competent reads the output.

What it is

Five layers from segmentation to defensibility.

Scatterplots and raw regression tables support the workflow; they are not the primary surface. The through-line is a scannable insight queue built for review under scrutiny.

5

Governance / defensibility

Case file, , approvals, exports, audit trails, workpapers.

4

Insight Player / Investigation Workbench

Queues, cards, lists, DAG branches, schema comparisons, status tracking — the primary investigation workbench, not a static scorecard.

3

Insight Translation Layer

taxonomy: statistical signals → organizational language (families of patterns reviewers can scan before raw diagnostics).

2

Compensation Modeling Engine

Regression, residuals, clustering, diagnostics, decomposition (including techniques such as ), scenarios.

1

Segmentation OS

Versioned segmentation schemas, axes, comparable groups, branches, diffs, hashes.

  • Investigation workbenchNot a dashboard that ends at a traffic light — workflow built for questions, branches, and review.
  • Segmentation-nativeEvery insight references how people were grouped — comparable work and schema version stay first-class.
  • Workpaper-grade defensibilitySnapshots, audit trails, and privilege-aware projections meant for counsel and expert sign-off.

What it does

Capabilities for investigation, not applause lines.

Marketing uses plain-language pay fairness; statutes and briefs often say pay equity. Same workflow — vocabulary matches the audience.

Bidirectional disparity detection

Surfaces unexplained pay differences under explicit controls — framed as privileged investigation inputs, aligned with bidirectional remediation, not preset verdicts on who must be adjusted.

Investigation branches

Rerun analyses after resegmentation, exclusions, or model choices; retain lineage between branches and the each step froze.

Frozen evidence snapshots

Freeze parameters, cohorts, and outputs so later work compares apples to apples — foundational for workpaper-style review.

Privilege-aware exports

Operational summaries vs. counsel-facing packets under your privilege zone policies — respecting how is actually managed (a legal question, not a product guarantee).

Threshold profiles per matter

Configure screening rules (including references such as the where appropriate) per investigation — statistics flag follow-ups; legal significance stays with experts.

Cluster intelligence (25-pattern taxonomy)

Plain-language cluster patterns translate modeling outputs into consistent organizational vocabulary across four families — so the queue is readable before anyone opens a scatterplot.

Statistical signals can suggest patterns worth privileged review ( framing is legally specific). Narratives generated inside the toolbox stay descriptive — “unexplained differences,” “recommended for privileged review,” not legal conclusions reserved for counsel.

Who it's for

Teams who already know this is expert work.

  • Compensation leaders owning architecture, policy, and credible internal narrative
  • In-house counsel evaluating exposure and defensibility of methods
  • Outside counsel and consulting firms running privileged investigations
  • HR business partners who need transparent cohort logic, not black-box scores

PEFA service

Pay Equity & Fairness Analysis (PEFA) — executive-grade engagement.

The PEFA offering (cataloged in GET2GREAT) packages the same posture as this product surface: structured problem framing, an explicit analytic plan, and outcomes your leadership and counsel can stand behind.

Problem

You need credible answers about pay fairness, coherent cohorts, and a narrative that survives expert questions — without pretending a single chart ended the inquiry.

Plan

Agree segmentation rules, exclusions, controls, and threshold policies; freeze evidence snapshots; run parallel investigation branches where real-world disagreement exists.

Outcomes

Workpaper-aligned documentation, prioritized follow-ups, privilege-respecting exports, and plain-language scaffolding your experts can endorse — accelerating their work rather than substituting for it.

External resonance

Industry voices align on bidirectional rigor — not vibes.

On Syndio's Ask Anything webinar series, Katie Bardaro discussed pay equity practice in a way that converges with examining compensation differences thoughtfully in more than one direction — the same substantive theme we treat as non-optional in product positioning. This page paraphrases that public conversation; verify wording with Mike before quoting anyone verbatim on the live site.

Bring pay fairness work into a defensible investigation posture.

If your team is past “dashboard theater” and needs cohort logic, frozen runs, and counsel-ready structure, start with a working session. For the longer narrative writeup (companion to this page), see the case-study track in PAT-140 — we'll link it here when it ships.

PAT-140 (pay fairness case study): long-form companion article — link will replace this note when published. Browse the case-study hub →