Skip to content
EMPOBase
en

How to write a situation report (SitRep) that decision-makers read

By the EMPOBase team · · 4 min read

Short answer

A good SitRep is short, uses the same structure every time, and starts with the key point. Say what has changed since the last report, what you know and what you do not, what you are doing, and what decision or help you need and by when. Separate facts from judgement, give a time stamp, and keep it to one or two pages.

Key points

  • Start with the key message and the decision you need.
  • Use the same headings every time so readers know where to look.
  • Separate confirmed facts from estimates and opinions.
  • Time-stamp the report and state the period and the source.

What is a SitRep for?

A situation report, or SitRep, tells decision-makers what is happening, what you are doing about it, and what you need. It is not a diary. The reader may be a country director, a coordinator, a donor or a cluster lead. They often have minutes, not hours, and many reports to read.

A SitRep succeeds when the reader can act on it after one pass.

Different readers need different things. A coordinator wants gaps and requests. A donor wants to know that you are in control, and whether anything affects the grant. A director wants decisions and risks. Write for the main reader and keep a short list of other readers, so that you know what to leave out of the main text.

What structure works?

Use one structure for every SitRep so readers learn where to look. A common order:

  1. Key message. Two or three lines: the most important point and any decision needed.
  2. What changed. New events since the last report.
  3. Needs and gaps. What people need, and what is not being met.
  4. Response. What your team did and plans to do.
  5. Constraints. Access, security, supplies, funding.
  6. Next steps and requests. Who must do what, by when.
  7. Contact and time stamp. Who wrote it, for what period, and when.

Here is a short sample of a key message and a first section, for style only: “Key message: Access to the north site is closed since Tuesday after flooding. We need approval by Friday to hire a boat. What changed: The main road was closed on Tuesday; two health sessions were postponed; no injuries reported.” Notice the short sentences, the date, and the direct request.

Add a small table of numbers if you must show several figures, with the period and source in the header, instead of long sentences full of digits.

How do you write the key message?

Write it last, put it first. It should work alone. Compare:

  • Weak: “This week there were several developments in the district.”
  • Better: “Flooding closed the main road on Tuesday. Two sites have had no deliveries for three days. We need approval by Friday to hire a boat.”

A reader who stops after the first paragraph should still know what to do.

How do you separate fact from judgement?

Decision-makers need to know how sure you are. Use clear words:

  • Confirmed: you or a reliable source saw it directly. Name the source.
  • Reported: someone told you, and you have not checked.
  • Estimated: your calculation, with the basis.
  • Assessment: your opinion or forecast; say it is one.

Give each number a date and a source. Say how you counted. Our article on reach totals and double counting explains why counts need a note.

A short habit helps: before you send, read each number and ask, “Who told me, and when?” If you cannot answer, mark it as reported or estimated, or take it out. Readers forgive uncertainty that is marked. They rarely forgive a figure that turns out to be wrong after a decision was made on it.

What mistakes make SitReps useless?

  • Burying the point. A long history comes before the news.
  • Changing the format. Readers waste time finding the same item.
  • Mixing old and new. Readers cannot tell what changed.
  • No ask. The report describes problems but requests nothing.
  • False certainty. Estimates are presented as facts.
  • Sensitive details. Names of people at risk or survivors of abuse do not belong in a widely shared report. Check your organization’s data and safeguarding rules first.

How do you make the habit stick?

Agree a template, a schedule and a recipient list. Have field staff write short SitReps from the start, not just in a crisis. Review a few each quarter to see whether they gave decision-makers what they needed. Ask readers for feedback, and cut any section nobody reads.

Practise on small events. A team that writes a short SitRep after a routine distribution will find it easy in a crisis. Rotate the writer among staff, so that more than one person can do it when someone is sick or away.

Keep every SitRep in one place, in date order. A series of reports shows trends that one report cannot, and later helps with donor reports and lessons.

Where EMPOBase fits

In EMPOBase, Field reporting includes SitReps, so teams use the same format and the reader finds all reports in one place. The AI assistant can draft SitReps from project information; you should read and correct the draft before sending. Field reporting works online only, and a submitted SitRep does not become an approved indicator result. See the field-to-results workflow for how reports and data relate.

Questions people ask

How long should a SitRep be?

One or two pages for most situations. If the reader needs more, link to an annex. A long report that arrives late helps nobody.

How often should SitReps be sent?

As often as the situation needs, and agreed in advance. In a fast emergency that may be daily; in a stable period, weekly or monthly.

What if you do not have the numbers yet?

Say so. Give a range or a best estimate, mark it as an estimate, and state when you expect firm figures. A clear gap is better than a number that later changes without notice.