Structuring & business sense
Opening questions of the case · About 2 minutes target per question
What it tests. MECE structuring: breaking an ambiguous problem into component parts without overlap or gaps.
Worked example. For a premium EV maker with a 12% profit decline despite 8% higher unit sales, the right framework dissects profit into Revenues (P x V) and Costs (FC + VC), not Porter's Five Forces or the 4Ps, because volume is up so the issue is price or costs.
Common traps. The over-engineering trap: choosing complex qualitative frameworks when the prompt needs a direct quantitative diagnostic.
How to handle it. Choose the option mapping closest to the fundamental economic drivers: revenues, costs, volume, capacity constraints or value-chain stages.
Dataset & information selection
Embedded in the case · About 1.5 minutes target per question
What it tests. Analytical data prioritisation: filtering out background noise to focus on the core metrics.
Worked example. To verify whether a margin drop is driven by production inefficiency, select the Bill of Materials (raw battery costs) and the labour-hours and plant-overhead logs, not the customer demographics or competitor pricing tables.
Common traps. The data-collection trap: selecting every table for fear of missing information, which the assessment explicitly penalises as disorganised.
How to handle it. Before selecting, ask: 'does this spreadsheet directly help calculate a variable in my core diagnostic equation?' If not, leave it.
Quantitative calculations
Several multi-step calculations · About 4 minutes target per question
What it tests. Multi-step business math and mental-math speed under time pressure.
Worked example. If battery packs are 40% of a £30,000 variable cost per unit and rise 15%, the new unit cost is £13,800 + £18,000 = £31,800, so a 30,000-unit run totals £954,000,000.
Common traps. The zero-check error: mismanaging zeros or decimals when scaling from a unit to a full production run (confusing millions with billions).
How to handle it. Write calculations cleanly on a physical scratchpad with units, and match the platform's explicit rounding and unit instructions before submitting.
Data interpretation (graphs & exhibits)
Embedded in the case · About 2.5 minutes target per question
What it tests. Graphical synthesis and business acumen: extracting a clear narrative from multi-variable visual data.
Worked example. If market share falls 15% to 10% while unit discounts climb 2% to 12%, the conclusion is that discounting is failing to halt a structural share decline, pointing to deeper product competitiveness issues.
Common traps. The dual-axis trap: reading the wrong axis and drawing false conclusions about the trend.
How to handle it. Spend 10 seconds reading the legend, both axis units and any footnotes before analysing the trend.
Open-ended written rationale
Embedded in the case · About 2 minutes target per question
What it tests. Written synthesis and concise, executive-level communication.
Worked example. 'Consolidating regional distribution centres addresses the root cause by eliminating redundant lease costs, a guaranteed £14m overhead reduction, whereas marketing introduces demand uncertainty.'
Common traps. The rambling trap: a long paragraph repeating case facts instead of a direct, data-backed conclusion.
How to handle it. State the recommendation immediately, give one supporting metric and contrast it with the alternative.
Timed video recommendation pitch
1 pitch · 60 seconds prep, 60 seconds record, no pauses or re-records
What it tests. Executive presence, verbal structuring and communication synthesis under pressure.
Worked example. State the recommendation in the first 10 seconds, give two supporting data points, outline the key execution risks and close with next steps.
Common traps. Countdown panic: stumbling or losing structure while watching the 60-second timer.
How to handle it. Use the pyramid principle and rehearse a clean three-point structure on the notepad during the prep window rather than scripting it.