The Salary-Expectations Answer Kit, Built Once to Deploy Across a Batch

Before you send a batch of applications, the pay field is a decision you want to make once and reuse, not a fresh judgment call on every posting. This guide is for job seekers running an active search across many companies at the same time. It builds a floor, target, and stretch figure set, an entry rule for each type of pay field you will hit, and a tracking method that keeps the number you gave each company consistent from the form through the recruiter screen.

Most advice answers "what do I put for one application." That is the wrong unit of work when you are filling forty forms. The real risk at volume is not picking a wrong number once; it is giving forty forms numbers you will contradict in a later screen, or letting your figure drift down as you tire. The fix is a kit you deploy, not a decision you re-litigate.

Why build the salary answer once, before the batch

Because the number you type is sticky, and at volume you will otherwise contradict yourself. Once a form is submitted, the applicant tracking system - the software that stores and sorts applicants, "ATS" from here - has flagged your figure as your stated expectation, and you almost never negotiate upward from it. A batch built on a single logged figure removes the contradiction risk entirely.

There are two failures a volume search creates that a single application never exposes. The first is the contradiction: you type one number into the form, then say a different, higher number on the call, and now you are breaking your earlier word in front of the person who holds your record. The second is drift. Across forty forms, decision fatigue lets your numbers creep down without you noticing. One documented tracker showed a candidate's target band slipping from $145K to $128K over 30 applications, which surfaced only because the band was logged per role. A fixed figure set plus a logged column is the only defense against both.

You are also outnumbered at the point of entry. In Refolk's index of professional profiles, the people screening your number vastly outnumber those setting the bands, so the figure you submit is read by someone optimizing for fit and budget fit, not by a compensation specialist who might debate your worth. That makes a defensible, consistent figure matter more than a clever one.

The figure set: floor, target, stretch

Build three fixed numbers from market percentiles, and anchor your ask at target, not at floor. Use the median as your fair-pay benchmark, the 25th percentile as your minimum acceptable rate, and the 75th percentile as a stretch target for exceptional experience. Your ask belongs in the upper half if your track record supports it, and you should never open below the midpoint.

The floor is the load-bearing number, because the bottom of your stated range is the number you will be offered. If the bottom is X, you will be offered X, so make X a figure you will not resent six months into the job. This is the single most common way the kit fails: people set their floor as a safe-looking lowball, then get offered exactly that.

Pull your percentiles from two or three sources, not one. Self-reported salary data skews high, so include the US Bureau of Labor Statistics as a neutral cross-check on median wages by region. Glassdoor, Payscale, Salary.com, and LinkedIn Salary are commonly cited, but treat any single one as a draft, not a defense.

The stated range: how wide, and where the bottom sits

Set one reusable range string with a 10 to 15 percent spread and your true floor as the bottom. A spread of ten to fifteen percent reads as considered; a spread of forty percent reads as a guess. The point is a single "$X to $Y" string you paste into every range field without re-deciding its width.

Employers budget wider than most candidates guess, which is why a tight floor-anchored number often lands well below the top of their band. The modal employer structure is a 30 percent band, meaning plus or minus 15 percent from the midpoint. The table below shows how employer band widths distribute and how many employees sit inside each - evidence that there is usually room above your number if you anchor at target.

There is a genuine disagreement in the sources here, and you should know it before you lock your width. The tight-spread camp argues 10 to 15 percent reads as deliberate and keeps you from capping yourself below the band top. An executive-coaching view argues the opposite: go wider to avoid naming a ceiling you would regret. I favor the tight spread for applications specifically, because a wide range lets the employer off the hook - pitching $225K to $240K when their range reaches $265K hands them the bottom. Keep your stated spread inside your real acceptable zone. If you want one more degree of flexibility without going wide, a bracketing range that spans your target, such as $90K to $110K for a $100K target, reaches about the same result as a single point but reads as more flexible.

A single number invites downward pressure; a tight researched range gives the recruiter a path to yes inside your zone.

Entry rules per pay-field type

Write one rule for each field type you will encounter, so you match the form to a rule instead of making a fresh decision. Four field types recur, plus the blank-allowed case: free-text, numeric-required single, range, and minimum-only. Below is the lookup card. Build yours once and keep it open during the batch.

One caution on the numeric-single field. One source advises selecting the lower end of your range or slightly below ideal to avoid screening yourself out of a search filter. That is a defensible read if you are worried about a hard budget cutoff, but it trades away anchoring power. My default is a figure slightly above target, because the single number you submit sets the ceiling you will be pulled toward, and you rarely recover upward from it.

Salary history bans do not remove the field

In a state that bans salary history, you still need a figure, and it matters more, not less. Pay transparency laws, salary history bans, and the desired-salary field operate independently. History bans prohibit asking what you currently earn; they do not prohibit asking what you expect. Missouri employers, for instance, cannot ask for or use pay history but can discuss expectations. So the desired-salary box stays legal and common even in ban states, which means it becomes the only pay anchor the employer can legally collect. Named ban states include California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Maine, Maryland, Massachusetts, Nevada, New Jersey, New York, Oregon, Vermont, and Virginia. Have your figure ready in every one of them.

The build procedure, end to end

Run these eight steps once to produce the kit, then deploy it across the batch. The first five are one-time setup totaling about seventy-five minutes; the last three are per-application and per-week habits. Each step names what "done" looks like so you do not over-polish the setup.

Writing a defensible figure set from your own history, then tailoring the number to each posting's market, is exactly the kind of repeatable work Refolk is built to carry, so you spend the two minutes per form entering a figure rather than rebuilding your rationale.

The tracker: one column most templates miss

Add a dedicated "figure I gave them" column, distinct from the posted range, because that is the number you must repeat on the call. A stock 15-column tracker already carries Company, Role, Status, Date Applied, Source, Recruiter Name, Salary Min, Salary Max, Location, Remote, Notes, Follow-up Date, Interview Round, Offer Amount, and Decision Date. Those Salary Min and Salary Max columns log the posted band - what the employer offered, not what you said. The critical add is the exact figure you entered, so drift is visible and no call contradicts a form.

Company | Role | Field type encountered | FIGURE I ENTERED | Posted range (min-max) | Date applied | Recruiter | Status
Acme | Senior Analyst | Range field | $135K-$150K | $130K-$160K | 2024-xx-xx | - | Applied

Logging the figure per role is what makes drift measurable. The documented slippage test is simple: after about thirty applications, look at the average of your figure-given column. If it has crept below your target, easy-apply roles are probably skewing junior of what you actually want, and you have been accepting that quietly. The same logging habit pays off elsewhere, since tracker-triggered follow-ups are cited as lifting response rates 2.5x over an average 19.9-week search, so the column earns its keep beyond pay consistency.

How this goes wrong: failure modes and false positives

The kit fails in predictable ways, and most failures look safe at the moment you make them. Here is each failure, the false signal that masks it, and the local check that catches it.

The placeholder gets read literally. The false positive is that the form accepts "000" or "999," so you assume it passed. An aggressive ATS may have flagged you or auto-sorted you low instead. Check: look for a free-text or notes box to add "negotiable," and re-read whether the field says "number" or "annual salary" before trusting a placeholder.

You enter your floor as your target. It feels safe and non-greedy. In reality, if the bottom of your stated figure is X, you will be offered X. Check: never type a number you would resent, and confirm the figure in the field is your target, not your walk-away.

Your range is too wide. You think wide equals flexible. Pitching $225K to $240K when their range reaches $265K lets them off the hook. Check: keep your stated spread inside your real acceptable zone, 10 to 15 percent.

You contradict your form number in the screen. The recruiter already has your logged figure, and raising it later means breaking your earlier word. Check: read your tracker's figure-given cell before every call.

Band drift across a long batch. You do not notice your numbers creeping down as you tire. Check: run the average-band slippage test after about thirty applications.

You assume a ban state means no salary field. History bans do not remove the expectations field. Check: keep a figure ready even in California and New York.

You trust one salary source. Self-reported data skews high. Check: pull two or three sources, including BLS.

Carry the figure into the screen without contradicting it

When a recruiter asks your expectations, ask once for their range; if they push back, repeat the exact figure you logged. The salary question opens the process, and the number you give in the first call sets a ceiling for everything after it. Saying "actually, I expected more" later means breaking your earlier word, so the screen number and the form number are one number, not two.

The move is simple and repeatable. If the recruiter has not shared their band, try once: "What range is budgeted for this role?" If they deflect, give your researched range - the same string you entered on the form. This keeps you from naming a new ceiling and keeps your record internally consistent, which is the whole reason you logged the figure in the first place.

If you want to see who is actually asking you the number, so you can calibrate who you are talking to before a screen, Refolk can surface the exact population on the other side of the field.

Keep the kit current across a multi-week batch

Reconcile weekly and re-pull your baseline if the search runs long, because a batch that spans weeks is where drift hides. Each week, scan the figure-given column against your floor, target, and stretch set, and confirm nothing has slipped. The average search in the tracking data runs close to twenty weeks, long enough for your sense of a fair number to erode without a written anchor.

Three triggers mean re-pull your baseline rather than trusting the old set: the search crosses several weeks, you add a new target title or market, or a posting's transparency-disclosed band sits consistently above your target, which signals the market moved under you. When any of those fire, redo step one and reset your three numbers. The kit is designed to be rebuilt in about seventy-five minutes, so refreshing it is cheap, and a current figure set is what keeps forty forms honest and one call from contradicting the record you already submitted.