You just got the email. The interview is tomorrow morning at 9 AM, and the case study prompt is three paragraphs long with a data set you have never seen. Your calendar for the rest of the day is already booked. This is the scenario that separates candidates who get offers from candidates who get a polite rejection — not because of raw ability, but because of how they spend the next 24 hours.
A case study interview with less than 24 hours notice is not a test of how much you can produce. It is a test of how you prioritize under pressure, how you communicate your process, and whether you can scope a problem intelligently when you do not have time to solve it perfectly. The candidates who fail usually fail because they try to do too much, stay silent when they should ask questions, or submit a bloated deck instead of a focused answer. This guide walks you through exactly what to do, hour by hour, along with copyable email templates for the two situations that matter most: asking clarifying questions and requesting a short extension.
Why the First Hour Decides the Outcome
Most candidates spend the first hour panicking or reading the prompt repeatedly. That is wasted time. The first hour is the only window you have to scope the problem before you start solving it. Everything after that is execution, and execution on the wrong interpretation is worse than no answer at all.
Use the first hour for four decisions:
- Decide what the interviewer is actually testing. Is this a market-sizing case, an operational case, a product prioritization case, or a strategy case? Read the prompt twice and identify the single skill they are evaluating.
- Decide what you can realistically produce. If you have four working hours, that is a one-slide answer, not a twenty-slide deck. Scope to the time available, not to the ideal answer.
- Decide what you cannot answer and need to clarify. Write down every ambiguity in the prompt. Then pick the two most consequential ones to ask about.
- Decide your communication channel. Will you email the recruiter, message the interviewer directly, or wait until the interview starts? The answer depends on the company's communication norms and how much time is left.
Common Mistakes When You're Under Time Pressure
The failure patterns in short-notice case interviews are predictable. Almost every rejected candidate commits at least two of the following.
- Trying to build a full deliverable. A polished 15-slide deck submitted at 3 AM is almost always worse than a clean 3-slide answer that directly addresses the question. Interviewers are evaluating your thinking, not your formatting endurance.
- Not asking any clarifying questions. Silent candidates look like they are guessing. A single well-chosen question signals that you understand where the ambiguity is and that you know how to resolve it.
- Asking too many questions. The opposite failure. If you send five clarifying questions the night before, you look unable to make reasonable assumptions — which is itself a red flag.
- Requesting an extension without justification or a plan. "Can I have more time?" with no reason given is a weak ask. "Given the data set size, an extra four hours would let me validate the assumption I flagged" is a strong one.
- Building the deck before doing the analysis. Structure follows insight. If you open PowerPoint first, you will spend your available hours designing slides that say nothing.
- Skipping the assumption documentation. Every case with incomplete data requires assumptions. The candidates who get offers write them down explicitly. The ones who get rejected bury them in the model and hope no one notices.
- Submitting at 3 AM without sleep. A tired candidate in the follow-up interview cannot defend their own work. Submit what you have at a reasonable hour and get rest.
- Treating the case as a solo exam. The case study interview is a conversation. If you present without inviting challenge, you look rigid.
A Step-by-Step Game Plan for the Next 24 Hours
This is the sequence that works when the clock is against you. Adjust the time blocks to your actual schedule, but keep the order.
- Hour 1 — Decode the prompt. Read the prompt twice. Write the one-sentence version of what is being asked. List every ambiguity. Identify the two clarifying questions that would most change your answer.
- Hour 1 (last 15 minutes) — Send the clarifying email. Use the template below. Keep it to two questions maximum. State your assumption for each in case they do not respond in time.
- Hour 2 — Sketch the answer on paper. One page. Structure: the recommendation, the three reasons that support it, the key risk, and the assumption that matters most. No slides yet.
- Hour 3 — Pull the numbers. Identify what data you actually need. If the data is not available, state the number you are using as a placeholder and flag it. Do not fabricate precision.
- Hour 4 — Build the deliverable. Three to five slides maximum. One slide for the recommendation. One for the support. One for the risk and mitigation. One for assumptions and open questions. If the format is a written memo, keep it to one page.
- Final 30 minutes — Rehearse the narrative out loud. You are not memorizing. You are finding the version of the story that sounds natural. If you cannot explain your recommendation in 60 seconds without notes, the structure is not clear enough yet.
- Before you sleep — Send a status note. One sentence to the recruiter confirming you are prepared and on schedule. This signals reliability.
- Morning of — Do not revise the substance. Re-read the deliverable once, then stop. Last-minute edits under stress usually introduce errors.
Copyable Email Templates for Asking Clarifying Questions
Sending clarifying questions the night before is a judgment call. If the prompt is genuinely ambiguous, ask. If you can make a reasonable assumption and document it, do that instead. When you do ask, keep it to two questions and always pair each question with the assumption you will use if you do not hear back.
Option A — Soft and Collaborative
Subject line options:
- Two quick clarifications on the case study prompt
- Clarifying questions ahead of tomorrow's case discussion
- Quick check before I finalize my case submissionDear [Recipient Name],Thank you for sending over the case study prompt. I've reviewed itand I'm looking forward to the discussion tomorrow.Before I finalize my approach, I wanted to check on two points:[Question 1 — e.g., "Should I assume the market data coversonly [Region], or is the scope broader?"]If I don't hear back, I'll assume [your assumption].[Question 2 — e.g., "Is the expected deliverable a slidedeck or a written memo?"]If I don't hear back, I'll prepare [your planned format].I'm on track to have everything ready before [Time]. Happy toadjust if the scope is different from what I've assumed.Best regards,[Your Name]Option B — Direct and Time-Aware
Subject line options:
- Case study — two scope questions before I finalize
- Quick scope check on tomorrow's case
- Clarification request — case studyDear [Recipient Name],I've started working on the case study and want to make sure Ispend the available time on the right version of the problem.Two questions:[Question 1]. My working assumption is [assumption].[Question 2]. My working assumption is [assumption].I'll proceed with those assumptions if I don't hear back tonight,and I'll flag them explicitly in the deliverable.Thank you,[Your Name]Option C — Minimal, One Question Only
Subject line options:
- One clarification on the case prompt
- Quick question on the case studyDear [Recipient Name],One quick question before I finalize my case submission: [Question].If I don't hear back, I'll proceed with [assumption] and note itin the deliverable.Thank you,[Your Name]Copyable Email Templates for Requesting a Brief Extension
Asking for more time is risky but sometimes necessary. The rules are simple: justify the request with a specific constraint, propose a specific new deadline, and confirm you can still deliver a strong answer within the original scope if the extension is not possible. Never frame the extension as a need — frame it as a choice that improves the output.
Option A — Soft and Reasonable
Subject line options:
- Request to extend the case study deadline by [Number] hours
- Case study timeline — one small adjustment request
- Quick note on the case study timelineDear [Recipient Name],Thank you again for the case study prompt. I've reviewed it andI'm looking forward to the discussion.Given the size of the data set, I would benefit from an additional[Number] hours to properly validate [specific area — e.g., thedemand assumptions / the cost model]. If that's possible, I coulddeliver a stronger answer by [Proposed New Time].If the timeline is fixed, I completely understand. I'll delivera focused answer by the original deadline and flag any assumptionsI was not able to validate.Please let me know which works better.Best regards,[Your Name]Option B — Firm and Confident
Subject line options:
- Extension request — case study deadline
- Case study — additional time for data validation
- Timeline check on the case studyDear [Recipient Name],I want to flag one constraint before I finalize my submission.The prompt asks for [specific requirement], which requires[specific data or validation step]. Given the current deadline,I can produce a strong recommendation with documented assumptions,but I cannot fully validate [specific element] in the timeavailable.If an extension of [Number] hours is possible, I can deliver amore complete answer by [Proposed New Time]. If not, I'll proceedwith the original deadline and note the open items explicitly.Happy to adjust based on your guidance.Best regards,[Your Name]Option C — Preemptive, Framed as Scoping
Subject line options:
- Scoping note on the case study
- Case study — proposed scope given the timeline
- Quick scope alignment before I finalizeDear [Recipient Name],Given the [Number]-hour window, I'm planning to scope the casearound [specific focus — e.g., the demand side only], which Ibelieve is the highest-value part of the prompt. That means Iwill not fully develop [other element] unless there is time.If you would prefer I cover [other element] instead, I can shiftfocus — but I'd need until [Proposed New Time] to do it properly.Otherwise I'll proceed with the narrower scope and note thetrade-off in the deliverable.Best regards,[Your Name]What To Do If You Don't Get a Response
Silence does not mean no. It means the recruiter or interviewer is busy, and you need to decide on your own. The correct response is almost always to proceed with your documented assumptions and deliver on the original deadline.
- If you asked clarifying questions and got no reply: Use the assumptions you stated in your email. Make them explicit in the deliverable. Mention them at the start of the interview: "I assumed X because I did not hear back, and I can walk through the alternative if that assumption is wrong."
- If you requested an extension and got no reply: Assume the original deadline stands. Deliver on time. Do not show up late or ask again in the interview.
- If you never got a reply and the deadline is still a few hours away: Send one short follow-up. One. Not two. Not three. A single line asking for confirmation is appropriate. Repeated follow-ups read as anxiety.
- If the interview itself starts without acknowledgment of your email: Do not open with "I never heard back from you." Open with the answer. You can mention the assumptions naturally when you present them.
Frequently Asked Questions
Q: Should I ask clarifying questions when I have less than 24 hours before a case study interview?
A: Yes, but only if the ambiguity is genuinely consequential. Pick the two questions that would most change your answer, state the assumption you will use if you do not hear back, and send the email within the first hour. Do not send five questions or ask about anything you could reasonably assume.
Q: Is it acceptable to request an extension for a case study interview?
A: It is acceptable if you frame it correctly. Justify the request with a specific constraint, propose a specific new deadline, and confirm you can still deliver a strong answer within the original scope if the extension is not possible. Never frame the extension as a need — frame it as a choice that improves the output.
Q: What should I do if I don't hear back after asking clarifying questions?
A: Proceed with the assumptions you stated in your email, make them explicit in the deliverable, and mention them naturally at the start of the interview. Do not send repeated follow-ups and do not open the interview by explaining that no one replied.
Q: How many slides should a case study deliverable have when I have less than a day to prepare?
A: Three to five slides maximum. One for the recommendation, one for the support, one for the risk and mitigation, and one for assumptions and open questions. A focused short deliverable that directly addresses the question always beats a longer one that was rushed.
Q: Should I stay up all night to finish the case study?
A: No. Submit what you have at a reasonable hour and get rest. A tired candidate cannot defend their own work in the follow-up discussion, and the interview panel is evaluating how you think under pressure — not how long you can go without sleep.
Q: What if the interviewer asks why I made certain assumptions during the case discussion?
A: Treat it as a request for your reasoning, not a challenge. State the assumption, explain why you chose it given the information available, and offer the alternative you would have used if the assumption were different. Documenting assumptions in advance is what makes this answer easy.