Knowledge Manager
.png)
A knowledge manager in an AEC firm owns the institutional memory that proposals are built from: the accuracy of project descriptions, the currency of resumes, the organization of past performance data, and the retrieval systems that make any of it usable under deadline.
Why this role exists separately from proposal coordination
Most AEC marketing teams conflate knowledge management with proposal coordination, and the work suffers for it. A proposal coordinator is working against an RFP deadline; a knowledge manager is working against entropy. Project data goes stale the moment substantial completion is reached, resumes drift from reality as staff take on new project types, and boilerplate narratives accumulate version conflicts across shared drives until no one is sure which paragraph reflects current firm capabilities. The knowledge manager's job is to prevent that drift before a pursuit kicks off, not to catch it during a two-week proposal sprint. Firms that lack a dedicated person in this role typically discover the gap when a shortlist interview falls apart because a highlighted project description contains a scope, dollar value, or client name that no longer matches the record.
What the role looks like inside a pursuit workflow
During go/no-go, the knowledge manager is the person who can answer whether the firm actually has three comparable projects to cite, not just three that sound similar. When an RFP drops, they supply the proposal coordinator with verified project data, current resumes, and any applicable past performance records rather than letting writers pull from whatever they can find in a shared folder. On SF-330 submittals, Section F (example projects) and Section G (key personnel participation) depend entirely on data that was captured and maintained well before the solicitation arrived. In debrief, the knowledge manager is positioned to update records based on client feedback so the next pursuit starts from a better baseline.
The misconception that this is a librarian function
Knowledge management in AEC is active, not archival. It requires negotiating with project managers and principals who do not prioritize data entry, setting standards for what counts as a "complete" project record, and maintaining enough technical fluency to recognize when a description has been genericized into uselessness. Firms running over 50 active project descriptions in a content library without a dedicated owner tend to find that retrieval fails not because content is missing but because tagging is inconsistent and no one has adjudicated duplicates. Kantiv surfaces verified project data, resumes, and client history during active pursuits by connecting to the maintained records a knowledge manager keeps current, which means the quality of what the platform surfaces is a direct function of how well that role is executed.
Related terms