SHL Management Scenarios: Our Method and 12 Practice Questions
A management scenario rarely asks whether an action sounds positive in isolation. It asks whether that action fits the facts: what is urgent, what is known, who has authority and what should happen next. ReasoningCampus offers SHL management scenarios preparation, with original cases that teach you to compare actions and explain your judgement rather than memorise “always” rules.
You might need to help a colleague, protect a client, delegate work or respond to repeated underperformance. The appropriate response can change when one fact changes: a first missed deadline is not the same as a repeated problem after agreed support. This lesson begins with the assessment context, develops a practical reading method and then works through those differences in detail.
Understand the management problem before rating the actions
SHL publishes information about management scenario products and response formats. Check the exact name and scale in your invitation. Our cases, suggested ratings and explanations are independent ReasoningCampus teaching material; they are not SHL items or an official scoring key.
| Theme | Decisive facts | Question to ask yourself |
|---|---|---|
| Performance and support | First occurrence or repeated issue; support already tried. | What needs investigating, and what is already established? |
| Delegation | Experience, novelty, capacity and decision authority. | What oversight is proportionate to the actual risk? |
| Quality or confidentiality | Known harm, urgency and the relevant procedure. | Which protective step should happen now? |
| Conflict and handovers | Ownership, shared facts and recovery time. | What decision will unblock the work? |
| Client expectations | Feasible delivery, essential needs and authority to commit. | What can be promised honestly? |
| Competing priorities | Capacity, impact and who can choose the trade-off. | Who needs a clear set of options to decide? |
There is no numerical formula that makes all management judgements correct. Where a scenario contains figures, calculate them carefully; where it asks about action, explain the link between the fact and the response. A useful explanation also says what new fact would change your view. The paired cases below show why “always escalate” and “always handle it yourself” are unreliable shortcuts.
SHL Management Scenarios: the ReasoningCampus decision method
Our method asks what is known, who owns the decision, what matters now, whether the action is feasible and how follow-up will happen. Apply those checks to each response, then explain what makes two apparently reasonable actions different. The checks organise the teaching; they are not SHL scoring dimensions or a rule that the longest response must be best.
Our focus in this lesson is managerial judgement: making a decision that fits the facts, the people involved and the work that needs to be done. We teach it through a repeatable method, examples with explained ratings and practice followed by feedback.
- Read the situation accurately. Separate stated facts from assumptions about motives or missing information.
- Compare actions fairly. Check responsibility, risk, deadlines and what each response leaves unresolved.
- Explain the difference. Use paired scenarios to see why a first mistake and a repeated problem need different responses.
- Turn feedback into a next step. Review your quiz answers by study area and return to the method you need.
Start here: confirm your assessment below, learn the five checks, then attempt the worked examples before the quiz. For our wider learning materials, see ReasoningCampus SHL test preparation.
Managerial judgement: identify the deciding fact
Before reviewing a rating, finish this sentence: “This action is more suitable here because the scenario states…”. In the paired examples below, a first missed deadline and a repeated pattern call for different follow-up. If you would give the same answer after that fact changes, check whether you are applying a slogan instead of evaluating the situation.
SHL Management Scenarios: format and timing
Check the exact assessment title in your invitation. “Management”, “Executive”, “Graduate”, a general SJT and a work simulation should not be treated as interchangeable product names.
| Main focus | Managerial judgement. |
|---|---|
| Response format | A rating scale for evaluating responses. |
| Listed maximum | 16 scenarios and 100 questions. |
| Average testing time | 40 minutes. |
| Allowed time | Untimed. |
| Sittings | One. |
Source: SHL Management Scenarios fact sheet (PDF), copyright 2018; checked on 13 October 2026. This is the document’s published specification, not a claim that every current employer invitation uses it.
Average duration is not a time limit. Do not turn the 40-minute estimate into an assumed countdown. Follow the assessment instructions you actually receive.
The fact sheet names three areas: Managing Objectives, People Management and Reputation Management. [1] In the original practice below, you will consider priorities, team issues, credible commitments and wider organisational needs.
How to approach SHL Management Scenarios questions
Start with the instruction. Evaluating each action is a different task from selecting one best response or putting all responses in order. Use the response format shown in your own assessment. For the exercises here, rate each option independently; you may use the same rating more than once.
The following five checks are a ReasoningCampus learning approach. They are not an official SHL scoring formula.
- Identify the decision.What needs to happen, by when, and to what standard? Keep the immediate problem separate from the longer-term improvement.
- Read the actual evidence.Notice previous conversations, agreed procedures, known risks and missing facts. Do not invent a motive, a policy or an emergency.
- Locate responsibility.What can the manager decide? Where is specialist advice needed? Which trade-offs belong to someone with wider authority?
- Match the action to the problem.Does the action fit the seriousness and history of the issue? Consider its impact on delivery, people and stakeholders.
- Check what happens next.A useful response often needs an owner, a deadline or a review. Ask whether it actually changes the situation, and what important part it leaves unresolved.
A useful habit: before choosing a number, finish the sentence “This response helps because …, but it leaves …”. That makes it easier to distinguish a strong answer from one that is merely polite, decisive or reassuring.
Apply the method: evidence, delegation, priorities and communication
Start with SHL’s stated task
SHL’s product description asks candidates to rate the effectiveness of each response to a workplace scenario on a six-point scale. [2] Start with that instruction: judge what the action would achieve in the situation. In the worked examples below, explain which stated fact makes an action useful, incomplete or inappropriate.
The rest of this section is a ReasoningCampus study method for the fictional exercises in this guide. It shows how to compare evidence, responsibility and consequences. It is not SHL’s scoring method, and the practice answers have not been validated against SHL results.
| Task | What you decide | How it appears here |
|---|---|---|
| Rate effectiveness | Evaluate each action separately against a defined scale. | Eight worked scenarios with 32 suggested learning ratings. |
| Select the best-supported response | Choose the option that best satisfies the facts and constraints. | Twelve new multiple-choice learning questions, with feedback at the end. |
| Rank responses | Put actions in relative order under the stated ranking rules. | Not used in this guide. |
Two different learning activities: the final multiple-choice quiz checks application of the guide’s principles. It is not a reproduction of SHL’s six-point rating interface.
Evidence: separate what happened from why it happened
A missed deadline tells you what happened, not why. Before assuming that someone lacks effort or ability, check the workload, access to tools, instructions and support already provided. Use the facts in the question; do not supply a reason the scenario never gives.
Use information selectively. Ask which missing fact could change the decision and whether you can obtain it in time. A short conversation may be valuable before responding to a first missed deadline. A confirmed incident may need immediate containment while its cause is investigated.
Delegation: make the task and decision limits clear
Giving someone work does not automatically give them authority to approve it. A colleague might compare proposals while the manager makes the final choice. Specify the result, decision limits, support, deadline and review point. You can remain responsible for the outcome without doing every task yourself.
Match oversight to the risk. Familiar, low-risk work may need light monitoring. A new method that will be repeated across many outputs benefits from an early qualified check. More approvals are useful only if they address a relevant failure point.
Priorities and risk: check feasibility before reassurance
A commitment needs enough time, capacity and authority to be credible. Identify dependencies as well as final deadlines: a late handover can make another person’s work impossible even when your own task looks small. Distinguish a flexible preference from an explicit requirement in the scenario.
Check the non-negotiable rules first. In these exercises, being quick or courteous does not make an action acceptable if it breaks a stated approval rule or launch requirement. Among the options that meet those rules, compare the effects on delivery, people and the wider organisation. If none is clearly better, look at the priorities and trade-offs in the question.
Communication: say who will do what, and check it happened
A useful message allows someone else to act. Separate confirmed facts from uncertainty; name the owner and next action; give a realistic update time. Escalate a decision when it exceeds your authority, bringing the evidence and available options. Continue to own the follow-through after the authorised decision is made.
Verify the result. An agreement is an intention. Completion means the action occurred. Effectiveness means the action actually improved the problem. A strong response explains how those later stages will be checked.
How to choose between two sensible management responses
Once you have used the five checks, compare the remaining options side by side. In our teaching exercises, this helps you explain a close decision without inventing a missing step.
- Find the shared benefit.What do both responses achieve? For example, both may tell a colleague that a deadline matters.
- Find the meaningful difference.Does one also establish a workable recovery plan, name an owner or check an approval? Credit only the steps actually stated, and consider any delay or extra work they create.
- Name the deciding fact.Finish: “I prefer this response because the scenario says …”. Then change that fact and ask whether your preference still holds.
Distinguish a better option from a merely more detailed one
A longer response is not automatically stronger. An added meeting can delay an urgent action; another approval can duplicate an existing control. Prefer the option whose extra steps solve a real problem in the scenario. When one option meets all the same requirements as another and also closes a material gap without creating a new drawback, you have a clear reason to prefer it.
Interpret the learning scale carefully
The six practice labels run from less to more effective. A one-point step does not represent a fixed improvement in ability: a rating of 6 is not “twice as good” as 3. Averaging these suggested ratings would not produce an SHL score. The final quiz uses a simpler approach: one point for each answer that matches its explained learning key.
Use the explanation as an argument you can inspect
A defensible explanation connects a stated fact to a consequence and then to a decision. If you disagree with a nearby rating, identify the exact assumption or trade-off behind the disagreement. That is more informative than treating every one-point difference as an objective error.
A worked planning decision: 18 hours available, 21 hours of work
It is Thursday morning. Your team has 18 productive hours available before Friday’s deadline. Report A needs 12 hours and Report B needs 9. The work estimates are reliable, the tasks can be shared between qualified colleagues, and both sponsors currently expect the full reports on Friday. No extra capacity has been agreed.
This is an original planning exercise to make a management decision easier to explain. It is not a sample from SHL’s assessment.
First establish what the numbers allow
The two reports need 12 + 9 = 21 hours. Available capacity is 18 hours, so the plan has a 3-hour shortfall. Telling the team to “make both deadlines” does not remove it. Moving the work between the same colleagues also leaves the total capacity unchanged.
| Possible change | What it resolves | What you must confirm |
|---|---|---|
| Add 3 hours of qualified help before Friday. | Capacity becomes 21 hours, matching the estimated work. | The person has the required skills and access, and the help creates no uncounted handover or review work. |
| Agree to remove 3 hours of lower-priority work from the scope. | The remaining work becomes 18 hours. | The authorised sponsor accepts the smaller deliverable and essential quality requirements are still met. |
| Move at least 3 hours of work beyond Friday. | No more than 18 hours remain due in the original window. | The revised deadline is approved, later capacity is available and downstream work can still proceed. |
Then check why “the hours fit” is not enough
Matching the totals is necessary for this plan, but it does not prove the schedule will work. A review may have to happen before a report can be sent. A specialist may be available only after the deadline. Training someone may use part of the time you expected to save. Check those conditions before making a commitment.
If you do not have authority to approve a change, bring the decision-maker the figures and workable options. Once a choice is approved, confirm the revised scope, owner and delivery time with the people affected.
Change one fact: what if the extra colleague needs two hours of your team’s help?
Three extra hours no longer close the gap if the handover consumes two of the team’s original 18 hours. Effective capacity is 18 + 3 − 2 = 19 hours, leaving 21 − 19 = 2 hours unresolved.
Method: count usable capacity after the costs of arranging the help. Then check whether another approved change closes the remaining gap.
Watch out for: counting the same person’s time twice or treating promised help as productive work before checking access, skills and availability.
Keep a short record of the reasoning error
After practice, write four lines. This turns a wrong answer into a specific check you can use next time.
| Prompt | Example note |
|---|---|
| Which fact did I overlook? | The new colleague needs two hours of the existing team’s help. |
| What did I assume? | I counted all three extra hours as a net gain. |
| Why did that change the decision? | The proposed help leaves a two-hour gap, so both original commitments are still unsupported. |
| What will I check next time? | Subtract setup, handover and review time before relying on additional capacity. |
Apply the same review habit to non-numerical mistakes: an overlooked approval rule, a missing owner or an assumption about why someone performed poorly. Revisit the relevant principle in the reasoning method, then try a fresh question.
SHL Management Scenarios practice: 8 worked examples
Read each situation, then evaluate all four responses using the learning scale below. Treat the options as separate alternatives, rather than a sequence of actions. Base your judgement only on the facts given.
These six labels belong to this practice guide. They do not reproduce SHL’s scale wording or scoring system. Nearby ratings can be debatable; the explanation and the distinction between responses matter more than matching a number.
Try the ratings before opening the explanation. You can revisit them as your understanding develops. No timer is needed for this first learning pass.
A reliable colleague misses a deadline
You manage a small operations team. Maya has missed an internal report deadline for the first time in a year. She normally delivers accurate work. You have not yet spoken to her, and you do not know what caused the delay. The report is needed tomorrow; there is no immediate service disruption.
Pay attention to: A first occurrence, with the cause still unknown.
ASpeak with Maya privately today, establish the cause, agree a realistic recovery deadline and check progress before the report is due.
BTell Maya privately that deadlines matter and ask her to send the report as soon as possible, without discussing the cause or agreeing a check-in.
CIssue a formal warning immediately because a missed deadline must have a consequence.
DComplete the report yourself this evening and say nothing because Maya usually performs well.
When you are ready, compare all four ratings with the worked explanation.
Worked explanation and suggested ratings
Begin with the difference between a known delivery problem and an unknown cause. The report is late, but this is a first occurrence from a normally reliable colleague and there is time to speak before tomorrow. That combination favours a private fact-finding conversation with a concrete recovery plan. It does not justify assuming either misconduct or that no intervention is needed. After the conversation, a newly discovered obstacle may change the support required; until then, the response should keep both delivery and fairness in view.
This addresses the immediate delivery problem while checking the facts. A private conversation allows support and clear expectations without assuming misconduct or excusing the missed deadline.
The message is relevant and private, so it has some value. However, “as soon as possible” leaves recovery vague, and the underlying obstacle may remain unresolved.
This moves to a formal response before establishing what happened. The first occurrence and strong previous performance favour a proportionate fact-finding conversation first.
The report may be delivered, but the approach silently transfers responsibility to you. It misses the chance to understand the cause, agree recovery or prevent another delay.
What to take forward: Support and accountability can sit in the same response. The strongest option names a conversation, a recovery action and a follow-up.
The same deadline problem keeps returning
You manage an operations team. Maya has missed the recurring internal report deadline four times. You have already discussed the causes, adjusted workload and agreed written expectations with weekly check-ins. No new obstacle has been identified. Your organisation’s stated performance procedure calls for a documented review at this stage, with HR advice; you can still agree a recovery plan for tomorrow’s report.
Pay attention to: Documented support has already been tried, and the next procedural step is specified.
AHold the documented review, hear Maya’s account, consult HR as required and agree both immediate recovery and the next review date.
BRepeat the same informal conversation and weekly check-ins, postponing the documented review indefinitely.
CAnnounce the missed deadlines at the next team meeting so colleagues can put pressure on Maya.
DAsk HR to advise you on the documented review, but make no plan for the report due tomorrow.
When you are ready, compare all four ratings with the worked explanation.
Worked explanation and suggested ratings
Compare this case with Maya’s first missed deadline. Here, expectations, workload adjustments, support and reviews have already happened, and the problem has continued. Repeating the same informal response indefinitely would ignore that history. The stated procedure calls for a documented review with HR guidance, but the work still needs a recovery plan and Maya should have the chance to provide relevant new facts. Documentation and support are compatible; the choice is not between public punishment and doing nothing.
This follows the stated procedure while keeping the discussion evidence-based. It addresses the repeated pattern, allows Maya to respond and protects the immediate delivery requirement.
A conversation can still help, but repeating an unchanged intervention overlooks the history. Delaying the stated next step leaves expectations and consequences unclear.
Public pressure creates avoidable embarrassment and does not resolve the performance issue fairly. The situation calls for a private, documented process with relevant support.
Seeking appropriate advice is useful. The response is incomplete because it leaves the immediate deadline unmanaged; the procedural review and delivery plan both need attention.
What to take forward: The change is not “be tougher”. It is “respond to the evidence and the stage already reached”. Compare option A here with option C in Scenario 1.
Delegating a familiar assignment
A routine client dashboard is due in five working days. Leon has completed the same dashboard accurately several times and has confirmed that he has capacity. The data source and requirements are unchanged. You are responsible for a separate, higher-priority service review due tomorrow.
Pay attention to: Proven task-specific capability, available capacity and a routine assignment.
ADo the dashboard yourself because you remain accountable for its quality, and delay tomorrow’s service review.
BGive Leon the outcome, quality checks and deadline, agree a midpoint update and remain available for exceptions.
CGive Leon the output, quality checks and deadline; ask him to flag exceptions immediately rather than scheduling a routine update.
DAsk Leon to send every intermediate calculation for your approval before continuing.
When you are ready, compare all four ratings with the worked explanation.
Worked explanation and suggested ratings
Ask what risk the supervision is meant to control. Leon has delivered this same dashboard accurately, the method is unchanged and capacity is available. Detailed approval of every calculation would add delay without addressing an identified gap. Clear standards and a deadline remain necessary. Both a light midpoint check and an exception-based update can be reasonable, depending on the context; the suggested ratings reflect how proportionate the proposed oversight is to the facts supplied, not an official SHL scoring rule.
Accountability does not require doing every task personally. Here, taking back familiar work displaces the more urgent responsibility despite a capable colleague being available.
The response makes ownership and standards clear while using Leon’s demonstrated capability. A proportionate update gives you visibility without disrupting his work.
This is defensible for an experienced colleague doing unchanged work. It provides less planned visibility than option B, but the clear escalation trigger makes it stronger than simply disappearing.
This may catch errors, but it imposes unnecessary supervision for a familiar task. It also consumes the time you need for the more urgent service review.
What to take forward: Judge oversight against the actual task and the person’s relevant experience. More checking is not automatically better management.
Delegating after the assignment changes
A client dashboard is due in five working days; your separate, higher-priority service review is due tomorrow. Leon has capacity and has produced accurate dashboards before, but this one uses a new calculation method he has never applied. The first output will inform a client decision. A colleague who knows the method can provide a short walkthrough today, and you can arrange a qualified check before release.
Pay attention to: The person is experienced, but the method is new and the output matters.
ADelegate the full dashboard with only the deadline and ask Leon to contact you if he notices a problem.
BArrange the walkthrough, ask Leon to produce a small sample first and schedule a qualified check before the final dashboard is released.
CTake over the entire dashboard immediately and cancel the higher-priority service review without discussing the conflict.
DArrange the walkthrough and a qualified final check, but do not review an early sample.
When you are ready, compare all four ratings with the worked explanation.
Worked explanation and suggested ratings
The important change from the previous delegation case is novelty. Leon now faces an unfamiliar method, and the output informs a client decision. A walkthrough makes the process understandable, an early sample catches misunderstanding before it spreads, and a qualified final check protects the decision. Those checkpoints target a specific risk. Simply giving a deadline provides too little support; taking over all the work would be excessive when suitable guidance and review are available.
Delegation is sensible, but Leon may not recognise an error in an unfamiliar method. The response leaves out support and validation that are both available.
This keeps ownership with Leon while addressing the specific knowledge gap. Early sampling can uncover misunderstandings before they spread across the full output.
The task needs support, but full takeover is not justified by the facts. Available expertise and a validation step offer a way to manage risk without silently sacrificing the other priority.
This provides meaningful support and a release control. An early sample would make the plan stronger by identifying misunderstandings while there is more time to correct them.
What to take forward: Compare the light supervision in Scenario 3 with the unsupported delegation here. The task’s novelty changes what an appropriate level of support looks like.
A defect just before release
A client file is due to be sent in 45 minutes. A colleague identifies a reproducible error affecting several figures. You have authority to pause the release. An analyst can establish the scope within 20 minutes, and your team’s release procedure requires known material errors to be resolved before sending. The client has not yet received the file.
Pay attention to: The defect is confirmed, containment is within your authority and a check is immediately available.
ASend the file on time and correct it later only if the client notices the problem.
BPause the release, assign the scope check and alert the account lead with a clear time for the next update.
CAsk your manager for permission to pause, while allowing the scheduled release to proceed unless a reply arrives.
DPause the release and ask the analyst to check it, but postpone all stakeholder communication until the work is finished.
When you are ready, compare all four ratings with the worked explanation.
Worked explanation and suggested ratings
Separate containment from investigation. The file is due to leave in 45 minutes, the error is known to be material, and you have authority to pause release. Stop the exposure first, then use the analyst’s 20-minute check to establish scope while informing the account lead and setting an update point. Waiting for a manager would consume the window without adding required authority. Pausing without communication is better than releasing the error, but it leaves others unable to plan around the delay.
This knowingly releases information that may mislead the client and conflicts with the stated release control. Meeting the clock does not make the underlying output acceptable.
This contains the confirmed problem and creates an immediate route to a decision. It also gives the relevant stakeholder a factual update without inventing a completion time.
Seeking input can be useful, but you already have authority to contain the issue. Waiting without stopping the release risks the avoidable outcome the procedure is designed to prevent.
The key containment action is sound. The missing update can still leave others making commitments based on an unchanged delivery time, so the response is only partly complete.
What to take forward: Separate the action needed now from the analysis needed next. A confirmed problem sometimes requires containment before the full picture is available.
A dispute over handovers
Two experienced team members disagree about who should prepare a recurring handover. Both have missed parts of it, and the written process does not assign a clear owner. You have heard their accounts separately. Neither reports threats or discriminatory behaviour. Today’s handover is still recoverable, and you are responsible for clarifying the team’s workflow.
Pay attention to: The process is ambiguous, and the immediate work still needs an owner.
AAsk the rest of the team to vote on which colleague is responsible for the problem.
BRemind both colleagues to be professional and let them negotiate ownership without a deadline.
CArrange a short joint discussion, agree today’s owner and deadline, document responsibilities for future handovers and review the next cycle.
DAssign an owner and deadline for today, then schedule a separate review of the recurring process with both colleagues.
When you are ready, compare all four ratings with the worked explanation.
Worked explanation and suggested ratings
The immediate obstacle is an unclear handover owner, not an established case of misconduct. Both people have been heard separately, and today’s work can still be recovered. A useful response therefore assigns ownership and a deadline, then addresses the workflow that produced the conflict. A short joint conversation can do both; a prompt operational decision followed by a scheduled review can also be strong. The comparison depends on whether each action actually unblocks today’s work and prevents the same ambiguity returning.
A popularity-based decision does not establish what the workflow requires. It can divide the team further and distract from the missing ownership rule.
Professional behaviour matters, but the response leaves the operational ambiguity unresolved. An open-ended discussion does not secure today’s handover.
This addresses the immediate deliverable and the process gap without choosing a side prematurely. The review checks whether the agreement works in practice.
This secures the urgent work and commits to a wider fix. It is a strong alternative, although the staged discussion may take longer to establish a shared understanding.
What to take forward: A people problem may also be a system problem. Look for the missing rule or handover, as well as the tone of the conversation.
A client asks for an unsupported promise
A client requests a new feature by Friday. Delivery staff say Tuesday is the earliest date they can currently support. An approved workaround may cover part of the client’s need, but you have not checked whether it is suitable. You can discuss scope and alternatives; you cannot promise a date the delivery team has not approved.
Pay attention to: The promised date would be unsupported; there may be a useful alternative.
AExplain the delivery constraint, clarify the client’s essential need, check the workaround with delivery and confirm only commitments the team can support.
BPromise Friday to preserve the relationship and then ask the team to find a way.
CTell the client that the request is impossible and close the discussion without checking the workaround.
DAsk the delivery lead to contact the client directly, but do not brief them on the client’s priorities or agree who will follow up.
When you are ready, compare all four ratings with the worked explanation.
Worked explanation and suggested ratings
Start with the commitment boundary: Friday is not a confirmed delivery date, and Tuesday is the earliest currently supported estimate. The client may have an essential need that a narrower workaround could meet, but that possibility has not been checked. Clarify the need, investigate feasibility with the delivery lead and return with an honest commitment. Promising Friday hides the constraint; closing the request immediately ignores a potentially useful alternative. Bringing in the delivery lead helps only if the discussion has a clear purpose and follow-up.
This combines honest communication with active problem-solving. It protects trust while exploring whether the client’s underlying need can be met another way.
The commitment exceeds your stated authority and contradicts the available delivery information. It transfers an avoidable problem to the team and puts client trust at risk.
This avoids an unsupported promise, but it ends the conversation before testing an available alternative. A firm boundary can still leave room for a useful solution.
Involving the person with delivery knowledge may help. The weak handover and missing follow-up make this less reliable than a coordinated response.
What to take forward: Protecting reputation means making credible commitments and handling problems openly. Reassurance without evidence can create a larger problem later.
Two sponsors, one limited team
Two internal sponsors ask your team to complete separate pieces of work by Thursday. Each request is reasonable, but your capacity estimate shows that both cannot be completed to the required standard. Neither sponsor can set the other project’s priority. Your manager owns the combined programme priorities and is available this afternoon.
Pay attention to: The conflict crosses your decision authority, and an informed escalation route is available.
APromise both deadlines and ask the team to work faster, without changing scope or obtaining more capacity.
BChoose the request from the more senior sponsor and inform the other sponsor after Thursday.
CPrepare effort estimates, consequences and scope options; ask your manager to resolve the trade-off, then confirm the agreed plan with both sponsors.
DTell both sponsors immediately that capacity is insufficient and ask them to agree a compromise, without setting a decision time or involving the programme owner.
When you are ready, compare all four ratings with the worked explanation.
Worked explanation and suggested ratings
The sponsors want different outcomes, capacity cannot deliver both by Thursday, and neither sponsor can prioritise the other one’s work. You therefore need a decision from the manager who owns that trade-off. Your contribution is to make the decision easy to assess: estimates, consequences and feasible options. Seniority alone is not the stated prioritisation rule. Asking the sponsors to compromise without a decision deadline may simply postpone the conflict until there is no time left to act.
This preserves appearances temporarily but does not resolve the capacity constraint. It creates commitments that the current plan cannot support.
The choice is not grounded in programme priorities, and delayed communication prevents others from adapting. Seniority alone does not resolve the stated authority conflict.
This escalates a decision that belongs at programme level while retaining responsibility for the evidence and follow-through. The sponsors receive a consistent, actionable plan.
Early transparency is useful and may start a constructive discussion. However, the response lacks a decision mechanism if the sponsors cannot agree, leaving the team’s priorities uncertain.
What to take forward: Escalation is useful when the decision exceeds your authority. Bring a clear trade-off and workable options, then take ownership of the agreed next steps.
Why one changed fact can change your rating
These two pairs are the central learning exercise. The same broad action can have a different value when the evidence changes. Before returning to a question, name the exact fact that matters.
Pair A: first occurrence or repeated pattern?
Scenario 1 starts with an unexplained, isolated delay. A private discussion and recovery plan are proportionate.
Scenario 2 adds previous support, repeated delays and a stated next procedural step. Continuing the same informal approach indefinitely now leaves a significant gap.
The deciding fact: what has already happened and been tried.
Pair B: familiar work or a new method?
Scenario 3 gives an experienced colleague routine work. Light oversight can be sensible.
Scenario 4 changes the method and makes validation important. Support and an early sample become more valuable, even though the colleague is still experienced.
The deciding fact: capability for this specific task.
Common traps in management scenario practice
| Tempting shortcut | A better check |
|---|---|
| “Always escalate.” | Is the decision outside your authority, or are you passing on something you can already resolve? |
| “Always handle it yourself.” | Would delegation or specialist input protect both quality and your other responsibilities? |
| “The kindest response is best.” | Does support come with a workable action and clear expectations? |
| “Consult everyone first.” | Who actually needs to contribute, and can an urgent containment action wait? |
| “Protect reputation by avoiding bad news.” | What information do stakeholders need to make sound decisions and maintain trust? |
| “There must be one high and one low rating.” | Are you rating actions independently or ranking them? Follow the stated instructions. |
Interactive managerial judgement quiz: 12 new questions
Choose the one answer best supported by each question’s stated facts. These questions test application of the learning method, including diagnosis, delegation, priorities and communication.
How it works: answer all twelve questions, then select “Finish quiz & see results”. Your choices can be changed before submission. The answer key, explanations for every option and study recommendations appear together at the end.
This is an original ReasoningCampus knowledge-and-application quiz. Each answer matching its learning key earns one point. The result is not an SHL score, percentile, pass mark or validated measure of managerial ability.
Quiz results and complete worked answers
You earn one point for each correct answer. The four study areas below help you decide what to revisit. Their scores describe your answers here, not your overall managerial ability.
- Evidence and diagnosis: Separate an observation from its possible cause. Check denominators, relevant conditions and missing information before attributing blame. Revisit the theory.
- Delegation and control: Match ownership, authority, support and review points to the task. Accountability can stay with the manager while work is delegated. Revisit the theory.
- Priorities and risk: Check every deadline, dependency and non-negotiable condition. Resolve a real constraint rather than relying on optimistic promises. Revisit the theory.
- Communication and accountability: Make the next action usable: state what is known, who owns the work, when an update is due and how commitments will be confirmed. Revisit the theory.
Question 1: Interpreting an uneven error pattern
Correct answer for this question: C. Anna’s observed error rate is higher; the cause still needs investigation.
Method: Calculate comparable rates → identify what the data establish → list plausible causes that still need evidence.
Calculate a rate before interpreting the counts. Anna’s rate is 9 ÷ 90 × 100 = 10%; Ben’s is 18 ÷ 360 × 100 = 5%. Anna therefore has the higher observed error rate, C. That calculation describes the recorded work; it does not establish why the rates differ. Case difficulty, support and other relevant conditions have not yet been compared.
A uses the raw number of errors while ignoring Ben’s larger workload. B correctly notices a two-to-one rate ratio but incorrectly turns it into a judgement about carelessness. D notices the workload difference yet fails to calculate the resulting rates. The proportionate management response is to inspect comparable cases and identify causes before deciding what support or action is appropriate.
Question 2: Delegating within an approval boundary
Correct answer for this question: A. Compare the proposals against the agreed criteria; bring your recommendation to tomorrow’s approval review.
Method: Identify the decision right → delegate the preparation → schedule the retained approval.
The work has two different parts: analysing the options and authorising the decision. A delegates the comparison and recommendation to a capable colleague while keeping the manager’s approval at the required review point. That uses available skill without transferring authority the colleague has not been given.
B lets the colleague commit beyond the stated authority. C keeps all the analysis with the manager even though the colleague can contribute. D accepts a supplier before the approval step. A useful delegation names the output, the deadline and the boundary: “Compare the options and recommend one for tomorrow’s review; do not commit us before approval.” The boundary makes the delegation usable rather than vague.
Question 3: Planning around a dependency
Correct answer for this question: D. Complete the extract from 09:00 to 11:00, then the presentation from 11:00 to 14:00.
Method: List durations and handovers → sequence the earliest binding deadline → verify the remaining task still fits.
Work backwards from the earlier deadline. The extract takes two hours and must be ready for the independent review by 11:00, so starting it at 09:00 finishes exactly on time. The three-hour presentation can then run from 11:00 to 14:00, ahead of its 16:00 deadline. D satisfies both requirements under the durations given.
A delays the extract until noon and misses the review. B spends the first hour on the presentation, leaving the extract unfinished until noon. C waits until the extract’s review deadline before beginning useful work. There is no need to attend the independent review in this scenario; adding that unstated dependency would change the problem. In practice, check whether the durations are estimates and whether a buffer is available, but solve the stated question first.
Question 4: Updating a stakeholder under uncertainty
Correct answer for this question: B. State the known impact, explain what is still uncertain and commit to another update at 14:30.
Method: Known facts → open questions → current action → next update time.
B separates the known impact from the unknown cause and restoration time, then commits to a next update at 14:30. That gives people actionable information without presenting a guess as fact. A scheduled update is something the communicator can control even when the repair time is uncertain.
A turns the next checkpoint into an unsupported restoration promise. C reports an unconfirmed cause as established. D leaves affected people without information until the incident ends. The useful structure is: what is affected, what remains uncertain, what is being done and when the next update will arrive. If new evidence confirms the cause or recovery time, the next message can become more specific.
Question 5: A performance problem with a shared cause
Correct answer for this question: A. Arrange the authorised access correction, then check that each colleague can complete a sample task.
Method: Identify the shared condition → remove the verified barrier within authority → retest performance.
The stated barrier is access: the three staff members know the process but lack the required permission. A addresses that barrier through the authorised administrator and checks a small sample afterwards. The sample confirms that access and execution now work together before the backlog grows.
B retrains people on steps they already understand, leaving the permission problem untouched. C transfers their work to others rather than resolving the dependency. D sets performance targets that staff cannot meet without access. Distinguishing “does not know how” from “cannot currently do it” is the central judgement here; different causes need different management responses.
Question 6: Two specialists and an integration gap
Correct answer for this question: D. Agree shared assumptions, section owners and an integration check before the final deadline.
Method: Separate work packages → define shared assumptions → assign ownership → check integration before release.
D gives the specialists shared assumptions, clear ownership of their sections and a point where the work will be integrated. The scenario says they have the skill and capacity, so the main risk is inconsistency between their outputs. Coordination should target that interface rather than remove their autonomy.
A allows incompatible assumptions to develop unnoticed. B has the manager do both sections despite the available expertise. C requires continuous mutual approval, adding unnecessary dependency to routine decisions. A brief agreement about definitions, format and integration is more proportionate. If the work were unfamiliar or unusually high-risk, additional checkpoints might be justified; those are not the facts supplied here.
Question 7: Containing an access error
Correct answer for this question: B. Restrict the unintended access and notify the designated incident team under the stated process.
Method: Contain within authority → activate the stated response route → preserve facts for follow-up.
B follows the explicit incident procedure: restrict the mistaken access immediately and notify the designated incident contact. You have the relevant authority, and the material is confidential, so delaying the protective step would leave the exposure in place. Preserve the information needed for the proper investigation.
A waits for permission that the scenario says you already have. C asks recipients to ignore the file but does not remove access or trigger the procedure. D deletes records that may be needed to understand the incident. The decisive facts are confidentiality, current exposure, your access-owner role and the specified procedure—not a general preference for escalating or acting alone.
Question 8: Handling a late change in scope
Correct answer for this question: C. Explain the one-day impact, offer feasible scope options and obtain the sponsor’s decision before changing the plan.
Method: Estimate the impact → present viable options → obtain the decision → update the shared commitment.
C makes the trade-off explicit before committing to the added analysis. The request adds work and moves completion beyond the original date; the change process gives the sponsor authority to approve that decision. Present the impact and feasible options, then obtain the required choice.
A accepts the change and reports the delay only afterwards, removing the sponsor’s opportunity to decide. B refuses every change without examining its value or feasibility. D promises incompatible outcomes under the stated capacity. A constructive response might offer the original scope on time or the expanded scope later, with the consequences of each. The right option depends on the authorised decision, not on pretending the constraint has disappeared.
Question 9: Knowing when a response should change
Correct answer for this question: D. The same requirement has repeatedly been missed after clear expectations, practical support and scheduled reviews.
Method: Check clarity of expectations → check support already offered → examine the subsequent pattern.
D adds a relevant history: the issue continued after expectations, support and a review point had been established. That changes the response from initial fact-finding towards the documented next step in the process, while still allowing the person to explain any new information. It is the repeated pattern after intervention that matters.
A is a new unexplained event and needs investigation. B attributes a first problem to a system outage, which points towards a different cause. C relies on unfamiliar working style rather than demonstrated failure against expectations. A fair review uses evidence about the work and the support already provided; it should not use personal similarity or irritation as a substitute.
Question 10: Choosing a proportionate quality check
Correct answer for this question: B. Complete one example, obtain the qualified check and apply any correction before producing the remainder.
Method: Locate the repeated failure point → validate an early example → correct the process before scaling.
B uses the available qualified review where it can prevent the most rework: on one sample before the whole batch is produced. The template is new, so the sample tests whether the instructions have been interpreted correctly. Any correction can then be applied consistently to the remaining work.
A postpones the same discovery until the whole batch may need correction. C assumes general experience removes the risk created by an unfamiliar template. D assigns technical approval to a manager who lacks the relevant expertise. The checkpoint is small, early and competent; those features make it useful without turning every later step into a full approval cycle.
Question 11: A launch gate and sunk effort
Correct answer for this question: C. Delay the launch, explain the unmet gate and agree corrective work followed by a new valid check.
Method: Identify the gate → compare the valid result → correct and retest before making the release decision.
The launch condition is at least 95% accuracy, and valid checking shows 88%. The gap is 95 − 88 = 7 percentage points. C respects the stated gate: explain the shortfall, correct the defects and retest before release. Six weeks of effort do not change the measured result or the acceptance condition.
A lets past investment override the current quality requirement. B substitutes a different measure that does not satisfy the accuracy gate. D removes errors from the evidence to create the appearance of passing. If the authorised decision-maker changes the requirement through a legitimate process, that would be a new fact; the scenario does not give permission to redefine it yourself.
Question 12: Turning agreement into a usable handover
Correct answer for this question: A. Confirm a named owner, the expected correction, a completion date and a check that the error no longer occurs.
Method: Owner → defined action → deadline → evidence of completion and effectiveness.
A turns a general agreement into an action someone can complete and someone can verify: name the owner, define the output, set a deadline and agree how completion will be checked. The error is recurring, so an intention without those details is not enough evidence that the cause has been addressed.
B records thanks but leaves the work undefined. C asks everyone to be more careful without assigning responsibility for the specific correction. D closes the issue when only agreement has occurred. The follow-up need not be elaborate: a named owner, a corrected sample by a stated time and a short check can be sufficient when they match the problem.
The quiz evaluates choices on this page without sending them to a server. Refreshing the page clears the attempt.
How to use your practice results
After each scenario, record the response on which your rating differs most from the suggested one. Write down the fact you relied on, the consequence you expected and the part of the response you may have overlooked.
- First pass: read slowly and explain your own judgement before opening the worked answer.
- Review: decide whether the disagreement comes from a missed fact, an invented assumption, a different view of risk or an incomplete follow-up.
- Context check: change one fact and explain whether your judgement should change. Use the two pairs above as a model.
- Next practice session: use new situations and apply the same checks. Recalling the suggested numbers from this page does not show that the method transfers.
Use the comparison as feedback. This page does not calculate an SHL percentile, pass mark or management profile. Its ratings are editorial teaching judgements for these particular fictional situations.
ReasoningCampus SHL preparation: managerial judgement study
This free ReasoningCampus lesson provides a complete introduction to our approach to scenario practice. If your invitation specifically names Management Scenarios, confirm that title before choosing further materials. The full preparation page covers our wider SHL offering; ask about current Management Scenarios coverage if it is not explicitly listed.
Choose your next practice step
- You assumed a motive that was not stated. Return to the evidence check and separate the reported behaviour from your explanation of it.
- You selected a helpful-sounding action that cannot meet the deadline. Check capacity, dependencies and decision authority in the planning example.
- Two responses still look equally suitable. Identify the deciding fact and compare what each action leaves unresolved, using the full explanations after the quiz.
Explore the ReasoningCampus SHL preparation materials and choose the areas named in your assessment invitation.
SHL Management Scenarios preparation: practical FAQs
Use these answers when choosing your preparation, comparing difficult responses or deciding what to study next.
What does ReasoningCampus teach in this SHL preparation lesson?
We teach a five-check method for evaluating managerial responses: identify the decision, read the evidence, locate responsibility, test whether the action fits the problem, and check the follow-up. You apply it to eight worked scenarios and a twelve-question quiz. This lesson is free; our full SHL preparation page lists the wider materials available and their current coverage.
My invitation only says “SHL assessment”. How do I choose the right practice?
Check the invitation and candidate portal for the exact assessment name and response instructions. If these are missing, ask the recruiter to confirm them before choosing a package. Do not assume that a management role means you will take Management Scenarios. Start with our SHL assessment invitation guide, then match your preparation to the confirmed task.
Should I rate every action, rank the options or choose one answer?
Follow the instruction for that activity. In this lesson, the eight worked scenarios ask you to rate each action independently; the final quiz asks for one best-supported answer per question. Ranking would mean putting responses in order, which neither activity requires. See the comparison of response formats before practising, and follow your actual assessment’s own rules.
Two responses both sound sensible. What should I compare?
Ask what each response actually resolves and what it leaves open. Check the owner, deadline, approval and follow-up; do not assume an omitted step will happen. For example, identifying a capacity problem helps, but it does not authorise a later deadline. Use the close-answer comparison to find the specific difference rather than choosing the longer or friendlier response.
Can I give two actions the same rating in the worked examples?
Yes. Our learning activity evaluates each action separately, so you can reuse a rating. Do not force a high and a low score into every scenario. If two options seem equally useful, explain what each achieves and misses before selecting a number. For a real assessment, use its stated rating rules.
When should a manager escalate instead of dealing with the issue directly?
In these exercises, check whether the decision exceeds the manager’s authority or requires a specified specialist process. Escalate the decision with evidence and workable options, while continuing any appropriate action you can take yourself. Avoid using escalation to pass on ordinary ownership. Compare the first missed deadline with the repeated problem: the history and stated procedure change the response.
Should an experienced colleague work independently or receive extra checks?
Check their experience with this task and method, not just their job title. Familiar work may need light monitoring; a new calculation method may need an early sample check and access to support. Compare Scenario 3 and Scenario 4. The teaching point is to match oversight to the actual uncertainty, rather than choosing “trust” or “control” every time.
What should I do when a scenario gives more work than the team can finish?
Establish the gap before promising delivery. Then check whether extra capacity, reduced scope or a changed deadline is feasible and who can approve it. Count handover and review time as well as production time. The 18-hour planning example shows why adding three hours of help can still leave work unfinished.
I have one evening to prepare. How should I use this lesson?
Use this as a study sequence, not a guaranteed readiness plan: confirm the test, read the five checks, then work through the two paired cases in Scenarios 1–4. Explain the fact that changes each decision. Next, attempt the quiz without opening another copy of the answers. Spend your remaining time reviewing missed reasoning steps. If your invitation names a different assessment, prioritise material for that assessment.
How do I use the quiz feedback instead of memorising the answer letters?
Answer all twelve questions and submit to see your results. For each missed question, write the overlooked fact, your unsupported assumption and the check you will use next time. Follow the results links to the relevant study area. A repeated attempt checks recall as well as understanding; use a new situation to test whether you can apply the method. See the review routine.
English is not my first language. How can I avoid misreading a scenario?
During practice, restate the task in one sentence: who must decide, what must happen, by when and under which restriction. Pay attention to words such as “already”, “only”, “before” and “must”; they can change the decision. Keep a short vocabulary list from your mistakes. Before the real assessment, ask the recruiter about available language or accessibility arrangements and permitted tools.
Are these official SHL answers, and does my quiz score predict a pass?
No. The scenarios, ratings and quiz are independent ReasoningCampus teaching material. Official SHL documents support the product information, not our answer key. The quiz gives one point per answer matching its learning key; it does not estimate an SHL percentile or employer pass mark. Use the explanations to improve your decisions rather than treating the total as a hiring prediction.
Choose the next guide that matches your invitation
- Understand your SHL assessment invitationIdentify the named assessment before selecting more practice.
- SHL tests candidate guideExplore the wider assessment types and their different purposes.
- SHL Verify G+ preparation guideUse this when your invitation includes a general ability assessment alongside workplace judgement.
Official SHL sources and practice notes
The product description and format information were checked against the official SHL documents below on 13 October 2026. Document dates and product names are retained so you can check whether they match your invitation.
Assessment documents
- SHL — Management Scenarios Assessment Fact Sheet (PDF). Copyright 2018. Source for the published format, timing and named assessment areas.
- SHL — Scenarios Management 2012 product description. Source for the scenario-based task and six-point response scale.
What comes from where: the two SHL sources support the product description and published specifications. The eight worked scenarios, suggested ratings, twelve-question quiz and step-by-step explanations are original ReasoningCampus practice material. They are not official SHL questions or answer keys.
For questions about this guide, contact ReasoningCampus. If a product specification changes, use the latest instructions from your assessment provider.
Teaching approach and editorial transparency
ReasoningCampus teaches the approach used in this lesson through original practice and worked explanations. AI assistance was used for research, drafting and implementation. The product information was checked against the two official SHL sources above; our explanations show how the stated facts support each learning answer.ReasoningCampus with AI-assisted research, drafting and implementation. Each practice explanation links the facts in its fictional scenario to a decision. The product facts were checked against the two official SHL sources above.
Read about ReasoningCampus, or send a correction or question. The guide does not claim personal experience of your employer’s test or reproduce confidential assessment content.
Continue your SHL preparation with ReasoningCampus
Use the full preparation page to inspect our wider SHL materials. For a Management Scenarios assessment, confirm the exact coverage you need before purchasing.
View full preparationVisit the ReasoningCampus homepage →ReasoningCampus provides independent educational preparation. It is not affiliated with, endorsed by or sponsored by SHL. SHL and its product names belong to their respective owners.
