3.3 Situational Assessment & Lessons Learned

What Situational Assessment Means for Contracting

FAI’s 1.5 Situational Assessment competency (three exam questions in the published distribution) rewards professionals who can re-frame the problem when reality moves. Contracting plans are hypotheses about market capacity, requirement stability, and risk. When the hypothesis breaks, competent teams update strategy; weak teams double down, hide the variance, or improvise outside authority.

Situational assessment is not endless delay. It is a disciplined loop:

1. Detect material change (mission, market, performance, legal, fiscal)
2. Diagnose impact on cost, schedule, performance, competition, and compliance
3. Decide among continue, adjust, re-solicit, restructure type/strategy, or stop
4. Document and communicate to the acquisition team
5. Capture the lesson so the next effort starts smarter

This loop shows up in pre-award (amendment vs. cancellation), award (discussions vs. award without discussions), and post-award (modification vs. new procurement; cure notice vs. show cause; exercise option vs. recompete).

---

Applying Lessons Learned to Current and Future Contracts

A lesson learned is a validated insight from prior experience that changes future behavior. “We had a rough time on the last radio buy” is a complaint. “The prior SOW omitted key interface tests, which drove three engineering change proposals; add those tests and a government lab validation gate” is a lesson learned.

Sources of lessons in DoD/federal practice

• Prior contract files and modification histories
• Contractor Performance Assessment Reporting (and equivalent past performance systems)
• Program after-action reviews and operational debriefs
• Inspector general, GAO, or internal audit findings (used as risk signals, not as personal attacks)
• Protest decisions that reveal evaluation or documentation weaknesses
• COR surveillance trends and quality escape data

Applying lessons without freezing innovation

Lessons should shape requirements, evaluation factors, CDRLs, incentive structures, and surveillance plans. They should not become unthinking copy-paste of last year’s flawed approach. Situational assessment asks whether the context still matches: same market? same threat? same commerciality?

---

Capturing and Sharing Knowledge

Knowledge that lives only in one specialist’s head is a single point of failure. Capture practices that exam logic respects:

• Decision memoranda that explain non-obvious judgments
• Updated templates (SOW libraries, evaluation factor banks, briefing checklists) when a defect is found
• Debriefs internal to the team after major awards, protests, or terminations — separate from offeror debriefs
• COR handoff packages when appointments change mid-performance
• Closeout notes that flag recurring claim themes or property issues for the next buy

Sharing must respect procurement integrity, source selection sensitivity, and controlled unclassified/controlled information rules. “Share widely” never means leaking proprietary proposal data or pre-decisional source selection information.

Exam cue: When a scenario shows a new specialist repeating a known failure mode, the best answer often includes consulting historical file data and team knowledge before releasing the solicitation or directing a contractor.

---

Aligning Management with Organization Vision and Mission

Tactical contracting actions can drift from strategic purpose. Situational assessment reconnects them.

Examples of alignment questions:

• Does this modification still support the validated capability the program exists to deliver?
• Is a short-term sole-source convenience undermining a long-term industrial base or small business objective the organization adopted?
• Does aggressive de-scoping “save” cost while destroying the performance outcome leadership actually needs?
• Are we exercising an option because it is easy, or because it remains the best value path for the mission?

Vision/mission alignment does not override statute. It prioritizes which compliant options advance the enterprise. When mission and a preferred vendor narrative conflict, mission plus compliance wins.

---

After-Action Thinking (Before the After-Action Report)

After-action thinking is a habit during the work, not only a meeting at the end. During a live procurement, ask:

• What assumption did we make that is now shaky?
• What early signal (industry questions, thin proposal quality, COR concerns) are we ignoring?
• If this becomes a protest or claim file, what will look indefensible?

A simple after-action frame used by high-performing teams:

On CON 3990V, answers that reflect this frame beat answers that only punish a person or “try harder” without changing the system.

---

Using Past Performance and Historical Data

Past performance is both an evaluation tool (pre-award) and a management sensor (post-award).

Pre-award uses

• Assessing confidence that an offeror will perform
• Structuring relevance comparisons (scope, magnitude, complexity)
• Informing responsibility-related risk (with proper processes)
• Calibrating surveillance needs if a riskier performer is selected under a tradeoff

Historical price and demand data

• Supports price analysis and IGCE credibility
• Reveals quantity breaks, seasonality, and monopoly pricing patterns
• Helps detect anomalies that warrant deeper analysis

Post-award performance data

• Feeds CPARS-quality narratives with evidence
• Triggers cure paths before terminal failure
• Informs option exercise and future acquisition strategy

Caution: Past performance is not destiny. Markets change; companies reorganize; corrective action can be real. Situational assessment weighs recent, relevant evidence and documented improvement — it does not cling to a five-year-old reputation when new facts contradict it.

---

Closed-Book Scenarios: When Facts Change Mid-Procurement

These patterns are classic for situational assessment items woven through the exam.

Pattern A — Requirement change after solicitation release

Facts: Draft SOW assumed one interface standard; cyber authority issues a new mandatory standard mid-RFP. Assessment: Continuing unchanged may produce unawardable or noncompliant solutions. Typical sound moves: Evaluate whether an amendment can preserve competition fairness; consider extending dates; if change is fundamental, assess cancellation and re-solicitation. Document the change driver and fairness analysis. Coordinate with PM and legal as needed.

Pattern B — Market reality contradicts acquisition plan

Facts: Plan assumed five offerors; only one responds; prices look high. Assessment: Competition assumptions failed. Typical sound moves: Analyze why (unduly restrictive specs? short response window? poor publicizing?). Consider amending to broaden competition, revisiting commerciality, or documenting limited-source realities honestly — not inventing competition that did not occur.

Pattern C — Funding shock

Facts: Partial-year funds only; full award as planned is impossible. Assessment: Strategy must match fiscal reality. Typical sound moves: Restructure CLINs/phasing if permitted, delay, or cancel; do not award without proper funds. Fiscal law constraints beat optimism.

Pattern D — Performance collapse post-award

Facts: Critical milestones missed; COR reports quality escapes; contractor cites Government delays. Assessment: Separate Government-caused delay from contractor default risk; preserve rights. Typical sound moves: Document; engage CO-led contractual remedies; avoid COR “helpful” scope rewrites; consider bilateral schedule relief only with consideration and authority; escalate disputes early.

Pattern E — Ethics or integrity signal appears

Facts: Evaluator receives gift offer; or OCI emerges late. Assessment: Integrity issues reframe everything. Typical sound moves: Stop, report through proper channels, quarantine tainted inputs, follow FAR Part 3/standards of conduct processes. Mission urgency does not authorize silence.

---

Integrating Assessment with Roles and Business Acumen

Situational assessment is where earlier chapter skills combine:

• Roles: Who may cancel, amend, modify, terminate, or settle? (Usually CO authority, with required concurrences.)
• Business acumen: Which option best balances mission value against risk and cost given new facts?
• Documentation: What record shows the old plan was reasonable at the time and the new plan is reasonable now?

Sunk-cost bias is the enemy: “We already spent three months on this RFP” is not a legal or business reason to award a defective requirement. Conversely, panic cancellation without analysis can waste competition and delay the mission. Assessment is the middle path: facts first, authority second, mission-aligned options third, file always.

---

Exam-Day Checklist for Situational Items

When a CON 3990V stem includes “however,” “subsequently,” “after release,” or “during performance,” slow down:

1. Underline the changed fact
2. Ask what assumption broke
3. Identify authority limits (warrant, appointment, fiscal, competition rules)
4. Eliminate answers that rely on informal direction or ignoring the change
5. Prefer answers that reassess, document, and choose a compliant adjustment
6. If lessons-learned language appears, pick the option that applies the lesson, not merely archives it

Memory hook: Detect → Diagnose → Decide → Document → Disseminate. That five-step rhythm is situational assessment in one line — and it is how contracting professionals protect both the mission and the public trust when the world refuses to stay still.