McKinsey Redrock Study 2026: Free Practice, Format, and Worked Answers

McKinsey Redrock Study is the data-interpretation exercise inside McKinsey Solve. Reported two-part format, Investigation-Analysis-Report flow, worked math examples, scoring caveats, and practical strategy. Confirm details from your McKinsey invitation.

Updated Sep 8, 2026By Esteban Ronsin
On this page

McKinsey Redrock Study is the data-interpretation module of Solve; candidate reports commonly describe a roughly 35-minute Study flow (Investigation, Analysis, Report) plus six independent mini-cases, while your invitation remains the source of truth.

The reported timing and mini-case count come from MConsultingPrep, StrategyCase, PrepLounge, and Prepmatter, checked June 10, 2026. McKinsey's official Solve page describes Solve as a gamified assessment that showcases problem-solving ability and says performance is considered alongside the rest of your application and any other assessments you are asked to take. For the umbrella view of how Redrock fits into Solve, see our McKinsey Solve guide. This article focuses on Redrock-specific prep: the reported format, the math, the scoring caveats, and how to practice without treating unofficial details as guarantees.

Live free simulator from Road to Offer for the McKinsey Solve Red Rock study. Practise this style of assessment in the browser, no account needed to start.

What does Redrock Study test?

Prepare to select relevant evidence, calculate with the right units, and explain what the result means. McKinsey's official Solve page describes the overall assessment, but does not publish a Redrock scoring matrix or guarantee a particular game sequence.

Practice phaseWhat you produceWhat to check
InvestigationA short journal of relevant factsRegion, period, population and units
AnalysisA calculation that answers the objectiveDenominator and unrounded intermediate values
ReportA numerical conclusion and suitable chartSame dataset and time basis as the analysis

This table is a Road to Offer practice framework. The phase descriptions come from third-party accounts, including the Redrock walkthrough reviewed for this guide. Your assessment instructions control navigation and timing.

Road to Offer online assessment flow from invitation to timed modules, data interpretation, process tracking, and interview prep follow-up

What Is the McKinsey Redrock Study?

Redrock study assessment flow with data, patterns, hypothesis, mini case, and decision steps

Candidate reports place you in the role of a researcher analyzing fictional wildlife population data, often involving wolf packs and elk across geographic regions. The fictional context is useful for prep because it removes prior-knowledge advantage and forces pure data interpretation.

Some third-party prep providers report a roughly 35-minute Redrock flow and a shorter mini-case section in recent versions. Treat that as preparation context, not a promise: McKinsey can vary assessment details by role, region, and cycle, and your invitation should override any prep-site description.

The core skill being tested is reading a chart or table and pulling the right number under time pressure. That is exactly what a graph drill rehearses, so build the reflex before you sit the Study.

Read a Redrock chart under pressure from the Road to Offer drill engine. Answer a real prompt and get AI-scored feedback. Free accounts include 3 drills per day for the first 3 days after signup.

How Does Redrock Work? The Two-Part Structure

Candidate reports describe two distinct parts. The boundary between them is critical for time management if your invitation uses this version.

Part 1: The Study Section (Three Sequential Phases)

Candidate reports describe the three Study phases as one-directional. If your version works that way, once you advance you cannot return, so missed data in Investigation cannot be recovered during Analysis.

Phase 1: Investigation (practice target: 6 min). You receive about a page of text plus charts and tables describing a research scenario. You drag relevant data points into a Research Journal. The discipline: read the research objective first, identify which calculations Analysis will require, and only collect the data points those calculations need. Candidates who grab every number end up with a cluttered Journal and slower Analysis.

Phase 2: Analysis (practice target: 9 min). You answer math questions using the data you collected. Some candidate reports describe an on-screen calculator that logs unrounded results and lets you reuse those values. If present, this feature is a major accuracy lever because manual re-entry of rounded numbers creates cascading errors.

Phase 3: Report (practice target: 6 min). You fill in a partially completed research report: numeric blanks, directional comparisons ("higher" vs. "lower"), and chart-type selection. If your Analysis answers were wrong, the Report fill-ins can propagate the error.

Part 2: The Cases Section (Six Independent Mini-Cases)

After the Study, candidate reports describe a set of standalone mini-cases. Each case is self-contained, so an error on one does not necessarily affect the others. This breaks the cascading-error problem of Part 1 and lets you recover from individual mistakes. In practice, aim for high accuracy across the set rather than chasing a published pass line.

What Math Does Redrock Test?

Redrock math skills map with percentages, rates, growth, ratios, and time check labels

Candidate reports suggest Redrock is math-heavy. The math is not advanced, but it must be fast and accurate under time pressure. Keep a consulting math formulas reference beside your practice and build the mental math speed these questions reward. Build automatic fluency with five concept areas:

ConceptWhy It AppearsCommon Trap
PercentagesPopulation share, density shareTreating a 30% rate vs 20% rate as "10% difference" instead of 10 percentage points
Percentage pointsComparing two ratesCalculating relative change of the rates instead of absolute difference
Growth rates(end - start) / start × 100%Forgetting to divide by the starting value, or confusing absolute change with rate
Weighted averagesPopulation-by-territory averagingUsing a simple average when the question asks for population-weighted
Ratios & probabilityComposition and likelihood questionsAveraging per-group ratios instead of computing the pooled ratio

Worked Example: Growth Rate Comparison (Analysis Phase)

Scenario: Compare wolf population growth in the Northern vs. Southern Region (Year 1 to Year 5). Northern: 240 → 312. Southern: 180 → 216.

  • Northern growth rate: (312 − 240) / 240 × 100% = 30%
  • Southern growth rate: (216 − 180) / 180 × 100% = 20%
  • Difference: 10 percentage points (not 10%, not 33%)

If your version includes calculator logging, save both rates before computing the difference. For pooled growth, retain the original population counts as well: the two rates alone do not tell you how much weight each region carries.

From research journal to completed report

Use the same original population example above. The research objective is: which region grew faster between Year 1 and Year 5, and what was the combined growth? This is a teaching exercise, not an official question.

Journal labelValue to retainWhy it matters
North, Year 1240 wolvesStarting denominator for North
North, Year 5312 wolvesEnding population for North
South, Year 1180 wolvesStarting denominator for South
South, Year 5216 wolvesEnding population for South

Do not add territory size to this journal unless the question asks for density. The objective asks for population growth, so area would not enter the formula. Preserve the year and region beside each number; four unlabeled values are not usable evidence.

Analysis. Combined Year 1 population = 240 + 180 = 420 wolves. Combined Year 5 population = 312 + 216 = 528 wolves. Combined growth = (528 - 420) / 420 × 100 = 25.71%, rounded only for this final display. Averaging 30% and 20% would give 25%, which weights unequal starting populations equally.

Completed report. "From Year 1 to Year 5, the combined wolf population rose from 420 to 528, an increase of 25.71%. North grew by 30%, compared with South's 20%, a gap of 10 percentage points. These observations show population growth; they do not establish its cause."

Chart choice. Use grouped bars to compare each region's Year 1 and Year 5 counts. Two observed dates do not show the path between them, so do not invent annual points or imply steady yearly growth. A pie chart would show composition, not the change requested here.

Run the short Redrock study to practice selecting evidence and using it in a new calculation.

Worked Example: Weighted Average (Analysis Phase)

Scenario: Calculate the island-wide wolf density weighted by territory.

RegionWolvesTerritory (km²)Density
Eastern Plains4801204.0
Northern Forest3601802.0
Western Coast240604.0
  • Weighted (correct): (480 + 360 + 240) / (120 + 180 + 60) = 1,080 / 360 = 3.0 wolves/km²
  • Simple average (incorrect for "island-wide"): (4.0 + 2.0 + 4.0) / 3 = 3.33

Read the question phrasing carefully. "Average density across the island" requires the weighted method. "Average of the three regional densities" requires the simple method. The wording determines which denominator is correct.

These growth-rate and weighted-average steps are the same arithmetic case interviews demand, just under a research wrapper. A timed math drill is the fastest way to make them automatic.

Drill case math under time from the Road to Offer drill engine. Answer a real prompt and get AI-scored feedback. Free accounts include 3 drills per day for the first 3 days after signup.

How Is Redrock Scored?

McKinsey does not publish a Redrock scoring matrix. Candidate reports and third-party prep discussions point to two useful practice dimensions.

Answer accuracy: straightforward correctness. Analysis answers matter because errors can cascade into Report. Use 80-85% accuracy and near-complete mini-case correctness as practice targets, not as official thresholds.

Process quality: assume the platform can observe your interaction pattern, including how you collect data, use the calculator, revise answers, and distribute time. Even when the exact scoring model is not public, a cleaner process reduces avoidable errors.

A clean practice profile looks like targeted Investigation notes, calculator logging on every multi-step calculation, deliberate chart selection, and few rushed reversals. Do not confuse this with an official scoring formula.

How Do I Prepare for Redrock?

A 5-step preparation sequence based on what successful candidates report on PrepLounge, MConsultingPrep, and StrategyCase:

  1. Build math fluency (Days 1-3). Drill percentages vs. percentage points, weighted averages, and growth rates until automatic. Our case interview math practice guide covers these exact operations.
  2. Memorize chart-type decision rules (Day 2-4). Bar = compare categories at one time point. Line = trend over time. Stacked bar = composition over time. Scatter = correlation. Pie = parts of a single whole. Histogram = distribution of one variable. Treat Report-phase chart selection as high-stakes in practice.
  3. Practice chart interpretation (Days 3-5). Give yourself 60 seconds per chart to extract the trend, outlier, and what the data does not show. Builds the rapid-assessment habit Redrock requires.
  4. Run timed simulations and Road to Offer drill reps (Days 5-10). Use a round-up of MBB assessment simulators for Redrock-like pacing, then use Road to Offer graph and math drills to repair the exact error type: exhibit reads, weighted averages, growth rates, and synthesis from data. Then bridge into live McKinsey practice cases so Redrock data habits show up in interviews.
  5. Review errors by category (ongoing). Math error → more drilling. Misread question → practice reading the question before the data. Chart error → revisit decision rules. Time blowup → adjust your phase budget.

Practice the Redrock evidence-to-answer loop

Work through the short original study, select the relevant evidence, and review the calculation. This is a diagnostic, not a full official Solve replica.

Common Redrock Mistakes (and Fixes)

The six errors that most often damage Redrock-style practice:

MistakeFix
Rushing InvestigationRead the research objective twice. Map every calculation Analysis will need before dragging.
Skipping calculator logging if it is availableSave every result before moving on. Drag logged values into chained calculations.
Confusing percentage with percentage pointsDrill 10-15 mixed problems before Solve. The distinction must be automatic under time pressure.
Wrong chart type under time pressureMemorize the decision rules above and make chart selection deliberate.
Spending >2 min on one mini-caseHard cap at 2 min. Best estimate, move on. Five careful cases beat four perfect plus one skipped.
Erratic process behaviorPractice the full Investigation-Analysis-Report sequence repeatedly until habits are systematic.

How should you divide a 35-minute practice session?

This is a Road to Offer study plan, not an official phase allocation. It adds up to exactly 35 minutes. Use the duration and navigation rules in your invitation for the real assessment.

SectionPractice timeTask
Investigation6 minRead the objective and collect labeled inputs
Analysis9 minCalculate and retain unrounded values
Report6 minCheck the conclusion and chart choice
Independent cases11 minPractice switching to fresh datasets
Buffer3 minRecover time or review where navigation permits
Total35 minOne timed practice session

The buffer is not permission to return to locked questions. Check each answer before advancing, and follow the actual interface if it differs from this practice plan.

Connected Resources

Redrock usually arrives alongside at least one more Solve module, so once your Redrock loop is stable, run the sibling formats the same way:

Redrock is one piece of McKinsey's screening process. Pair this guide with:

Clearing Solve gets you to the live round. Rehearse the kind of McKinsey case that round opens with.

Practice a McKinsey first-round profitability caseMcKinsey

Profitability · medium

Practice a McKinsey first-round profitability case

Energy / Retail

Practice this case free

Sources and Further Reading (checked 2026-06-10)

Frequently asked questions