STAR, CAR, SAR — and the structure that beats all of them

Career advice books have been arguing about example structures since the 1970s. STAR is the original — taught in graduate development programmes at IBM and General Electric in the 80s, then absorbed into every recruitment textbook since. CAR came later as a "cleaner" version. SAR is a Civil Service variant. PAR shows up in some private-sector training. SOARL is what you get when consultants get involved.

They're all describing the same underlying thing. Some of them just hide it better.

Here's what's actually being scored — and the structure that works whether the application asks for STAR, CAR, SAR, or just says "give us an example".

What the acronyms are doing

Each acronym is breaking an example into stages, in slightly different ways:

  • STAR — Situation, Task, Action, Result. Splits "Situation" (the context) from "Task" (what specifically needed doing).
  • CAR — Context, Action, Result. Merges Situation and Task into "Context".
  • SAR — Situation, Action, Result. Same as CAR with a different first label.
  • PAR — Problem, Action, Result. Starts with what was wrong.
  • SOAR / SOARL — Situation, Obstacles, Actions, Results, (Learning). Adds an obstacle stage and sometimes a reflection stage.

They're all variants of the same four-part move: set the scene, name what needed doing, describe what you did, give the outcome.

The interesting question isn't which acronym to use. It's which of those four parts actually moves your score.

The two parts that don't matter as much as you think

Most candidates spend most of their writing on Situation and Task — the setup. They explain the organisational context, the team structure, the wider problem facing the department, the strategic implications.

Assessors skim through this. Quickly.

What they're scoring isn't whether you can describe a complex situation. It's whether the situation you've described is sufficient context for them to make sense of the action that follows. That's a much lower bar than candidates assume. Two sentences usually does it. Sometimes one.

The same applies to Task. If the Situation is clear, the Task is usually implied. "The department had three weeks to respond to a Ministerial query covering an area no one in the team had worked on before." That's the Situation and the Task in one sentence. You don't need a separate paragraph saying "I was tasked with...".

The setup should be tight. The reason it should be tight is to leave room for the parts that actually score.

The two parts that move your score

Action. This is where the marking happens. Assessors are scoring how specific, how personal, and how plausible your actions are. They want first-person verbs ("I drafted", "I challenged", "I decided to escalate") not impersonal ones ("It was decided to..."). They want decisions, not activities. They want to see your thinking, not just your doing.

A weak Action section says: "I worked with stakeholders to gather requirements and developed a project plan."

A strong Action section says: "I started by mapping who actually held the decision rights — there were four people listed on the approval flow but only one whose sign-off was load-bearing. I went directly to her, framed the trade-off (cost vs. delivery date), and got a steer in the first 48 hours. Then I built the formal plan back around that constraint."

Same activity. Wildly different scoring.

Result. This is the second place scoring happens. Assessors want outcomes, quantified where possible, and they want the outcome to be yours. "The project was delivered on time" is weak — the project would have been delivered by someone. "We delivered three weeks early because the early sign-off let us parallel-track procurement" is strong — it ties the outcome to the action.

If you can't quantify (timing, cost, scale, satisfaction, retention, whatever), describe a qualitative shift specifically. "The director invited me into the next quarter's planning round" tells the assessor more than "the project was well-received".

The fifth part nobody asks for

The acronym frameworks stop at Result. But the highest-scoring examples — the ones that move you from a 5 to a 6 or 7 in a structured interview — always include a fifth element that none of the acronyms explicitly ask for.

Call it What I Learned, or What I'd Do Differently, or So What.

It's the reflection. One or two sentences after the Result that show the assessor you've thought about the example, not just lived it.

"What surprised me was how much faster decisions moved when I went to the decision-maker directly rather than through the formal route. I've used that pattern since whenever a process feels stuck."

That's not in STAR. It's not in CAR. It's not in SAR. But it's what separates a good example from a memorable one in the assessor's mind. And in any structured scoring rubric that includes a "demonstrates reflection" or "shows judgement" criterion, this is where those points are scored.

The structure that works for everything

So the underlying structure — the one that satisfies STAR, CAR, SAR, and adds the missing fifth element — is:

  1. Context (one or two sentences) — where, when, what was at stake
  2. Action (three to six sentences) — first person, verbs, decisions, your thinking
  3. Outcome (one or two sentences) — quantified or specifically qualitative
  4. Reflection (one sentence) — what you learned or would do differently

That's it. Roughly 60% of your word count should be Action. The Context is short. The Outcome is sharp. The Reflection is one line.

If you use this structure, you'll satisfy any STAR-marker, any CAR-marker, any SAR-marker, and you'll outscore candidates who religiously stuck to one of those acronyms because you've added the fifth element they didn't.

When applications ask explicitly for a specific acronym

Some applications still ask for STAR specifically. Some Civil Service guidance documents still recommend it by name.

When that happens: keep the labels in your head, not on the page. You don't need to write "Situation: …" "Task: …" as headers. Just write the example using the underlying four-plus-one structure above, and the assessor will naturally extract Situation, Task, Action, and Result from your prose. They'll also get the Reflection that the framework didn't ask for, and they'll mark you higher for it.

The acronyms are a teaching tool, not a template. The structure underneath is what scores.