The Recommendation You Gave 4 Months Ago — Find It
Iuri Madeira
The email arrives at 4:30 PM on a Thursday. Your client's VP of Operations writes: "In the meeting back in January, your team recommended a specific approach for restructuring the supply chain team. Can you send me the details? I need it for a board presentation tomorrow."
You were in that meeting. You remember the discussion. You made the recommendation. It was a good one. Now you need to find it.
The problem isn't that you forgot. It's that the recommendation lives somewhere in four months of meeting notes across a client engagement that's generated dozens of documents. And you need to find the old client meeting notes with the exact details before tomorrow morning.
The Notebook Dive
If you're like most consultants, here's what happens next.
You check your calendar for January meetings with this client. There were six. You pull up your notes for each one, scanning for anything about supply chain restructuring. The first three are about a different workstream entirely. The fourth mentions supply chain but in the context of a different recommendation. The fifth — maybe? The discussion was about team structure, but you're not sure this is the meeting.
You check your notebook. Your physical notebook, the one you used in Q1 before switching to a new one in March. You flip through pages, trying to match dates. Your handwriting from that period is particularly rushed because you were staffed on three projects simultaneously.
Forty-five minutes later, you think you've found it. You piece together the recommendation from notes across two meetings — the initial discussion in January and a follow-up in early February where the specifics were refined.
This is not a rare scenario. This is a regular Thursday for most management consultants.
The Math of Lost Time
Let's be conservative. You spend 30 minutes searching for past recommendations, decisions, or discussion details twice a week. That's an hour a week. Four hours a month. Roughly 50 hours a year spent looking for things you already know and already documented.
At consulting billing rates, that's a meaningful number. But the real cost isn't just your time — it's the quality of your response. When finding information is painful, you do one of three things:
- You paraphrase from memory. You give the client an approximate version of what you recommended, missing specific details that might matter.
- You over-invest in searching. You spend an hour being thorough, pulling time from other clients or from your evening.
- You ask a colleague. "Hey, do you remember what we told them about the supply chain team?" Now two people are trying to reconstruct the recommendation from memory.
None of these produce as good an outcome as simply finding the original notes.
What If Finding It Took 30 Seconds?
Imagine instead: you read the VP's email and type into a search bar: "supply chain team restructuring recommendation for Acme Corp."
The search returns the exact meeting notes — January 18th, the discussion about reorganizing the supply chain team into regional pods. It pulls the related follow-up from February 3rd where the team sizing was finalized. The specific recommendation is there: three regional leads, a shared center of excellence, phased rollout starting with North America.
You copy the relevant section, paste it into a reply, and send it at 4:35 PM. Five minutes from email to response, with the exact details your client needs.
This is what semantic search does. It finds notes by meaning — "supply chain restructuring recommendation" — not by the exact keywords you happened to use in January. Even if your notes said "reorg proposal for SC team" or "ops restructuring options," semantic search understands the concept and surfaces the right documents.
Going Further: Asking Questions Across Your Notes
Sometimes you don't just need to find a document — you need to synthesize information from multiple meetings.
"What were all the recommendations we made to Acme Corp during Q1?" isn't answered by a single meeting note. The answer is spread across eight meetings, three internal working sessions, and a draft deliverable.
AI Chat reads across your entire note archive and gives you a synthesized answer: "During Q1, your team made four primary recommendations to Acme Corp: (1) restructure supply chain into regional pods, (2) consolidate procurement under a single VP, (3) implement demand planning software, and (4) renegotiate three key supplier contracts. Sources: Jan 18 meeting, Jan 25 workshop, Feb 3 follow-up, Feb 14 deliverable draft, Mar 2 steering committee."
Each point sourced. Each meeting linked. Assembled in seconds instead of hours.
The Accumulation Problem
This problem gets worse over time, not better. In your first month on an engagement, you have a handful of notes and fresh memory. By month six, you have hundreds of pages and fading recall.
Most consultants develop coping mechanisms:
- Summary documents. Weekly or monthly summaries of key decisions. But writing summaries takes time, and they're only as good as your discipline in creating them.
- Email trails. Sending yourself key decisions by email so you can search your inbox. Functional but fragmented.
- Shared trackers. Decision logs, action item databases. Great in theory, often incomplete in practice because updating them is one more task in a packed day.
These are all manual solutions to what's fundamentally a search problem. If you could search your raw notes by meaning and get accurate results, you wouldn't need the coping mechanisms.
What Changes When Finding Is Easy
When retrieving past work becomes effortless, it changes how you work:
You reference more. In client conversations, you cite specific past discussions with confidence. "In our February workshop, we agreed on three criteria for vendor selection" — and you can pull up the details right there.
You build on previous work. Instead of half-remembering a framework you developed for a previous client, you find it, adapt it, and apply it. Your work compounds.
You respond faster. When the urgent email comes in asking for details from three months ago, you answer in minutes, not hours. The client sees a consultant with an exceptional grasp of the engagement history.
You hand off better. When a colleague takes over part of the engagement, they can search the note archive by meaning instead of depending on your memory for context.
The recommendation you gave four months ago shouldn't be lost in a notebook somewhere. It should be findable in the time it takes to type a question.
Explore how consultants use semantic search and AI chat at our consultant solutions page.