A COR is a government official authorized by the Contracting Officer to oversee contract execution, monitor performance, and manage day-to-day administration. The COR ensures contractors meet all obligations, deliver quality products/services, stay on schedule and budget. While the Contracting Officer retains legal authority, the COR handles operational relationships and can address routine issues without CO approval.
Opening Definition
A COR is a government-delegated representative responsible for overseeing contract performance, monitoring deliverables, and ensuring contractors meet contractual obligations. CORs serve as primary day-to-day contacts while Contracting Officers maintain final authority.
Why It Matters for Tech Companies
The COR is your most important day-to-day contact. While Contracting Officers have legal authority, CORs manage operations constantly. Strong COR relationships accelerate approvals, resolve disputes informally, and influence contract modifications favorably. Poor relationships result in performance complaints and unfavorable modification discussions. For tech companies, CORs often have technical expertise and understand solutions better than COs. Leveraging this relationship strategically improves outcomes significantly.
How It Works in Practice
COR Responsibilities: Monitor invoices for accuracy, receive/inspect deliverables, review compliance with performance metrics, attend progress meetings, and document performance. CORs can approve small changes, accept work meeting specifications, and issue informal directives within delegated authority. Example: On a $2M IT services contract, your COR reviews monthly invoices, attends biweekly meetings, inspects system updates, and validates 99.5% uptime performance. When the agency needs a minor $15K requirement change, the COR can informally approve it. A $200K+ change requires formal CO modification. Authority Limits: COR delegated authority is defined in their delegation letter and contract. They typically cannot obligate funds beyond $10K-$50K (varies by agency). Major changes, payment disputes, or contract interpretation require CO involvement.
Common Mistakes to Avoid
- Bypassing the COR: Going to CO or agency leadership instead of COR creates friction.
- Assuming COR approval means CO approval: COR saying "that's fine" doesn't authorize expensive work without formal modification.
- Poor documentation: When COR says "handle informally," follow up in writing. If they won't put it in writing, that's a red flag.
- Not understanding COR limitations: Expecting CORs to resolve interpretation disputes or override contract language frustrates both parties.
- Neglecting relationship building: Contractors delivering on promises and making COR's job easier get better treatment and faster approvals.
Key Facts and Numbers
- COR delegation required per FAR 1.600
- Authority varies by agency
- Typical $10K-$50K approval limit
- CORs face personal liability for exceeding authority
- Common titles: Technical Monitor, Project Manager, QA Specialist
Related Terms
Contracting Officer • FAR • Past Performance
Related Guides
Managing Government Contracts Effectively • Contract Administration Best Practices
Frequently Asked Questions
What's the difference between a COR and Contracting Officer?
Contracting Officer has legal authority to bind government and is accountable for compliance. COR is delegated for day-to-day management but cannot override terms or make major commitments.
Can the COR tell me to do work not in the contract?
Not officially. If directed out-of-contract work, request written directive and ask if formal modification is coming. Performing without modification may result in non-payment.
What should I do if I disagree with COR's performance assessment?
Discuss professionally with COR to understand concerns. If unresolved, escalate to Contracting Officer in writing. Document your position and evidence clearly.
How often should I communicate with the COR?
Frequency depends on contract complexity. Active service contracts typically require weekly status meetings. Supply contracts may need monthly or quarterly reviews.