14.1 Contract Administration Fundamentals (FAR Part 42)

14.1 Contract Administration Fundamentals (FAR Part 42)

Quick Answer: Administer Contract (FAI 4.1.1, about 10 questions) lives mainly in FAR Part 42—contract administration and audit services. Know assignment of administration, post-award orientation, COR nomination/delegation and authority limits, performance monitoring, payment-related admin awareness, and past performance evaluation themes. The Contracting Officer typically retains modification and termination authority unless lawfully delegated; CORs recommend and report—they do not freestyle scope changes.

Award is not the finish line. After signature, the Government must manage performance, protect funds, maintain the file, and convert contractor outputs into mission results. FAR Part 42 — Contract Administration and Audit Services is the primary map for that work. On CON 3990V, post-award items often fail candidates who still think "administration = waiting for invoices" or who let a COR "approve" a constructive change because the program was urgent.

Why contract administration is a scored competency

Post-Award is 38 questions of the 150-item exam; Administer Contract alone is about 10. Those items rarely ask for obscure form numbers. They ask:

Administration is lifecycle risk management. Weak admin produces unauthorized commitments, delayed detection of nonperformance, payment disputes, and past performance ratings with no supporting evidence.

FAR Part 42 at a conceptual level

Part 42 covers policies and procedures for contract administration and audit services that support administration. For CON 3990V initial readiness, internalize these clusters:

You do not need every Part 42 subpart citation memorized. You do need the authority map and the next-step judgment when performance, payment, or delegation goes sideways.

Assignment of contract administration

After award, administration functions may be:

1. Retained by the procuring Contracting Officer / procuring activity, or
2. Assigned/transferred (in whole or in part) to a Contract Administration Office (CAO)—common in DoD for many supply and some service contracts through established CAO networks.

Conceptual rules:

Exam trap: "Once a CAO is assigned, the procuring CO may never issue a modification." Not the automatic rule—know that retention of CO authority for mods/terminations is typical, and any delegation must be real, written, and within policy.

Exam trap: "Assignment of administration means the contractor is no longer bound by the original contract." False—assignment changes who administers for the Government, not the contractor's performance obligations.

What "administration functions" feel like on the exam

Think of a checklist of post-award workstreams:

• Monitoring delivery/schedule and technical compliance
• Receiving and reviewing reports required by the contract
• Coordinating quality assurance and inspection interfaces (with Part 46)
• Supporting invoice/payment review processes
• Managing Government property when applicable
• Documenting performance issues and past performance inputs
• Coordinating audit support for cost/billing questions
• Escalating potential changes, claims, or termination indicators to the CO

Post-award orientation

Post-award orientation (sometimes called a post-award conference) is a structured kickoff so both parties start from a shared understanding.

Orientation is not a second negotiation of price or a chance to rewrite requirements without a modification. If orientation reveals a true requirement error, the CO addresses it through proper contract action—not informal COR "clarifications" that expand scope.

Scenario — Orientation as secret renegotiation. At kickoff, the PM and contractor "agree" to add two extra monthly reports because it "helps the program," with no mod and no funding discussion. Wrong. That is a change. Document the need and route to the CO for a proper modification if warranted.

COR nomination, delegation, and limitations of authority

The Contracting Officer's Representative (COR) is a designated individual (often technical/program) who assists the CO by monitoring contractor performance. CON 3990V loves COR authority traps.

Nomination and delegation themes

What CORs typically may do

• Monitor technical performance against the PWS/SOW and QASP
• Review deliverables for technical adequacy and recommend acceptance/rejection paths
• Document performance (good and bad) and report to the CO
• Interface with the contractor on technical clarification within scope
• Support invoice review with technical input (e.g., "was the work performed?")
• Identify potential problems early and recommend CO action

What CORs typically may not do

Exam cue: If the stem has a COR "approving extra work," "telling the contractor to ignore a clause," or "agreeing to a price increase," the correct next step almost always involves stopping the unauthorized direction and engaging the CO—not celebrating "customer service."

Scenario A — Friendly COR. COR emails: "Go ahead and replace all 50 units with the upgraded model; we'll sort paperwork later." Contractor complies and bills more. Correct framing: Unauthorized direction; potential constructive change / unauthorized commitment; CO must assess, document, and resolve lawfully—do not normalize "paperwork later."

Scenario B — Passive COR. COR never visits the site, never reviews monthly reports, then at option exercise says "performance was fine." Wrong. Monitoring is a duty; past performance and option decisions need evidence.

Monitoring performance

Performance monitoring is the continuous comparison of what the contract requires to what the contractor delivers.

Monitoring principles for the exam:

1. Risk-based — higher risk work gets denser surveillance.
2. Documented — undocumented "everyone knows they're late" fails audits and claims defense.
3. Timely escalation — chronic delay or quality failure is a CO problem, not a perpetual COR coaching loop.
4. Fair and factual — feedback should map to contract standards, not personal preference.
5. Consistent with contract type — cost-type needs cost/performance insight; fixed-price still needs quality and schedule vigilance.

Payment-related administration awareness

You are not expected to be a DFAS technician, but you must understand the admin link to payment:

Exam trap: "If the COR likes the contractor, pay everything." Payment follows the contract and evidence of performance, not popularity.

Past performance evaluation themes

Part 42 and related policy expect the Government to evaluate contractor performance and feed past performance information systems (for future source selections). Conceptual exam points:

• Evaluate against contract requirements and documented performance.
• Provide ratings and narratives that are supportable—not retaliatory, not boosterish fiction.
• Afford contractor comment opportunity where procedures require.
• Use performance assessment to inform options, awards, and future evaluations—not as a surprise at recompete only.
• COR inputs often draft assessments; CO/agency process finalizes responsibility for official ratings.

Scenario — No contemporaneous records. At CPARS/past performance time, the team invents a glowing narrative because "they're the only vendor who can do this next year." Wrong. Ratings need factual basis; dishonest past performance corrupts future competitions.

CO retains authority for modifications and terminations (typical rule)

Memorize this authority spine:

CO (warrant)  ->  binds Government: award, mods, terminations, many remedies
COR (delegation) -> monitors, documents, recommends within written limits
CAO (assigned functions) -> performs specified admin tasks for the Government
PM / technical -> requirements ownership; cannot create contract obligations alone

When performance fails, do not invent a COR-led "termination." When scope must change, do not invent a COR-led "mod." Escalate with a documented package: facts, contract cites, impact, recommended CO action.

Connecting Part 42 to the post-award chapters ahead

• Part 46 (Section 14.2) — quality assurance and acceptance details that feed admin monitoring.
• Part 44 (Section 14.3) — subcontract consent and purchasing system themes the CO/admin team may handle.
• Changes / claims / terminations (later chapters) — admin evidence is what makes remedies defensible.
• Closeout — clean administration throughout makes closeout faster and less contentious.

CON 3990V closed-book anchors

• Part 42 = contract administration + audit services support.
• Assign admin deliberately; know who does what.
• Post-award orientation aligns parties—does not secretly renegotiate.
• COR = written limited authority; monitors and reports.
• CO typically keeps mods and terminations.
• Monitor, document, escalate; pay against the contract; rate past performance honestly.

---

Bottom line: Contract administration under FAR Part 42 is active post-award management—assignment, orientation, COR discipline, performance monitoring, payment awareness, and past performance. On CON 3990V, choose answers that protect CO authority, force written limits, and treat admin as evidence-based mission control, not passive invoice processing.