Someone asks who approved a decision from a few months back. The person who made the call has switched teams, the chat thread is buried, and the doc just says "approved" with no name. You need a real answer, not a guess. Here is how to rebuild the approval trail from what you already have.
Why the trail goes cold
Approvals rarely happen in one clean place. A decision gets proposed in a doc, debated in chat, blessed in a meeting, and recorded (if at all) somewhere else. Each step lives in a different tool. Months later, no single place holds the whole story, so the answer feels lost even though every piece still exists.
The good news: approval leaves marks. Your job is to collect the marks in order and let them point at a person.
Where the marks usually hide
Before you start searching, it helps to know the handful of places approval tends to leave a trace. You are looking for the moment someone with authority said yes, and that moment almost always lands in one of these:
- A reaction or short reply in chat. A thumbs up from the right person on the right message is a real yes, with a timestamp attached.
- A comment on the doc. Doc tools keep comment history even after threads are resolved. An "approved, go ahead" comment is often still there if you reopen resolved threads.
- The meeting where debate stopped. Notes, a recording, or even the calendar invite tell you who was in the room when the call closed.
- The system that enforces the decision. A merge, a deploy, a paid invoice, a signed contract. These carry an approver and a time by design, and they are the hardest to fake or misremember.
Knowing these ahead of time keeps you from wandering. You are not reading everything. You are checking four specific kinds of place.
Start from the decision, not the person
Do not begin by asking around who approved it. Begin with the decision itself, stated in one sentence. What exactly was decided, and roughly when? A tight description keeps your search narrow. "We moved the launch to April" is searchable. "The launch thing" is not.
Once you can name the decision and its rough date, you have the two anchors every later step needs.
Rebuild the trail step by step
Work through these in order. Stop as soon as you have a clear name and a source you can show someone.
- Find where it was recorded. Search your doc tool and ticket system for the decision in plain words. The record may already name an approver. If it does, you still verify, but now you have a lead.
- Search chat around the date. Use the rough date to narrow the channel. Look for the moment the debate stopped and someone said a version of "yes, do it." That message, with its author and timestamp, is often the approval itself.
- Check the meeting where it closed. If the decision closed in a meeting, the calendar invite gives you the attendees, and the notes may name who signed off. The person who ran the meeting is a strong lead when the notes are thin.
- Follow the artifact. Code merges, budget sign-offs, and contracts carry their own approver fields. A merged pull request, an approved invoice, or a signed order names a person and a time you can trust.
- Ask one person, with evidence in hand. If you still need confirmation, go to the most likely approver with what you found: "This thread from March 9 looks like your sign-off, can you confirm?" A specific question gets a fast, reliable answer. An open question ("who approved this?") gets a shrug.
What actually counts as approval
Not every "sounds good" is an approval. Before you write a name down, be honest about what you found. Real approval has three parts: the right person, a clear yes, and the authority to give it. A teammate cheering in chat is not the same as the budget owner agreeing to spend.
If the person who said yes did not hold the authority, you have found agreement, not approval. Note both, and note the gap. That gap is often the real reason a decision later fell apart.
When you truly cannot find one
Sometimes there is no approval to find, because no one ever gave one. That is a real answer, and an important one. Do not paper over it by picking the most senior name in the thread and hoping. Write down what you actually found: the decision was made, here is who made it, and there is no record that anyone with authority signed off.
An honest "no approval on record" is more useful than a confident guess, because it tells the team something true about how the call happened. It may explain why the decision is being questioned now. And it points at the fix: the next decision like this one should route through a named approver before it moves, not after someone asks.
Write it down so you never do this again
Once you have the answer, spend two minutes closing the loop. Add the approver's name, the date, and a link to the proof, right where the decision lives. The next person who asks should find it in one place, not repeat your whole search.
Better still, capture the approver at decision time going forward. A single field ("approved by, on this date, see link") turns a future investigation into a five second lookup.
How StandIn fits
Most of this work is reconstruction: piecing together an answer that no one wrote down clearly. StandIn cuts the reconstruction out. You write one short brief at the end of your day, including the calls you made and who signed off, and while you are away it answers your teammates from that record, with a source under each answer. When the record does not say who approved something, it says so plainly instead of guessing. The trail stays warm because it was written down the day it happened.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.