The Deadline Offer Call, Scored to Accept, Extend, or Decline

You hold one acceptable offer with a written response deadline, and at least one other interview loop is still unfinished. This guide scores that offer against each open loop on five dimensions and returns one of three verdicts - accept and stand down, request a specific extension, or decline and continue - each tied to a written threshold you can check against your own case. Use it the day the written offer lands, not the day before it expires.

What the deadline offer call decides

The deadline offer call decides one thing: what you do with this offer before it expires, given the realistic odds and timing of every loop still open. It is the "bird in hand versus pipeline" question, made explicit enough to score.

Three terms, defined once:

• Loop: one employer's interview process for one role, from first interview to decision.
• Upside loop: a loop that, if it produced an offer, would beat the offer in hand on your own baseline. A loop that would not beat it does not count, however exciting it feels.
• Stage-weighted odds: your probability of an offer from a loop. You start from a published conversion rate that matches the employer, then adjust for how far you have got.

The call has three possible verdicts:

1. Accept and stand down. Sign, then withdraw from the other loops.
2. Request a specific extension. Ask once for a named new date, sized to when your best upside loop will decide.
3. Decline and continue. Turn the offer down and keep searching.

Five dimensions feed the verdict:

1. The offer against your personal baseline.
2. Stage-weighted odds of each pending loop.
3. Time each loop needs to reach a decision, compared with the deadline.
4. Financial and visa runway.
5. How far the deadline can flex.

Three jobs are out of scope: speeding up the other employers, withdrawing cleanly, and backing out of an offer after you sign. Each has its own guide in this library, and the last section points to them.

The five dimensions and how to score each

Score each dimension 0, 1, or 2 using the rubric below. You score loop odds and loop timing once for every upside loop. The cut-points are mine, picked so the verdict thresholds stay checkable. The inputs behind them come from public benchmarks and your own records.

Offer against baseline

Your baseline is a walk-away number plus a short list of must-haves, written before you reread the offer. It shows whether this is an offer you could commit to. Berkeley's career center is blunt about it: do "not accept offers that you cannot fully commit to."

It lies when you write the baseline after reading the offer, because then the offer sets the bar. Build it from your current or last pay, your fixed costs, and the level of roles you have been applying to.

Loop odds

This shows how likely a loop is to produce anything at all. It lies when you apply a funnel-wide rate to a final round, or when you read a warm interviewer as a probability. The next section covers how to set it.

Loop timing

This shows whether a loop can give you an answer you can use before you have to answer this offer. It lies when you count from the last interview and forget approval steps, or when you assume a campus timeline where none applies.

Runway

Runway shows how long you can afford to be without this offer. It is the earlier of two dates: your cash date (when savings and any benefits stop covering costs) and, if you hold a visa, your status date. It lies when you count the wrong visa clock or assume you will get the maximum unemployment benefit.

Deadline flex

Flex shows how much time the employer will actually give, and you only learn it by asking. It lies when a 48-hour deadline is a closing tactic rather than a held requisition, or when an extension agreed "in principle" never gets put in writing.

How to set stage-weighted odds for an open loop

Start from the published interview-to-offer rate that matches the employer's size and segment. If you are past the final round, treat that rate as a floor. No public source reports a clean final-round or onsite-to-offer rate, so anything more precise than a band is false precision.

The rates disagree because their denominators count different things. Some count every person interviewed, some count interview events, and some count only candidates who reached a given stage. Enterprise funnels also screen hard before the interview, so people who reach interview there convert at 72.2%, against 7.0% at small businesses in the same dataset. Size the employer first, then pick the row.

How to band a loop:

• Pick the row that matches the employer's size and segment. For a campus offer, use the NACE campus row, and remember it reaches you secondhand.
• Adjust at most one band upward if you are past the final round and hold a concrete signal, such as a reference request, compensation questions, or a team-match conversation. That is my heuristic, not a measured rate.
• Never adjust upward on tone. A friendly debrief is not a signal.
• Ask how many steps remain. Interviews per technical hire rose 52% over five years, from 11.6 to 17.6. A round called "final" in a technical loop may not be final.

These rates are snapshots, and they move. Ashby's series has been as low as 5% for business roles and 3.9% for technical roles at an earlier trough. Check the source's latest release before you rely on a row.

If you used Refolk to tailor the application, the fit score it gave that posting is a fair input for nudging a loop up or down within its band. It measures how well your history matches the posting. It is not a probability, so do not let it move a loop across two bands.

How long each pending loop needs to reach a decision

To project when a loop will decide, add the median length of every stage it still has to clear to today's date. Then compare that date with the deadline, and with the deadline plus a 3 to 7 day extension.

The procedure for each loop:

1. Count the stages left, including approval and any team-match step.
2. Add the median for each one to today's date.
3. Ask the recruiter when they expect to decide, and keep whichever date is later.
4. Score timing against the rubric.

Two consequences shape every verdict.

Extension headroom is about one stage. A 3 to 7 day extension roughly matches the 6-day median from final interview to offer. It cannot cover the 12 to 20 day gap from first to final interview. So the only loops that can earn an extension are ones already past their final round.

Campus timelines don't stack. NACE measures the campus gap from interview to offer at nearly 27 days, which is longer than its roughly two-week response window. A campus loop that interviews on the day an offer arrives will usually miss that offer's deadline.

How far an offer deadline flexes, and when it counts as exploding

Corporate offers usually give 3 to 7 business days and campus offers about two weeks. The extensions commercial guides report cluster at 3 to 7 days. An exploding offer has a deadline short enough to block a reasonable decision, but schools set the line anywhere from 48 hours to under two weeks.

What the window evidence supports:

• The clock starts on the written letter. It starts on the date of the written offer letter, not the verbal call. Look for a section titled "Offer Validity" or "Acceptance Deadline."
• Short corporate windows are normal. Startups and roles with urgent needs may give as little as 24 hours.
• Extension length is a norm, not a right. Indeed says "you can likely ask for a week at best." No one has published how often extensions are granted, so score flex from the answer you get, not from a base rate.

Whose rules your recruiter answers to

The longer campus windows protect you only when the employer recruits through your school's program. Dartmouth says so directly: "employers outside of the recruiting program are not bound to our timelines." Most candidates are not dealing with a campus recruiter.

In a 25-profile sample of those campus recruiters, Jane Street and Meta lead in the US, and Jane Street and Hudson River Trading lead in the UK. The inference I draw from the headcount is that most experienced hires negotiate with a recruiter who answers to no campus policy. That comes from headcount, not from a measured policy rate. Confirm it for your own case by asking whether the offer came through your school's program.

When to ask, and whether to ask twice

Ask early, ideally within 24 hours of the written offer, and never on the deadline itself. The sources disagree on two points:

• Order. NACE has the candidate say up front when they will respond, so the extension request comes first. Commercial guides put the request after you have checked the competing timelines. I side with asking inside 24 hours using your projected dates, then using the acceleration step to firm them up.
• Repeat asks. One guide says never ask more than once. Another allows a second ask if something new has happened. Plan for one ask and size it correctly.

Subject: [Role] offer - timing of my decision

Hi [Name],

Thank you again for the offer for [role]. I'm excited about [one specific thing about the team or work], and I want to give you an answer I can fully commit to.

I am finishing [one / two] processes that started before your offer arrived, and I expect their outcomes by [date]. Could we move my response date from [current deadline] to [requested date]? I will give you a firm answer on or before that date, and sooner if I can.

It would also help to understand what happens to the role if I need that time. Is the position held for me through that date?

Thank you,
[Your name]

Runway dates that override the score

Runway is the earliest date you would run out of legal status or money if you declined. For visa holders it overrides every other dimension. Write it down as a calendar date, not a number of days.

On the H-1B clock, the grace period runs up to 60 days from termination or until your authorized validity ends, whichever comes first. You get one per authorized validity period, so a grace period already used does not come back. On benefits, the number of weeks can vary within a single state depending on your earnings history. Use the state agency's determination, not the maximum.

To set the date, take the earlier of your status date and your cash date. Then compare it with your best upside loop's projected decision date, plus your own estimate of how long it takes to go from a yes to starting work.

Scoring procedure: from written deadline to verdict

Run these eight steps in order the day the written offer arrives. Most of the work fits in one afternoon, plus a day of waiting on recruiter replies.

Verdict thresholds

Each verdict fires only when every condition in its row holds. "Best loop" means the upside loop with the highest combined odds and timing score.

Two edge cases:

• Best loop scores Timing 2. It will decide before the deadline, so you need no extension. Ask it to confirm its date, hold, and rescore when it reports.
• Offer 0 and Runway 0. Neither verdict fits cleanly. Negotiate the gap against your walk-away before deciding, because you cannot afford to decline and the offer as written fails your baseline.

Note what the decline row does not allow. A strong offer (score 2) is never given up for a probability, and a marginal offer is given up only when runway is long and the best loop's odds sit in the top band.

DEADLINE OFFER SCORE
Offer: [employer] / [role]
Written deadline: [date] [time] [time zone]   Found under: [section heading]
Walk-away number: [ ]   Must-haves: [ ]
Offer vs baseline (0/1/2): [ ]

Status date: [ ]   Cash date: [ ]   Hard runway date: [earlier of the two]
Runway (0/1/2): [ ]

Loop | Beats offer? | Stage | Rate row used | Odds (0/1/2) | Projected decision date | Timing (0/1/2)
[employer] | Y/N | [stage] | [source, segment, rate] | [ ] | [date] | [ ]
[employer] | Y/N | [stage] | [source, segment, rate] | [ ] | [date] | [ ]

Best upside loop: [ ]
Extension asked for: [date]   Asked on: [date]   Answer: [confirmed date / firm no]
Flex (0/1/2): [ ]

Verdict: ACCEPT AND STAND DOWN / REQUEST EXTENSION TO [date] / DECLINE AND CONTINUE
Threshold met: [rule line]
Rescore if: [named trigger]

A worked case

Say a mid-market employer offers you a role with a deadline five business days after the letter. The offer clears your walk-away but misses a want, so it scores 1. You have no visa and your cash covers several months beyond any loop, so runway scores 2.

• Loop A is an enterprise employer. You finished the final round and they asked for references. The enterprise row puts odds above 30%, so odds score 2. The 6-day median from final interview to offer lands it a few days past your deadline, so timing scores 1.
• Loop B is a small business where you have only had a first interview. The 7.0% row puts odds at 0, and it still needs about 12 days plus 6, so timing is 0. It drops out of the verdict.

The extension row fires, so ask once for Loop A's projected date. If the answer is a firm no, the decline row fires: Offer 1, Runway 2, best loop Odds 2, Flex 0. If the offer had scored 2, a firm no would have meant accepting instead.

How the deadline call goes wrong

Most bad deadline decisions come from wrong inputs, not wrong logic: a misread rate, a borrowed timeline, or a visa clock counted from the wrong start. Check each of these before you trust a verdict.

1. Applying a funnel-wide rate to a final round. If you read 7.3% as your odds after an onsite, you understate them, because sources count people or interview events differently. What it looks like: you accept early because the pipeline "looks thin." Check: confirm the source's denominator, and band from your stage.
2. Assuming the campus window applies to you. An experienced hire expects two weeks and gets three days. Dartmouth confirms that employers outside its program are not bound. What it looks like: you plan an extension around a norm the employer never agreed to. Check: ask whether the employer is recruiting through your school's program.
3. Treating every 48-hour deadline as real. Some deadlines are a closing tactic. A recruiter-written mailbag on exploding offers separates a held requisition from "a company that's using urgency as a closing tool." What it looks like: you panic-sign without asking a single question. Check: ask what happens to the role after the deadline, as the extension template does.
4. Counting on cooldown math after a decline. The published re-interview cooldowns at large tech employers apply to rejections, not declines. A decline may face no cooldown or an unknown one. How often declined offers get reopened is not publicly established, and the stories of later offers after a decline are anecdotes. What it looks like: you decline believing the door stays open. Check: ask the recruiter directly whether a passed loop stays valid, and for how long.
5. Asking for a second extension. The first extension buys time. Asking again reads as indecision. One account describes a candidate coming back on day five asking for three more days. What it looks like: the goodwill you built during the offer stage drains away. Check: size the first request to the latest projected decision date among your upside loops.
6. Miscounting the visa clock. A candidate counts 90 days but is on STEM OPT and has already used some. What it looks like: a runway score of 2 that is really a 0. Check: get the SEVIS unemployment count from your DSO.
7. Assuming 26 weeks of benefits. The number of weeks varies between states and within them. Texas runs from 10 to 26 weeks depending on earnings history. What it looks like: your cash date sits months later than it should. Check: get the state agency's determination before you score runway.

Most bad deadline calls are input errors: a borrowed rate, a borrowed timeline, a miscounted clock.

There is also a false positive built into the method itself. The odds bands rest on published averages, and your loop is one case. A loop banded at 2 can still say no. That is why the decline row also demands long runway, so that a no from the best loop leaves you room to keep searching.

After the verdict: next moves and keeping the score current

The verdict hands you to another job. Act on it the same day, and rescore only when a named trigger fires, not each time you feel uneasy.

Where each verdict goes next:

• Accept and stand down. Sign, then withdraw from your other loops using the Search Stand-Down Standard, which checks your offer state before you withdraw anywhere. If a better loop comes back after you sign, The Signed-Offer Renege prices what backing out would cost.
• Request a specific extension. Send the template, then use The Offer-in-Hand Pipeline Reference and The Interview Follow-Up Cadence to push each upside loop toward a decision inside the new date.
• Decline and continue. Decline in writing and thank the employer. Then refill the pipeline. Refolk can tailor your resume and cover letter to each new posting from your own history, which cuts the time it takes to restart.

Rescore when any of these happen:

• An upside loop moves to a new stage, adds a round, or gives you a decision date.
• The employer answers your extension request.
• Your status date or cash date changes.
• A new loop starts that would beat the offer. Score it, but remember that a loop at first interview almost never fits inside one extension.