The Offer-Deadline Week, One Case Across Four Live Processes

You have one written offer with a deadline and three other processes at different stages, and you need to know exactly what to send to whom, in what order, until you hold a decision. This guide is for a candidate in that exact week. It carries one worked case across seven days, with the real messages, the day each went out, which process moved, which went silent, and the wrong turn that cost a day.

Most published advice gives you three disembodied tips: buy time, tell the others, drop the ones you do not want. All true, all useless at 9pm on the day the offer landed. What you need is a schedule. Below is the case of a candidate I will call the runner, holding one offer and juggling three live loops, laid out as a continuous timeline you can put your own calendar against.

The four processes, and the one number that decides everything

Before you send anything, write down all four processes and rank them by genuine interest, not by stage. The offer's own rank on that list decides whether you push the others at all.

Here is the runner's board on day 0. The offer arrived Monday morning.

The single most important fact on this board is that the offer ranks third. That means the runner is not trying to escape Company A; they are trying to find out whether B or C can catch up before Friday. If the offer had ranked first, most of this guide would not apply - you would simply accept and stop.

Notice the structural trap already visible on the board. Company B, the one the runner wants most, has only an onsite left. Company C is a full round behind. Company D is a screen away from nowhere. The runner's leverage is real only where the process is late-stage, and it is negative where it is early. That asymmetry drives every move that follows.

Is my deadline even normal?

A deadline under one week is what career sources call an exploding offer; over a week is generally considered reasonable. Individual-contributor roles typically get 3 to 7 business days, and senior or executive roles get one to two weeks. Before you treat your deadline as aggressive, check it against the range.

The runner's deadline was Monday morning to Friday 5pm: four and a half business days for an IC role. That sits at the aggressive end of normal, not off the map. It is short enough to justify asking for more time and short enough that the other processes may not be able to catch it. Both facts matter.

If your deadline is under 72 hours, treat the whole week compressed into two days and skip straight to deciding whether any target can plausibly move in that time. If it is genuinely a week or more, you have room to run the full sequence below with slack.

Why acceleration is hard, and when it works anyway

Acceleration works only when the candidate is about to become unavailable, and never because it helps the candidate. When a company compresses its process, it is protecting its own interest in a top choice it is about to lose. That single mechanism explains every yes and every no in this section.

The reason acceleration so often fails is that most processes have a fixed floor on speed that goodwill cannot move. Recruiters depend on internal partners - coordinators, hiring managers, panel members, background-check vendors, and compensation teams - and some approvals run only once or twice a week. One company required CEO sign-off on every offer. A recruiter with twenty years in the field reports seeing only one or two companies consistently turn an offer around in 48 to 72 hours. And role level compounds it.

Read that table as a reality check on your ask. Asking a 95-day software process or a 120-day executive process to collapse into a five-day window is asking for a 20x compression that no amount of enthusiasm delivers. What a late-stage process can give you is a decision-in-principle - a verbal yes conditional on formalities - not a full loop run in a week.

This is why the runner pushed B hard and pushed C only lightly. B had one step left, so a yes was mechanically possible by Friday. C had a full round plus internal debrief, and each additional interview round adds roughly five to seven days for scheduling, conducting, and feedback. C could not realistically catch the deadline, and the runner treated it accordingly - a courtesy push, not a bet.

The runner's week, hour by hour

Here is the whole case as one timeline. Watch day 2 closely; that is where the wrong turn happened.

Day 0, Monday, 10am. Offer from A lands by phone. The runner asks for it in writing with the exact date, time, and time zone, and gets an email back confirming Friday 5pm PT. This takes fifteen minutes and it is the foundation for everything: without a written deadline, the runner has nothing to quote to B and C, and cannot ask A for an extension credibly.

Day 0, Monday, 11am. The runner ranks the four processes (the board above) and drafts the acceleration messages to B and C. Both go out by early afternoon. D gets a short, warm decline.

Day 0, Monday, 4pm. B's recruiter replies within hours: they can pull the onsite forward to Thursday and promise a same-day debrief. This is the late-stage payoff working exactly as the mechanism predicts - B wanted the runner and moved to protect that.

Day 1, Tuesday. C's recruiter replies: enthusiastic, will "see what we can do," no date. This is the friendly-but-fixed-cadence signal. The runner logs it as a soft no and stops investing in C.

Day 2, Wednesday - the wrong turn. Here is where the runner lost a day. Anxious about Friday, they emailed A on Wednesday morning asking for an extension to the following Wednesday, before B's Thursday onsite had happened. A's recruiter came back Wednesday afternoon: they could grant until Monday, not Wednesday. The runner had spent their one extension request blind and got a shorter grant than they needed, when waiting one more day - until after B's onsite - would have let them ask for exactly the right amount of time or not ask at all. Sequence sources put target-contact first for precisely this reason: you spend the extension chip once, so spend it knowing what you need.

Day 3, Thursday. B's onsite runs. Same-day debrief comes back positive, verbal yes to follow "by tomorrow midday."

Day 4, Friday. B's written offer arrives Friday 11am, an hour before the runner would have had to decide on A under the Monday extension. The runner accepts B, declines A with thanks, and withdraws from C. One signed acceptance, all others closed.

Spend the extension chip once, and spend it knowing exactly what you need it for.

The lesson from day 2 is the whole reason the sequence has an order. B moved. C did not. A gave less time than asked because the runner asked too early. Had the runner waited until after B's Thursday onsite to contact A at all, they might not have needed an extension - or could have asked for the two clean days they actually required.

The procedure, in order

This is the sequence the runner followed, corrected for the day-2 mistake. Contact the still-live processes first, close the loop with the offering company last, and never ask for your extension before you know whether targets can move.

There is one genuine dispute over step three. Some structured-recruiting coaches say never ask a still-interviewing firm to accelerate before they physically extend an offer: do not ask them to bring forward a yes-or-no, and only once they extend an offer can you ask to delay signing. That advice fits on-cycle recruiting and highly structured pipelines. For most open-ended processes, the runner's approach - report the deadline to late-stage targets and ask them to move - is the mainstream sequence. Know which world you are in before you choose.

The two messages that carry the whole week

The acceleration message and the extension message do different jobs and are framed differently. The acceleration ask says "I want you, help me keep you in the running." The extension ask says "I need time to do this justice." Getting the framing wrong is how these backfire.

Subject: Update on my timeline

Hi [name],

I wanted to give you an honest update. I've received an offer from another
company with a decision deadline of Friday 5pm PT. I'm genuinely more excited
about the role here, which is why I'm writing rather than just deciding.

Is there any possibility of moving the remaining step forward so I can weigh
both properly? I'll make myself available at any time that helps, and I'm happy
to send references or a work sample today to remove anything that's waiting on me.

Completely understand if the timeline can't flex - I just didn't want to decide
without giving you the chance to stay in the running.

Thank you,
[you]

Subject: Response to your offer

Hi [name],

Thank you again for the offer - I'm genuinely enthusiastic about it. To give a
decision this important the consideration it deserves, I'd like to confirm my
response by Monday [date] at [time/zone]. I'm committed to coming back to you by
then.

Please let me know if that works on your end. I appreciate your flexibility.

Best,
[you]

When you need to find the person who can actually move a process - the in-house recruiter or the TA lead who can approve an offer inside your window - describe them precisely rather than guessing. Refolk turns that description into a named list, so you can address the human with authority instead of the inbox.

How this goes wrong: the seven failure modes

The most valuable part of running an offer week is knowing how it fails before it does. Each mode below has a false positive - the thing that makes you think it is working - and a check.

• Pushing an early-stage process reads as an ultimatum and gets you dropped. False positive: the recruiter says "we'll try." The check: real cases show silent drops even after "top candidate" signals - one candidate interviewed ten times over four months, was told to keep the recruiter posted on other offers, and was dropped after reporting one. Watch for a next-day rejection instead of a schedule.
• Bluffing an offer you do not hold. False positive: it works once. The check: if a company asks for the written deadline you cannot produce, the bluff collapses, and some firms use exploding offers precisely to catch offer-shoppers. This is why step one is a written deadline.
• Asking a big or slow process to compress structurally. False positive: the recruiter is warm and encouraging. The check: ask what the fixed approval cadence is - hiring committees and CEO sign-offs run weekly regardless of goodwill, so a friendly recruiter cannot beat the calendar.
• Requesting the extension at the buzzer. False positive: you feel you are being decisive. The check: measure days of lead time, not hours - last-minute or post-deadline asks read as disrespect. Ask as early as you can commit to a firm date.
• Framing acceleration as a demand. False positive: you sound urgent and serious. The check: reread the message; if it offers no flexibility on your side, it is an ultimatum, not a request.
• Signalling you are less than enthusiastic to the process you most want. False positive: you think honesty about your options helps. The check: if the interviewer thinks you are less than enthusiastic you probably will not get an offer - do not make them feel like your fallback plan.
• Accepting and then continuing to interview (reneging). False positive: "it was only verbal." The check: university career offices treat both verbal and written acceptance as binding, and recruiters move between firms and remember.

The reneging risk deserves its own weight because it is the one mistake that follows you. Reporting an offer is a genuine filter, not free leverage - it can trigger a fast yes or a fast no, and one survey cited reports that 50% of candidates have accepted a job and backed out before starting. That the behavior is common does not make it safe. Refolk's index shows why the cost is uneven: the UK recruiter pool of 7,489 is about one-fifteenth the US pool of 113,888, so in a smaller market a burned bridge is far likelier to reappear across the table.

Before you send anything, run this checklist

Use this to check your own week against the runner's before you make the first move. If any item is unchecked, fix it before you send.

Keeping the plan current when the week actually starts

Your real week will diverge from the runner's, and that is fine - what has to survive is the order. Contact the live processes first, close the loop with the offering company last, and hold your extension request until you know what your targets can do. The runner's day-2 mistake was not a bad message; it was a good message sent one day too early.

Two things are genuinely time-sensitive and worth re-checking against your own case rather than trusting the numbers here. First, whether a given process can move at all: the honest question to a recruiter is not "can you speed up?" but "what is the fixed approval cadence, and is a decision-in-principle possible by Friday?" A yes to the second is worth more than enthusiasm about the first. Second, whether your deadline still qualifies as aggressive: if the offering company grants an extension, recompute your window and re-rank whether any target can now realistically catch it. A three-day grant can turn an impossible C into a live contender, or confirm that only B was ever in the race.

Run the week as a schedule, not a scramble. You already know who you want, you know your deadline, and you know that pushing works only where you are late-stage and wanted. The rest is sending two messages in the right order and letting the calendar do the deciding.