Data sourced from SAM.gov, USAspending, FPDS, Grants.gov. 110+ supplementary federal data feeds. View methodology →
100M+ government records · 110+ gov/news sources · Synced from live federal sources
Explore 100M+ federal records across SAM.gov, Grants.gov, USAspending, FPDS, and 110+ federal sources.
Search all opportunities →Every government contract exists because a Contracting Officer signed it. Understanding the authority, constraints, and incentives of the acquisition workforce is essential for any contractor that wants to build effective government relationships and avoid costly mistakes.
This guide covers the key roles in the government acquisition workforce — COs, CORs, the OSDBU, and program managers — and provides practical advice on working with each of them effectively.
100M+ government records · 110+ gov/news sources · Synced from live federal sources
The COR is a government employee designated by the CO to serve as the “eyes and ears” of the CO on a specific contract. The COR monitors contractor performance, reviews deliverables, and reports performance issues to the CO. While the COR interacts with the contractor daily, their authority is strictly limited.
What a COR can do:
What a COR cannot do:
CORs are required to complete training and receive a formal delegation letter from the CO that specifies their responsibilities. The OFPP standardized COR training requirements across the government in 2011, replacing the previous patchwork of agency-specific programs.
The terms COTR (Contracting Officer's Technical Representative), GTR (Government Technical Representative), and COR (Contracting Officer's Representative) have been used interchangeably across federal agencies for decades. In 2011, the Office of Federal Procurement Policy (OFPP) standardized the title to COR across all civilian agencies, and DoD followed with similar guidance.
Despite the standardization, you will still encounter the COTR title in older contracts, some agency regulations, and everyday conversation. The roles are identical — the only difference is the title. When reviewing a contract, look for the “Contracting Officer's Representative” designation letter, regardless of which acronym the agency uses.
Some agencies have also used variations like “Contracting Officer's Technical Monitor” (COTM) and “Task Order Manager” (TOM) for similar oversight roles. In all cases, the individual's actual authority is defined by their delegation letter from the CO, not by their title.
Every major federal agency has an Office of Small and Disadvantaged Business Utilization (OSDBU) — or in the case of DoD, an Office of Small Business Programs (OSBP). The OSDBU is the agency's advocate for small business participation in the procurement process and a critical resource for small businesses looking to do business with that agency.
OSDBU functions include:
The OSDBU is one of the most underutilized resources available to small businesses. Meeting with the OSDBU before a solicitation is released can provide valuable intelligence about upcoming requirements, agency priorities, and the competitive landscape. Many OSDBU offices hold regular “vendor outreach sessions” or “one-on-one” meetings that are open to any small business.
The OSDBU director typically reports to the agency head or deputy, giving them visibility and influence across the agency's procurement activities. Building a relationship with the OSDBU is one of the highest-ROI activities for any small business entering a new agency market.
One of the most important dynamics in government contracting is the relationship between the government Program Manager (PM) and the Contracting Officer (CO). Understanding this relationship helps contractors navigate the often-confusing landscape of government direction.
The Program Managerowns the mission requirement. They define what the government needs, develop the statement of work, evaluate technical proposals, manage the budget, and oversee the program's execution. The PM knows the technical substance of the contract better than anyone.
The Contracting Officerowns the contract. They translate the PM's requirements into a legally binding agreement, manage the procurement process, negotiate with the contractor, and are the only person who can commit the government to contractual obligations.
Tension between these roles is common. The PM may want to direct the contractor to do something different from what the contract specifies, but only the CO can authorize contract changes. Contractors often feel caught between a PM who wants something done and a CO who has not approved it.
Best practice:When a government PM asks you to do something that appears to change the scope, price, or schedule of the contract, acknowledge the request, document it in writing, and inform the CO. Ask the CO to issue a modification before performing the work. This protects both you and the PM. It is not adversarial — it is how the system is designed to work.
For anything contractual, use email or formal correspondence. Oral agreements are not enforceable against the government. If a CO tells you something verbally, follow up with a confirming email.
When making a request or raising an issue, reference the specific contract clause that applies. COs respond to clause-based arguments because that is their framework for decision-making.
COs manage dozens of contracts simultaneously. Provide clear, concise correspondence. Include relevant background so they do not have to look it up. Draft proposed modification language when requesting changes.
Do not try to go around the CO by escalating to their supervisor or to the PM. COs have independent authority and react poorly to end runs. If you disagree with a CO decision, use the disputes process.
Notify the CO early when you anticipate performance issues, cost overruns, or schedule delays. COs appreciate transparency and are more willing to work with contractors who surface problems before they become crises.
COs face funding limitations, audit scrutiny, protest risk, and policy guidance that constrain their flexibility. Understanding these constraints helps you frame requests in terms the CO can approve.
A warrant is the legal document that grants a Contracting Officer the authority to enter into, administer, or terminate government contracts and to make related determinations and findings. Warrants specify the dollar threshold of the CO's authority (e.g., up to $25 million, up to $100 million, or unlimited). Only warranted Contracting Officers can legally obligate the government. Actions taken by government personnel without a warrant — even if they appear to give direction — do not bind the government and are not enforceable by the contractor.
COR (Contracting Officer's Representative) and COTR (Contracting Officer's Technical Representative) are functionally the same role. The OFPP standardized the title to "COR" in 2011, replacing COTR, GTR (Government Technical Representative), and other variations. Some agencies still use the COTR title informally, but the official designation is COR. Regardless of title, the role involves monitoring contractor performance on behalf of the contracting officer. CORs do not have the authority to direct changes, modify contracts, or obligate the government.
No. A COR does not have the authority to direct contract changes, modify the scope of work, increase the contract price, or extend the period of performance. Only the Contracting Officer can make changes to the contract. If a COR verbally directs the contractor to perform work outside the contract scope, the contractor should request written direction from the CO before proceeding. Performing work based on COR direction alone creates significant risk because the government may not be obligated to pay for unauthorized work.
Always communicate with the CO in writing for anything contractual — requests for equitable adjustment, claims, disputes, notification of issues, and questions about contract interpretation. Email is acceptable for routine matters, but formal correspondence (letters on company letterhead) is appropriate for significant contractual issues. Keep the COR informed on technical matters, but remember that only the CO can make binding decisions. Be professional, cite specific contract clauses when relevant, and maintain complete records of all communications.
Research agency procurement patterns, track contracting officers by agency, and understand buying behaviors to build more effective government relationships.