Tracking Pay Range Disclosure Updates

Pay range disclosure rules continue to expand across jurisdictions. These laws require employers to publish a salary range on a job posting, or to provide one on request. The exact rules differ by state and city: some cover only external job postings, others also cover internal promotions and transfers. In every case, the employer must know its own pay bands well enough to publish them accurately.

Why this reaches beyond HR

Transparency norms reinforce a broader enterprise theme: stakeholders expect accurate, accessible data, not a data set that was correct once and never checked again. A pay range that no longer matches what the company actually pays fails the same way a stale record fails anywhere else in the business — it looks authoritative and is wrong.

The same principle applies to supplier data

Supplier masters carry the same risk. A supplier record is only useful if it reflects the supplier as it exists today: current certifications, current ownership, current risk status, current commodity codes. Inaccurate records undermine diversity, risk, and ESG commitments in specific, traceable ways:

• A diversity spend report overcounts or undercounts certified suppliers whose certification status changed since the record was last checked.
• A risk review flags a supplier whose issue was already resolved, or misses one whose issue is new.
• An ESG report cites a supplier against criteria the supplier no longer meets.

The fix is a cycle, not a cleanup

A one-time data cleanup does not solve either problem, because pay bands and supplier facts both keep changing. Pay bands need a review cycle tied to market movement. Supplier masters need a review cycle tied to supplier-side events: certification renewals, ownership changes, address changes, and risk incidents. Treating that review as a recurring process, not a project with an end date, is what keeps the underlying data usable when someone actually has to act on it.