Study guide
14.1 Contract Administration Fundamentals (FAR Part 42)
DAWIA DoD Contracting Professional Certification CON 3990V
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts & Logistics 1.2 Certification Path, Eligibility & Retakes 1.3 Closed-Book Study Strategy for CON 3990V
2 FAR System & Regulatory Map
2.1 FAR Structure, Authority & Hierarchy (Part 1) 2.2 Definitions & Key Terms (Part 2) 2.3 FAR Part Title Map for CON 3990V
3 Guiding Principles: Skills, Roles & Situational Assessment
3.1 Skills and Roles Across the Contract Lifecycle 3.2 Business Acumen for Contracting Decisions 3.3 Situational Assessment & Lessons Learned
4 Guiding Principles: Contract Principles
4.1 Core Contracting Principles 4.2 Competition, Integrity & Transparency Principles 4.3 Terms, Conditions & Contract Formation Fundamentals
5 Ethics, Teams & Communication
5.1 Standards of Conduct & Conflicts of Interest (FAR Part 3) 5.2 Team Dynamics in Acquisition Teams 5.3 Communication and Documentation Best Practices
6 Pre-Award: Plan Solicitation
6.1 Acquisition Planning (FAR Part 7) 6.2 Market Research (FAR Part 10) 6.3 Competition Requirements & JOFOCs (FAR Part 6)
7 Pre-Award: Sources, Commercial & Simplified
7.1 Publicizing Contract Actions (FAR Part 5) 7.2 Required Sources of Supplies and Services (FAR Part 8) 7.3 Commercial Acquisition & Simplified Procedures (Parts 12 & 13)
8 Pre-Award: Request Offers & Seller Awareness
8.1 Building the Solicitation Package 8.2 Requesting Offers: Methods, Evaluation Factors & Clauses 8.3 Seller Planning, Offer Preparation & DFARS Awareness
9 Socioeconomic Programs & Small Business
9.1 Small Business Programs & Set-Asides (FAR Part 19) 9.2 Socioeconomic Preferences & Rule of Two 9.3 Pre-Award Small Business Subcontracting Considerations
10 Award Foundations: Contract Types
10.1 Fixed-Price Contract Types (FAR Part 16) 10.2 Cost-Reimbursement & Hybrid Types 10.3 Selecting & Documenting Contract Type
11 Award: Price & Cost Analysis
11.1 Price Analysis Techniques 11.2 Cost Analysis, Certified Cost or Pricing Data & TINA/TCPD 11.3 Cost Realism & Fair and Reasonable Pricing
12 Award: Negotiation & Source Selection
12.1 Planning Negotiations & Pre-Negotiation Objectives 12.2 Source Selection Methods & Competitive Range (FAR Part 15) 12.3 Responsibility Determinations & Award Documentation (Part 9)
13 Award: Manage Disagreements
13.1 Bid Protests (FAR Part 33) 13.2 Size Status & Pre-Award Challenges 13.3 Managing Disagreements & Constructive Resolution
14 Post-Award: Administer & Quality
14.1 Contract Administration Fundamentals (FAR Part 42) 14.2 Quality Assurance & Surveillance (FAR Part 46) 14.3 Subcontract Management & Consent (FAR Part 44)
15 Post-Award: Changes, Claims & Disputes
15.1 Contract Modifications & Scope 15.2 Constructive Changes, REAs & Claims 15.3 Disputes Under the Contract Disputes Act
16 Terminations, Closeout & Exam Integration
16.1 Terminations for Convenience & Default (FAR Part 49) 16.2 Contract Closeout & Records (Parts 4 & Closeout) 16.3 Lifecycle Integration, High-Yield Traps & Exam Day
14.1 Contract Administration Fundamentals (FAR Part 42)
Key Takeaways Explain This Topic AI
FAR Part 42 governs contract administration and audit services: assigning administration, post-award orientation, performance monitoring support, and related audit/administration interfaces so the Government manages the contract after award.
Assignment of contract administration may retain functions with the procuring Contracting Officer or transfer specified administration to a Contract Administration Office (CAO); the CO typically retains authority for modifications and terminations unless properly delegated.
Contracting Officer's Representatives (CORs) act under written nomination and delegation with clear limitations of authority—they monitor technical performance and report; they do not independently bind the Government with changes, terminations, or unauthorized commitments.
Post-award orientation, performance monitoring, payment-related administration awareness, and past performance evaluation themes keep the file current and mission-aligned through performance.
Administer Contract (FAI 4.1.1, ~10Q) tests whether you know who may act, what must be documented, and how COR/CAO roles support—but do not replace—CO authority after award.
Last updated: August 2026
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:
Exam question pattern What you must show
Who may bind the Government after award? Warranted CO (or properly delegated authority)—not the COR, PM, or specialist alone
- What happens right after award? Assignment , orientation , baseline surveillance setup
- How do we know performance is on track? Monitoring, COR reports, metrics, issue escalation
- How do we protect the file? Documentation of directions, problems, payments, past performance inputs
- When does admin become a change/termination problem? Route to CO early—do not paper over with COR emails
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:
- Cluster Substance you must know
- Assignment of administration Which office/official performs which post-award functions
Contract administration office (CAO) When administration is transferred/retained; functional split with procuring office
- Post-award orientation Aligning parties on requirements, responsibilities, and communication
- COR / property / surveillance support Technical monitoring under written authority
Audit services interface Awareness that audit support (e.g., DCAA themes) aids cost/admin decisions—not that you memorize every audit type
Indirect cost / billing admin themes Conceptual awareness that cost-type and certain billings need admin scrutiny
Past performance information Collecting and using performance history as policy requires
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:
Retained by the procuring Contracting Officer / procuring activity , or
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:
- Principle Practical meaning
- Function-based assignment Specific admin functions can be assigned even when others stay with the procuring CO
Clear responsibility File and parties must know who does surveillance, property, quality interface, payment support, etc.
Procuring CO still owns the deal Business relationship, major contractual remedies, and often modifications/terminations remain with the CO unless properly delegated
Communication channel Contractor should not receive conflicting directions from three offices
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 goal Why it prevents later fights
- Confirm scope, schedule, and deliverables Surfaces misreads of the SOW/PWS before work drifts
- Clarify roles (CO, COR, CAO, contractor PM) Stops "who told me to do that?" chaos
- Review reporting, inspection, and acceptance paths Aligns Part 42 admin with Part 46 quality
- Address security, GFP, data rights, travel as applicable Reduces surprise noncompliance
- Set communication protocols Official direction vs technical discussion
- Identify risks and early watch items Enables proactive surveillance
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
- Theme Closed-book point
- Written designation COR authority comes from written nomination/delegation by the CO (agency process/forms)
- Training / qualification Agencies require COR training/certification standards before effective designation
- Specific contract Delegation is for the named contract(s)/order(s)—not a general warrant to run contracting
- Duties listed Surveillance methods, reporting frequency, and authorities (and non-authorities) should be clear
- CO retains contracting authority COR does not become a second CO
- 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
Prohibited / beyond authority Why it is dangerous
Issue modifications or change scope/price/schedule bilaterally Only the CO binds the Government on contract actions
- Direct work outside the contract Creates unauthorized commitments / constructive changes
- Terminate the contract Termination is a CO action under Part 49 themes
Promise payment beyond contract terms Payment authority and allowability still follow the contract and finance rules
Waive contract requirements informally Waivers/changes need proper contractual vehicles
Disclose source selection sensitive or proprietary info improperly Integrity and competition residue after award still matters
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 tool Use
- Contract requirements (PWS/SOW, specs, CDRLs) Baseline of "done right"
- QASP / surveillance plan (Part 46 link) Risk-based what/when/how of Government checks
- Contractor reports & metrics Schedule, quality, cost (as required)
- COR logs / site visits / sampling Independent Government observation
- Invoice & progress reviews Payment should track performance reality
- Issue trackers / cure communications Early documentation of shortfalls
Monitoring principles for the exam:
Risk-based — higher risk work gets denser surveillance.
Documented — undocumented "everyone knows they're late" fails audits and claims defense.
Timely escalation — chronic delay or quality failure is a CO problem , not a perpetual COR coaching loop.
Fair and factual — feedback should map to contract standards, not personal preference.
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 :
- Awareness theme Contracting judgment
- Match work to invoice Technical acceptance/performance input supports paying the right amount
- Withholds / deductions Contract remedies and quality/inspection outcomes can affect payment
- Cost-type billing scrutiny Provisional billing and cost allowability themes require admin/audit awareness
Prompt payment concepts Government must process proper invoices timely; improper invoices get returned with reasons
Do not pay for out-of-scope work just because it happened Performance outside the contract is a change/claim problem first
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.