Communication & Direction & Strategy

Situation Report (SITREP)

Create shared awareness

Core Idea

SITREP helps teams create shared situational awareness by giving leaders concise, context-rich updates on what’s happening, what’s been done, what’s next, and what needs attention.

The Map vs. The Terrain by Bill Fournet

Bill writes about Situation Report (SITREP) in chapter 8.

Get the book
Steps
5
Read Time
3min
Full PowerPlay
How Often
As Needed
Audience
Leaders
Managers, Team & Project Leads
01When to Use
  • 01Conditions are changing quickly
  • 02Leaders need frequent updates on an active project or initiative
  • 03A project reaches a point where decisions or escalations may be needed
  • 04Multiple parts of the organization need a shared view of the current situation
  • Data without enough context
  • Leaders unclear on what matters
  • Misinterpretation across teams or levels
  • Slow communication loops during changing conditions
  • Status reports that bury the current situation
02What It Is

The Technique

SITREP creates shared awareness.

Teams can provide plenty of updates and still leave leaders unclear on what’s actually happening. The missing piece is often context: what the information means, what has changed, what matters now, and where attention is needed.

SITREP gives that context a consistent structure. Every update covers the current situation, completed actions, next actions, and any issues, risks, or decisions that need attention. It stays brief, factual, and written for the people who need to use it.

The result is a shared picture of the situation that helps teams communicate faster and reduces misinterpretation.

03How It Works

Step by Step

01
Audience

Know who needs the update

Before you write, identify the primary audience for the SITREP.

As a rule, write the update as if you’re handing it to someone two levels above you. That forces you to include the context a senior leader would need without assuming they know the details.

Ask:
1. What does the stakeholder or customer need to know?
2. What does leadership need to decide?
3. What does the team need to execute?

Use those answers to decide what belongs in the update and how much context to include.

A useful SITREP gives the reader enough context to understand the situation quickly.

02
Situation

Describe what’s happening now

Give the reader the current state in plain language.

Focus on what matters now rather than retelling the history of the project.

Ask:
1. What is the current state?
2. What context does the reader need to interpret the rest of the update?
3. What has changed since the last SITREP?

Keep this section clear and jargon-free.

Context helps the reader understand the meaning of everything that follows.

03
Actions

Show what's done and what's next

Report completed work and upcoming commitments.

For completed actions, list the tasks, milestones, or commitments that matter.

For next actions, specify:

What will be done?
By whom?
By when?

Avoid vague commitments that make it difficult to see progress or accountability.

Specific next actions make the update useful between reporting cycles.

04
Issues

Surface what needs attention

Call out issues, risks, and decisions explicitly.

Issues:
1. What problem exists now?
2. What’s the plan to resolve it?
3. When is resolution expected?

Risks:
1. What could become a problem?
2. How likely is it?
3. What could the impact be?
4. What are you doing about it?

Upcoming Decisions:
1. What decision is needed?
2. What are the alternatives?
3. What does the team recommend?
4. When is the decision required?

If nothing needs attention, say so clearly.

The reader shouldn’t have to hunt for the thing that needs their attention.

05
Discipline

Keep it brief and factual

A SITREP should be fast to absorb.

Aim for two to three minutes verbally and three to five minutes in writing.

Before sending, check:

✓ Is the language factual and neutral?
✓ Is the current situation easy to understand?
✓ Are issues, risks, and decisions explicit?
✓ Does analysis belong somewhere else?
✓ If nothing has changed, can you simply say, “No change since last SITREP”

Keep reporting separate from deeper analysis and strategy discussions.

Clarity is more valuable than verbosity.

04Adapt to Your Situation

Your Context

The core technique stays the same — but how you apply it shifts depending on your role, your team, and your environment.

Use SITREP as the standard update format across active projects rather than reserving it for the most visible work.

Introduce the format at kickoff and work through the first few updates together so everyone understands what belongs in each section.

Once the structure becomes familiar, teams spend less time reinventing updates and leaders spend less time asking for clarification.

Make the format part of your expectations.

If an update is missing context, clear next steps, or an explicit decision or escalation, send it back using the SITREP structure.

That feedback teaches the team what a useful update looks like and improves reporting over time.

05Pitfalls

Watch your footing

Turning the Situation section into project history
Mixing reporting and analysis
Letting frustration or blame enter the tone
Take it with you
Get the PDF + Lead for Tomorrow

The one-page Situation Report (SITREP) PDF reference, plus weekly tools and techniques to help you lead through uncertainty — from Bill's Lead for Tomorrow newsletter.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*

No spam. Unsubscribe anytime. Your information is never sold or shared.

Work With Bill

Want to build this into your leadership team?

PowerPlays are the techniques Bill teaches in his keynotes, workshops, and executive coaching engagements with organizations across the country.

Get the PDF