5.3 Communication and Documentation Best Practices

Communication and Documentation Are How Contracting Becomes Defensible

FAI blueprint row 1.7 Communication and Documentation (six questions) rewards professionals who can move information accurately among people and into the contract file. On CON 3990V, you will repeatedly face choices between a clever verbal fix and a slower written, authorized path. The exam’s steady preference is clear: communicate early, write plainly, file completely, and keep official channels clean.

Documentation is not bureaucracy for its own sake. It is how a public organization proves fair treatment of offerors, justifies prices, shows authority for obligations, and enables a successor CO to administer the contract without folklore.

---

Early and Frequent Communication

Most acquisition failures are communication failures that arrive late wearing a FAR costume.

Pre-award communication that pays for itself

• Internal: PM, technical, contracting, legal, and finance align on need, constraints, and evaluation logic before the solicitation freezes bad assumptions
• Market: RFIs, draft solicitations, and industry days reduce unanswerable questions and unrealistic requirements
• Team: Evaluation teams train to the factors; CORs help shape surveillance-relevant CDRLs early

Award-phase communication discipline

• Exchanges with offerors follow the chosen procedure (for example, clarifications vs. discussions under FAR Part 15 concepts)
• Technical questions route through contracting channels so all competitors receive fair treatment when fairness requires it
• Negotiation objectives and results are shared with the decision authority, not trapped in private side chats

Post-award communication cadence

• Kickoff meetings establish CO/COR authorities and invoice/surveillance rhythms
• Performance issues are raised early with facts, not stored for a surprise CPARS ambush
• Potential changes are flagged before costs accumulate under ambiguous direction

Exam instinct: If a scenario shows avoidable surprise, look for the answer that would have used earlier structured communication.

---

Unambiguous Written Documentation

Spoken agreement is fragile. Written documentation should be:

1. Clear — a reader who was not in the meeting can understand the decision
2. Complete enough — who decided, what was decided, key facts, alternatives, risks
3. Consistent — matches the solicitation, contract, and prior file entries
4. Timely — contemporaneous notes beat reconstructed memory after a dispute
5. Authorized — signed/approved by the person with authority when approval is required

Ambiguity is a cost driver. Compare:

• Weak: “Contractor will support as needed for the exercise.”
• Stronger: “Contractor shall provide 4 on-site network engineers, 0600–1800 local, during Exercise BLUE from 1–15 Sep 2026, at Site X, in accordance with PWS §3.2.”

The same discipline applies to internal decision memos. “We went with Option B because it felt right” is not business documentation. “We selected Option B because market research showed three capable sources, IGCE variance was within X, and schedule risk of Option A exceeded mission need date” is documentation.

---

File Documentation Standards

The contract file is the official story of the acquisition. While agency file checklists vary, CON 3990V-level expectations consistently include the idea that files must support:

• Why the acquisition strategy and procedure were chosen
• How competition was sought or exceptions justified
• What was solicited and awarded (and at what price/terms)
• How price/cost was determined fair and reasonable
• Who was authorized to act (warrant, COR appointment, approvals)
• What happened after award (mods, performance issues, invoices, remedies, closeout)

High-value file artifacts (names vary by local process)

• Acquisition plan / strategy documentation (when required)
• Market research results
• Solicitation and amendments
• Abstracts, evaluations, source selection decision documentation
• Responsibility determinations and related checks
• Price negotiation memorandum / business clearance products
• Award documents and funding documents
• COR appointment letters and surveillance records
• Modifications with supporting analysis
• Claims, disputes, and termination records when applicable
• Closeout checklist and final payment support

Closed-book emphasis: You may not remember every form number. You must remember that significant judgments require a retrievable written basis in the file.

---

Emails as Part of the Record

Modern acquisition runs on email and chat-adjacent tools. Treat electronic messages as potential record material, not private conversation.

Implications for exam scenarios:

• A COR email directing new work can be evidence of constructive change even if labeled “FYI”
• A specialist’s email promising award to a vendor can create fairness and authority problems
• Side-channel evaluations in personal email undermine source-selection documentation
• “Delete this after reading” does not remove legal risk and is a red-flag integrity cue

Communication hygiene

• Use official systems and distribution that match records policy
• Prefer precise subject lines and reference contract/solicitation numbers
• Separate discussion drafts from decision messages when possible
• If you make a decision by email, ensure the file captures it (or a formal memo that supersedes the chain)
• Do not negotiate final terms solely in unsearchable private threads that never reach the file

Memory hook: If you would not want the email in a protest record, do not send it — or rewrite it until you would.

---

Documenting Negotiations and Business Decisions

Negotiation documentation is where business acumen becomes auditable. Whether under formal Part 15 discussions or other negotiated actions, strong practice records:

• Pre-negotiation objectives (price, terms, priorities, walk-away points)
• Authorities and participants
• Offers/counteroffers and rationales
• Fact basis for cost/price positions (analysis summary)
• Concessions traded and residual risk accepted
• Final agreement and how it maps to the award document

Business decisions beyond pure price also need a trail:

• Why a contract type was selected
• Why an exception to competition was used (if used)
• Why a higher technically rated proposal was worth a price premium (if tradeoff)
• Why a modification is in scope and represents a good deal for the Government
• Why a remedy/forbearance approach was chosen for a performance failure

On CON 3990V, when an answer option says “document the determination in the contract file,” take it seriously — especially when the alternative is “proceed based on verbal leadership direction alone.”

---

Facilitating Understanding Among Parties

Communication skill is not only writing volume; it is shared understanding.

Among Government teammates

• Translate FAR constraints into mission language for PMs (“here is what we can do by date X lawfully”)
• Translate technical needs into contract language for the file and the contractor
• Confirm read-backs on critical decisions: “We are agreeing that CLIN 0002 delivery moves to 30 Nov via bilateral mod, not by COR email.”

With industry (competition-sensitive)

• Provide the same essential information to competitors when fairness requires it
• Answer questions through amendments when the answer affects the competition
• Keep discussions within the rules of the selected procedure
• Avoid revealing other offerors’ identities, prices, or rankings improperly

With the contractor (post-award)

• Kickoff clarity on authority: who may give technical direction vs. contractual direction
• Use written notices required by the contract for cures, show-cause, stops, etc.
• Put interpretations of ambiguous clauses into documented bilateral understanding when needed
• Ensure surveillance feedback is factual, timely, and linked to contract standards

Facilitation techniques that appear in competent practice (and exam-correct instincts):

• Agendas and decision logs for multi-party meetings
• Single Government voice for contractual direction
• Visual CLIN/schedule summaries for complex mods
• Explicit parking of issues that require legal/finance before “agreement theater”

---

What CON 3990V Emphasizes on a Closed-Book Exam

You will not open a clause book at the testing center. Communication/documentation items often reduce to:

1. Must this be written? (almost always yes for decisions that affect rights, money, or fairness)
2. Who must communicate it? (CO for contractual direction; COR for authorized technical surveillance communication; contracting channel for competitive exchanges)
3. Does the file explain the business judgment? (price reasonableness, tradeoffs, exceptions)
4. Is the communication fair and authorized? (no leaks, no side deals, no unauthorized commitments)
5. Would a successor CO understand what happened? (if not, documentation is incomplete)

High-yield “document this” list for recall

• Source selection decisions and evaluation results at the required level
• Fair and reasonable price determination basis
• Sole-source / limited competition justifications when used
• Negotiation objectives and outcomes for significant negotiations
• COR appointments and significant performance assessments
• Modifications and the analysis supporting price/scope
• Claims, disputes, and termination rationales
• Ethics/integrity incidents and recusal actions when they affect the procurement

High-yield “do not rely on verbal only” list

• Scope changes and new work starts
• Award promises
• Evaluation feedback that could be unequal among competitors
• Funds availability assumptions
• “We’ll ratify later” directions

---

Integrated Scenario: Communication Failure Unmasked

Mid-performance, the contractor invoices for tasks the PWS does not clearly include. The COR says, “I told them on a call to handle it; everyone knew.” There is no mod, no memorandum for record, and the CO first learns of the issue when finance questions the invoice.

Communication/documentation autopsy:

• Early issue elevation failed (CO out of the loop)
• Verbal direction created ambiguity and constructive-change risk
• Email/call not reduced to authorized written contract action
• File cannot defend payment or refusal cleanly

Correct recovery pattern on the exam: stop informal direction, gather facts in writing, involve the CO, determine whether a modification, rejection, or claims process applies, and rebuild documentation going forward.

---

Linking Communication to Ethics and Team Dynamics

• Ethics: Transparent, equal communication protects process integrity; secret preferential calls destroy it
• Teams: Role-clear communication prevents two Government voices from giving opposite directions
• Business acumen: Documented tradeoffs show stewardship of public resources
• Lifecycle: Pre-award clarity reduces post-award documentation emergencies

Memory hook: Say it early, write it clearly, file it completely, route it through authority. That pattern captures FAI 1.7 and will save points across Award and Post-Award items that never mention the word “communication.”