Colleague Performance and Ownership Scenarios
Key Takeaways
- Colleague-ownership SJT themes test whether you balance support with accountability: help the person understand impact and recover, without permanently taking over their work.
- Stronger first responses often explain implications of missed work, leave ownership with the colleague, and offer help or coaching proportionate to the situation.
- Weaker patterns include pure scolding without support, immediate punitive escalation when early support is still appropriate, and doing the whole task yourself so forgetfulness is rewarded.
- CVF anchors are primarily We take ownership, We support and inspire, We are emotionally aware, and We collaborate—plus respect for a colleague’s dignity while standards are upheld.
- A reported pattern of forgetfulness still does not justify humiliation or silent cover-ups; address the current need and enable better next behaviour.
Why Colleague-Ownership Themes Appear on the SJT
Many national sift Situational Judgement Test items put you inside a team, not only face-to-face with the public. A classic theme is colleague performance and ownership: someone forgets a task, cuts a corner, or leaves shared work incomplete, and you must judge how effective different first responses would be.
These items are not law exams. You do not need force policy numbers or disciplinary codes. You need Level 1 practitioner judgement: protect the shared outcome, treat the colleague with dignity, leave appropriate ownership with them, and avoid both cold abandonment and soft rescue that removes responsibility.
The Competency and Values Framework (CVF) 2024 language that most often colours these ratings includes:
| CVF element | How it shows in colleague-ownership items |
|---|---|
| We take ownership | You do not ignore a problem that affects the team or the public; you also avoid “owning” someone else’s whole job forever |
| We support and inspire | You help people improve, not just criticise them |
| We are emotionally aware | You notice stress, newness, or defensiveness and still stay professional |
| We collaborate | Shared work needs honest, constructive contact between teammates |
| Respect and empathy (value) | Standards without humiliation |
| Courage (value) | You do not cover up errors or gossip instead of acting |
The Anchor Teaching Scenario (Original Illustration)
Use this teaching vignette to learn rating logic. It is not an official College of Policing keyed sample, and no fake “official mark scheme” is claimed.
Stem (teaching only): You are working with a new team member on a shared incident-related task that requires accurate paperwork so the next shift can continue the work safely and fairly. The colleague has forgotten to complete their part of the paperwork. Other colleagues have already mentioned a pattern of forgetfulness. The deadline for handover is soon. You notice the gap in time to act. Four possible actions are offered (typical competing shapes on this theme):
- Stop to explain implications and offer help — calmly explain why the missed paperwork matters for the next shift and the people affected, ask whether they need support, and leave them responsible for completing it (with proportionate help if needed).
- Tell them it is purely their responsibility — a cold or scolding reminder with little explanation and no offer of help, then walk away.
- Inform a supervisor immediately as the first and only step — escalate the forgetfulness pattern before any supportive attempt to fix the current gap when the situation still allows a direct professional conversation.
- Do the write-up yourself — silently complete their paperwork so the handover looks fine and the colleague never has to own the miss.
Your SJT job is always the same: rate each listed action independently on the five-point effectiveness scale for impact as a first response, using only scenario facts.
Rating Logic: What Usually Looks Stronger
Supportive coaching that keeps ownership with the colleague
Actions that explain implications, invite help if needed, and still leave the colleague to complete their work usually map to higher effectiveness bands in teaching terms. Why?
- The shared outcome is protected (handover quality, public-facing continuity, team reliability).
- The colleague learns cause and effect, not only “you are wrong.”
- Ownership stays with the person who missed the task — essential under We take ownership and fair team culture.
- The offer of help shows We support and inspire and emotionally aware practice, especially with a new team member who may still be learning systems.
| Stronger elements often present together | Why they help |
|---|---|
| Clear, factual explanation of impact | Turns a scold into learning; reduces repeat risk |
| Ownership left with colleague | Builds responsibility; does not reward forgetfulness |
| Proportionate offer of help | Supports development without taking over |
| Calm, private, professional tone | Dignity; less defensive reaction |
| Focus on the current gap and better next time | Fixes now without only punishing |
Teaching framework rating for action 1 above: often Effective to Very effective as a first response when the stem allows time to speak and the miss is correctable — because it balances support, accountability, and shared outcomes. Neighbouring positive bands depend on how complete and proportionate the action is on the exact stem wording.
Pattern of forgetfulness does not delete support
Candidates sometimes over-correct when the stem mentions a pattern. A pattern is a warning light, not a licence to humiliate or to skip basic professional support on the immediate task. Effective first responses still often:
- Secure the current shared outcome with the colleague still owning their piece.
- Address the pattern through constructive conversation, clearer checklists, or — if the stem makes clear that informal support has already failed and risk is serious — appropriate escalation.
Escalation can be right when framed as needed; jumping to a supervisor as a pure punitive habit when a direct fix is still open is usually weaker as a first response.
Rating Logic: What Usually Looks Weaker
Pure scolding without help
“It’s your responsibility — deal with it” with no explanation and no support may feel like “high standards.” On impact, it often:
- fails to ensure the paperwork actually gets done well
- increases defensiveness in a new colleague
- misses support and inspire and emotional awareness
- can leave the shared outcome still at risk
Teaching framework: often Slightly effective at best if it creates some pressure to act, or Ineffective if it does not help resolve the gap — and can slide toward Counterproductive if the tone is humiliating or delivered publicly in a way that damages trust.
Immediate punitive escalation without first support (when context allows)
Telling a supervisor as the only first move, when the stem still allows a timely, professional conversation and a fix, can:
- skip collaboration and local ownership
- model “report first, help never” for minor correctable misses
- damage psychological safety without improving the handover
Escalation is not always wrong. It becomes more appropriate when risk is high, the colleague refuses to engage, the pattern has already been addressed without change, or the stem signals that only a supervisor can unlock the resource or authority needed. Rate the action as written against the facts given — not against a private rule that “never tell a supervisor” or “always tell a supervisor.”
Teaching framework for early punitive-only escalation: often Slightly effective to Ineffective as a first response when support and direct ownership are still available; higher if the stem makes clear that risk or prior attempts require it.
Doing the write-up yourself
Silently completing the colleague’s paperwork can look like “team player” behaviour. Impact analysis is harsher:
| Problem | Why it weakens effectiveness |
|---|---|
| Removes ownership | Colleague never practises the skill or feels the consequence |
| Rewards forgetfulness | Pattern is more likely to continue |
| Hides risk | Supervisors and next shift may not know reliability is an issue |
| Your capacity | You may neglect your own work or burn out covering others |
| Integrity of records | Completing work as if they did it can create accuracy and accountability problems depending on how it is framed |
Teaching framework: often Ineffective to Counterproductive — especially if it conceals a repeated problem that affects public-facing or multi-shift work. A limited assist (pair-working while they still complete and sign their part) is different from full takeover.
Worked Rating Table (Teaching Only)
Using the anchor stem, a reasoned independent-rating framework (not an official key) might look like:
| Action shape | Impact reasoning | Framework band (typical) |
|---|---|---|
| Explain implications + offer help + leave ownership | Fixes handover, develops colleague, protects shared outcome | Effective / Very effective |
| Cold “your problem” with no help | May create pressure but weak learning and weak support | Slightly effective / Ineffective |
| Escalate to supervisor first as pure habit | May create record but skips available local fix and support | Often Slightly effective / Ineffective unless stem demands it |
| Do their write-up yourself | Short-term cosmetic fix; removes ownership; rewards pattern | Ineffective / Counterproductive |
Remember independent rating rules: two weak actions can share a low band; you need not force a full 1–5 spread.
Additional Mini-Vignettes (Recognition Practice)
Mini A — Missed shared admin before a public appointment
A colleague forgets to prepare a short briefing note needed before a community meeting you both support. You have ten minutes and some capacity.
| Action idea | Ownership read |
|---|---|
| Help them structure the note quickly while they type and own the content | High — support + ownership |
| Write the whole note alone and never mention the miss | Low — takeover + cover |
| Mock them in front of partners for being “always late” | Low — humiliation; counterproductive culture |
| Refuse all help and hope the meeting fails so managers notice | Low — public service and collaboration fail |
Mini B — Colleague asks you to cover “just this once” again
They have asked three times this week for you to finish their tasks. Today’s ask is small.
Stronger thinking: help if the public or team outcome truly needs it and set a clear boundary that they complete their own work going forward, or agree a fair temporary swap with visibility. Weaker thinking: endless silent covering, or a public dressing-down.
Mini C — You made a similar mistake last month
Empathy helps tone; it does not require you to hide their miss or yours. Ownership includes accurate acknowledgement of problems so learning happens.
Counterproductive Patterns to Recognise Fast
Train yourself to down-rate these when they appear as listed actions:
- Public humiliation of a colleague “to teach a lesson.”
- Gossip without action — talking about the forgetfulness to everyone except the person who needs to fix it.
- Covering up errors so the team looks perfect on paper.
- Favouritism — fixing everything for a friend while refusing basic help to someone you like less.
- Passive collusion — watching a miss harm the next shift and doing nothing.
- Ownership theatre — dramatic blame language with no plan to complete the work.
Decision Checklist for Colleague-Ownership SJT Items
Before you rate each action, ask:
- What shared outcome is at risk (handover, public service, safety of next steps, team reliability)?
- Does this action fix the current gap or only express frustration?
- Does the colleague still own their responsibility, or has the action removed it?
- Is support proportionate (new starter, complexity, time pressure) without becoming permanent rescue?
- Is tone respectful even when standards are firm?
- If escalation appears, is it justified by the stem as a first response, or is it a punitive shortcut?
- Would this response encourage better next behaviour or reward forgetfulness?
Balance sentence to remember
Support without ownership is rescue. Ownership without support is abandonment. Effective team practice holds both.
Use that balance whenever a stem offers coaching, scolding, escalation, or takeover as competing actions. Rate impact, not how “tough” or “nice” the option sounds in isolation.
In a colleague-ownership SJT theme, a new teammate has forgotten shared paperwork and a pattern of forgetfulness has been mentioned. Which first-response shape is generally strongest under CVF-aligned rating logic?
Why is silently doing a colleague’s full write-up often a weaker SJT action even if it “helps the team” in the short term?
A stem allows time for a professional conversation about a correctable missed task. Informing a supervisor as the first and only step is most likely to be weaker when:
Which counterproductive pattern should you generally rate lower in colleague performance scenarios?