Institutional Knowledge
.png)
Institutional knowledge is the accumulated, firm-specific information that exists across people, past projects, and client relationships: who did what, what worked, what was said in a debrief, and why a team made a particular design or fee decision.
Why It Disappears Faster in AEC Than in Other Industries
AEC firms lose institutional knowledge at an unusually high rate because the work is project-based and the workforce is mobile. A principal who leaves takes client context, pursuit history, and subcontractor relationships that were never written down anywhere retrievable. Proposal files sit in network folders organized by project number, not by client or market sector, so the pattern of what a repeat client actually values stays buried in old PDFs. The average tenure gap between a senior BD director and a mid-level coordinator means that two people working the same account may have almost no shared context about that client's past objections or award criteria.
Where It Lives During a Pursuit
In practice, institutional knowledge surfaces in three places during a live pursuit: the kickoff conversation, the résumé and project sheet pull, and the debrief review if anyone saved it. The kickoff conversation is the most fragile, because it exists only in real-time recall and meeting notes that may never be filed. Teams chasing a two-week RFP window rarely have time to excavate a past SF-330 submission, compare it to the scoring feedback, and apply those findings before the deadline. That gap is where boilerplate replaces verified context.
The Strategic Cost of Not Capturing It
Firms that treat institutional knowledge as a byproduct of project delivery rather than a managed asset repeat the same positioning mistakes across pursuit cycles. A BD director who has watched a firm lose the same agency client three times to the same competitor should be able to pull a documented read on why, not reconstruct it from memory in a kickoff meeting. Capture planning, debrief notes, and project close-out interviews are the standard mechanisms for preserving this context, but they only work if the outputs are findable at pursuit time. Kantiv is built specifically to surface that captured context during active pursuits, so the team starts from what the firm already knows rather than from a blank scope document.
Related terms