2026 Pay Transparency Checklist for Multi-State Careers Pages

Salary transparency is no longer a side issue for careers pages. For distributed hiring teams, one job posting can touch multiple state rules, multiple recruiting systems, and multiple handoffs between recruiters, hiring managers, and whoever owns the public careers site.

The operational problem is straightforward: if the right fields do not exist before a role goes live, the posting will either ship incomplete or force recruiters to patch details manually after the fact. This checklist focuses on five states with clear official guidance that multi-state hiring teams commonly run into: California, Colorado, Illinois, New York, and Washington. It is an operating guide for job-page design and workflow, not legal advice.

What your careers page system should store before publish

A modern job posting template needs more than a title, location, and apply button. At minimum, your publishing workflow should be able to hold:

a salary range or fixed pay amount
a benefits summary that is specific enough to match the role
other compensation details when applicable, such as bonus, commission, or equity
a role description that can be shown publicly when required
application instructions and deadlines where they matter
jurisdiction logic for where the work is performed, where the role reports, and whether the role is remote

If those fields live only in recruiter notes or compensation spreadsheets, the public posting will drift from what your team actually intends to offer.

The five-state checklist

California

California says employers with 15 or more employees must include the pay scale in any job posting.
The Labor Commissioner interprets that rule to apply if the position may ever be filled in California, either in person or remotely.
California defines pay scale as the salary or hourly wage range the employer reasonably expects to pay for the position.
California does not require bonuses or benefits to be included in the posting, although employers may choose to include them.

Operationally, California is the clearest reminder that a national careers page cannot treat remote roles as law-free just because the company is headquartered elsewhere.

Colorado

Colorado requires employers to disclose compensation in job postings and notices, both internal and public.
The required disclosure must also include information about benefits and how and when to apply.
Colorado's transparency rules are connected to internal mobility workflow too: employers must disclose available job opportunities to employees and then disclose who was selected to fill the position.
Colorado also requires employers to preserve records of wages and job descriptions.

That makes Colorado a workflow problem, not just a copy problem. Your public posting template, internal opportunity notice, and recordkeeping process need to line up.

Illinois

As of January 1, 2025, Illinois requires employers with 15 or more employees that make specific job postings to include the position's pay scale or compensation and benefits in internal and external postings.
The rule applies when the work will be performed at least in part in Illinois, or when the role reports to a supervisor, office, or work site in Illinois.
If an employer or its third party externally publishes a specific posting, the employer must make that opportunity known to all employees within 14 days.
Illinois allows a hyperlink to satisfy the pay and benefits requirement only when it leads directly to the pay and benefits for that specific position. A broad link to a general compensation page is not enough.

For recruiting operations teams, Illinois is a strong case for storing role-level benefits text and keeping an internal notification step inside the same publish workflow.

New York

New York requires employers with four or more employees to include a salary, hourly rate, or range of pay in advertised job, promotion, and transfer opportunities.
The rule applies to opportunities performed at least in part in New York and to opportunities performed outside the state when they report to a supervisor, office, or work site in New York, including remote roles.
New York says postings must contain the job description in addition to the pay range, except in limited situations where the title itself clearly conveys the duties.
If compensation is fully commission-based, the posting must say that clearly.

New York is a useful reminder that pay transparency is not only about numbers. Your public posting also needs a role description that actually matches the opportunity being advertised.

Washington

Washington requires employers with 15 or more employees to include a wage scale or salary range, a general description of all benefits, and a general description of other compensation in job postings.
If the employer is offering only a fixed wage amount, it must disclose that fixed amount instead of a range.
Washington says the range should reflect the employer's most reasonable and genuinely expected compensation range at the time of posting and warns against open-ended language such as "and up" without a real ceiling.
Washington also gives employers a five-business-day opportunity to correct a non-compliant posting after notice before enforcement proceeds.

Washington is where vague templates break down quickly. If your careers CMS cannot store benefits and other compensation separately, your team will end up improvising in public.

One publishing workflow that prevents most errors

Map the role to the relevant jurisdictions before the posting is created. Use work location, reporting location, and remote eligibility, not just company headquarters.
Generate the public posting from structured fields, not from a recruiter-written paragraph alone.
Require compensation and benefits review before publish, especially for multi-state and remote roles.
Render role-specific job description text, not only a generic department template.
Store a copy of the final posting and the inputs used to generate it so recruiting and legal teams can verify what was shown publicly.
Connect external posting to internal notification steps where state rules require it.

If your process depends on recruiters remembering which state needs benefits text, which state needs a job description, and which state needs internal notice timing, the process will fail under load. The system has to carry that logic.

A practical pre-publish checklist for hiring teams

Confirm whether the role can be performed in, reports into, or recruits candidates from a covered state.
Check that the posting contains either a real pay range or a fixed pay amount, not an open-ended placeholder.
Verify whether benefits and other compensation must appear in the public posting.
Make sure the public job description is present where required and matches the actual scope of the role.
Validate that application instructions, deadlines, and links are current.
For externally posted roles, confirm whether employees also need notice of the opportunity.
Archive the final version that was published, including linked pay and benefits content if your workflow uses direct hyperlinks.

Where Apikuo fits

This is exactly the kind of process that should live in your hiring operations layer instead of scattered across email, ATS notes, and ad hoc edits to a careers site. Apikuo is useful here when it becomes the publish gate: one place to store job-page fields, one workflow to enforce required review, and one record of what candidates actually saw.

The value is not simply compliance. Clearer compensation and benefits fields reduce candidate confusion, shorten recruiter follow-up, and make job pages easier to trust.

Conclusion

Hiring teams do not need fifty different posting templates. They do need one reliable publishing workflow that can add the right fields for the right role before a posting goes live. California, Colorado, Illinois, New York, and Washington already make that operational discipline hard to avoid. The teams that handle it well will have cleaner careers pages, fewer last-minute corrections, and a better candidate experience from the first click.

A 2026 Pay Transparency Checklist for Multi-State Careers Pages