The 72-Hour Post-Earnings Triage Plan for One-Person IR Teams
September 7, 2026
4 minutes reading time
You don’t need a full IR department to run a serious post-earnings process. You need 72 disciplined hours and a repeatable checklist that tells you exactly what to mine, who to brief, and which investors to call back first.
The mistake most lean IR teams make is treating earnings as an event. The better model is triage: a short, standing workflow that turns a noisy quarter into a ranked action list before the next week starts.
What the first 72 hours are for
The goal is not to explain everything immediately. The goal is to separate signal from noise while the questions, reactions, and trading patterns are still fresh.
For a one-person IR team, that means three jobs:
Identify what changed in the market’s read of the quarter.
Separate the few questions that need management input from the many that do not.
Document follow-up so the same issues do not resurface in the next cycle.
If you try to do all of that ad hoc, you end up reacting to whoever emails first. Triage gives you a defensible order.
Day 1: capture the raw inputs
Within the first day, pull together the materials that define how the quarter was heard, not just how it was written.
Transcript or call notes, with repeated questions flagged.
Trading and volume reaction, especially the first session and the first week.
Inbound questions from shareholders, analysts, and internal stakeholders.
Any language from management that confused listeners or invited follow-up.
This is where many teams lose time. They know the call “went fine,” but they never convert that impression into structured notes. A simple tagging system is enough: revenue, margin, guidance, liquidity, capital allocation, regulation, customer concentration, and anything else that drove the most attention.
Day 2: rank what actually matters
Not every question deserves a management callback. Rank issues by business importance, investor concentration, and repetition.
A useful filter is:
Does this affect the core investment case?
Did multiple investors ask the same thing?
Did management answer it cleanly the first time?
Would a follow-up reduce confusion or create more of it?
That last question matters. Some follow-ups are useful because they close a gap. Others are a trap because they turn a small ambiguity into a larger conversation. The point of triage is not to answer everything; it is to avoid amplifying the wrong things.
Day 3: brief management with a decision list
By the third day, IR should not be sending a long recap. It should be sending a short decision memo.
Keep it concrete:
What the market appears to believe about the quarter.
Which questions need clarification in the next external touchpoint.
Which investors deserve direct callbacks.
What will be tracked until the next earnings cycle.
That format helps management see that IR is not just relaying noise. It is managing the company’s post-earnings memory.
Where the workflow breaks down
The common failure is not lack of effort. It is lack of order. Solo IR teams often keep the notes, the follow-ups, and the investor history in separate places, which makes every quarter feel like starting over.
This is where a centralized workflow earns its keep. FiskLabs call analytics and investor CRM tools can help by centralizing transcript tagging, question logging, and follow-up tracking so the next 72-hour review starts from a clean record instead of scattered files.
What good looks like
A strong post-earnings process produces a few visible outcomes:
Management gets a short list, not a transcript dump.
Investor callbacks are prioritized by importance, not by inbox order.
Recurring questions are tracked across quarters.
IR can show what changed in sentiment, attention, and follow-up needs.
That is the real value of a triage plan. It does not make earnings quieter. It makes them usable.
If your team is small, the answer is not to add more commentary after every quarter. It is to build a disciplined 72-hour habit that turns chaos into a working list and keeps your next earnings call from solving the same problems twice.
