Formal After Action Reviews are conducted at the company level and above to capture diverse insights and improve future operations

• A. At the battalion level and above
• B. At the company level and above
• C. At the platoon level and above
• D. During training exercises

Answer: (B)

Learning from the field is more than a good habit in Army training and leader development. It’s a discipline. After Action Reviews, or AARs, are the structured conversations that turn experience into clearer plans for the next time out. If you’ve been wondering when these formal debriefs actually happen, here’s the concise answer you’ll hear in most Army units: formal AARs are typically conducted at the company level and above. That means battalion-level folks and higher often participate, ensuring the discussion captures a wide range of perspectives and the lessons learned can ripple through the bigger team.

Let me explain why the company level is the sweet spot for formal AARs.

• Diversity of perspectives matters. At the company level, you’ve got leaders and specialists from multiple platoons, plus staff officers, drivers, radio operators, medics, and maybe a few attached teammates. A single platoon can identify issues, but adding the view from other platoons and from higher levels helps you see how a problem or a win fits into the larger picture.

• It’s about accountability and dissemination. When you bring in the company commander, the first sergeant, and the platoon leaders, you set a tone that feedback is real and actionable. The insights don’t stay in one room; they move up to impact training priorities, resource allocation, and standard operating procedures across the unit.

• The cadence aligns with leadership development. Company-level AARs are frequent enough to keep momentum, but formal enough to document lessons and track improvements. This cadence supports a culture where learning is observed, discussed, and translated into better performance in the next operation or exercise.

Now, what exactly makes an AAR formal, and how does it differ from more informal debriefs you might have right after a mission or a training event?

• Formal AARs have a defined structure. They typically start with the objective or mission statement, lay out the facts of what happened, move into analysis about why things went the way they did, identify key lessons learned, and close with clear action items and owners. The process is repeatable, so everyone knows what to expect and how to contribute.

• The tone is constructive, not punitive. This is crucial. The aim is improvement, not blame. Leaders model how to accept constructive feedback, acknowledge success, and commit to practical changes.

• The duration is planned. A formal AAR is scheduled, with a facilitator who keeps the discussion on track. The clock matters, because you want to cover data, perspectives, and decisions without turning into a long monologue or a finger-pointing session.

What does a formal AAR look like in practice?

Imagine a company-led live-fire exercise or a complex field maneuver. After the event, a formal AAR is convened with attendees from every platoon, plus key staff and, if needed, higher echelons. The format often follows these lines:

• Setting the stage: Here’s the mission, the commander’s intent, and the criteria for success.

• The facts: What happened, in sequence, using data, times, and observable outcomes. This part stays objective—no judgments yet.

• Analysis and discussion: Why did things happen as they did? What decisions helped, and where did things break down? Different viewpoints surface here, which is exactly why company-level attendance matters.

• Lessons learned: What are the enduring takeaways that apply beyond the current event?

• Recommendations and action plan: Who will fix what by when? What resources are needed? How will success be measured next time?

This structure helps ensure the conversation stays practical and sharable. The insights aren’t confined to the room; they are captured in a formal record that can guide training plans, SOP updates, and leadership development efforts for months to come.

AARs aren’t the only debriefs you’ll see, though. There are informal “hotwash” debriefs right after a segment or a mission, often led by platoon leaders. These quick, on-the-spot discussions are valuable for immediate adjustments but lack the breadth and formal accountability of a company-level AAR. The hotwash is the sprint; the formal AAR is the marathon. Both matter, but they play different roles in sustaining readiness and learning.

Who participates, and why that matters

• Company leadership and staff. The company commander and the first sergeant set the tone, model accountability, and ensure that findings translate into concrete next steps.

• Platoon leaders and key NCOs. They bring the ground truth from the trenches—the day-to-day realities, tough decisions, and the realities of morale and tempo.

• Support and attached disciplines. Depending on the event, you might see engineers, medics, signal specialists, or other teams at the table. Their input helps ensure the lessons are comprehensive and not siloed.

• Higher echelons when appropriate. A Battalion or Brigade representative can help connect the dots to larger training priorities and resource implications.

If you’re a student of AR 350-1 and the leader development framework, you’ll recognize this as a deliberate step to cultivate a culture of continuous improvement. AARs aren’t about policing mistakes; they’re about turning experiences into knowledge that makes future actions more effective. That blend of accountability, transparency, and learning is at the core of professional growth for leaders at every level.

A few practical tips for making formal AARs work

• Come prepared with data and notes. Facts trump opinions in the opening moments. Gather after-action data, objective results, and any after-action notes before the gathering.

• Stay outcome-focused. Tie the discussion to outcomes the unit cares about—speed, accuracy, safety, cohesion, timeliness. When it’s easy to slip into “what went wrong,” steer back to “how do we fix it” with clear owners.

• Facilitate, don’t dominate. A good facilitator invites quiet voices to speak up and ensures loud voices don’t drown out others. The goal is a balanced, thorough picture.

• Document clear next steps. Every recommendation should map to an owner and a deadline. Without accountability, even the best AAR fades away.

• Link to learning and development. Translate lessons into improved training objectives, updated SOPs, or leadership development activities. The value isn’t just for the moment; it expands the unit’s capability over time.

Common misperceptions, cleared up

• AARs are not blame sessions. They’re learning conversations aimed at improvement. As soon as you frame it as a blame game, you shut down honest discussion.

• If it happens at platoon level, is it “unofficial”? A platoon-level debrief can be invaluable for quick feedback, but formal, documented AARs are typically reserved for company level and above to ensure consistency and reach.

• The purpose isn’t to critique every tiny detail; it’s to identify meaningful patterns, systemic issues, and actionable changes.

Why this matters for Army training and leader development

AR 350-1 anchors a culture where leaders continuously refine their approach—how they plan, how they lead, and how they learn. AARs play a pivotal role in that ecosystem. They give leaders from squad to company a structured way to reflect, to share insights, and to mobilize improvements across the organization. The company level acts as a hub where different parts of the unit converge: the inventory of experiences becomes a single, coherent map for the next operation or exercise.

A short mental model you can carry forward

Think of AARs as a bridge between action and preparation. The bridge starts at the moment a mission or training event ends. The formal AAR spans the space between what happened and what you will do next. The company-level forum is the architectural firm behind that bridge, drawing up the plans so teams can cross smoothly next time.

If you’re navigating Army training and leader development material, you’ll notice this emphasis on structured reflection and cross-unit learning. The lessons aren’t confined to a single event; they are intended to shape decision-making, leadership behavior, and the way teams coordinate under pressure. In a world where situations shift quickly, that kind of learning cadence isn’t optional—it's essential.

To sum it up, formal After Action Reviews are most effective when anchored at the company level and above. Why? Because that level brings the right mix of voices, aligns on accountability, and ensures the insights travel far enough to make a real difference. They are not a one-off critique but a steady practice that strengthens judgment, sharpens leadership, and builds a culture where lessons learned become better still in the field and in the classroom alike.

If you’re curious about the broader framework behind these debriefs, you’ll find AR 350-1 emphasizes training and leader development with an eye toward practical, lived learning. The AAR is a tangible tool in that toolbox—a formal, structured conversation that turns lived experience into clearer, repeatable action. And that, in the end, is how soldiers stay prepared, agile, and ready to lead when it matters most.