Marcus Henry
The Federal Narrative Framework

CCAR

Challenge. Context. Action. Result. The standard storytelling structure for KSAs, ECQs, and leadership applications across the federal government.

At a glance

The shape of a strong CCAR

C
~15%
C
~15%
A
~45%
R
~25%
Challenge Context Action Result

Action gets the most real estate. Reviewers want to see what you did, not the situation that surrounded you. Challenge and Context exist to make the Action legible. Result proves it mattered.

Component breakdown

What each piece is doing

C
Challenge

The problem, opportunity, or situation that required someone to step up. Frame it sharply enough that the reader feels the stakes.

  • What was broken, blocked, or at risk?
  • Why did it matter to the mission?
  • What made it hard or non-obvious?
C
Context

The conditions around the challenge. Your role, the stakeholders, the constraints, the timeline. Just enough scaffolding for the reader to evaluate your judgment.

  • What was your role and authority?
  • Who else was involved?
  • What constraints (time, budget, policy) shaped the decision space?
A
Action

What you personally did. First person, specific verbs, sequenced decisions. This is the heart of the narrative. Surface the judgment call and name the alternative path you didn't take.

  • What did you decide, and why?
  • What did you build, run, change, or escalate?
  • What did you do that someone else might not have?
R
Result

The measurable outcome and the downstream impact. Numbers first when you have them. End on something that proves the work mattered beyond the immediate task.

  • What changed because of what you did?
  • What's the metric, the count, the percentage?
  • What's the second-order impact or the lesson?
Worked example

One story, four moves

Challenge
When the COVID-19 pandemic forced our installation into emergency posture, leadership needed a way to screen every person entering the gate, thousands per day, against a constantly shifting set of public health criteria. The paper-and-clipboard process couldn't keep up, and a single missed flag could put the entire workforce at risk.
Context
I was serving as the communications lead, not a developer, when the Surgeon General's office asked whether we could stand something up in days, not months. We had no procurement runway, no dedicated engineering team, and screening criteria that were changing weekly.
Action
I built a low-code screening app on the platform our team already had licensed, shipped a working prototype in 72 hours, and ran it past medical and security stakeholders in parallel rather than serially. When the criteria shifted, I treated the app as living infrastructure: I updated logic the same day, pushed the change to the gate within an hour, and documented every revision so the medical team could audit it. I chose speed over polish, deliberately, because a clipboard process was the alternative.
Result
The app screened over 40,000 personnel in its first month, eliminated the paper bottleneck at the gate, and was adopted by adjacent commands within the region. The episode taught me that agility, naming and accepting tradeoffs in real time, is itself a leadership competency, not a workaround for the absence of one.
Watch for

Common ways CCARs go sideways

📚
Buried Action

Three paragraphs of Context, one sentence of what you did. Reviewers can't score what they can't find.

👥
"We" instead of "I"

Federal rubrics score individuals. "Our team rolled it out" is invisible. "I led the rollout" is scoreable.

📉
Vague Result

"It went well" earns nothing. "Cut processing time from 14 days to 3" earns the point.

🎯
Wrong competency

A good story attached to the wrong rubric still loses. Map the Action to the competency definition, explicitly.

🔍
No judgment call

If the path was obvious, the story is weak. Name the alternative you rejected and why.

📖
Narrative over signposting

Especially in video prompts: rubrics reward explicit competency naming. Beautiful stories that never say the magic words underscore.

Related framework

CCAR vs STAR

CCAR

Federal applications
CChallenge
CContext
AAction
RResult

Separates the problem (Challenge) from the surrounding conditions (Context). Built for written narratives where reviewers need to evaluate judgment under specific constraints. Standard for KSAs, ECQs, leadership program applications.

STAR

Behavioral interviews
SSituation
TTask
AAction
RResult

Collapses Challenge and Context into a single Situation block, then isolates the specific Task you owned. Better suited to spoken interview answers where the listener needs less scaffolding to follow along.

The bottom line

A good CCAR isn't a story about a thing that happened. It's evidence of judgment, structured so a stranger with a rubric can find the points.