The Low Screen Number Reset, One Loop Carried From Slip to Final Offer

You told a recruiter a salary number at the screen. You now know it sits below the band, and you are still in the loop. This guide is for candidates who want to raise that number before the offer is written without handing the employer a reason to walk. I take one loop from the slip to the final offer figure: the band math, the reset trigger, the written revision, the pushback, and the wrong turn. You can run the same sequence on your own loop.

How much does a low screen number actually cost you?

Nobody has measured this for job candidates. In buyer-seller negotiation studies, the first number explains between roughly 14% and 86% of the variation in final prices. Those same studies show how to weaken the effect: bring information that contradicts the first number.

Here is what the research shows. Every row is a negotiation simulation, not a hiring loop. Where the source did not state the variance explained, I derived it as r squared.

The table points to three things you can use:

• Experience shrinks the effect. The correlation drops from about .5 to about .37 when negotiators have relevant professional experience. Your recruiter has that experience. So do you, once you have the band.
• Contradicting information removes it. In the Galinsky and Mussweiler experiments, negotiators who focused on information that contradicted the anchor erased its effect on final settlements. For you, that information is the employer's own band.
• More issues mean a weaker anchor. The large meta-analysis (374 effects, 90 studies, N = 16,334) found that first-offer effects shrink as the number of issues grows. Splitting one figure into base, bonus, and equity spreads the anchor across several numbers.

There is also a reason not to panic. One recruiter wrote on Blind: "If the range is 150k - 175k and you tell me your salary expectations are 110k, the MINIMUM I'm going to give you is 150k." Firms with a standard offer per level often pay that floor whatever you said. If that is your situation, the real risk is where in the band you land, not falling below it. That is anecdote, though, and the counter-case on Ask a Manager reports an offer of $80,000, "$10,000 less than what I told the recruiter was my floor." Treat the low number as a live risk.

The worked loop: what was said, and what the band is

The loop in this guide is a composite of public posts. The band and the stated number are the figures a recruiter used in that Blind post: a 150,000 to 175,000 range and a 110,000 answer. The level downgrade and the refusal come from other public posts. I use those sources' dollar figures exactly and compute everything else from them.

Fork 1: reconstruct the slip (about 10 minutes)

Before anything else, write down exactly what you said. In the worked loop, the note reads:

• Figure stated: 110,000
• Component: base salary, not total comp
• Channel: phone screen, verbal
• Also typed into: the application's desired-salary box

Assume the recruiter has it on file. A Blind commenter put it plainly: "recruiters keep very detailed notes." In Greenhouse, a desired-salary box is a custom application question the employer sets up on the posting. The answer lands on your candidate profile and can be linked to a custom field. Greenhouse's offer-exception emails show approvers the band and the offer. Nothing public establishes whether they also show your screen expectation, so assume someone can see it.

The trap at this fork is mixing base and total comp. One Blind poster "low balled my salary and RSU+ bonus" in one breath. If you did the same, write down each component you named, or note that you named none.

Fork 2: get the band and the level (about 1 day)

The band is the contradicting information the research points to, so it comes before any revision. It is useless without the level, because one posted range can span several levels.

How you get it depends on where the role sits. Trackers disagree on how many US states require disclosure (counts of 14, 16, and 18 all appear), so check the current rule on the state labor department's site before relying on this table.

Two details matter for a reset:

• Washington rejects open-ended ranges such as "$60,000/per year and up" or "up to $29.00/hour". If a posting there shows one, the employer has not met the rule, and you can reasonably ask for a real range.
• The EU directive's Recital 32 says the range should not stop you negotiating outside it. Article 5(1) puts the range "in the job vacancy notice or before the job interview." Not every member state has finished turning the directive into national law, so check yours.

If the posting does not settle it, ask the recruiter one question: "Which level is this role budgeted at, and what is the range for that level?" In the worked loop the answer comes back as one level with a 150,000 to 175,000 base range. That is the band from here on.

Sizing the gap: compa-ratio and range penetration

Two numbers show how far below the band your stated figure sits. Compa-ratio is your number divided by the band midpoint. Range penetration is how far into the band your number reaches, from 0% at the minimum to 100% at the maximum. Together they take about 15 minutes and turn "I think I lowballed" into a figure you can put in writing.

• Compa-ratio = stated number ÷ midpoint
• Range penetration = (stated number - minimum) ÷ (maximum - minimum)

Get the direction right. One widely read HR-software glossary gives the inverted form, "Salary Midpoint/Actual Salary", in one place. That turns a low number into a ratio above 1 and makes the gap look like a surplus.

Here are the worked loop's figures against the 150,000 to 175,000 band, with a midpoint of 162,500:

Negative penetration means the stated number sits below the floor of the employer's own range. Here it is 40,000 below the minimum and 52,500 below the midpoint. At that distance a reset rests on the employer's own document, not on how you feel about the number.

For context on where new hires land, one compensation-software vendor recommends targeting new hires at 85 to 95% compa-ratio. One compensation-benchmarking analysis of 15,000 new hires found a median of 1.05 for AI/ML new hires, against 0.97 for existing employees. Those figures disagree with each other and come from different populations, so use them only to see that a reset to the midpoint is not an unusual ask. They are not a prediction.

In the worked loop, the reset figure is the midpoint, 162,500. I pick the midpoint rather than the floor for a reason. The first-offers research says the number you put in writing becomes the new reference point, and an offer at the minimum already gives the employer a figure below the midpoint.

Which reset triggers hold up, and which one failed?

A reset holds when it names a fact you learned after the screen. Recruiters on Blind describe the level as the main lever and competing offers as the other. A revision that only says "I reconsidered" has drawn outright refusal.

Four triggers are worth considering. They do not carry equal weight:

The comp-structure trigger also works for a mechanical reason. Once the employer shows you base, bonus, and equity separately, one anchored figure becomes several, and the research says anchors weaken as issues multiply.

For the scope trigger, you need the posting's requirements laid out against your own history before the debrief, not from memory on the call. Refolk tailors your resume to the specific posting and scores how well you actually fit it. That gives you a written scope comparison to point to when you say the role is bigger than it read.

The wrong turn in the worked loop

The first draft of the revision in the worked loop read, in substance: "I've thought about it more and would like to revise my expectation to 162,500." It named no new fact. That is the shape that draws the response a candidate reported from a Fortune 500 recruiter, who "said 'we don't operate that way' and told me once someone tried doing that and he pulled the plug."

The draft was discarded. The version that went out rested on Fork 2: "You confirmed this role is budgeted at [level], with a base range of 150,000 to 175,000. My 110,000 was given before I had that information." Same number, but now it is anchored to a fact the employer supplied.

The reset a number cannot fix

The Atlassian case on Blind shows the other failure. The candidate stated total comp of 375k+ at the screen and was told after the phone screen that only the "$310k band" was available. That is a level problem, not an anchoring problem, and revising the number does nothing about it. A recruiter on Blind described the same mechanic: "if you crush your FB interview and get an L6 offer from them, but have an off day with us and only get approved at L4, there's not much I could do." If the band drops after interviews, ask about the level before you blame your screen answer.

When does the number lock?

In practice the number locks when the recruiter submits the offer for approval in the applicant tracking system, not when you stop talking about pay. A revision before that point costs the employer no approval work. A revision after it can void the approvals and restart the cycle.

The mechanics, by system:

• Greenhouse. "Creating a new offer version and re-triggering the offer approval process voids the original offer and any associated approvals already issued." Editing a field marked with the Refresh icon also voids prior approvals. An offer outside the range can trigger extra approvers, such as the CFO and CEO.
• Ashby and Lever. These re-approve only when someone changes a field an admin has marked for re-approval. You cannot see that setting from outside, so ask.
• Workday. I could not verify how its screen fields behave.

Sources disagree on how late is too late. Blind commenters say "you can change your mind until you sign the agreement." Ask a Manager warns that employers dislike reversals at the end. The tracking-system mechanics favour going early. No recruiter has published a cutoff, so the safe deadline is the one you can check: ask whether the offer has gone to approval yet.

Who you are actually persuading matters too. In Refolk's index of professional profiles there are 21,285 US profiles titled Technical Recruiter (in a 25-profile sample, 21 held exactly that title) and 4,864 US Compensation Analyst, Partner, or Manager profiles. Sampled employers in the second group include Figma, Meta, and Okta.

A Blind commenter ranks that power as "Finance > HM > Recruiter." Your recruiter cannot approve the reset alone. What they can do is forward a clear, dated email. A verbal revision on a call leaves them nothing to forward.

The reset procedure, step by step

Run these in order. In the worked loop, Forks 1 and 2 have already happened. The revision goes out after the debrief and before the offer is created.

The revision email that went out in the worked loop, generalised:

Subject: Updated compensation expectations - [Role title]

Hi [Recruiter name],

Thank you for confirming that this role is budgeted at [level], with a base range of [minimum] to [maximum].

When we spoke on [screen date], I gave [stated figure] as my expectation. I gave that before I had the level and range, and since the screen I have learned [one sentence: the level / the scope / the comp structure].

Based on that, my updated expectations are:
- Base salary: [revised base]
- Bonus: [revised bonus or "open, pending structure"]
- Equity: [revised equity or "open, pending structure"]

Could you share this with [hiring manager name] before the offer is drafted? And could you let me know whether the offer has gone to approval yet, so I can make sure this reaches the right people in time?

I remain very interested in the role.

[Your name]

Expect the pushback to quote your screen answer back to you. Blind's advice is short: "Ask them why it's low. Explain your research. Sometimes they make mistakes."

Hi [Recruiter name],

I understand I said [stated figure] on our first call. Since then you confirmed the range for [level] is [minimum] to [maximum], and my earlier figure sits below the bottom of that range.

Could you help me understand why the offer would be set below your own range for this level? If the level has changed since the interviews, I would like to understand that, since it changes what we are discussing.

My updated expectation of [revised base] stands, for the reason in my email of [revision date].

[Your name]

How this goes wrong

Most failed resets do not fail on the number. The candidate gets the band, the level, or the timing wrong, or sends the revision without a reason. Here are the eight ways I see it go wrong, each with the check that catches it.

1. Treating lab correlations as cause. The 86% figure is a correlation from a simulation, and position strength can drive both the opening number and the result. Check: in your own notes and emails, say "associated with," never "this will cost me X%."
2. Mistaking a wide posting for a band. An $80K to $180K posting usually spans two or three job levels. False positive: you compute a comfortable compa-ratio against the midpoint of the wrong level. Check: confirm the level before running any arithmetic.
3. Misreading a level downgrade as an anchor problem. The Atlassian candidate moved from a 375k+ ask to a 310k band after interview feedback. False positive: you blame your screen answer and revise the number, but the employer re-levelled you. Check: ask whether the level changed before you touch the number.
4. Revising after the approval request. In Greenhouse this voids approvals and adds a cycle that may involve the CFO or CEO. Check: ask the recruiter in writing whether the offer has gone to approval.
5. Sending a trigger with no new information. This is what draws "we don't operate that way." Check: the trigger sentence must name a fact learned after the screen, as in the worked loop's second draft.
6. Assuming the recruiter passed your number on. Ask a Manager notes that "sometimes the recruiter isn't even passing along your salary expectations." False positive: silence reads as acceptance when nobody upstream ever saw the revision. Check: restate the number in writing and ask that it reach the hiring manager.
7. Mixing base and total comp. If your screen figure blended salary, RSUs, and bonus, a base-only revision can read as a demand for more on top. Check: revise each component on its own line.
8. Using an inverted formula. Midpoint ÷ actual turns a 67.7% compa-ratio into roughly 148% and makes the gap look like a cushion. Check: compa-ratio is always actual ÷ midpoint, and a stated figure below the minimum must give a negative range penetration.

The employer's own band is the counter-anchor. Without the level attached, it can point you at the wrong midpoint.

Classifying the offer and keeping the record current

When the offer arrives, label it one of three things and recompute its two percentages. Old number means at or near what you said at the screen. Reset number means at or near your written revision. Between means anywhere in the gap. The label tells you whether the revision moved anything and what to say next.

In the worked loop, the outcomes look like this against the 150,000 to 175,000 band:

• Old number (around 110,000): compa-ratio 67.7%, penetration -160%. This sits below the employer's own range. Reply with the band and ask whether the level changed. If it did, you are in failure mode 3.
• Between, at the minimum (150,000): compa-ratio 92.3%, penetration 0%. This is the outcome the Blind recruiter described as the minimum. The revision may have done nothing, because a level floor would have produced the same figure, so do not credit it automatically.
• Reset number (162,500): compa-ratio 100%, penetration 50%. The written revision held.

I cannot tell you which outcome is most likely. No survey with a published method covers it, and the public anecdotes range from "the MINIMUM I'm going to give you is 150k" to an offer below the stated floor. Your own record is the only data you will have, so keep it carefully.

Before the next pay conversation, if the reset worked, put the revised figure into your positioning everywhere else. When Refolk tailors your resume and cover letter to the next posting at the same level, the version you send matches the level you just priced, so you are not anchoring low on paper while revising upward on the phone.

Two things change over time and are worth re-checking on every new loop. First, disclosure rules: state counts differ by tracker, and EU member states are turning the directive into national law at different speeds, so check the labor authority for the role's location rather than a summary page. Second, the tracking system: ask each recruiter which system they use and whether the offer has gone to approval. The lock point is a software setting, and it can differ between employers using the same product.