McKinsey publishes no standard number of days to complete Solve and no public extension or late-start policy. Read the deadline in your own invitation, ask your recruiter about a non-technical conflict before it passes, and contact Solve technical support immediately if the assessment itself fails.
| Point | Answer | Status |
|---|---|---|
| Assessment length | McKinsey says the length is in your invitation email. That is the time for the assessment, not a public completion window. | Official |
| Standard completion window | McKinsey gives no universal number of days or link-expiry rule in the sources reviewed. | Not published |
| Deadline extensions and late starts | No public approval criteria, grace period, or guaranteed outcome. | Not published |
| Non-technical questions and accommodations | Ask your recruiter; McKinsey says accommodations are available for qualifying needs. | Official |
| Fault during Solve | Contact Solve support when the fault arises; support may provide extra time or reset the link, depending on the issue. | Official |
How long do you have to complete McKinsey Solve after the invitation?
McKinsey does not publish a standard number of days from a Solve invitation to completion; its official FAQ says the invitation states your assessment length, while your own invitation must resolve your actual deadline. Read the calendar date, hour, and timezone in your email before deciding when to sit. If any part is absent or unclear, ask the recruiter who sent it for the precise cutoff in writing.
Application deadline
When must your application be in?
Not published
It belongs to the role or recruiting cycle you applied to. None of the Solve sources reviewed here gives one, and it says nothing about when Solve is due.
Window to start
By when must you sit Solve?
In your invitation
Your cutoff is whatever date, hour, and timezone your own email gives. McKinsey publishes no general number of days, so someone else's window tells you nothing about yours.
Assessment length
How long is the sitting itself?
Official
McKinsey's FAQ says the length is stated in your invitation email. It gives no public number of minutes, and the length is not a completion window.
- Application submitted
- Invitation to cutoff: length not published
- The sitting, somewhere inside it
Illustrative and not to scale: the drawing shows how the three clocks nest, with no real dates or durations. The tags follow McKinsey's August 2025 Solve FAQ and Solve page, checked October 11, 2026.
Length and deadline answer different questions. The length tells you how much uninterrupted time to reserve for the sitting. The deadline tells you when that sitting must be completed under the instructions sent to you. The invitation guide shows what to extract from the email, and the 65, 85 or 95 minute guide covers reported game combinations without turning them into a deadline rule.
The application clock varies by route, which is why it cannot stand in for your Solve date. The guides for MBA candidates and experienced hires cover what is known about timing on those paths, and who receives a Solve invitation explains why applying does not tell you when, or whether, the email arrives.
Original fictional scenario: your invitation says to finish on Friday evening and separately lists the assessment length. You have an exam on Friday afternoon. Do not infer that starting just before the stated cutoff will be accepted after it. Ask the recruiter about the cutoff and a feasible alternative now. If the email names a different timezone, confirm that with the recruiter rather than relying on someone else's invitation. Neither McKinsey's Solve page nor its FAQ publishes a general completion window. For the broader application sequence, use the Solve timeline guide.
Can you get an extension to the McKinsey Solve deadline?
McKinsey does not publish a Solve deadline-extension policy or guaranteed grace period; for an exam, travel, illness, or other non-technical conflict, its official FAQ directs you to your recruiter. A recruiter can tell you what applies to your invitation, but this public guidance cannot predict whether your request will be approved. Ask before your cutoff where possible, state the conflict briefly, and propose a specific time you could complete the assessment.
Official
- Non-technical questions go to your recruiter.
- Accommodations exist for a disability, health condition, or specific learning difficulty. Ask your recruiter.
- For a technical fault, support may give extra time or reset the link, depending on the issue.
- A fault you never reported to support earns no reset exception.
Not published
- Whether an extension request is approved, and on what grounds.
- Any grace period after the cutoff.
- How long a recruiter takes to answer.
- What documents an accommodation request needs.
Left column: McKinsey's Solve FAQ (August 2025). Right column: points absent from every McKinsey source reviewed on October 11, 2026. Figures that circulate on prep sites for these points are unverified.
The distinction matters because McKinsey describes a separate remedy for technical faults during the assessment: its support team may grant extra time or reset a link depending on the issue. That statement is about an issue support can diagnose, not a published right to move a calendar deadline for an exam or travel. A request also is not approval. Until your recruiter confirms a change, plan around the deadline already sent to you.
If you need an accommodation because of a disability, health condition, or specific learning difficulty, McKinsey's FAQ explicitly says to speak to your recruiter about potential accommodations. Give the recruiter enough information to route the request and ask what the formal process needs. The public FAQ does not specify documentation, approval time, or a deadline adjustment for any individual case. See the McKinsey accommodations page linked from the FAQ for the broader process. The test-day guide covers assessment rules and setup after your timing is settled, and the Solve FAQ roundup has short answers to the neighbouring questions.
Who should you contact about a deadline, a technical fault, or an accommodation?
McKinsey's official Solve FAQ sends non-technical timing and accommodation questions to your recruiter and technical assessment faults to [email protected] or the live chat; it does not say either channel automatically changes your completion deadline. Route the problem by its cause, then include the timing risk in your message so the person helping you knows why it is urgent.
What is putting your date at risk?
- An exam, trip, or illness before you start
- A cutoff or timezone you cannot read clearly
- An accommodation you need
- A deadline that passed with no fault
Your recruiter
Official route
Answers how the calendar deadline applies to you. Whether a change is approved is not published.
- The link will not load
- The technical check fails
- A game freezes or its graphics go missing
Solve support, while it is happening
Official route
Email [email protected] or use live chat. Support can diagnose the link and may give extra time or reset it, depending on the issue.
- A fault that now threatens the cutoff
Both, for different decisions
Our reading
Support works on the fault. The recruiter is the one to ask how the calendar cutoff will be handled.
This decision path is our editorial reading of the contact instructions in the August 2025 FAQ. McKinsey publishes no automatic extension from either message.
| Situation | Useful details | Limit |
|---|---|---|
| Conflict before starting | Invitation deadline, brief conflict, feasible alternative time, request for written confirmation. | Extension outcome is not published. |
| Accommodation need | State that you need to discuss an accommodation and ask for the process before the sitting. | The FAQ gives no case-specific approval rule. |
| Technical failure during Solve | Time the issue arose, the affected step, and a description in words. | Extra time or a link reset depends on the issue. |
| Missed deadline without a fault | State the actual cutoff and what happened; ask whether any next step remains. | No published late-submission outcome. |
If you cannot find the recruiter contact, reply to the invitation sender or use the recruiting contact it identifies. If the trouble is the assessment link itself, the official Solve FAQ (PDF, August 2025) supplies the technical support address and live chat route, and the guide to Solve system requirements and tech issues covers what the technical check does and does not tell you. Do not send a test content screenshot: McKinsey's Solve rules prohibit recording or capturing the assessment except for an accommodation approved in writing.
What should you say when asking your recruiter for more time?
McKinsey gives no official email template for a Solve extension, so send a short request with your invitation deadline, the non-technical conflict, a feasible alternative, and a request for confirmation before you rely on any changed date. The recruiter is the official contact for this question; the wording below is an original fictional template, not a McKinsey form or a promise that an extension will be granted.
- To
- The recruiter named in your invitation
- Subject
- Solve completion deadline for your application or role
- 1. The deadline as written
- Hello recruiter name, I received the Solve invitation with a completion deadline of date, time, and timezone.
- 2. The conflict, briefly
- I have brief conflict at that time and want to complete the assessment in an uninterrupted slot.
- 3. A workable alternative
- Would it be possible to complete it by proposed date and time?
- 4. A request to confirm
- Please let me know whether the original deadline still applies or if there is another step I should follow. Thank you, your name.
Replace each underlined slot with your own details. Sending this does not change your deadline: only a written reply from the recruiter does.
Keep the reason truthful and concise. If the issue is an accommodation, say you need to discuss one and ask how to submit any required information; do not assume this ordinary deadline template replaces the accommodation process. If the invitation gives a scheduling tool, follow its instructions as well, but do not treat a visible slot as proof that a different completion cutoff was approved. Keep the recruiter's reply with your invitation so the date you act on is clear.
Original fictional scenario: a candidate has an exam overlapping the only quiet block before the invitation cutoff. Their request names the cutoff and a workable alternative. If the recruiter cannot approve it, the candidate can use the remaining available block or ask what options exist; this guide cannot promise another sitting. For a practical plan once the timing is known, see the Solve prep plan.
Is the Solve completion deadline the same as the timed assessment length?
No: McKinsey officially says your Solve invitation states the assessment length, while it publishes no universal completion deadline or rule that the game may finish after a stated cutoff. Treat the calendar deadline, the game's timed tasks, the untimed tutorials, and the technical check as separate planning items. Your own invitation and any written clarification from your recruiter determine the deadline you should use.
Cutoff in your invitation
- Technical check. It runs after you click the link and before Solve starts.Official
- Untimed tutorials. Each task opens with one, so they sit outside the timed work.Official
- Timed tasks. The length is the figure in your invitation email.In your invitation
- Margin. Spare room in case the check or a tutorial takes longer than you expect.Our advice
Illustrative and not to scale. The public sources do not say whether an invitation's stated length includes the check and tutorials, define no grace period, and do not say how a partly completed game is treated at the cutoff. This is a planning method, not a McKinsey timing rule.
The official FAQ also recommends a slot where you will not be disturbed and can finish without interruption, so book the whole strip as one block rather than only the listed minutes. For how reported sittings divide between games, the Red Rock time budget shows one candidate-reported game clock in detail, with your own invitation taking priority.
Original fictional scenario: your invitation has a Friday cutoff after a day of travel. You reserve an earlier quiet block that also allows for the technical check and tutorials. For setup requirements, use the test-day checklist.
Can you start McKinsey Solve close to the deadline?
McKinsey does not publish a late-start or finish-after-cutoff rule for Solve, so starting close to your invitation's deadline carries an unknown risk even if the link opens. A working link is evidence that you can access the check at that moment, not written permission to finish after the cutoff. Confirm any ambiguity with your recruiter before you start.
Cutoff in your invitation
Started with margin
Started close to the cutoff
- 1 Technical check
- 2 Untimed tutorials
- 3 Timed tasks
- 4 Margin
- Past the cutoff: no published rule
An original fictional comparison, not to scale. McKinsey does not say what happens to work that runs past a cutoff, so the hatched stretch is an unknown, not a penalty we can describe.
Original fictional scenario: a candidate returns from travel shortly before the deadline and sees that the link still opens. The official FAQ says a technical check comes before Solve and each task has an untimed tutorial, so the candidate cannot infer that the visible link leaves enough time to complete. A safer decision is to ask for a deadline clarification while there is still time to act, then choose an uninterrupted block based on the reply. If the recruiter is unavailable, follow the existing deadline as written and do not invent a grace period.
If your start is late because the tech check fails or the link will not load, that is a technical issue. Contact support at once, describe the fault and its start time, and tell the recruiter if the deadline is at risk. If you simply had no available slot, ask the recruiter about a non-technical extension. The invitation guide helps check the link and timing details; the Solve tips guide covers preparation habits once you have a viable slot.
What should you do if a technical issue interrupts Solve?
McKinsey's official Solve FAQ says to contact [email protected] or live chat when a technical issue occurs; support may provide extra time or reset the link depending on the issue, but it cannot make a reset exception if you did not contact support at the time. Do this while the fault is happening, whether the problem is a failed tech check, missing graphics, a frozen task, or an inaccessible link.
Report it the next day
You close the frozen game, try again later, and write to support once the sitting is over.
McKinsey's FAQ says no reset exception is made for a technical issue you did not raise with support.
Report it as it happens
You stop, email [email protected] or open live chat, and describe the fault while it is on screen.
McKinsey's FAQ says support may give extra time or reset the link, depending on the issue.
Both outcomes are as stated in the August 2025 Solve FAQ. Neither is a calendar extension: ask your recruiter about the deadline separately.
Describe the error in words, include when it began and which step you reached, and follow support's instructions before refreshing, leaving, or trying to restart. Keep any support reference you receive. If the deadline could pass during the investigation, inform the recruiter separately and ask how the calendar cutoff will be handled. A support response about the technical problem is not the same as a recruiter-approved deadline change. The system requirements guide lists the device facts McKinsey does publish, so you can rule out an avoidable fault before the day.
Original fictional scenario: the game freezes after a tutorial. The candidate uses the official support route immediately and describes the screen without photographing it. If support diagnoses a link fault, it may offer extra time or reset the link; that outcome depends on the issue. McKinsey also prohibits recording and screenshots of the live assessment except under an approved written accommodation. The test-day guide has the wider setup and integrity rules.
What happens if you miss the McKinsey Solve deadline or submit late?
McKinsey does not publish what happens to a Solve application after a missed deadline or late submission, so neither automatic rejection nor acceptance can be promised from the public sources reviewed. Contact your recruiter promptly, state the deadline in your invitation and what occurred, and ask whether you can still complete Solve or whether your application has another next step.
If a technical fault caused the delay and you contacted Solve support when it happened, give the recruiter the support reference and describe the sequence. Support handles diagnosis and possible link remedies; the recruiter handles the application question. If you did not contact support during the fault, the official FAQ specifically says no exception for a reset can be made on that basis. It does not state a general policy for every late submission, so do not turn that reset rule into a blanket rejection rule.
Original fictional scenario: a candidate realizes the next morning that the cutoff has passed. They send the recruiter a short factual message and ask what, if anything, can still be done. Repeatedly trying the link cannot establish that a late attempt will count. If the candidate completed the game but sees no confirmation, they describe that possible technical problem to support promptly and tell the recruiter about the deadline risk.
A missed sitting also raises the question of a second chance. McKinsey publishes no retake or waiting-period rule either, and the guide to retake and reapply rules sets out what is and is not known. For how a completed result is weighed, see how the Solve result is used, the application timeline, and the score and results guide.
How should you prepare if only 48 hours remain before the deadline?
If your Solve deadline is close and no extension has been confirmed, use the 48-hour section of the prep plan, choose a protected sitting slot, and try one independent free practice run; this is our preparation advice, not a McKinsey requirement. First resolve any timing or technical uncertainty that could prevent you from sitting at all. Then use the remaining preparation time for the task type where you need the most practice.
- Settle the date
Reread the cutoff and timezone. Send the recruiter any open question now, and plan around the written deadline until a reply changes it.
- Book the block
Reserve one uninterrupted slot with room for the technical check, the tutorials, and a margin.
- Do one practice run
Pick a practice format and complete its free run; SFL Classic has no countdown.
- Review your own mistakes
Note the specific errors you made, not a generic list of tips.
- Check the device and the link
Use a PC or Mac, open the invitation, and keep the support address to hand.
Our preparation advice. McKinsey says no preparation is needed for Solve; the PC or Mac requirement and the support route are from its FAQ.
Start with your invitation and its stated length. The official FAQ says no business knowledge or gaming experience is required and that each task has an untimed tutorial. Candidate reports describe different game combinations, so the invitation and live instructions take priority over any generic sequence. If you want to rehearse the data work, use the Red Rock method; if checking combinations is harder, use the Sea Wolf method. If you can only fit one, which game to practise first helps you choose. The Sustainable Futures Lab guide explains its reported versions without claiming McKinsey has confirmed their mechanics.
The practice chooser leads to one complete free run of each of four Road to Offer practice formats: Red Rock, Sea Wolf, SFL Classic and SFL Island. Start without an account, then create a free account to finish and keep the score, points breakdown and worked feedback on each submitted decision, including visual explanations; no payment is needed. Learning mode offers coaching and feedback step by step across all four formats, untimed in the clocked games, with the matching game pack, Solve pack or qualifying Annual access. Build a free Solve plan from your invitation length and test date, then create a free account to view and save its dated practice steps, with a 28-day preparation limit. This is independent practice on Road to Offer, not the official assessment or a prediction of your McKinsey result. Leave your final block for device check, link access, and a quiet uninterrupted sitting. During the live assessment, McKinsey's rules prohibit outside websites, applications, AI tools, prepared notes, and help from another person unless it has approved an accommodation in writing. For the larger purpose and format of Solve, see the Solve overview.
Sources and evidence boundaries
- Official, checked October 11, 2026: McKinsey's Solve page and Solve FAQ (August 2025 PDF). The FAQ is the source for length in the invitation, untimed tutorials, the technical check, contact routes, support remedies, and accommodations. The Solve page also identifies the technical support address and integrity rules.
- Official, checked October 11, 2026: assessment integrity expectations apply to assessments and interviews generally; the Solve-specific FAQ supplies the rules cited above for this assessment. The disability accommodations page is linked from that FAQ.
- Reported: candidate forum question titles show that people ask about appointment windows, deadline extensions, extra time, and late submission. They establish the questions, not McKinsey's decisions in individual cases. No reported number of days is used here as a rule.
- Unknown in the public sources reviewed: a standard completion window, extension approval criteria, a grace period, treatment of a partly completed game at the cutoff, and the outcome of a missed or late deadline. Your invitation and direct written guidance from your recruiter govern your case.
