How to build and deliver a training for a newly appointed COR that is actually about the contract they are going to watch. Not the certification course, not the generic COR handbook, the contract they have in their hand.
A newly appointed COR has probably already sat through a certification course. That course teaches the theory of COR responsibilities: what a COR can and cannot do, the basics of surveillance, ethics, and the paperwork structure of the job. It is generic by design because it has to work for every COR in every contract.
Contract-specific training is different. It is the session the contracting officer sits down and delivers about one contract, to the person who is going to watch it. The goal is for the COR to leave the room understanding the actual scope, the actual performance standards, and the specific things to watch for on this particular contract. Someone appointed to watch grounds maintenance and someone appointed to watch janitorial services need very different content even though the underlying COR rules are identical.
The CO cannot deliver a useful contract-specific training from memory. Before the session, the CO needs to sit down with the contract file and actually work through it. That means reading the PWS end to end, skimming the clauses for anything unusual, reading the QASP, reading the offeror's technical proposal if it was incorporated by reference, and making sure any attachments like wage determinations, government furnished property lists, or security requirements are fresh in the CO's mind.
A training built from an unread contract file will miss the things that actually matter on that contract. The requirements that get the COR in trouble are usually the ones buried in a performance standard on page 37 of the PWS, not the ones on the cover page.
Some content appears in every contract-specific training regardless of what the contract is for. It is the minimum viable set that makes the COR useful and keeps them out of trouble.
| Area | What the COR needs to walk away knowing |
|---|---|
| The contract basics | Contract number, contractor name, period of performance, total value, type of contract, and the place of performance. The COR should be able to answer these questions without looking them up. |
| Scope of work | What the contractor is obligated to perform, what the contractor is not obligated to perform, and how the COR recognizes the boundary. This comes straight from the PWS. |
| Performance standards | The measurable outcomes the government can hold the contractor to, where they live in the contract, and how the COR documents whether they are being met. |
| The surveillance plan | How and how often the COR is supposed to observe performance, what records to keep, and what tool to record them in. For most federal service contracts this is the SPM (Surveillance and Performance Monitoring) module inside PIEE, where the COR logs observations through smart forms like the COR Status Report, Contract Discrepancy Report, and Trip Report. |
| COR authority and boundaries | What the COR can do under their appointment in JAM (Joint Appointment Module, the PIEE module where the CO formally appoints CORs and stores their trainings) and, just as importantly, what the COR cannot do. Cannot direct new work, cannot change the scope, cannot commit the government to anything with cost, schedule, or performance impact. The COR routes those things to the CO. |
| Escalation path | Who the COR calls when something is off. Not a fuzzy "the contracting office," but a name, a phone number, and the fallback if that person is out. |
| Documentation standards | What gets logged, how often, and where. Dated observations, photos where appropriate, contractor responses, and anything the COR flags for the CO. |
| Red flags to report immediately | Safety issues, suspected fraud, personal conflict of interest, contractor performance that looks like a termination candidate, anyone asking the COR to do something outside the boundaries of their JAM appointment. |
This is the content that has to be in the training regardless of whether the contract is grounds maintenance, janitorial, or something more specialized. The next section is what changes when the contract type changes.
The core content is the same. The watchpoints, the standards, and the specific failure modes change completely based on what the contract is buying. A grounds maintenance training that gets poured into a janitorial COR's head will miss most of what actually matters. Part of preparing a contract-specific training is sitting with the PWS and asking, "What is the unique shape of this work, and what should the COR be looking at that they would not know to look at from the generic course?"
| Aspect | Grounds Maintenance | Janitorial | Transient Alert |
|---|---|---|---|
| Primary work rhythm | Seasonal and weather-driven. Heavy in growing season, light in winter. Single missed cut is visible for weeks. | Daily and weekly frequencies. Highly repetitive. Single missed service is visible the next morning. | On-demand response. Triggered by aircraft arrival, not a schedule. Response time is the main KPI. |
| Where performance is judged | Visual quality standards: turf height, edging lines, trash policing, bed condition, irrigation operation. | Cleanliness standards by area type: restroom, office, common area, with frequency tables in the PWS. | Aircraft servicing: marshaling, chocking, grounding, lav/potable water, towing, parking, fueling coordination. |
| What the COR walks | Randomized turf surveys, high-visibility areas like gate approaches and flagpole areas, irrigation checks after storms. | Surprise inspections at random buildings, bathroom and breakroom checks, after-hours verification. | Flight-line observations during actual transient ops, checklists tied to each aircraft movement. |
| Safety focus | Chemical handling, equipment operation, debris from mowing near vehicles and pedestrians. | Chemical handling, slip hazards, blood-borne pathogen response, after-hours building access. | Flight-line driving qualifications, FOD, hearing protection, proximity to running engines, explosives where applicable. |
| Likely customer complaints | "The grass is too tall," "they missed my building," "the sprinklers are running during the rain." | "The bathroom is out of paper," "the trash was not picked up," "the breakroom was skipped." | "The aircraft waited too long," "the lav truck was late," "the marshaller was not on the spot." |
| Typical contract structure | Firm fixed price with recurring services priced by month or acreage, plus an indefinite quantity line for extras. | Firm fixed price monthly recurring, with add/delete provisions for square footage changes. | Firm fixed price recurring with per-aircraft or per-movement variable components. |
The single most useful thing a CO can do in a contract-specific training is physically walk the PWS with the COR. Open the document, turn to the scope section, read the key paragraphs together, answer questions, move to the performance standards, read those together, and continue to the deliverables and any special conditions. The COR ends the session knowing where things are in the document and having heard the CO's voice on the parts that matter.
Summaries hide the language the COR will be held to. If the performance standard says the contractor will mow turf to a height of three inches plus or minus one-half inch during the growing season, the COR needs to have seen those exact words in the PWS, not a bullet that says "mow grass regularly." When a contractor later argues about acceptable tolerance, the COR is operating from the contract language rather than from a summary that softened it.
The Quality Assurance Surveillance Plan (QASP) is where the government records how it intends to watch the contractor. It identifies the performance objectives, the performance standards, the acceptable quality levels, the surveillance methods, and the frequency of surveillance. A well-built QASP gives the COR a direct answer to the question "what am I supposed to be looking at this week?"
In the contract-specific training, the QASP deserves its own block. Walk through the surveillance methods the QASP actually prescribes. If it says the COR will conduct random sampling of 10 percent of buildings on a monthly basis, the COR needs to know what that looks like in practice: how to generate the sample, how to record the results, how to calculate the acceptable quality level, and what to do when performance drops below the threshold.
The mechanics of the session matter more than the slide design. A few things that tend to work:
The training itself is not done until it is recorded in JAM. JAM is where the CO appoints CORs and where their trainings are stored, and a single COR typically has a running list of trainings in JAM across every contract they have been appointed to. The contract-specific training for this contract becomes one more entry on that list.
A short training record uploaded to JAM is usually sufficient. It should capture the contract number, the date of the training, who attended, the topics covered, and an acknowledgement from the COR that they understand their appointment and the boundaries of their authority. The COR and CO sign it and it goes into JAM attached to this COR's appointment for this contract.
At the annual review, the training record is one of the first things the CO verifies. The annual review itself is a structured smart form inside SPM called the Annual COR File Inspection Checklist. One of its required fields is "Assigned Duties Stated," and another is a set of signature dates that the checklist is looking for on the original training record. If the contract-specific training entry is missing or does not match the contract the COR was appointed to, that is a finding before the checklist can be fully completed.
The following is a slide-deck mockup of the contract-specific training a CO might deliver for a grounds maintenance contract. The fictional contract is Base Grounds Maintenance Services at Buckeye AFB, Contract FA4890-26-D-0012, awarded to GreenLawn Solutions for a one year base plus four one-year options at approximately $420,000 per year. Speaker notes are shown under each slide.
Five scenarios on contract-specific COR training. Pick the best answer and check it.
A new COR has just completed the DoD-required COR certification course and has been appointed to a base grounds maintenance contract. The CO schedules a contract-specific training session. What is that session supposed to accomplish that the certification course did not?
During the contract-specific training, the COR asks, "How am I supposed to know how often to walk the site and what to sample?" Which contract document gives the most direct answer to that question?
The grounds maintenance COR is walking the site when a building manager stops her and says, "While you are out here, can you tell the crew to also trim the hedges around my building? It would be faster than going through the contracting office." The COR wants to be helpful. What is the right response, and what should the contract-specific training have prepared her to say?
A CO built a solid contract-specific training deck for a grounds maintenance COR last month. This month he is appointing a COR for a janitorial contract and is thinking about reusing the same deck unchanged. Is that a good idea?
The CO is working through the annual review of a COR who has been on a grounds maintenance contract for nine months. The CO needs to confirm that the COR received contract-specific training at the time of appointment and verify what was covered. Where should the CO look for that evidence?