A running estimate turns fresh intelligence, reports, and observations into a continuing view of the operation. It tracks progress, risks, and likely effects against the commander’s intent, helping staff spot when plans need adjustment. Unlike a status snapshot or decision log, it keeps the assessment moving.

Multiple Choice

The continuous assessment of the current situation used to determine if the current operation is proceeding according to the commander's intent?

A running estimate is the ongoing assessment of the current situation used to determine if the operation is moving in line with the commander's intent. It’s a living analysis that continuously incorporates new information—intel, reports, and observations—to update understanding of the environment, progress toward objectives, risks, and potential courses of action. This keeps the plan aligned with what the commander intends and helps decide whether actions are producing the desired effects or if adjustments are needed. A Situation Report, by contrast, provides a snapshot of what is happening at a given moment rather than an integrated, forward-looking assessment tied to intent. An Operational Review is typically a formal, periodic evaluation of operations, not a constant, real-time assessment. A Decision Log records decisions but does not itself drive the current evaluation of whether those decisions are achieving the intended outcomes.

Running Estimates: Keeping CBRN Operations Aligned with Command Intent

Chemical, biological, radiological, and nuclear operations can change quickly. A hazard may shift, new information may arrive, or a protective measure may affect the mission in an unexpected way. In this moving environment, leaders need more than a snapshot of what is happening. They need a continuing assessment that helps them judge whether the operation is still moving toward the commander’s intent. That assessment is called a running estimate.

A running estimate is a staff function, but it is not just paperwork. It is a living analysis of the situation, updated as facts, assumptions, and conditions change. For CBRN staff, it connects field observations and technical information to operational decisions: What has changed? What does it mean for the mission? Are current actions producing the intended effects? And what might need to happen next?

A picture that keeps moving

A situation report can tell a commander what is happening at a particular time. A running estimate goes further. It interprets what is happening and considers what it means for the operation.

Think of the difference between a photograph and a map marked with a route, hazards, and possible detours. The photograph captures a moment. The map helps people understand where they are, where they are going, and what could get in the way. A running estimate is closer to the latter: it links current conditions with objectives, risks, resources, and possible actions.

That matters in CBRN work because information rarely arrives in a neat package. A unit may report an unusual odor, a sensor may register a reading, and a medical team may notice a pattern among casualties. Each item could be important, but none should be treated as a complete explanation by itself. Staff members assess the reliability of the information, compare it with other reporting, and consider how it affects the mission.

The estimate should also distinguish known facts from assumptions and gaps. That distinction is easy to overlook when events move fast. Yet it helps prevent a tentative report from quietly becoming accepted truth. If the evidence is uncertain, the assessment should say so—and identify what information would reduce that uncertainty.

From data to operational meaning

CBRN staff handle information from many sources: hazard reports, detection equipment, intelligence, weather data, medical observations, logistics updates, and reports from units in the field. The running estimate brings those sources together, then frames their operational meaning.

For example, a change in wind direction may affect where a hazard could travel. On its own, that is a weather update. In the estimate, it may become a concern about the safety of a route, the placement of protective resources, or the timing of a movement. The value lies not simply in collecting facts, but in explaining how they relate to the commander’s goals.

This work often draws on core planning considerations:

  • Mission and objectives: What must the force accomplish, and what conditions support success?

  • Current situation: What is known about hazards, friendly forces, the wider environment, and relevant constraints?

  • Resources and capabilities: Are people, equipment, supplies, and technical support available where they are needed?

  • Risks and opportunities: What could disrupt the operation, and what conditions might help it succeed?

  • Information gaps: What remains uncertain, and how could that uncertainty affect a decision?

  • Possible adjustments: What changes to tasks, timing, protection, or priorities may be worth considering?

These points are not a mechanical checklist. They are prompts for analysis. A strong estimate gives the commander a useful view of the situation without burying the central issue under every detail collected by the staff.

The link to commander’s intent

Commander’s intent describes the purpose of an operation and the conditions that define success. It gives staff and subordinate leaders a shared reference point when circumstances shift. A running estimate helps show whether current actions still support that purpose.

Suppose an operation is intended to preserve freedom of movement while reducing exposure to a suspected hazard. New reporting then suggests that a key route carries a greater risk than first understood. The estimate should explain the change, its likely effect on the mission, and any implications for available actions. The commander can then decide whether to adjust the route, change the timing, add protective measures, or accept a stated level of risk.

The estimate does not make the decision for the commander. It supports decision-making by turning scattered information into an understandable assessment. That difference is important: staff work informs command judgment; it does not replace it.

And intent is more than a phrase repeated in a briefing. It provides a test for current actions. If a task is consuming resources but no longer helping achieve the intended outcome, the staff should be able to surface that concern. Sometimes the plan is sound but the situation has changed. Sometimes the situation is stable, yet the plan is not producing the expected effect. Either way, the estimate helps reveal the gap.

A staff product, not a solo effort

In CBRN operations, a useful running estimate depends on coordination. The CBRN staff may have technical expertise, but the full operational picture also involves intelligence, operations, logistics, medical, engineering, communications, and other staff sections. Each may see a different part of the problem.

A detection report, for instance, may matter to the CBRN section, but its consequences can reach much further. Operations may need to consider movement or task priorities. Logistics may need to review protective supplies. Medical personnel may assess possible exposure patterns. Intelligence staff may compare the report with other indicators. Sharing those connections helps ensure the estimate reflects the operation as a whole, not just one technical lane.

Clear communication matters just as much as collaboration. A concise assessment should make it easy to find the main judgment, supporting information, uncertainties, and potential effects. Long technical detail may be necessary in an annex or supporting product, but a commander should not have to hunt through pages of raw data to find the operational point.

It also helps to record when information was received and when an assessment was updated. In a changing situation, a statement that was reasonable an hour ago may no longer be useful. Dates, times, sources, and confidence levels provide context and help staff members track how their understanding has changed.

Updating the estimate without losing the thread

A running estimate is continuous, but that does not mean every line changes constantly. Some conditions remain stable; others shift sharply. Staff members need to update the estimate when new information could affect the mission, risk, resources, or available actions—not merely because another report has arrived.

This calls for judgment. An isolated sensor reading might require confirmation before it changes the assessment. Several independent reports pointing in the same direction may warrant immediate attention. The staff should explain why information matters, how confident it is, and what follow-up is needed.

A decision log serves a different purpose. It records decisions that have been made, often including the time and authority involved. That record is useful, but it does not assess whether the operation remains on course or whether a decision is producing the desired effect. Similarly, a formal operational review may examine performance at set intervals, but it is not a substitute for the ongoing assessment needed during execution. And a situation report remains valuable for communicating current conditions—it simply offers a different kind of product.

These tools work best together. The situation report describes a current picture, the decision log preserves command choices, and the running estimate interprets developments over time. Each has a distinct job.

Why it matters in CBRN operations

CBRN conditions can create uncertainty, pressure, and competing demands. A running estimate gives leaders a disciplined way to keep reassessing the relationship between the situation and the mission. It can reveal that a hazard is moving, a capability is stretched, an assumption no longer holds, or an action is not achieving its intended effect.

The key is to keep the estimate connected to command intent. It should be current enough to reflect meaningful changes, clear enough to support decisions, and honest about what remains unknown. In that sense, a running estimate is less like a static report and more like a compass check: it does not choose the destination, but it helps the team see whether the path still leads where the commander intends to go.