# The Expedite Request Reference, Each Open Loop Keyed to Its Stage Ask

*Sort every open interview loop against an offer deadline by stage, then send each one an ask it can grant, with the facts to share and the reply that ends it.*

- Canonical URL: https://www.refolk.ai/candidates/guides/expedite-request-stage-reference
- Pillar: Offers and negotiation
- Format: Reference
- Published: 2026-11-18
- Last reviewed: 2026-11-18
- Reading time: 22 min
- Keywords: how to ask other companies to expedite after getting an offer, tell recruiter I have a competing offer deadline, should I name the company of my other offer, can a company speed up hiring committee for competing offer, does asking to expedite hurt my chances, got an offer still interviewing elsewhere what to do

## Key takeaways

- An expedite request can shorten steps that wait on people, like scheduling, debriefs and comp approval, but a hiring committee that meets weekly can gain at most one cycle however politely you ask.
- Offer approval holds the most recoverable time: in Ashby's benchmark, slow-quartile companies add an extra 6.88 days after the decision on technical roles and 5.94 days on business roles.
- Google team matching runs roughly 2 to 8 weeks by candidate reports, so a loop at that stage almost never finishes inside a 5-day offer deadline.
- Share your deadline with every loop, but hold the competing number until the comp stage, because naming a number pulls you into proof requests.
- In a 25-profile sample of US Technical Recruiters in Refolk's index, 6 worked at staffing or consulting firms, and an agency recruiter cannot convene a client's hiring committee.
- No public data shows how often employers grant expedite or extension requests, so set your own cutoff at one business day before the deadline and decide then.

You have an offer with a deadline, and other interview loops are still open. This reference has one row for each pipeline stage, from pre-screen to verbal offer. Each row gives the ask that stage can realistically grant, roughly how many days it can save, which facts to share, the message to send, and the reply that tells you the company is out. Use it to sort live loops against a fixed date. It also says plainly where the public evidence runs out.

## What an expedite request can and cannot shorten

An expedite request can shorten steps that wait on people: interview scheduling, debriefs and compensation approval. It barely touches steps that wait on a calendar, like a committee that meets weekly or team matching. Find the step that is actually blocking each loop and ask about that step. Never ask a calendar-gated step to go faster.

A few terms used throughout:

- **Loop:** one company's interview process for one role.
- **Debrief:** the meeting where interviewers compare notes and recommend hire or no hire.
- **Hiring committee:** a separate group that reviews the interview packet and approves or rejects the hire, independent of the interviewers.
- **Team match:** the step at some large employers where a candidate who has passed committee is placed with a team that has open headcount.
- **Comp approval:** the internal sign-off on the offer's numbers before a letter goes out.

Here is what the public record says about how long each stage takes. The Basis column matters. Employer-stated figures are the company's own claims, candidate-reported figures come from forums and interview guides, and secondary figures are third-party summaries.

| Stage | Duration | Basis |
|---|---|---|
| First to last interview (technical) | 17.9 days median | Ashby benchmark |
| Amazon loop to decision | 5 business days or fewer | Employer-stated |
| Amazon loop to debrief | 1 to 5 business days | Candidate-reported |
| Google hiring committee | 1 to 3 weeks | Candidate-reported |
| Google team match | 2 to 8 weeks | Candidate-reported |
| Google offer assembly after match | 3 to 7 days | Secondary |

For business roles, the Ashby median from first to last interview is 14.4 days. Ashby's overall median time to hire is 30 days for business roles and 40 days for technical roles. Two gaps in the evidence matter here:

- No public benchmark gives a general median for the time from final interview to offer.
- No source says which steps can be compressed. Every "can save" figure in this guide is my own derivation from the durations above, not a measured result of asking.

### Where the recoverable days are

Most of the slack sits after the hiring decision. Ashby does not publish a median for that part of the process, but it does publish how much longer the slowest quartile of companies takes than the fastest:

| Step | Business | Technical |
|---|---|---|
| Decision to offer | +2.68 days | +2.17 days |
| Offer turnaround | +3.26 days | +4.71 days |
| Total (derived) | +5.94 days | +6.88 days |

**+6.88 days - Extra time slow-quartile companies take after the hire decision on technical roles**

Ashby benchmark, summed from decision-to-offer and offer-turnaround gaps; this is the most recoverable slack in any loop.

Scheduling sits at the other end of the scale. Ashby measures a median of 3.7 hours to confirm an interview with automated scheduling and 5 hours when it is done manually. Booking the slot is fast. What a scheduling ask can win is calendar availability: an earlier open slot for you and the interviewers.

> A committee that meets weekly saves you at most one week, however politely you ask.

### Which loops to push hardest

Risk also changes with stage. About 24% of candidates pass the onsite stage and about 81% pass the offer stage. Pressure applied early lands on a filter that rejects most people. Pressure applied late lands on a stage most people clear. This is my inference from pass rates. Nobody has measured it directly.

#### Where to push and where to ask for a date

Horizontal axis runs from Calendar-gated step to People-gated step. Vertical axis runs from Early stage, low pass rate to Late stage, high pass rate.

| Quadrant | What it means |
| --- | --- |
| Committee or team match | Ask when the next sitting is, plan around it, and do not ask for speed |
| Debrief, offer approval, verbal | Push for a dated commitment, because this is where days come back |
| Pre-screen with full loop ahead | Ask for a timeline once, and expect to let it go |
| Mid-loop or onsite booked | Ask to batch the remaining rounds into the fewest days |

*Push hardest on late, people-gated stages, and for calendar-gated stages ask for the next sitting date instead of more speed.*

## The stage lookup: ask, days, and disclosure for each loop

Find the row for each loop's stage. It gives the one ask that stage can grant and a rough count of the days it can save. Those day counts are derived from published durations because no source measures what an expedite request actually recovers. Treat them as ceilings, not promises.

### Early stages

| Stage | Realistic ask | Days it can save | Share |
|---|---|---|---|
| Pre-screen | A written timeline | Rarely enough: loops run 14.4 to 17.9 days median | Deadline only |
| Mid-loop | Batch remaining rounds | Calendar slack only; booking takes hours | Deadline; name if a known rival |
| Onsite booked | Earlier slot plus a debrief date | Gap between slots, plus debrief slack | Deadline; name if a known rival |

### Late stages

| Stage | Realistic ask | Days it can save | Share |
|---|---|---|---|
| Awaiting debrief | Debrief on the earliest day | Up to 4 business days where debriefs run 1 to 5 | Deadline, name |
| Committee or team match | Next sitting date | One weekly cycle at most | Deadline, name; number if asked |
| Offer approval | Approval date and letter date | Most slack: up to 5.94 to 6.88 days | Deadline, name, number |
| Verbal given | Written letter by a named date | The verbal-to-letter gap | Deadline; nothing new |

### Pre-screen

- **Ask:** whether the process can realistically finish before your date, and if not, what the normal timeline is.
- **Why it rarely fits:** Amazon says it decides within 2 business days of a phone screen, but the whole loop is still ahead of you after that. With a median of 14.4 to 17.9 days from first to last interview, a 5-day deadline almost never fits.
- **Message line:** "Is it realistic to complete your process before [date], or should I plan around your normal timeline?"
- **Out reply:** "We can't commit to that timeline." One practitioner's verdict on that phrasing: "that's your answer."

Before you spend effort on a pre-screen loop, check that it deserves the weight. [Refolk](/candidates) scores how well your history fits a posting, which tells you quickly whether this loop is worth risking a deadline for.

### Mid-loop

- **Ask:** group the remaining rounds into as few days as possible before your deadline.
- **What it can save:** only calendar slack. Confirming a slot takes hours, so the gain comes from finding earlier openings, not faster admin.
- **Message line:** "Could the remaining rounds be grouped into as few days as possible before [date]?"
- **Out reply:** no slot offered before your deadline, or "we can't commit to that timeline."

### Onsite booked

- **Ask:** an earlier onsite slot, plus a committed date for the debrief that follows.
- **What it can save:** the days between the booked slot and the earliest open one, plus whatever debrief slack the company has.
- **Message line:** "Is an earlier onsite slot available, and when would the debrief be held after it?"
- **Out reply:** the slot cannot move and the debrief date lands after your deadline.

### Awaiting debrief

- **Ask:** hold the debrief on the earliest possible day.
- **What it can save:** Amazon states a decision within 5 business days of the loop, and candidates report debriefs happening 1 to 5 business days after it. Pulling a debrief from day 5 to day 1 saves up to 4 business days, which is my derivation.
- **Message line:** "Is it possible for the debrief to happen by [date]?"
- **Out reply:** the panel cannot meet before your deadline, or the recruiter misses a date they committed to.

### Committee or team match

- **Ask:** when the next committee sits, and whether an out-of-cycle review exists for candidates with a deadline.
- **What it can save:** one weekly cycle at most. At Google, secondary sources say committees meet weekly. A hire recommendation moves to a compensation committee and then to team matching, which candidates report takes roughly 2 to 8 weeks. Meta, per one source, runs team selection before the offer.
- **What the evidence says:** a Stripe-side practitioner says "the honest answer is that HC genuinely can't be moved up." One secondary source claims recruiters can request out-of-cycle committee debriefs when an active offer exists. That claim is unverified.
- **Message line:** "When does the next committee sit, and is there any option for a review before [date]?"
- **Out reply:** "We can't meet that deadline so you should take the other job and best of luck with it."

### Offer approval

- **Ask:** the expected approval date and the date the written letter will arrive.
- **What it can save:** the most of any stage. Slow-quartile companies add 5.94 to 6.88 days after the decision. Google's offer assembly after a match is put at 3 to 7 days by a secondary source.
- **What to expect:** this is where proof requests come in. Have a redacted document ready before you send the number.
- **Message line:** "When do you expect approval, and by what date could I have the written offer?"
- **Out reply:** no approval date offered at all. Some candidates fear a low offer made in a rush to compete, but that fear is not a documented pattern.

### Verbal given

- **Ask:** the written letter by a named date.
- **What it can save:** the gap between verbal and written offer. Slow-quartile offer turnaround runs +3.26 days for business roles and +4.71 days for technical roles.
- **Why it matters:** UT Austin's career center treats requiring a verbal acceptance before issuing a written offer as an exploding offer, meaning one that expires before you can reasonably compare. A verbal offer is not a finished offer.
- **Message line:** "Could you confirm the date I'll receive the written offer letter?"
- **Out reply:** a written date promised and missed more than once.

## The disclosure rows: deadline, employer name, number, letter

Share the deadline with every loop. Share the employer name when it is well-known or a direct competitor. Share the number only once the loop reaches compensation, and share the letter only when someone asks for it, redacted to the totals. Sources disagree about names and numbers, and none of them ties disclosure to pipeline stage, so the stage column below is my own judgement.

| Fact | Share at | What it proves | How it backfires |
|---|---|---|---|
| Deadline | Every stage | You leave the market on a date | Hollow without a written offer |
| Employer name | Debrief onward, or known rival | The competing offer is serious | An unknown name adds nothing |
| Number | Offer approval | What you must be paid to stay | Triggers a proof request |
| Letter | Only on request, redacted | That the number is real | Comp anchors on base salary |

What the named sources say:

- **Haseeb Qureshi on naming:** "if it's a well-known company or a competitor, then definitely mention it. If it's a no-name or unsexy company, you should just say you received an offer. If it's expiring soon, you should mention that as well."
- **The opposing view:** disclose "the timeline and pressure, not the specific competing offer details or numbers."
- **On numbers over names:** one source argues that "I have a competing offer at $X total comp" is more powerful than "I'm also talking to Company X." Another calls "a specific number without the company name" the middle ground.

I tie the number to the comp stage for one reason. In documented cases, proof requests come up at the compensation committee, not when timelines are discussed. Blind posts describe Google recruiters asking for an "offer letter or similar documentation as a proof of the competing offers." Before comp, the number does nothing for your timeline. It only puts you into proof-handling earlier than you need to be.

> **Watch out:** Never send a number you cannot document
>
> A recruiter warns that comp teams "see tons of offer letters every year." An inflated figure gets caught at the proof request, and only a deadline-plus-total you can back up survives that check.

**Reply to a request for competing-offer proof**

```
Version A - sharing:
Hi [Name], happy to help. Attached is the compensation section of the offer with base, bonus, equity and sign-on totals visible and other terms redacted. The decision deadline is [day, date].

Version B - declining:
Hi [Name], I'd prefer to keep the letter itself confidential, but I can confirm the total compensation is [$X] and the decision deadline is [day, date]. Happy to answer any specific question about the structure.
```

*Use the first version if you will share a document; use the second if you would rather not.*

No recruiter survey defines what counts as acceptable proof, so this is not established publicly. What candidates report being accepted is a screenshot of the comp section or a redacted letter. A practitioner claim that Google's fast track needs "a written competing offer with a firm deadline" is unverified.

## Who receives the request and what they can move

Your request goes to a recruiter, who has to carry it to whoever owns the blocking step: a coordinator, the hiring manager, a committee or the comp team. Only a recruiter employed by the hiring company can do that. Every ask passes through these layers, so it moves at the pace of the slowest one.

#### Who an expedite request passes through

1. **Recruiter** - Receives the ask, escalates it, commits to a date
2. **Recruiting coordinator** - Owns calendars for remaining rounds and onsites
3. **Hiring manager and panel** - Owns the debrief date and the hire recommendation
4. **Hiring committee** - Meets on its own cadence, often weekly
5. **Comp team** - Approves numbers and releases the written letter

*The recruiter is only the front door, and the layer that owns the blocking step decides how many days come back.*

Here are the people at the first two layers in Refolk's index of professional profiles:

| Segment | Count | Derived |
|---|---|---|
| Technical Recruiter, US | 21,161 | 30.1x UK |
| Technical Recruiter, UK | 702 | 1.0 |
| Recruiting Coordinator, US | 6,580 | 3.2 recruiters per coordinator |

**3.2 - US technical recruiters per recruiting coordinator in Refolk's index**

Derived from 21,161 Technical Recruiters and 6,580 Recruiting Coordinators; scheduling asks may queue behind this thinner layer, though causation is unverified.

Coordinators are scarce compared with recruiters. That is one plausible reason a scheduling ask can take longer than the hours it takes to book a slot. It is a derived ratio, not a measured cause.

One more number matters more. In a 25-profile sample of US Technical Recruiters in Refolk's index, 6 worked at staffing or consulting firms. That is 24% of the sample, though the firm classification is unverified. An agency recruiter can pass your ask to the client but cannot convene the client's committee or approve its comp. If your contact works for an agency, ask who at the hiring company they will escalate to.

## How to send the requests, step by step

Get the deadline in writing first. Then classify every loop by stage, cut the ones that cannot finish, and send one stage-specific ask per loop on the same day. Make your decision one business day before the deadline.

#### From offer deadline to a decision on every loop

1. **Fix the deadline in writing** - Confirm the decision date by email with the company that made the offer, and ask once for an extension. Done when a dated deadline sits in an email.
2. **Tag every loop with one stage** - Give each open loop exactly one stage label from the lookup tables. About ten minutes; done when no loop has two labels or none.
3. **Cut loops that cannot finish in time** - Compare each stage's typical remaining duration with the days left, for example a Google team match against a 5-day deadline. Done when you have a ranked list of loops worth asking.
4. **Send one stage-specific ask per loop** - Email each recruiter the same day with your deadline and the ask from that stage's row. Every message states the deadline and asks a question with a date in it.
5. **Let the recruiter escalate internally** - The recruiter takes the ask to the coordinator, hiring manager, committee or comp team, put at 24 to 72 hours by practitioners but unverified. Done when the recruiter commits to a date.
6. **Handle proof requests within a day** - Send a letter or comp screenshot redacted to the totals, or decline and restate the total. Reply within one day.
7. **Read replies and decide by deadline minus one** - Sort each reply into live or out, decide one business day before the deadline, then accept or withdraw politely in writing.

### Asking the offering company for time

Step 1 needs its own rules because it happens with the company that made the offer, not the loops you are chasing. Ask for an extension once. Wellfound-sourced advice calls repeated asks "a bad look." There are no published norms for experienced hires to point to:

- **Campus offers:** NACE says most routine offers carry a one- to two-week deadline and asks employers to "be open to reasonable requests for additional time." Rutgers asks employers for "a MINIMUM of two weeks from the date of the written offer."
- **Experienced hires:** no published standard applies. One guide reports "most companies will give you 2 - 5 business days, sometimes up to a week," but cites no data.
- **Exploding offers:** Wellfound calls any offer that expires in under a week an exploding offer.

How often extensions are granted is not established. One source says it plainly: "We found no data on how often employers grant these requests." If the extension is refused, read the refusal as information. One recruiter says that every extension denial they saw "was because they had a backup candidate they liked."

### Order of operations

Sources disagree on the order. ApplyGoat says to ask the offering company for time first and then push the other loops. One Blind commenter would wait for a second offer before telling the first company anything. I follow ApplyGoat's order. You need a fixed date before any ask to the other loops means anything.

> **Rule:** No dated written offer, no expedite ask
>
> Ask a Manager's position is that without another offer about to take you off the market, you can't really ask a company to speed up. Hold every message until the deadline is in an email.

**Stage-keyed expedite email**

```
Subject: Timeline question - [Role] candidacy

Hi [Recruiter name],

I'm still very interested in the [Role] position. I've received an offer from another company and need to give them an answer by [day, date].

[Paste one stage line:]
Pre-screen: Is it realistic to complete your process before then, or should I plan around your normal timeline?
Mid-loop: Could the remaining rounds be grouped into as few days as possible before [date]?
Onsite booked: Is an earlier onsite slot available, and when would the debrief be held after it?
Awaiting debrief: Is it possible for the debrief to happen by [date]?
Committee or team match: When does the next committee sit, and is there any option for a review before [date]?
Offer approval: When do you expect approval, and by what date could I have the written offer?
Verbal given: Could you confirm the date I'll receive the written offer letter?

If that isn't possible, I completely understand. Could you let me know either way by [date two business days before deadline]?

Thanks,
[Name]
```

*Keep the opening and closing the same for every loop; paste in only the one stage line that matches that loop's row.*

The pre-screen line adapts a published script that asks whether it is "possible to expedite the remaining steps or give me a sense of your timeline." Every stage line asks a question that can be answered with a date. A date is something you can hold a recruiter to and a feeling is not.

When you rank loops in step 3, rank on fit as well as timing. A loop that can finish in time but is a weak match is not worth an ask. Refolk's fit score against each posting gives you that ranking without rereading every job description under deadline pressure.

## How expedite requests go wrong

Most failures come from misreading which stage a loop is at, or from sharing a fact before the stage that can use it. Each item below shows what the false signal looks like and how to check it.

1. **Asking with no real offer.** The false positive is treating "positive feedback" as an offer. Feedback is not a deadline and does not take you off the market. *Check:* do you have a dated offer in writing? A Blind commenter's version: "Don't stir things up when you have no chips to play."
2. **Asking a committee to speed up scheduling.** At this stage, a request to go faster runs into a weekly cadence that caps the gain at one cycle. *Check:* ask "when does the next committee sit?" and plan around the answer.
3. **Treating a verbal offer as done.** Approval can stall. In one documented case, a recruiter promised approval after already missing earlier promises. *Check:* ask for the written letter's date and count a missed date as a signal.
4. **Inflating the number before a proof request.** A number that looks fine in an email falls apart once comp asks for the document, and comp teams "see tons of offer letters every year." *Check:* only state a number you could document today.
5. **Trusting an agency recruiter's promise.** In Refolk's sample, 24% of US Technical Recruiters were at staffing or consulting firms. They cannot convene a client's committee, so a date they commit to depends on someone else. *Check:* is the recruiter employed by the hiring company? If not, who at the company owns the date?
6. **Reading a passed committee as an offer.** Committee approval is not the end. "An offer also requires a team with open headcount to match you," and team matching is reported at roughly 2 to 8 weeks. *Check:* ask whether a team is identified and when the comp step starts.
7. **Showing the full letter.** Comp teams may anchor on base salary alone and ignore the rest of the package. *Check:* redact everything except the totals before sending anything.
8. **Misreading the recruiter counts.** The UK count of 702 Technical Recruiters may be low because UK recruiters often hold other titles, such as "Talent Partner." *Check:* search variant titles before treating the 30.1x ratio as a difference in market size.

> **Watch out:** The most expensive false positive
>
> Positive feedback, a passed committee and a verbal offer all feel like an offer and are not. Each one has a next step that can stall, so ask for the date of the next step before counting the loop as near done.

## Reading replies and closing each loop

A company is out when it says it cannot meet your date, when it will not commit to any date, or when it misses a date it committed to. Any loop without a committed date by one business day before your deadline is out for this decision, whatever its reasons.

Documented phrasings that mean stop waiting:

- "We can't meet that deadline so you should take the other job and best of luck with it."
- "We can't commit to that timeline." One practitioner's read: "that's your answer."
- From the offering company, a flat refusal to extend. One recruiter ties every such denial they saw to a backup candidate the company liked.

No published threshold says how long silence means no, such as "no reply in 3 business days." Set your own cutoff and tell each recruiter what it is, which is why the email template asks for a reply two business days before the deadline. Being dropped is possible. One Ask a Manager commenter describes a company where she "interviewed TEN TIMES over the course of FOUR MONTHS" dropping her. No data shows how often a borderline loop changes its outcome after an ask, so do not send one hoping it will.

Close every loop in writing, whatever you decide. Accept or decline the offer before the deadline. Withdraw from each open loop with a short note that thanks the recruiter and leaves the door open.

#### Before the deadline passes

- [ ] The offer deadline is in a dated email from the offering company.
- [ ] I asked the offering company for an extension once, and only once.
- [ ] Every open loop has exactly one stage label.
- [ ] Loops whose typical remaining duration exceeds my deadline are ranked last, not quietly ignored.
- [ ] Each message states my deadline and asks a question containing a date.
- [ ] No message shares the employer name or number at a stage whose row says hold.
- [ ] Every number I shared matches a document I could produce, redacted to totals.
- [ ] Each recruiter I asked works for the hiring company, or I know who there owns the date.
- [ ] My decision cutoff is set at one business day before the deadline.
- [ ] Every loop I am leaving has a short written withdrawal sent or drafted.

### Keeping this reference current

The durations in this guide come from a benchmark, one employer's own statement and candidate reports, and each of them can change. Rather than trusting the figures here, re-check them:

- **Benchmarks:** look for the latest Ashby recruiting operations benchmark and compare its stage medians with the tables above.
- **Committee cadence:** ask each recruiter directly how often their committee sits. That answer beats any secondary source.
- **Your own log:** record every date a recruiter commits to and whether they met it. After one offer cycle, you will have better data on your loops than anything published.

## Frequently asked questions

### Does asking other companies to expedite hurt my chances?

No public data measures it, so nobody can give you a rate. Documented cases exist both ways, including one candidate dropped after ten interviews over four months. Asking late in a process is probably less risky than asking early: about 81% of candidates pass the offer stage against roughly 24% at onsite, so late pressure lands on a stage most people clear. That is an inference, not a measurement. The lowest-risk ask is a question with a date, not a demand.

### Should I name the company that gave me the other offer?

Name it if it is well-known or a direct competitor, and otherwise just say you have an offer and when it expires. That is Haseeb Qureshi's rule. Other guides say to share only the timeline and keep the offer details private, and no source maps the choice to pipeline stage. My default is to name the employer from the debrief stage onward, where it can affect how hard the recruiter pushes internally.

### Can a company speed up its hiring committee for a competing offer?

Usually only by one cycle, if at all. Committees at companies like Google are reported to meet weekly, and a Stripe-side practitioner says the committee genuinely can't be moved up. One secondary source says recruiters can request out-of-cycle reviews when an active offer exists, but that is unverified. Ask when the next committee sits, not whether it can go faster, and plan around that date.

### Should I tell the recruiter the number on my competing offer?

Only once the loop reaches compensation approval, and only a number you can document. At that stage a total comp figure carries more weight than a company name. Earlier, it does little for the timeline and pulls you into proof requests, which in documented cases come at the comp stage. If asked for proof, send the comp section redacted to the totals, never the full letter.

### How long should I wait for a reply before treating a company as out?

No published threshold exists, so set your own: any loop that has not committed to a date by one business day before your deadline is out for this decision. Practitioners put internal escalation at 24 to 72 hours, but that is unverified. Ask each recruiter to reply by a date two business days before your deadline, which gives you a clear signal and a day of margin.

### I got positive feedback but no offer yet. Can I still ask others to expedite?

Not credibly. Without a dated offer in writing, you have nothing that takes you off the market, and Ask a Manager's advice is that you can't really ask a company to speed up without one. Positive feedback is the most common false positive here. Wait until the offer and its deadline arrive in an email, then send your asks the same day.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/expedite-request-stage-reference*
