A Contracting Officer's Representative is a person designated in writing by the contracting officer to assist in the technical monitoring or administration of a contract. The authority comes from FAR 1.602-2, which requires a CO to designate and authorize a COR for all contracts and orders other than those that are firm-fixed price without surveillance needs.

The reason the role exists is practical. The CO is legally responsible for contract performance, but COs are rarely on-site watching the work get done. The COR is the CO's eyes and ears. They observe what the contractor is actually doing, document it, and report back. They do not replace the CO. They extend the CO's situational awareness to the place where the work is happening.

Per FAR 1.604, CORs are required to maintain a file for each assigned contract. This isn't optional, and it has specific content requirements. More on that in Section 6.

DoD Instruction 5000.72 establishes a tiered COR certification framework built around the complexity and risk of the contract. Contracts are classified as Type A, B, or C, and each type carries different COR certification level requirements.

This training focuses on Type A. If you're working a cost-plus or T&M contract, or anything with incentive structures, the Level I certification is not sufficient. Know what you have before you nominate someone.

A COR is not a COR until the CO issues a written Letter of Designation (LOD). The LOD is the legal instrument that establishes the COR's authority. Without it, the person is just an interested party with no official role in contract administration.

The LOD must specify the duties delegated to the COR. This matters because if it is not in the LOD, the COR has no authority to do it. Vague LODs create vague authority, which leads to CORs either overstepping or being paralyzed when something goes wrong.

For DoD, the nomination and designation process runs through JAM (Joint Appointment Module) within PIEE. This is covered in Section 5.

Type A is FFP, low risk. The price is set. You are not tracking labor hours or cost against a budget. Your primary job is making sure the contractor is delivering what the SOW says they should deliver, flagging when they are not, and communicating up to the CO.

For Type A specifically, the most common failure mode is a COR who starts directing the contractor's day-to-day operations as if they are a supervisor. That is the employer-employee relationship test from FAR 37.104, and it is a personal services violation. Monitor the results of the work, not the method.

This is where a lot of offices go wrong. Both the COR appointment process and the COR's ongoing surveillance documentation have designated systems of record within PIEE (the Procurement Integrated Enterprise Environment at wawf.eb.mil). Using a different system, or duplicating records across systems, creates administrative confusion and fails audits.

The following is the controlling language from DAFFARS 5304.802(f), reproduced verbatim:

FAR 1.604 requires the COR to maintain a file for each assigned contract. The COR file is not the same as the contract file. It is a separate, COR-specific record of what the COR did throughout the life of the contract.

In practice this means surveillance checklists, inspection records, performance documentation, correspondence with the contractor related to performance, and any reports submitted to the CO. For Type A contracts, this does not need to be extensive, but it does need to exist and be current.

There is a mindset in some contracting offices that a COR's job is essentially to watch and report, and that any actual direction to the contractor has to flow through the CO. Taken too far, this makes the COR useless and makes the CO the single point of contact for every minor operational question on every active contract.

The better approach is to think carefully about what the COR should be able to direct within the scope of the existing contract, write those authorities explicitly into the LOD and the contract, and then trust your COR to use them. The key word is "within scope." A COR directing something that changes what the contract requires is an unauthorized commitment. A COR directing something that falls within the scope of work already contracted is just good administration.

The starting position should be trust. If a COR loses that trust through poor judgment or overreach, you address it. But a COR appointed with zero meaningful authority is administrative theater. If you are not willing to empower your COR to make routine decisions within scope, you have taken on the surveillance burden yourself and just given someone a title.

CORs and CPARS. CORs are responsible for writing up their assessment of contractor performance for the Contractor Performance Assessment Reporting System (CPARS). The CO has final sign-off on the rating, but in practice the COR's input should be taken seriously. The COR is the one observing the work. The CO reviews the COR's write-up against the PWS, enters the rating, and moves on.

A lot of friction between COs and CORs shows up at CPARS time, and most of it traces back to a relationship where the COR was never really trusted or empowered to begin with. If the CO has been engaged with the COR throughout the contract and the COR has been doing their job, CPARS should not be a fight. The COR writes their piece, the CO compares it to what the PWS required, and the rating reflects what actually happened.

COR appointment is a CO responsibility. Here is what the CO needs to verify before the LOD is issued:

Do not nominate the first person who volunteers. The COR needs to actually understand the requirement. For a service contract, that usually means someone who works closely with the contracted function and can meaningfully assess whether the contractor's performance meets the standard. A COR who cannot tell good performance from bad performance is not protecting the Government's interests.