The After-Action Report Nobody Reads, & How to Fix It
The AAR Graveyard
Somewhere, deep in a shared drive that nobody has touched since 2021, there is a folder called "After-Action Reports."
It contains forty-seven documents. Thirty-one are named some variation of AAR_Final_v3_ACTUAL.docx. Twelve have never been opened by anyone other than the person who uploaded them. Six were opened once, skimmed for roughly ninety seconds, and closed. This is where most after-action reports go to die.
It's not that the people who wrote them didn't care. They sat down with good intentions, stared at a blank document, and began reconstructing events from memory because the notes were scattered across three apps and a legal pad that's probably under something. By the time the report was finished, it was too late to matter and too long to read. So it got filed. Forgotten. The folder keeps growing. Nothing changes.
Meet Ted, Top AAR Writer
Ted is not necessarily a top performer. He's not the most senior analyst on his team, doesn't have a journalism background, and has no superhuman ability to write under pressure. And yet, every time an incident happens, Ted's after-action report lands in inboxes within 48 hours. Structured. Readable. Specific enough to actually be useful.
His supervisor forwards it upstairs without edits, and the operations team pulls it up in planning meetings two weeks later. People actually read Ted’s reports, because someone always replies during these meetings with either a question, a follow-up, or a "good catch on the section 3 finding."
Where Most AARs Go Wrong
Ted has seen enough bad AARs to understand exactly where they break, and it's almost never the writing.
The first crack appears the moment an incident ends. Everyone debriefs, disperses, and moves straight to the next fire. The report gets added to next week's to-do list. Then the week after that. By the time someone actually opens a blank document, the details that were vivid two weeks ago have softened into something harder to pin down, and the analyst who was closest to the action has already started a new project.
Then there's also a structure problem. Most AARs get written without a template, without an agreed scope, without any shared understanding of what the finished thing should look like. Nobody ever decided who it was actually for — too granular for leadership, too thin for analysts, and too long for anyone trying to get through their inbox before noon. So the writer makes it up as they go, but when the reader opens the document, they sense the absence of a map, and close it.
Ted's First Move: Capture, Don't Compose
While his colleagues are still debriefing, Ted has already opened Indago and started building a Collection. Not writing. Not outlining. Collecting.
Field notes from the team, relevant press coverage, data exports from monitoring feeds, internal memos, timestamped incident logs — everything that touched the event goes into a dedicated Collection built specifically for it. Think of it as a curated evidence file: every source Ted adds is something he's already looked at and decided belongs. Nothing gets in by accident and nothing relevant gets lost in a tab he closed three days ago.
This step takes maybe fifteen minutes and front-loads the quality of everything that follows. Indago's AI drafts only from what's inside the Collection, not from whatever it might find elsewhere. That means every claim in Ted's eventual report traces back to a source he's already reviewed. No hallucinations, no invented citations — just his sources, organized and ready.
By separating gathering from writing, Ted removes the constant interruption of stopping mid-sentence to find a source. By the time he's ready to generate the report, he hasn't written a word, and most of the hard work is already done.
The Template That Does Half the Work
With his sources locked in, Ted does something most analysts don't do: he opens a template before he opens a blank document.
Inside Indago's template library, Ted keeps a purpose-built AAR structure he's refined over several report cycles — event summary up front, structured analysis of what worked and what didn't, impact quantification, corrective actions with names attached. With the architecture already there, Ted doesn't have to decide where anything goes — the template defines purpose, audience, tone, and section logic in advance, so scope creep never gets a foothold. The scaffold holds everything in place; Ted just has to fill it, which he can do quickly.
The Report Writes Itself (Almost)
Ted hits generate. With his Collection loaded and his template selected, he submits the job to Indago's AI, and the draft comes back roughly 75 to 85% complete. Ted's job from here is editorial and analytical. He reads for accuracy, adjusts language where the AI was slightly too confident or not confident enough, and tightens anything that runs long. He adds one or two recommendations that only someone who was physically in the room would know to include — the kind of context that lived in a look exchanged across a table, not in any document.
That last 15% is where Ted's expertise shows up, and he gets to spend it entirely on judgment. The report is finished in under an hour and reads like it took considerably longer.
Why Ted's Reports Always Get Read
Most AARs were written to satisfy a process rather than drive a decision. The implicit message is: I did my job, now you do yours — extract the insight, figure out the implications, determine who owns the follow-up. That's too much to ask of a busy person skimming their inbox on a Tuesday.
Ted’s reports are well-done and arrive quickly, and they don't ask anything of the reader. Every stakeholder who opens one knows immediately what they're looking at: what happened, what it means, what needs to happen next, and whose name is next to each action item.
Your Turn
If your after-action reports are sitting unread in shared drives, arriving too late to matter, or taking so long to write that you've mentally moved on, then take a page out of Ted’s book.
Indago is Ted’s secret weapon, and it can be yours, too. Book a demo and we'll show you what that looks like.