The Pre-Close Call Run, From Test-Close Questions to a Written Recap
Run the days between final round and offer approval as a dated sequence, and send a same-day recap so the approval packet carries your exact package, not a yes.
Key takeaways
- Recruiter pre-close scripts aim to get commitment to every part of the offer before it is presented, so any unconditional yes on the call can be logged as an acceptance.
- In Refolk's index there are about 7.1 US recruiters for every compensation professional, and the person who approves your numbers relies on the recruiter's packet, not on anything you said.
- Get the level name and the band for that level before you state any number, because a wide posted range can span several levels.
- An equity percentage means nothing without its denominator: ask whether the share count is fully diluted and what it includes, since some companies quote only outstanding shares.
- In Pew data on people who asked for more, 66 percent got more than the first offer but 38 percent landed below their ask, so set each stated number above your walk-away.
- Send a written recap the same day as the call, restating level, base, bonus, equity count and denominator, sign-on, and start date, and mark it as not an acceptance.
Your final round just ended and the recruiter is calling to ask "what will it take?" or "if we offered X, would you accept?" before anyone writes the offer. This playbook is for the candidate taking that call. It covers the days from final round to offer approval in order, gives you a reply to each scripted test-close question that doesn't commit you, and ends with a same-day written recap that the recruiter takes into the approval step.
What is a pre-close call, and why does it shape the offer?
A pre-close call is the recruiter's conversation between your final round and the offer approval. Its purpose is to find out exactly which package you would accept, so the one they submit gets a yes. Most of the offer gets decided on this call, because the package that goes for approval is built from what you say here.
Two terms:
- Test-close question: any question that asks you to commit to a hypothetical offer, such as "If they offer this base with this bonus, would you accept?"
- Approval packet: the package the recruiter submits internally (level, base, bonus, equity, sign-on, start date) plus their notes on you.
The scripts behind this call are written for recruiters, and they say plainly what they're for: getting commitment to every aspect of the offer before presenting it. Top Echelon's assumptive-close guidance tells recruiters to strip subjective words "such as if, were, would, and could." When you say "if," that's exactly the word the script is designed to remove. Your job is to keep the condition in what you say and then put it back in writing.
Who is on the other end, and who isn't
The person who approves your numbers almost never hears the call. They read the recruiter's packet.
| Function (US) | Profiles in Refolk's index | Top sampled title |
|---|---|---|
| Recruiting | 36,351 | Technical Recruiter (13 of 25) |
| Compensation / Total Rewards | 5,124 | Compensation Manager (12 of 25) |
| Recruiters per comp professional | 7.1 (derived) | - |
Whether you are talking to an agency or in-house recruiter also predicts how scripted the call will be. In Refolk's index, 36% of the top employers in a 25-profile sample of US recruiters were agencies, and every test-close script I found was written for agencies ("my client"). The German sample looks different:
| Market | Profiles in Refolk's index | Top title in sample | Agency share of top employers |
|---|---|---|---|
| United States | 36,351 | Technical Recruiter, 52% | 36% (Experis, K2) |
| Germany | 765 | Talent Acquisition Partner, 52% | 8% (Wipro) |
| US to Germany multiple | 47.5x (derived) | - | - |
What this shows: in the US sample, Experis (6) and K2 Partnering Solutions (3) account for 9 of 25 profiles, and in-house employers such as Snowflake, HubSpot, and H2O.ai also appear. The German sample is led by in-house teams: Siemens, GetYourGuide, Delivery Hero, Airbus. If your recruiter says "my client," expect a scripted test-close. What it can't show: a 25-profile sample tells you the mix, not how any one recruiter behaves, so prepare the same way either way.
How long does the window between final round and offer approval run?
At large employers, the first 24 to 72 hours after a final round usually covers only the debrief. One published Cisco timeline puts the whole run from final loop to written offer at 15 to 29 business days. The long part of the process is the time after your recap, while you wait.
| Stage (Cisco, published timeline) | Business days |
|---|---|
| Final loop to debrief | 5 to 7 |
| Debrief to offer approval | 7 to 14 |
| Approval to verbal offer | 1 to 3 |
| Verbal to written offer | 2 to 5 |
| Total (derived) | 15 to 29 |
The other published timelines say similar things:
- Meta: 2 to 4 days for interviewer debriefs, then a wait of up to a week for the weekly Hiring Committee review.
- NVIDIA: the hiring committee reportedly meets every 2 weeks.
- Google: 3 to 7 days for formal offer assembly.
- A generic timeline: compensation approval on days 3 to 5, when the recruiter assembles base, bonus, equity, and sign-on inside the approved band, then the offer call on days 6 to 14.
All of these come from aggregator blogs that don't show how they were built. Treat them as rough guides, not deadlines to chase the recruiter with.
Final round to written offer
- Debrief closesFeedback submitted and hire decision made, about 2 to 7 business days
- Fact pull and callYou get the anchors, then state one number per component
- Written recapSame-day email, marked not an acceptance
- ApprovalBand placement and sign-off, 3 to 7 days up to 7 to 14 business days
- Verbal then written1 to 3 business days to verbal, 3 to 10 to written
Sources also disagree about when the test-close happens. Top Echelon tells recruiters to test the close "at every sourcing stage." Recruiteze puts it after the client approves the offer and before it's presented. Bolywelch puts it right after the final interview. So you may get a test-close question at the screen too. This guide covers the one after the final round, because that's when your answers go straight into the approval packet.
Which facts do you need before you state any number?
You need five anchors before you name a figure: the level, the band for that level, the bonus basis, the equity count with its fully diluted denominator, and the start-date limits. Without them, a number you state can be reasonable and still land in the wrong band.
| Fact | What it proves | How it misleads |
|---|---|---|
| Level name | Which band applies to you | A wide posted range spans several levels |
| Band for that level | Where your number sits | The range quoted is for the posting, not your level |
| Bonus basis | What the target % is paid on | A % with no basis or payout terms |
| Equity count and denominator | What you actually own | A % calculated on outstanding shares only |
| Start-date limits | Whether your notice period fits | A "flexible" date that turns fixed in the letter |
This question is documented and easy to reuse word for word: "Which level is this role budgeted at, and what is the range for that level?"
Where in the band a first offer lands
Compa-ratio is pay divided by the midpoint of the band, expressed as a percentage. Compensation-practice sources say new hires typically land between 80 and 95 compa-ratio, which means below the midpoint. No survey with a published method measures how many offers actually land below, at, or above the midpoint, so treat this as a working assumption. To check it, ask for the band's minimum and maximum. If the recruiter shares the midpoint, you can see where an 80 to 95 placement puts the base.
If you aren't sure which level you match, compare your history against the posting's requirements line by line. Refolk scores that fit from your own history against the posting, so you go into the level conversation with evidence, not a guess.
Equity facts to request
Equity guides agree on what to ask for:
- the fully diluted share count, and what it includes
- the strike price compared with the latest 409A valuation, plus the date of that 409A
- the latest preferred share price
- the size of the option pool, and how much of it is unallocated
- the liquidation preference stack
A 409A is the independent valuation a private US company uses to set the strike price on options. Per Carta, it's valid for up to 12 months, so a date tells you whether the valuation is current. An option pool at 30% or more of fully diluted shares signals heavy future dilution.
What a fully diluted denominator can include
- SAFEs and convertible notesHow these are modeled into the count, if at all
- Unissued option pool reserveShares set aside but not yet granted
- Granted options and warrantsRights already issued to employees and others
- As-converted preferredInvestor shares counted as if converted to common
- Outstanding commonThe smallest base, and the one that makes your percentage look largest
Nobody has published which of these facts companies usually share before the offer and which after it. Ask for all of them, and write down which ones the recruiter declines to give. A refusal is useful information in itself.
Hi [Name], Thanks for getting back to me. Before we talk numbers, could you share a few details so we're working from the same package? 1. Which level is this role budgeted at, and what is the range for that level? 2. Bonus: what is the target percentage, and what is it paid on? 3. Equity: the grant size in shares, the fully diluted share count it is measured against, what that count includes, and its date. 4. If options: the strike price, the date of the latest 409A, the latest preferred price, and how much of the option pool is unallocated. 5. Any constraints on start date. Happy to cover these on the call if that's easier. [Your name]
Swap in the role name; drop the equity lines for public-company RSUs and ask for the grant value basis instead.
Which pay-range rights still apply after the final round?
In several US states and across the EU, you have a right to the pay range at this stage, and in many places the employer may not ask about your pay history at all. Some disclosure rules only kick in at a certain hiring stage, and those stages are still in effect after your final round.
| Jurisdiction | When you can get the range |
|---|---|
| Delaware | After the initial interview |
| New Jersey | Once you are deemed a candidate |
| Oregon | In the final stages of hiring |
| Rhode Island | On request, before comp is discussed |
| EU (Directive 2023/970) | Before the first interview, unprompted |
What else applies:
- Pay history bans. Massachusetts passed the first salary history ban. One dated tracker counts eighteen states plus DC that restrict asking about or relying on pay history statewide. Virginia now bars private employers from asking applicants for salary history.
- After the offer. Washington requires larger employers to share the minimum salary on request after an offer.
- EU. Article 5(2) of the Pay Transparency Directive bans asking about current or previous pay directly, on forms, or through third parties such as recruiters. Countries are putting it into national law at different speeds: Poland's recruitment rules are already in force, while the Netherlands is running late.
- Moving targets. Some states, Connecticut among them, are switching from on-request to proactive disclosure on set effective dates.
What isn't established: whether a history ban stops a recruiter from asking about "current comp" on a call after the final round. The statutes say "any stage," but nobody has published a ruling on this exact question. To check, look up your state labor agency's guidance or your country's transposition status. Laws on this change on fixed effective dates, so check again for each search.
The pre-close run, step by step
This is the procedure from the end of the debrief to a written offer you can decide on. Steps 2 to 4 are yours and fit into one working day. The rest is the employer's queue, and your job there is to compare numbers, not chase.
Final round to written offer
- Wait out the debriefInterviewers submit feedback and the hiring decision gets made, about 2 to 7 business days at large employers. You are done when the recruiter contacts you, so don't chase on day 3.
- Pull the package factsOn the day the recruiter reaches out, spend about an hour getting the level, the band for that level, the bonus basis, the equity count with its fully diluted denominator, and the start-date limits. You are done when every component has an anchor.
- Run the pre-close callState one number for each component, each above your walk-away, and answer every test-close question with a condition attached. You are done when the recruiter has a full package to submit and has not heard a yes.
- Send the written recap the same dayEmail the recruiter a restatement of level, base, bonus, equity count and denominator, sign-on, and start date, marked as not an acceptance. Send it before the package goes for approval.
- Hold through band placement and approvalPublished durations run from 3 to 7 days (Google) to 7 to 14 business days (Cisco). You are done when the portal shows Offer Approval or the recruiter calls back.
- Compare the verbal offer to your recapIt usually comes 1 to 3 business days after approval. Check each line against the recap and raise any difference in writing.
- Review the written offer before decidingThe standard range is 3 to 10 business days from verbal. Confirm it matches the recap, then give your decision in writing.
Timing notes:
- Step 2 is the only step with a real deadline you set yourself. If the recruiter wants the call within the hour, ask for the level and band at the start of the call, before you discuss anything else.
- Step 3 has no documented length. Plan for a short call, and have your numbers written down in front of you.
- Step 4 loses most of its value if it arrives after the recruiter has submitted the package.
How to answer each test-close question without a binding yes
Give a number when you're asked. Attach a condition to every commitment: it holds once you see the written offer. Being precise protects you better than being vague, because a vague answer just prompts more questions.
Setting the one number per component
Before the call, write one number each for base, bonus target, equity, and sign-on. Put each one above your walk-away number, meaning the lowest package you would accept. The evidence on whether asking pays:
- In Pew Research Center data on people who asked for more pay, 28 percent got exactly what they asked for, 38 percent got more than the first offer but less than their ask, and 35 percent got only the first offer.
- In a field experiment with about 3,858 tech job seekers, reported by UCLA Anderson Review, those who countered gained an average of 12.45 percent.
Two-thirds of people who asked got more, and more than a third of them landed below their ask. So the number you state has to leave room above your floor. No published data breaks down how much base, equity, and sign-on each tend to move, so don't assume one component is the flexible one.
The documented questions, and what to say
| Test-close question | What it's testing | A response that isn't a yes |
|---|---|---|
| "If they offer [base] with [bonus], would you accept?" (or the bundled version with PTO, health, and days in-office) | Commitment to a partial package | "At that base and bonus, at the level we discussed, I'd be in a strong position to accept once I see the full written offer, including equity and start date." |
| "What number would let you accept today, and what's behind that number?" / "What compensation would you need to say yes?" | Your floor, and whether you'll decide on the spot | "For this level, my numbers are [base], [bonus target], [equity], and [sign-on], based on the band you shared. I'll decide on the written offer, not today." |
| "If they offered you more to stay, what would you say?" | Counteroffer risk | "My decision is about this written package. I'm not using it to renegotiate where I am." |
| "Is there anything that would stop you from accepting?" | Hidden objections | Name the open items: "Only the ones we've covered: confirming the level, the equity denominator, and the start date in writing." |
| "If the comp is right, how ready are you to accept, 1 to 10?" | A score that gets logged as intent | "A nine, conditional on the written offer matching what we've discussed today." |
| "So if they do the certain something, you'd definitely accept, right?" (reverse close) | Turning one concession into a full yes | "It would settle my main open item. I'll give you a decision when I have the whole offer in writing." |
When asked "When could you give notice, and what start date works?", give a date range tied to a signed written offer: "[N] weeks after I sign the written offer, so around [date]."
Don't soften any of these into hedges. One recruiter script marks "I'm pretty sure I'll take it" as not a yes and follows it with "What would make you sure?" A soft answer gets read as hesitation and keeps the questioning going. A precise answer with a condition ends that line of questioning.
A condition you say out loud turns into a commitment in someone else's notes unless you write it down.
What goes in the same-day written recap?
The recap is an email, sent the same day as the call, that restates level, base, bonus, equity count and denominator, sign-on, and start date, and says plainly that it is not an acceptance. It's the only version of your answers that reaches the approval step in your own words.
Practitioners describe getting a verbal acceptance before the written offer as routine. One recruiter writes: "Personally I will not give a written letter until I have a verbal accept." One Amazon recruiter told a candidate that a written offer would follow only after acceptance, and that verbal acceptance is final. Whether a verbal yes binds you depends on where you are. One candidate guide says a verbal acceptance binds neither side. The ANU's HR policy says a verbal offer and verbal acceptance can create a contractual relationship.
Nobody has published tested recap wording that reliably stops a stated number from being treated as an acceptance. The template below uses plain conditional language. If the stakes are high, such as a large equity grant or a relocation, have a local employment lawyer read your recap before you send it.
Subject: Recap of today's call, [Role], not an acceptance Hi [Name], Thanks for the call today. So the package that goes for approval matches what I said, here is my recap: - Level: [level name], band [minimum] to [maximum] as you described it - Base: [amount] - Bonus: [target %], paid on [basis], paid [frequency] - Equity: [count] [options or RSUs], against [fully diluted share count] shares as of [date], which includes [what it includes] - Strike and 409A (if options): [strike price], 409A dated [date] - Sign-on: [amount] - Start date: [date], [N] weeks after a signed written offer These are the figures I would need to see in a written offer. This email is not an acceptance. I will give my decision once I have reviewed the full written offer. If anything here differs from your notes, please let me know before the package goes for approval. [Your name]
Send before the recruiter submits the package; delete lines that don't apply, but keep the last two paragraphs.
Keep the recap consistent with what you claimed when you applied. If Refolk tailored your resume to this posting, that version is the record to check your level claims against, so the recap doesn't argue for a level your application never claimed.
How does the pre-close go wrong?
Most failures come from something the candidate believed was true that the recruiter's notes recorded differently. Each failure below comes with what it looks like and a check you can run.
- "If we offered X, would you accept?" answered "yes." The scripts aim to get commitment to every part of the offer before presenting it. The false positive: you think you've shared a preference, and the recruiter has logged an acceptance. Check: does your recap use conditional wording and say "not an acceptance"?
- Soft answers read as hesitation. "I'm pretty sure I'll take it" triggers "What would make you sure?" and more probing. Check: did every answer contain either a number or a named open item?
- Equity percentage on the wrong denominator. Some companies quote only outstanding shares, which makes your percentage look bigger. The false positive: a percentage that looks generous because it's measured against the smallest base. Check: ask what the denominator includes and its date.
- The 409A or preferred price mistaken for what your shares are worth. Multiplying your options by the preferred price values rights you don't hold. Preferred shares come with protections that common shares and options don't. Check: value options against the strike price and the 409A, and read the liquidation preference stack.
- A wide posted range that spans several levels. The band you discussed isn't the band for your level. The false positive: your number sits "in range" but is placed at the lower level. Check: get the level name before stating any number.
- Recap sent after the package is submitted. The approval packet already carries the recruiter's notes, so a late recap can't correct them. Check: send it the same day as the call.
- Chasing based on aggregator timelines. The published durations don't show their method, and an approval queue of 7 to 14 business days is normal at some employers. Check: ask the recruiter on the call when they expect approval, and follow up only after that date.
- Assuming a verbal yes isn't binding. Jurisdictions differ, and some recruiters treat a verbal yes as final. Check: answer with a condition and confirm in writing.
There's also a fear that keeps people from stating any number: that negotiating will get the offer withdrawn. A secondary report of a George Mason University study says hiring managers withdrew about 1.73 offers out of roughly 26.9 after candidates negotiated. I couldn't verify the primary source, so read that as "uncommon, poorly measured," not as a precise rate. Set it against the Pew finding that two-thirds of people who asked got more than the first offer.
What to check before the verbal offer arrives, and how to keep this current
Before the approval comes back, confirm that every component is anchored, stated, and recapped in writing. When the verbal offer comes, compare it with the recap line by line, not against what you remember from the call.
Before you hang up and before you hit send
- I have the level name and the band minimum and maximum for that level, in writing or in my call notes.
- I know the bonus target percentage and what it is paid on.
- I have the equity count, the fully diluted denominator, what it includes, and its date.
- For options, I have the strike price and the date of the latest 409A, and I know if it is older than 12 months.
- I stated exactly one number for each component, and each one sits above my walk-away.
- No answer on the call was an unconditional yes, including the 1 to 10 readiness question.
- My recap went out the same day, before the package was submitted, and says it is not an acceptance.
- I know whether my state or country gives me the range on request at this stage, and I asked for it if so.
- I have the recruiter's expected approval date, and I won't follow up before it.
Keeping it current:
- Check jurisdiction rules again for each search. Salary history bans, on-request range rules, and EU national laws change on fixed effective dates. Use your state labor agency's site or your country's transposition status, not the table above, as the final word.
- Treat published timelines as rough. If a recruiter gives you a date, that replaces any aggregator figure.
- Use the recap as the comparison document. When the verbal offer comes, any line that differs from your recap gets a written follow-up the same day. When the written offer comes, review each pay line and equity clause against the recap before you give a decision.
Questions job seekers ask
Should I give a number when the recruiter asks my salary expectations after the final interview?
Yes, give a number, but only after you have the level and the band for that level. At this stage the recruiter needs a full package to submit for approval, and refusing to answer leaves them to fill the gap on their own. State one number for each component, set above your walk-away, and tie it to the level you were told. Then confirm it in a written recap that same day.
Is saying yes to 'if we offered X, would you accept?' binding?
It may be, and you shouldn't assume it isn't. One candidate guide says a verbal acceptance binds neither side. A university HR policy says a verbal offer and verbal acceptance can create a contractual relationship, and one Amazon recruiter told a candidate that verbal acceptance is final. The rules differ by jurisdiction. Answer with a condition, such as 'at that package I'd be ready to accept once I see it in writing', and repeat that condition in your recap.
What should I ask before the offer is written?
Ask for five things: the level the role is budgeted at, the range for that level, what the bonus target percentage is paid on, the equity count with its fully diluted denominator, and any start-date limits. For startup equity, also ask for the strike price, the date of the latest 409A, the latest preferred price, how much of the option pool is unallocated, and the liquidation preference stack.
Can the recruiter ask my current salary on the pre-close call?
In many places, no. Eighteen US states plus DC restrict asking about or relying on pay history statewide, and Article 5(2) of the EU Pay Transparency Directive bans asking about current or previous pay, including through recruiters. Nobody has publicly settled whether a 'current comp' question after the final round counts. The statutes say 'any stage', so check your state labor agency or your national transposition status.
Will negotiating at this stage make them pull the offer?
Withdrawal looks uncommon, but the evidence is thin. A secondary report of a George Mason University study says hiring managers withdrew about 1.73 of roughly 26.9 offers after candidates negotiated. I couldn't verify the primary source. On the other side, Pew data shows 66 percent of people who asked got more than the first offer. A precise number with a condition attached is less risky than leaving your answer vague.
How long after the pre-close call should I expect the offer?
Expect days to weeks, not hours. One published Cisco timeline puts debrief to offer approval at 7 to 14 business days, then 1 to 3 business days to the verbal offer and 2 to 5 more to the written one. Meta reportedly holds a weekly hiring committee, and NVIDIA's reportedly meets every two weeks. These timelines come from aggregators that don't show their method, so treat them as rough guides.
Put this to work
Paste your career in once. Every application after that is written for you.
Drop a resume or a LinkedIn URL. I rank the live openings against it, rewrite the resume and write a cover letter for the best of them, and fill in the employer's form when you press the button. You read, you decide what goes out.
01Drop your resume
A PDF or a LinkedIn URL. About a minute, once.
02I rank the openings
Every weekday morning, the live catalog scored against your history. Up to 20 worth your time, not two hundred links.
03Each one is written up
Resume rewritten for the posting, a cover letter, a fit score. Press send, or let me fill in the form.
- New matches ranked and written before you are up.
- Every bullet stays inside what your history supports. Nothing invented.
- Queued, submitted, interviewing, offer: one screen, not a spreadsheet.
Free, no card. Up to 25 applications sent a week, and nothing is sent until you say so.