The APMP BOK 2025 update, decoded

The Association of Proposal Management Professionals (APMP) maintains a public Body of Knowledge — the BOK — at apmp.org/bok. It is the closest thing the proposal profession has to a canonical reference text. Practitioners pursuing APMP certification at Foundation, Practitioner, and Professional levels are graded against the BOK’s competencies. Vendors who write about proposal practice cite it. Curricula at firms that train proposal teams are organized around it.

A revised edition has been positioned for release in 2025. This post is a research-team note on what the BOK is, how it has evolved across prior revisions, and what we can — and cannot — say about the 2025 update from the public surface.

A note on what this post is not. We do not have advance access to the 2025 revision. APMP has not publicly committed to a final structure as of this writing, and we will not invent chapter titles, competency lists, or section numbering. Where we describe the 2025 update, we describe what is publicly visible from APMP’s communications, public webinars given by APMP staff, and references in third-party industry blogs. Where we cannot verify, we say so.

What the BOK is

The APMP BOK is a competency framework. It enumerates the skills, knowledge areas, and processes that define competent proposal practice and groups them into named domains. Historically the domains have included capture management, proposal strategy, content development, project management, business development life cycle, executive summary craft, and post-submission activities — though the exact organization has shifted across revisions.

For a practitioner sitting an APMP certification exam, the BOK is the syllabus. For a proposal team adopting a process, it’s a reference for what’s load-bearing in the discipline and what’s optional. For a proposal-software vendor, it’s a vocabulary check: if a vendor’s marketing material talks about “win themes” and “color-team review” without any reference to the underlying competency frame, the vendor probably doesn’t know the field.

The BOK exists alongside, not in competition with, the Shipley Proposal Guide (now in its seventh edition). Shipley is more prescriptive — a step-by-step methodology with named processes, color-team protocols, and a bid-decision matrix. The BOK is more descriptive — an enumeration of competencies that any methodology, Shipley-included, addresses to varying degrees. Most mature proposal shops use both: Shipley as the operational manual, the BOK as the competency frame their hires are graded against.

How the BOK has evolved

The BOK is not static. APMP has revised it at intervals over its history, with each revision reflecting changes in the profession that practitioners had been working around informally for years.

A few public-facing arcs across prior revisions, drawn from APMP’s published communications and from the third-party training material that tracks these revisions closely:

Expansion from federal-centric to commercial. Early proposal-discipline literature, including the early BOK editions, was heavily oriented to federal contracting — the world of FAR, of SF330s, of the Department of Defense and General Services Administration solicitation conventions. Successive revisions broadened the frame to cover commercial B2B proposals, where the surface area is different (no FAR, but DDQs and security questionnaires; no SF330, but vendor evaluation panels) and the competencies overlap but don’t equate. A practitioner reading a 2010-era BOK and a 2020-era BOK side by side could see the commercial expansion happening.

Recognition of capture as distinct from proposal management. Capture — the work of understanding a buyer before writing begins — has been part of mature proposal practice for decades, but earlier BOK structures sometimes folded capture into proposal management. Later structures broke it out as its own competency domain, which matched what mature proposal shops had already been doing in their org charts.

Greater attention to color-team review beyond pink/red/gold. The Shipley color codes are the dominant nomenclature, but APMP material has at points addressed variant color schemes (green for cost review, white for retrospective) that some shops use in addition to the core three. Across revisions the BOK has tracked this without prescribing a single color code mandate.

Increased attention to content management and reuse. The earliest BOK material treated proposal content largely as bespoke per-pursuit. Later revisions formally acknowledge content libraries, knowledge bases, and structured reuse as competencies in their own right. This is the arc that maps most directly to where the proposal-software category lives today — Loopio, Responsive, RFPIO and their successors are operating in a competency space the BOK had to grow to acknowledge.

These are arcs visible in retrospect. Prior revisions shipped without anyone announcing “we are formally adding capture as a domain”; the formal recognition followed years of practitioner use.

What’s reasonable to expect in 2025

Based on what APMP has publicly signaled — and we are deliberately not citing private channels here — three threads are visible.

AI and grounded-AI competencies. APMP webinars and conference panels in 2024 and 2025 explicitly engaged with generative AI in proposal work. Practitioner attitudes range from enthusiastic adoption to skepticism, and the BOK as a competency frame has had to develop language for AI-assisted drafting that doesn’t either anoint AI as a category-killer or dismiss it as a fad. Where the 2025 BOK lands on this is the change practitioners will notice first. Specifics — chapter names, competency phrasings — we don’t have, and we won’t invent.

Procurement-side and buyer-side competency. A growing share of APMP’s audience works on the procurement-side of the table — running RFPs as buyers, evaluating vendor responses, structuring DDQs. Earlier BOK revisions oriented heavily to vendor-side competencies. The 2025 update is likely to expand buyer-side coverage, given the volume of buyer-side practitioners now in the membership. Again, we don’t have the specifics.

DDQ and security-questionnaire integration. The vendor security questionnaire as a discrete instrument has metastasized in the past five years. Safe Security has reported that some enterprise security teams now process 500-plus questionnaires per year. The BOK’s earlier treatment of “due diligence” was light. A 2025 update that reflects current practice would integrate DDQ response as a first-class competency rather than a footnote within proposal management.

We expect these threads. We don’t claim them as facts.

Where this matters for the practitioner

A few things that follow regardless of the specific 2025 changes.

Certification candidates should track the revision date. APMP certification exams are graded against a specific BOK version. A candidate sitting Foundation in October 2025 against a BOK that revised in mid-2025 is studying a moving target if they’re using older preparation material. APMP publishes the operative version on their certification page; check before booking the exam.

Training programs will lag. Third-party APMP training providers — there are several at varying quality levels — refresh their material on a rolling basis after a BOK revision, not in lockstep. Buyers of APMP training in late 2025 should ask the provider explicitly which BOK version their material has been updated against.

Organizations operating against an internal proposal methodology will need to map. A firm that runs proposal operations against its own playbook usually uses APMP language as a vocabulary layer. When the BOK shifts a competency name or breaks a competency out into multiple domains, the internal playbook may need a corresponding update — not a wholesale rewrite, but an alignment edit so the firm’s ongoing certifications stay coherent.

What we recommend reading

The BOK landing page at apmp.org/bok is the primary source. Read it.

For the methodological complement, the Shipley Proposal Guide remains the most prescriptive operational manual in the field. The current edition (seventh, 2018) is now several years old and reflects a pre-generative-AI proposal world; a successor edition has been informally referenced in APMP and Shipley circles but not, to our knowledge, formally announced as of this writing. We will track that and update.

For the buyer-side perspective, public procurement guides — VisibleThread on government proposal mechanics, the federal acquisition regulation itself — give context the BOK doesn’t fully cover. Procurement-side practitioners have their own canon (the Institute for Supply Management’s CPSM material, the National Institute of Governmental Purchasing) that doesn’t overlap with APMP’s BOK directly but informs it.

The honest part

A research-team post about a body of knowledge that is being revised, by a body we are not part of, is a post written under a constraint we want to be explicit about. We are reading what’s public. We are reading practitioner commentary. We are not pretending to know the contents of a document that hasn’t shipped.

When the 2025 BOK ships and the change list is public, we will write a follow-up that is concrete in places this post is qualitative. The follow-up will cite the specific changes; this one cites the trajectory.

For practitioners deciding what to do in the meantime: keep reading what APMP publishes directly, keep treating the operative published BOK as the syllabus your certifications are graded against, and treat predictions about what’s in the 2025 revision — including ours — as predictions, not facts.