The Pay-Transparency Search Brief for Recruiting Agencies

Compensation ambiguity creates avoidable friction between an employer, a recruiting agency, and candidates. “Competitive salary” can describe a market position, a broad internal band, or no approved number at all. A useful search brief makes the compensation decision operational: what is paid, to whom, on what basis, in which location, and when the information will be shown.

This article uses public guidance as a boundary, not as a universal legal checklist. The Department of Labor explains federal wage requirements, while state and local agencies set additional rules in many jurisdictions. The framework below is buyer guidance. It does not determine which laws apply to a particular search.

Normalize the compensation field

Before asking an agency to source, record the compensation basis: annual salary, hourly wage, commission, bonus, equity, shift differential, overtime eligibility, or a combination. State whether the range is base pay only, a total cash range, or something else. If a bonus is discretionary, label it as such rather than adding it to an implied guaranteed amount.

Field	Decision record	Why it matters
Pay basis	Hourly, salary, draw, commission, or mixed	Prevents incomparable offers
Range	Minimum, maximum, and approval owner	Gives the agency a usable boundary
Variable pay	Formula, eligibility, and timing	Separates likely from possible pay
Benefits	Included, excluded, or summarized separately	Avoids replacing pay with vague value
Location	Worksite, remote states, travel, and time zone	Determines market and rule scope

The agency should not invent a range from a job-board estimate. Ask it to return to the client when the approved range is missing, stale, or inconsistent with the role brief. A recruiter can provide market context, but that is different from authorizing a compensation commitment.

Treat location as a search variable

“Remote” is not one location. A candidate may work from a state where a disclosure rule applies, from a city with a local ordinance, or from a worksite whose rule differs from the candidate's residence. Record the actual work arrangement, the employer's permitted hiring locations, expected travel, and any relocation support. Then map each posting and outreach channel to the relevant location assumptions.

The agency's channel plan should say which range appears on the employer career page, job board, recruiter message, event material, and candidate conversation. A range that is visible in one channel but omitted in another can produce inconsistent candidate experiences and make later comparison difficult.

Ask what the law actually requires

The Department of Labor's FLSA materials distinguish minimum-wage and overtime requirements from the employer's broader compensation decisions. State and local pay-transparency rules may address posting content, applicant requests, employee disclosures, recordkeeping, or enforcement. Because these rules change, the client and agency should verify the current rule for the worksite and candidate location rather than relying on a static national summary.

Ask counsel or the relevant public agency about open questions such as range width, bonuses and benefits, promotion postings, internal applicants, third-party postings, and remote candidates. Record the checked date and source. A recruiter should be able to explain the operating instruction it received without presenting editorial research as legal advice.

Design an evidence test for the agency

Give every agency the same role brief and ask it to return: proposed posting text, compensation language, channels, location assumptions, candidate questions, and escalation points. Score whether the agency preserved the approved range, separated guaranteed and variable pay, surfaced unresolved terms, and avoided unsupported claims. This measures process reliability rather than placement success.

Run the test on a difficult role with real constraints. For example, compare an hourly role with shift premiums to a salaried role with a bonus. Ask the agency to show how it would explain the difference to candidates and how it would record a change after approval. The purpose is to expose handoff defects before a live search.

Make candidate conversations consistent

Candidates should hear the same approved compensation description from the agency, the hiring manager, and any external job posting. Provide a short approved script with room for questions. Instruct recruiters not to imply that a candidate's salary history determines the offer unless the employer has confirmed the practice is permitted and appropriate. Keep a record when the range changes, who approved it, and which candidates received the revised information.

Do not ask an agency to negotiate against an undisclosed ceiling. If the client can adjust pay for scarce skills, define the approval path and evidence required. If the range is fixed, say so internally and let the agency qualify candidates against the actual role rather than promising flexibility it cannot deliver.

Contract controls and limitations

The services agreement should identify who owns legal monitoring, who approves the range, who updates postings, who corrects a mistaken disclosure, and how quickly the agency must notify the client. Include a rule for third-party boards and cached postings. Define record retention for the brief, approval, posting, candidate communication, and correction.

This framework does not list every jurisdiction or predict enforcement. A range can be technically present and still be misleading if it omits material variable-pay terms or does not match the job actually offered. Recheck the applicable requirements when the worksite, role, pay basis, or recruiting channel changes.

Trace one change across the distribution chain

A practical diligence exercise starts with a fictional role whose approved base-pay range changes after advertisements have been prepared. Give the agency the new approval and ask it to identify every affected output. The response should include the source job page, directly managed board listings, known downstream copies, recruiter templates, and candidates who received the earlier information. This tests change propagation rather than knowledge of legal terminology.

Keep the units fixed during the exercise. If the original brief specifies an annual base salary, a later message about total potential earnings must not silently replace it. Ask the agency to show base pay, contingent components, currency, and pay period in separate fields. A reviewer should be able to reconstruct which approved amount appeared in each channel without reverse-engineering a recruiter email.

Use a second scenario involving a newly permitted work location. The legal owner determines the applicable disclosure instruction; the agency must demonstrate how that instruction reaches posting and outreach staff. The test fails operationally if the owner updates the brief but the distributed advertisement continues to describe an obsolete location or unsupported pay basis.

Record correction latency as an observed process measure, with a clear start and end event. The start might be receipt of the approved change; the end might be verification of the controlled posting. A downstream platform that has not refreshed should remain an open exception rather than being counted as corrected because a request was sent. Do not convert this exercise into a promise that every external copy updates instantly.

For a pilot, choose a narrow set of channels so the client can inspect each correction. Expand only after the evidence shows that responsibility and verification survive a real change. Job posting administration support can maintain the distribution record while the employer retains compensation approval. Discuss that workflow using a sanitized change example.

Reconcile a compensation change across an active search

Use a fictional warehouse supervisor search to test the handoff. The employer approves an hourly base range and a separate evening shift premium. Later, the hiring manager changes the opening to a daytime schedule. The agency must identify whether the approved base range stays the same, whether the premium disappears, and whether any other promise depended on the evening assignment. The compensation owner answers those questions before anyone rewrites the advertisement.

Build a change record around the specific requisition rather than a generic salary field. Record the old approved wording, the replacement wording, the schedule assumption, the effective instruction time, and the person authorized to approve it. Keep the premium separate from base pay in both versions. Otherwise, a recruiter may describe the change as a pay reduction while another describes it as an unchanged range, leaving candidates with incompatible accounts of the same opening.

Next, compare the change record with the channel inventory. A correction on the agency website does not establish that a syndicated board, saved recruiter template, or previously scheduled message has changed. Give each affected surface its own observation and owner. Where the agency cannot edit a third-party copy directly, retain the correction request and distinguish a requested update from a verified one. Do not report every channel as current because the primary posting looks right.

Finally, ask the recruiter to review the candidates already in conversation. The useful question is which version each candidate received and whether an approved clarification is needed. Avoid sending a blanket explanation that introduces irrelevant terms to people who never saw the earlier version. Preserve the communication reference and any unresolved question for the hiring manager. This exercise evaluates version control, approval boundaries, and candidate communication; it does not establish that the compensation itself satisfies every applicable disclosure rule.

Sources

1. U.S. Department of Labor, Fair Labor Standards Act - checked October 2, 2026.
2. U.S. Department of Labor, FLSA Fact Sheet #17A: Exemption for Executive, Administrative, and Professional Employees - checked October 2, 2026.
3. California Department of Industrial Relations, California Equal Pay Act and Pay Transparency FAQs - checked October 2, 2026.
4. New York State Department of Labor, Pay Transparency - checked October 2, 2026.

Frequently Asked Questions

Should an agency publish a range before the employer approves it?

No. The agency should escalate the missing decision and use only approved language. A guessed range creates downstream corrections and candidate distrust.

Is a broad range automatically unlawful?

Not necessarily, but a range can be unhelpful or noncompliant depending on the applicable rule and facts. Verify the current requirement with counsel or the relevant agency.

Should benefits appear in the range?

Separate base pay, variable pay, and benefits unless the applicable rule or approved posting format says otherwise. Candidates need to know what is guaranteed and what is conditional.