Lessons Learned in Procurement

Lessons learned are the institutional memory of the acquisition system. Without systematic capture and application of procurement experience, each contracting office repeats the mistakes of predecessors and forfeits the efficiency gains that could flow from prior successes. Lessons learned programs are required by DoD policy and recommended by OMB guidance across the civilian acquisition community.

What are Lessons Learned in Procurement?

Lessons learned in procurement capture knowledge at multiple stages of the acquisition lifecycle:

• Pre-award lessons: What market research approaches were effective? Which solicitation formats and evaluation structures worked well for the commodity or service type? Were proposal instructions clear enough to produce competitive proposals?
• Source selection lessons: Were evaluation criteria weighted appropriately? Did offerors understand what the government valued? Were evaluation timelines realistic?
• Contract administration lessons: Which contract types managed risk effectively for this type of work? Were performance metrics clear and measurable? How effective were incentive provisions?
• Close-out lessons: Were acceptance criteria clear? Were disputes resolved efficiently? What would have made transition to the next contract smoother?

DoD components are required by DoD Instruction 5000.02 and service-specific guidance to capture lessons learned at program milestones and major acquisition events. The DoD Lessons Learned Management System (LLMS) and service-specific portals collect and share acquisition lessons across the enterprise.

Civilian agencies participate in the Acquisition Gateway's lessons learned repository and contribute to OMB's strategic sourcing knowledge base. The Federal Acquisition Institute (FAI) also maintains resources for civilian agency contracting officers.

For contractors, understanding common government lessons learned in their customer agencies' contracting history provides competitive intelligence: agencies that have previously had proposals fail to address mission context, had cost growth on certain contract types, or struggled with vague performance metrics are likely to adjust their solicitations based on those experiences.

Why lessons learned matter for government contractors

Contractors who systematically capture lessons from their own proposal processes, contract performances, and close-out experiences continuously improve their operations. Contractors who track government-published acquisition reviews and lessons learned (from Inspector General reports, GAO decisions, and program office assessments) better anticipate government preferences and avoid approaches that have caused problems for previous contractors.

Example

After a large IT modernization program experiences significant cost growth and schedule delays, the DoD IG conducts an assessment and publishes findings. Key lessons: the solicitation's requirements were too prescriptive, limiting innovative technical approaches; the evaluation criteria underweighted past performance; and the contract's fixed-price structure was inappropriate for a development effort with high technical risk. Future solicitations for similar programs incorporate these lessons: performance-based requirements, heavier past performance weighting, and cost-plus contract types for development phases.

Frequently Asked Questions

Are government lessons learned documents publicly available?

Many lessons learned documents are releasable and can be found through the DoD Lessons Learned Management System (public portal at lessons.dau.edu), Inspector General reports, GAO bid protest decisions, and after-action reviews published by contracting organizations. Some lessons learned from classified programs are not publicly released.

How can contractors formally contribute to government lessons learned?

Contractors can contribute to government lessons learned by participating in contractor feedback sessions that some agencies conduct after source selections, by responding to industry engagement requests, and by submitting formal past performance information that documents what worked and what did not in contract execution.

What is the difference between a lessons learned report and an after-action review?

An after-action review (AAR) is a structured discussion conducted immediately after an event (such as completing a major contract phase or source selection) with the participants. A lessons learned report is a more formal document that synthesizes findings from one or more AARs into sharable knowledge that can inform future actions. AARs feed into lessons learned reports.

How do contractors use lessons learned to improve their proposals?

Contractors who monitor GAO bid protest decisions learn what evaluation deficiencies result in protests, what source selection approaches have been found legally deficient, and what technical evaluation standards agencies must meet. This information directly improves proposal strategy by revealing which evaluation arguments the GAO has found persuasive in past protests.