Rebuilding job posting data so salary ranges are mandatory, auditable fields
Virginia pay transparency law compliance now starts inside the Applicant Tracking System, not in a policy PDF. Under Va. Code § 40.1-28.7:9, every employer operating in Virginia must treat the salary range in job postings as a required data element, with a defined wage or salary field that cannot be bypassed by hiring managers or recruiters. If your ATS still allows a blank pay range or free text for compensation, your data architecture will fail the new state transparency law requirements and leave you exposed when employees or regulators review postings.
Under the new law, Virginia employers must include a wage or salary range in every internal and external job posting, and those ranges job by job must be based on existing pay practices, historical pay ranges, or budgeted compensation. That means HRIS and People Ops teams need structured fields for salary ranges, pay ranges, and salary bands that are linked to each job, not buried in unsearchable attachments. In practice, that can mean configuring fields such as “Minimum Base Pay,” “Maximum Base Pay,” and “Pay Grade Code,” then enforcing validation rules so that no job posting can be approved unless a good faith pay range is entered and tied to a specific compensation structure in the HR database.
For multi state employers, the safest pattern is to standardize pay transparency across all job postings rather than building one workflow for Virginia pay and another for other jurisdictions with different transparency laws. In practice, that means mapping every job to a canonical pay range in your HR master data, then exposing that range automatically in the ATS template for employees and external candidates. A simple compliance checklist can help: confirm that every Virginia requisition has a non-null salary range, verify that the range matches the HR master record, and log the timestamp and user for any edits. If your team still struggles with inconsistent employee records across systems, start by reviewing guidance on master data management for HR and then extend those principles to wage, salary, and pay equity fields.
Defining defensible compensation ranges and documenting pay decisions
The law does not just ask for any number, it expects a defensible salary range grounded in real compensation data and consistent pay practices. Virginia pay transparency law compliance therefore requires employers to define salary ranges and pay ranges using documented pay scales, historical wage data, or budgeted compensation amounts that can be shown to regulators or employees. If your compensation team cannot explain how each pay range was calculated, your transparency law posture will look weak when employees start asking questions or when an investigation requests supporting documentation.
From a data governance perspective, every employer should maintain a central compensation table that links each job to its salary bands, target wage salary, and any geographic differentials across the state. At minimum, that table might include columns such as Job Code, Job Title, Location, Pay Grade, Minimum Salary, Midpoint, Maximum Salary, and Effective Date. That table should feed both job postings and internal pay decisions, so that hiring managers cannot improvise a new pay range or salary history based adjustment outside the approved structure. To manage privacy and regulatory risk around wage and salary history inquiries, you can borrow techniques from a structured privacy risk assessment for HR data and apply them to compensation, pay equity analytics, and employee level wage records.
Because the law bans salary history inquiries, any employee or prospective employee pay decision must be justified by role, market data, and internal equity, not by prior wage or salary history. Voluntary disclosure of salary history by employees or candidates can only be used to increase compensation, never to depress the offered pay range or wage salary level. Official Virginia Department of Labor and Industry guidance interpreting Va. Code § 40.1-28.7:9 describes a 15 business day correction window before litigation, during which an employer can cure a violation after receiving notice, so employers will need clear audit trails showing when a job posting was corrected, which pay ranges were updated, and how employees were notified.
Operational workflows for history inquiries bans, multi state coverage, and HRIS evidence
The ban on pay history inquiries forces a redesign of everyday hiring workflows, especially for hiring managers used to asking about prior wage or salary in early screening calls. To align with Virginia pay transparency law compliance, HRIS and ATS teams should remove any salary history fields from application forms, disable history inquiries prompts in recruiter scripts, and retrain employees who conduct interviews. For prospective employee interactions, the focus should shift to explaining the good faith salary range, clarifying pay practices, and documenting any compensation exceptions inside the HR system with fields for “Exception Reason,” “Approver,” and “Approval Date.”
Multi state employers now face a patchwork of transparency laws, and Virginia joins a growing list of state regimes that regulate pay transparency, salary ranges, and wage data retention. Rather than coding one off rules for each state, leading employers are building a single compliance layer that tags every job with its jurisdiction, required pay range, and applicable transparency law obligations. That same layer can support other regulatory programs, as shown by data driven compliance work such as Iowa mandatory reporter training for HR, where employees, managers, and systems must align on clear reporting requirements and consistent recordkeeping.
For HRIS and People Ops leaders, the practical test is simple, and it goes beyond Virginia pay alone. Can you produce, within hours, a list of all job postings in the state, the salary ranges and pay ranges attached, the date each posting went live, and any corrections made within the 15 day window? If the answer is no, your data architecture for pay, wage, compensation, and employee records still needs work, because regulators and employees will not accept promises, only evidence. A periodic self audit that pulls this report, checks for missing or inconsistent ranges, and confirms that no salary history fields remain in workflows can turn the legal standard into a repeatable operational routine.