3.1 Skills and Roles Across the Contract Lifecycle

Why Skills and Roles Matter on CON 3990V

FAI blueprint row 1.1 Skills and Roles is a six-question slice of Guiding Principles, but it shows up everywhere else on the closed-book exam. Award and post-award items rarely ask only for a FAR cite — they ask who may act, who must concur, and who merely advises. If you confuse a Contracting Officer’s Representative (COR) recommendation with Contracting Officer (CO) authority, you will pick the wrong next step even when you know the regulation.

CON 3990V assesses initial readiness against the Contracting Common Technical Competencies. Those competencies are not job titles; they are skill clusters used across the lifecycle: shaping requirements, soliciting and evaluating offers, negotiating price and terms, administering performance, managing changes, and closing the file. Your exam job is to connect the skill to the right role and the right phase.

---

Contracting Common Technical Competencies (Conceptual Map)

Think of competencies as “what good contracting work looks like,” independent of GS grade. On the exam, a scenario often states a mission need and a messy fact pattern; you must identify which competency is in play and which team member owns the decision.

These clusters sit inside Guiding Principles because technical skill without role discipline creates unauthorized commitments, protests, and mission delay. The competency model also recognizes that contracting professionals operate in a buyer–seller system: industry is not the enemy, but industry incentives differ from public-sector incentives.

---

Buyer vs. Seller Perspectives in the Competency Model

CON 3990V is a Government contracting exam, yet FAI’s model expects you to understand seller behavior. Buyer (Government) and seller (contractor) optimize different outcomes from the same contract vehicle.

Exam application: When a question says the contractor “refuses to proceed” after a verbal direction from a COR, do not answer as if the contractor is simply uncooperative. Ask: Was the direction within COR authority? Was it a constructive change? Who must issue a written modification? Competency includes reading the commercial logic without abandoning statutory and regulatory limits.

---

Core Roles on the DoD Acquisition Team

DoD acquisition is a team sport. FAR principles and agency procedures assume an integrated set of functions. CON 3990V loves scenarios that mix titles so you must separate influence, recommendation, and binding authority.

Contracting Officer (CO)

The CO is the Government’s agent with a warrant. Within the dollar and type limits of that warrant, the CO may:

• Enter into, administer, and terminate contracts
• Make determinations and findings required by regulation
• Direct changes only through proper modification authority
• Decide claims under the Contract Disputes Act (as the contracting officer)

Critical closed-book fact: no one else binds the Government by personal promise, email, or “we’ll sort the paperwork later.” An unauthorized commitment is a failure of role discipline, even when the mission was urgent.

Contract Specialist / Buyer Support

Specialists prepare solicitations, conduct research, draft evaluations, build price analyses, and assemble files. They often do most of the day-to-day technical work, but final obligation, award, and many formal determinations remain the CO’s. On the exam, if the option says “the specialist awards the contract,” treat that as a red flag unless the person is also a warranted CO acting as such.

Contracting Officer’s Representative (COR)

The COR is appointed in writing by the CO to perform surveillance and technical liaison — typically monitoring performance, inspecting/accepting deliverables (when authorized), reviewing invoices against performance, and documenting contractor performance for the CO. The COR does not:

• Change the contract statement of work, schedule, or price
• Direct the contractor to perform work outside scope
• Make final claims decisions
• Obligate additional funds

COR strength is eyes on performance. COR risk is constructive change through informal direction.

Program Manager (PM) / Requiring Activity

The PM owns mission outcomes, requirements quality, and much of the technical trade space. PMs drive need dates, performance priorities, and acceptance criteria. They do not award contracts or independently redefine contractual requirements after award. Healthy teams keep the PM close for requirements clarity while keeping the CO as the single voice of contract direction.

Legal Counsel

Legal reviews strategy, protests, disputes, intellectual property, organizational conflicts of interest, and nonstandard terms. Legal concurrence is often mandatory for certain actions (for example, some justifications, protests, or dispute positions), but counsel does not replace the CO’s business decision or warrant.

Finance / Budget / Resource Managers

Finance certifies funds availability and tracks fiscal constraints (purpose, time, amount). A CO cannot create a valid obligation without proper funding. Exam scenarios often hide a fiscal issue behind a “schedule pressure” story — if funds are not available or are the wrong color of money, the correct next step is fiscal resolution, not creative contracting language.

---

Managing Contracts Across the Lifecycle While Satisfying the Mission

“Customer satisfaction” in federal contracting is not the same as commercial hospitality. The customer is the mission and the taxpayer, expressed through the requiring activity’s validated need and the contract’s terms. Lifecycle management means the team continuously answers three questions:

1. Are we still buying the right thing? (requirements stability, market change, threat change)
2. Is performance acceptable against the contract? (metrics, inspection, surveillance)
3. Are we documenting decisions so a successor and an auditor can follow them? (file completeness)

Pre-award role emphasis

• PM and technical experts define need and evaluation priorities.
• Contracting leads market research packaging, competition strategy, and solicitation quality.
• Legal/finance gate high-risk clauses and funding assumptions.

Award role emphasis

• Contracting leads evaluation integrity, price reasonableness, negotiations, and award decision documentation.
• PM validates technical understanding of proposals when evaluations require it.
• CO remains the award decision authority (or Source Selection Authority structure as designated).

Post-award role emphasis

• COR and PM watch performance and quality.
• Contracting manages modifications, options, disputes, and closeout discipline.
• Finance tracks funding mods and invoices against obligation status.

Mission satisfaction fails when teams optimize a single phase: a “fast award” that produces an unadministrable contract, or a “friendly COR” who informalizes every change until claims explode.

---

When to Escalate

Escalation is a competency, not a confession of weakness. On CON 3990V, the correct answer is often to stop, document, and elevate rather than “work it out offline.”

Escalate promptly when:

• The proposed action exceeds warrant limits or appointment authority
• There is an apparent unauthorized commitment
• A protest, claim, or formal dispute appears or is threatened
• Facts suggest fraud, conflict of interest, or integrity issues
• The contractor alleges a constructive change or refuses work based on ambiguous direction
• Mission need requires a scope change that is more than administrative
• Team conflict is blocking a time-sensitive acquisition decision and local procedures require elevation

Do not escalate as a substitute for basic homework: incomplete market research, unread clauses, or failure to talk to the COR about performance data. Escalation packages should state the issue, authority question, options, risk, and recommended decision — that is business acumen applied to team dynamics.

---

DoD Acquisition Team Concept in Exam Language

Expect scenarios written like this:

The program office needs software changes before a deployment. The COR tells the contractor to start immediately and “the mod will catch up.” The contractor incurs costs. Who is responsible for what, and what should happen next?

A strong closed-book response pattern:

1. Identify the unauthorized or improper direction risk (COR exceeded authority if directing new work).
2. Stop informal direction; route through the CO for a proper change order/modification if within scope and funded.
3. Involve finance for funds and legal if dispute posture is forming.
4. Document facts for potential ratification or claims handling per procedure.

Another pattern tests who leads communication with offerors during discussions: contracting owns exchanges that affect the competition; technical evaluators provide content through the contracting channel so fairness and documentation survive protest scrutiny.

---

Exam Scenario Drill: “Who Does What?”

Memory hook: Recommend widely, direct narrowly, bind only with a warrant.

If you can assign each action to a role, name the competency cluster, and spot the escalation trigger, you are exam-ready for Skills and Roles — and you will answer many Award/Post-Award items faster because the human workflow becomes clear before the clause cite.