Write Follow-Up Notes That Help a Consultant Researcher

A consultant researcher's inbox fills up with manager updates every week, and most of those emails just repeat the slides from the meeting. The researcher already has the slides. What actually helps is a short note that records the question that was asked, the evidence you promised to send, and the action the researcher agreed to take next. Get this note right and a colleague can read it six months later and understand exactly what happened. Get it wrong and it either adds noise or, worse, creates a written record that overstates where the relationship stands.

Why This Note Usually Goes Wrong

Sales habits creep into consultant relations work without anyone deciding it should happen. A relationship manager spends years writing update emails to prospects and clients, and those emails are built to persuade. Phrases like you loved the presentation or we are clearly the strongest option in this space feel normal in that context. They cause real problems in a note to a research analyst who is evaluating your firm against a defined process and defined criteria.

A consultant researcher reads your note looking for two things. Does it accurately reflect what was said in the room, and can it be handed to a colleague or filed away without a phone call to clarify what you meant. A note that is full of enthusiasm and short on specifics fails both tests. It also puts the researcher in an awkward spot, because if their internal notes say something different from yours, they now have to reconcile two records, and yours looks like the one written to manage perception rather than to inform.

Prepare While the Details Are Still Sharp

Write the note within a few hours of the meeting, before the specifics blur into your general sense of how it went. Reread your own meeting notes rather than relying on memory, and separate three categories of information. What the researcher actually asked. What you or your team agreed to provide, including a date. What happens next in the review process, as the researcher described it, not as you hope it unfolds.

This preparation matters more when the meeting itself was loosely structured. A tight agenda produces a tight note almost automatically, because you already have a list of topics and owners to work from. If your meetings tend to wander, fix that earlier in the process. Build a Useful Agenda for a Consultant Research Refresh walks through how to structure the meeting itself so the note afterward has less work to do.

Before you start writing, decide what you are not going to include. A consultant does not need your full library of white papers, your standard capabilities deck, or a general update on headcount, unless the researcher specifically asked for it. Attaching a broad set of materials because it is available signals that you did not listen closely enough to know what was actually requested.

What to Say in the Note

Open with one factual sentence that states what was discussed, with no interpretation attached. You asked how the team documents changes to its investment process and how research staff can verify those changes is a sentence the researcher can read once and confirm as accurate. It does not need adjectives.

After that sentence, describe only the materials that respond to the request. For each item, name what it is, why it answers the question, and who on your team can address anything left unresolved. If the researcher asked about three topics and you are sending five documents, cut two of them or explain in one line why you included them.

Here is how that plays out in a real exchange. The researcher says, "Our team is reviewing capacity and personnel continuity this quarter, and I want to see documentation before we schedule a site visit." You respond, "I can get you the approved capacity response and current team documentation by Wednesday." The researcher adds, "Our operations group usually has follow up questions after their first pass, so expect another round before this moves further."

Your written note after that meeting should say something close to this. You asked for our approved capacity response and current team documentation ahead of a possible site visit. I will send both by Wednesday. You mentioned that your operations group typically has additional questions after their initial review, and we should expect a second round of requests before any site visit is scheduled.

Notice what that note does not say. It does not say the researcher was impressed, because nothing in the conversation supports that. It does not say a site visit is confirmed, because the researcher described it as something that depends on another team's review. It states the request, the commitment, and the sequence, in that order, and nothing else.

Mistakes to Avoid

A few habits undermine an otherwise solid note. Softening language turns a request into a compliment, and it is worth catching yourself on this one specifically. If you write you loved our process, replace it with you asked for the process documentation. If you write we are a leading option, replace it with you are comparing several approaches. The researcher's own language protects you. Your enthusiasm does not.

Guessing at next steps instead of reporting what the researcher told you is another common slip. A note that says we expect to move to finals soon is a guess unless the researcher said that. State only what was actually said about the process, and if the researcher gave no indication either way, do not fill the gap with optimism.

Missing a deadline you named in the note without saying anything is worse than either of those. If you told the researcher Wednesday and Wednesday arrives without the materials, send an update before the deadline passes, not after. A short note explaining that the documentation will arrive a few days late because of an internal signoff step is far better than silence followed by a late delivery.

Attaching unrelated materials rounds out the list. A capacity update is not the moment to also forward your latest fund commentary, even if it is well written and current. Every extra attachment is one more thing the researcher has to sort through to find the piece that actually matters.

Before you send anything, check names, dates, and commitments against your actual meeting notes rather than your memory of how the meeting felt. A difficult moment in the meeting can also bleed into the tone of a note without you noticing. If a researcher pressed you hard on a risk model or a similar technical point, that tension can show up as either defensiveness or overcorrection afterward. Handling a Consultant's Challenge to a Risk Model covers how to keep that kind of exchange factual in the room, which makes the note much easier to write once the meeting ends.

Practice and Score This Skill

A manager coaching a consultant relations team can turn this into a repeatable drill rather than a one time lecture. Take a real or realistic meeting transcript, have the team member write the note from it, and score the result against a short set of questions. Does the opening sentence state the request without adding interpretation. Does every attached item map to something the researcher actually asked for. Does the note distinguish a confirmed commitment from a possible next step the researcher described. Would a colleague who was not in the meeting understand exactly what happened and what is owed by when.

Run this drill on a range of meeting types, not just the easy ones. A cordial meeting where everything goes well is not the hard case. The hard case is a tense meeting, or one where the researcher raised a concern you were not fully prepared to answer, because that is when the temptation to write a flattering note is strongest.

DealSpeak's Asset Management practice conversations let a consultant relations professional rehearse this exact moment against an AI counterpart that plays the researcher realistically, then get scored on the note that follows. Practicing the meeting and the note together, rather than treating the note as an afterthought, is what makes the coaching stick.

A good follow up note is not a writing exercise. It is evidence that your firm listens carefully and reports accurately, which is exactly what a consultant researcher is evaluating every time they read one. Get the habit right and it quietly becomes one of the strongest signals you send during the entire review process.