Proposal Management Knowledge Capture: When Expertise Walks Out the Door

Your proposal manager has announced her retirement. She has been with the company for years and has managed hundreds of bids. The good news is that she’s kept the proposal library up to date. The templates, previous submissions, CRM records and folders full of resumes, case studies and company information have all been carefully organized and tagged.

Everything seems to be in order. Then the questions start.

• Which of those case studies are best for this opportunity?
• Who really needs to review the cybersecurity response?
• Which SME knows the history behind that unusual client requirement?

This is when the sinking feeling sets in that so much of your proposal operation was never really about the files.

Our clients have asked us about maintaining continuity when experienced proposal professionals retire, leave the company, change roles or get promoted. The underlying risk is all the same: when one person becomes the keeper of company knowledge, a lot can walk out the door with them.

And this is becoming harder to ignore as more experienced employees retire. Organizations can replace headcount. Replacing years of operational knowledge, institutional memory and hard-earned judgment is considerably more difficult.

Start With the Basics

Getting that information out of personal folders, inboxes and individual memory is the obvious first step. (It’s also the easier part.)

Before trying to capture years of experience and judgment, start with the information that should already be documented and accessible to the wider team. In many organizations, some of this exists, but not necessarily in a form that is easy to find or trust.

Writing for APMP’s Winning the Business, Jackie Mastropolo points to a well-organized, current content library as a way to preserve vetted answers to recurring customer questions and reduce the amount of proposal content that has to be recreated from scratch. She also recommends regular lessons-learned reviews to capture what worked and what should change next time.

You don’t need to preserve everything your proposal manager has accumulated over the years. What matters is creating a content library that the team can rely on: the current version, a clear owner, and something people can find when they need it.

Capture the Judgment Behind the Answer

Harvard Business School professor emerita, Dorothy Leonard, and Walter Swap use the term “deep smarts” to describe the intuition, judgment and knowledge, both explicit and tacit, that experienced employees accumulate over time. Much of it becomes second nature, which makes it a challenge to transfer when someone leaves.

Proposal professionals build that kind of knowledge too, and it shows up first in the content itself. A content library might hold several relevant case studies, for example, but it can’t always tell you which one will resonate with a particular buyer. A newer proposal professional may instinctively reach for the biggest logo. But if the buyer is a smaller, cautious organization worried about becoming a small account among much larger ones, that enterprise reference could work against you. Experience tells you when a client who looks and feels more like them is the stronger choice.

Triage takes judgment too. With experience, you can read an RFP and quickly get a feel for where the real work and risk sit. A newer person might start at question one and work through in order, giving each response roughly equal weight. Experienced proposal managers know that some questions warrant real effort and others don’t.

These decisions can become so automatic that the person making them may not even think of them as decisions anymore.

So don’t limit the handoff to “Where are your files?” Ask why a particular example was chosen, or which content someone always double-checks before it goes out. Those answers say far more about how a person works than a folder of finished proposals ever could.

Don’t Forget the People Factor

Proposals are collaborative from start to finish, which means a large share of what an experienced proposal manager knows is knowledge about people.

Knowing how to work with different SMEs and SME groups is, in my experience, one of the biggest things that never quite makes it into a document. Some of it is straightforward. You can record how much lead time people need, how they prefer to receive questions, or which SMEs own particular subjects. But there is another layer that comes from working with people over time.

Every proposal team has its version of this. One SME goes quiet because they missed the group message, so a private reminder two days before the deadline usually works. Another doesn’t appreciate being chased and doesn’t need to be, because they reliably deliver on time. Someone else needs a very specific ask before you’ll get a useful response. Another will need a quiet nudge from their manager before the proposal moves up their priority list. An organizational chart won’t tell you any of that.

And it isn’t simply etiquette. When an experienced person decides not to chase someone unnecessarily, they’re protecting a relationship they’ll need for the next 30 bids, not just this one. A newer person, who's only being measured on getting this one proposal over the line, might happily overdraw on goodwill they don't yet know they'll need next month

Some of this knowledge is hard to document because it probably shouldn’t be documented. You can hardly put “don’t chase that person too often, they’ll get annoyed” in a shared onboarding file.

The same applies when the job involves telling people things they don’t particularly want to hear. An SME’s response needs rewriting. A claim Sales wants to make can’t be substantiated. The opportunity might not be worth pursuing at all. Knowing how to deliver that message without creating unnecessary animosity is part knowledge, part relationship and part experience.

The Files Look Complete When They Aren’t

If you had to hand your RFP responsibilities to someone new tomorrow, this is what you should worry about most: not that there are obvious holes in the files, but that the files look complete when they aren’t.

A successor may reasonably trust what’s there, with no way of knowing about the “you had to be there” context around it: approved content that’s quietly out of date, a reference customer who shouldn’t be called right now, a claim Legal has said not to make again. None of those things necessarily marks itself as risky. Stale content can look every bit as authoritative as good content.

That creates a different kind of knowledge problem. The danger isn’t always that the next person knows too little. It’s that they confidently use something an experienced person would have known to avoid.

Recent changes create the same blind spot. A process may have shifted in a meeting, a Teams conversation or an email thread from months ago and never made it into the formal documentation. Someone who wasn’t there has no reason to know anything changed, so they also have no reason to ask.

Experience, in that sense, can be surprisingly mundane. Sometimes it simply means you happened to be in the room when something changed, or you have built the relationships that cause someone to mention the change in passing, and that’s difficult to recreate from a library alone.

Don't Ask for a 100-Page Manual

When an experienced employee is leaving, asking her to document everything she does sounds sensible. The problem is that much of what you want to capture may not occur to her until she is actually doing the work.

The most effective approach is to work live bids together. Not a training exercise in the abstract, but a real proposal with a real deadline, followed by a conversation about the decisions that were made. Why did we swap that case study? Why did that requirement get extra scrutiny? Why did we bring one SME in early and leave another alone until later? The doing teaches part of it. The debrief is where much of the insights and expertise get transferred.

Past proposals can help too. Pull out a successful bid, one that went badly, or one that became much harder than expected, and talk through what happened. Where did the team get stuck? What did an experienced person notice that others missed? What would they do differently now?

Most documentation records the result: the approved answer, the final version, the process that was followed. Far less of it records the thinking behind those decisions, and that thinking is often the more valuable asset.

The same principle can apply to a content library. A short note explaining not only what a piece of content is, but when and why to use it, will be far more useful to the next person than another finished response.

Test the Handoff Before the Person Leaves

Once you think you have captured the important pieces, let someone else take the lead on a proposal while the experienced manager is still available. Give the successor the same content, tools and process they will have after the handoff. Then watch what happens.

Every “Who should I ask about this?” or “What do we normally do here?” points to another dependency that needs attention.

Watch for the opposite problem too. Newer people often follow what is written down more literally because they can’t yet tell where the exceptions are and may not feel they have the standing to override the approved answer or template.

Experienced people are often more comfortable deviating from the rules because they have seen enough situations to know when the usual answer doesn’t quite fit. That confidence is earned through being right, and occasionally wrong, over many bids.

Not every gap needs another document. Some lead to a clearer ownership rule or a better prompt. Others tell you where mentoring and experience still matter.

Make the Knowledge Easier to Use

An experienced proposal manager usually knows where to look, which version to trust and what matters for the opportunity in front of her. Take that person out of the equation and even a well-stocked content library can suddenly become much harder to navigate. This is one place where AI can help.

Proposal-specific AI can make approved content, experience and source material easier to surface in the context of the work underway. That reduces the dependence on one person remembering where something lives and can bring organizational knowledge closer to the proposal workflow itself.

At QorusDocs, we think this is a more useful measure of AI than simply how quickly it can generate a first draft. If years of company knowledge have been captured and governed properly, AI can help more people actually use it.

But AI inherits the same blind spot as a new employee. Both have access to what was recorded. Neither automatically has the lived context that never made it into the record.

Some of that context can be captured. Rules and prompts can flag situations that deserve attention. Decision trees can support recurring choices. Content can include guidance about when and why to use it. However, reading the buyer, understanding the relationships around the work and sensing when the standard answer is wrong are much harder to reduce to a rule.

The point is not to put every bit of human judgment into a system. It is to capture what reasonably can be captured so the next proposal manager doesn’t have to carry quite as much of the organization around in her head.

Turn Person-Dependent Knowledge into Team Capability

A successful handoff should let another capable person step in without constantly having to find the one person who knows how things truly work.

Before an experienced proposal professional leaves, use the handoff as a stress test.

• Can the team find the right content? Something relevant is a start; what matters is the current, approved version they can fully trust.

• Does someone clearly own it? Important content should have an owner who is responsible for keeping it accurate.

• Does the content say when and why to use it? Where there are several versions of an answer, the note explaining which one fits which buyer is the part that carries the judgment.

• Do you know what in the library is no longer safe to use? Out-of-date content, unhappy references and claims the company has been told not to repeat look exactly like everything else. Flag them, or the next person will find them the hard way.

• Can someone else run a live proposal? Let the successor take the lead while the experienced manager is still available. Every question that sends them back to her reveals another dependency.

• Are lessons from completed proposals making their way back into the system? A stronger answer, newly uncovered experience or a better way of handling a requirement should not disappear into the final submission.

• Can your technology help the next person use what the organization already knows? Good proposal technology, including AI, should make approved content, experience and relevant context easier to find and use. It should reduce dependence on individual memory, not simply create another place to store information.

You’ll never capture every bit of judgment someone has developed over a career. That isn’t a realistic goal.

A better measure is whether the knowledge they leave behind has become easier for the rest of the team to find, understand and build on. If it has, you’ve done more than prepare for one retirement. You’ve made the proposal function less dependent on any one person.

Your best proposal knowledge shouldn’t live in one person’s head. QorusDocs helps teams connect governed content, experience and AI-assisted workflows so the knowledge your organization has built is easier to find, use and carry forward. See how QorusDocs can help your team protect and put its proposal knowledge to work. Get a demo.