Most SDVOSB firms spend the majority of their business development energy focused on the contracting officer — the person with the pen. That is reasonable. The CO makes the award decision, signs the contract, and has authority over contract modifications. But once performance begins, the person who shapes your day-to-day experience, your past performance rating, and your recompete position is not the CO. It is the Contracting Officer’s Representative.
The COR — sometimes called the Contracting Officer’s Technical Representative (COTR) or the Government Technical Representative (GTR) depending on the agency — is the government employee delegated to monitor contract performance on the CO’s behalf. On most service contracts, the COR is a program or technical staff member who works daily with your team, reviews your deliverables, approves your invoices, and submits the performance assessments that become your CPARS record. Understanding the COR’s role and investing in that relationship is one of the highest-return activities available to an SDVOSB during contract performance.
What the COR Is — and Is Not — Authorized to Do
The COR operates under a delegation letter from the CO that specifies exactly what they are authorized to do. This is important, because CORs frequently operate at the boundary of their authority and sometimes exceed it without realizing it. Understanding the scope of a COR’s authority helps you respond correctly when they make requests or give direction.
What CORs are typically authorized to do: monitor technical performance against the PWS, review and approve deliverables, verify that work is being performed in accordance with the contract, and submit performance assessments and documentation to the CO. They can provide technical direction within the scope of the existing contract, recommend contract modifications to the CO, and withhold approval of invoices for work they assess as deficient.
What CORs are not authorized to do: change the scope of the contract, authorize work beyond the contract’s requirements, commit the government to additional costs, or direct you to perform work outside the Statement of Work without a formal modification. This is one of the most common sources of contractor problems in federal contracting — a COR asks a contractor to perform additional work, the contractor does it to be cooperative, and then there is no vehicle to pay for it because no modification was ever issued.
When a COR asks you to do something that appears to expand scope, the correct response is not to refuse — it is to ask whether a modification will be issued. Document the request in writing, confirm your understanding of the task, and explicitly note that you will proceed once a modification is executed if the work is outside the current contract scope. This protects both you and the COR.
How CORs Are Assigned and What Their Incentives Are
CORs are program staff who are typically collateral-duty — the COR assignment is added to their existing job, not their primary function. They receive COR certification training (usually FAC-COR Level I, II, or III, depending on contract complexity) and are given a delegation letter with specific authorities. Many CORs are technically expert in the subject matter of your contract but have limited formal contracting training. Some are highly engaged; others treat the COR assignment as an administrative burden on top of their real work.
Understanding the COR’s position matters for managing the relationship. A COR who is not engaged is a risk: they may not review your deliverables promptly, approve invoices slowly, or fail to document performance issues that should be addressed early. A COR who is over-engaged and technically confident can unintentionally direct work outside scope. Neither extreme is ideal.
The COR’s primary accountability is to the program, not to you. Their job is to ensure the government gets what it paid for. A COR who gives you an Exceptional rating on CPARS is not doing you a favor — they are accurately reflecting that you performed. Their incentives align with your interests when you perform well and conflict with them when you do not.
The COR’s Role in CPARS
The COR is the primary drafter of CPARS assessments. On most contracts, the COR initiates the assessment, writes the narrative, and assigns the preliminary rating. The CO reviews and approves (or modifies) the assessment before it is finalized. The contractor then has the opportunity to review and comment before the record is locked.
This means your CPARS record is, in practice, written by the person you work with every day — not by a distant official reviewing your file. The COR’s personal experience of your team’s performance, communication, responsiveness, and judgment is what becomes your past performance record. That record follows you into every future proposal for three to five years.
The practical implication is that CPARS management is not a documentation exercise you handle at the end of the contract. It is a relationship you build from day one. A COR who has nine months of positive interactions with your team will write a different CPARS narrative than a COR who had nine months of friction, missed deliverables, and difficult communications — even if the technical output was identical.
Building the COR Relationship from Day One
The post-award kickoff meeting is where the COR relationship begins. Most contractors treat the kickoff as an administrative milestone. The contractors who win recompetes treat it as a relationship-establishing conversation. Come to the kickoff with specific questions about how the COR prefers to communicate, what their priorities are for the program, what has frustrated them about past contractors on this work, and what success looks like to them beyond what is written in the PWS.
Establish communication rhythm early. Weekly status touchpoints — even brief ones — prevent the accumulation of unaddressed issues that become performance problems. A COR who hears about a problem from you before it affects the program is a COR who sees a proactive, trustworthy contractor. A COR who discovers a problem independently is a COR who questions your situational awareness and transparency.
Put agreements in writing. When the COR approves a technical approach, confirms a schedule, or provides direction, follow up with a brief written summary — an email is sufficient. This is not adversarial; it is professional. It protects both parties by creating a contemporaneous record of decisions and prevents the kind of “I thought you said” disputes that damage relationships and generate claims.
Managing Disagreements with the COR
Disagreements with CORs are normal. They arise over deliverable quality, schedule interpretation, scope questions, and sometimes over the COR’s own confusion about what the contract requires. How you handle disagreement determines whether you resolve it or escalate it into a formal dispute.
Start with the contract. When a COR takes a position that you believe is incorrect, pull the relevant PWS language, the applicable clause, or the deliverable specification and discuss it directly. Most disagreements between well-intentioned parties are resolved at this level. Frame the conversation as collaborative — you want to understand their concern and find an approach that works — not as a challenge to their authority.
If the COR’s position appears to conflict with the contract and informal resolution fails, escalate to the CO. Document your escalation in writing, note that you attempted to resolve the issue at the COR level, and state the specific contract provision at issue. Escalating to the CO over a COR is not a relationship-ending move when done professionally and infrequently. It becomes relationship-ending when done reflexively, publicly, or repeatedly over minor issues.
Never work around a COR by going directly to the program office or agency personnel they report to without notifying the COR and CO first. The COR represents the CO’s interests. Going around them signals that you do not respect the contract’s governance structure, and that signal reaches the CO.
COR Turnover and Transition Risk
COR turnover is one of the most underappreciated risks in federal contract performance. A COR who knows your team, trusts your judgment, and has approved your approach to the work is replaced by a new COR who arrives with different priorities, different communication preferences, and no institutional memory of prior decisions. Everything you built over six months of relationship management starts over.
When COR turnover occurs, treat it as a re-onboarding. Schedule a dedicated transition meeting, walk the new COR through the contract history, the current status of deliverables, any standing agreements with the prior COR, and your team’s approach to the work. Provide a brief written summary of this transition meeting. Invest the same relationship-building effort you made at kickoff.
The risk is that a new COR will re-evaluate decisions the prior COR made and raise concerns about approaches that were already approved. If you have contemporaneous documentation of prior approvals, you can address these situations factually and non-defensively. If you do not have documentation, you are in a weaker position. This is one more reason to put agreements in writing throughout performance, not just at the start.
The COR as a Recompete Asset
A COR who has worked closely with your team for one or two years has knowledge about your performance, your people, and your approach that no competitor can replicate. That knowledge is your most valuable recompete asset — provided it is positive.
During recompete positioning, the COR can legitimately share information about incumbent performance with the acquisition team. A COR who tells the program office that your transition plan was smooth, your technical team is excellent, and continuity with your firm would minimize program risk has done more for your recompete position than anything in your proposal. A COR who has reservations about your performance will share those reservations too, often more directly than any CPARS narrative.