The annual COR review happens inside a structured smart form that PIEE calls the Annual COR File Inspection Checklist. The CO opens it from the COR Surveillance and Oversight view of the contract, fills in a set of required fields, attaches supporting documents, signs it with a password, PIN, or one-time password, and submits. The completed checklist lives in the COR Documents section of the contract's SPM record and shows up on the portfolio-level dashboards the contracting office runs.

Because the form has required fields, the review has a floor. A CO cannot accidentally produce a review that leaves signatures, dates, or the item-reviewed narrative blank. And because submission auto-notifies the COR, the QAPOC, and the ACO, the review generates its own communication instead of waiting on a separate email chain.

JAM and SPM each hold half of what the annual review is checking. JAM is where the appointment itself lives: the designation letter, the training records, the supervisor acknowledgement, and any termination or modification of the appointment. SPM is where the surveillance activity lives: the Status Reports the COR posted, the Correspondence Reports, the Contract Discrepancy Reports the COR raised, the Trip Reports, and any Memorandum for the Record the CO or QAPOC logged against the file.

The Checklist itself is an SPM smart form, but SPM pulls most of the JAM side in as read-only context: Appointment Info, Designation Letter, Termination Letter, Certifications. The CO does not retype any of it. They verify that what JAM is showing matches the current state of the contract and of the COR's training, then enter what the form asks for and make the call on the surveillance side.

The form is short on the page but specific about what it wants. The required fields set the shape of the review:

• Month and Year of review. Anchors the record in time and lines the review up with the appointment anniversary.
• Appointment From Date and Appointment To Date. Pulled directly from the JAM designation letter. The CO confirms these still match the contract period and any modifications that changed the scope.
• Assigned Duties Stated. A confirmation that the duties in the designation letter still describe what the COR is actually doing on this contract.
• Date Signed by COR, Date Signed by Supervisor, Date Signed by CO. The three signatures on the original designation letter, verified as on file in JAM.
• Signed by Contractor. Confirmation that the contractor counterpart received and acknowledged the COR letter.
• Item Reviewed. The working narrative of the review. The CO lists which SPM records and JAM documents were pulled, what they saw, and what they concluded. This field carries the body of the review.
• System Access and Documents. Confirmation that the COR still has the PIEE, EDA, and WAWF access the contract requires.
• Attachments. Up to 24 MB of supporting documents per submission. Typical contents include the designation letter, the training certificate, and copies of the SPM entries the CO used as the review sample.
• Signature. Password, PIN, or one-time password from the CO before submission.

The Checklist is faster to fill in after a short preparation pass. Ten to fifteen minutes per COR, in roughly this order:

• Pull the COR Surveillance File view for the contract. This is the read-only full-file view in SPM that stitches JAM and SPM together in one place. Everything the CO is about to check is visible here.
• Confirm the appointment is still valid. Active designation letter, no pending termination, contract still inside the period of performance.
• Confirm training currency. Baseline certification and the contract-specific training from Topic I-16 should both be uploaded and current. If the contract has been modified in ways that changed the duties, a refresher should also be on file.
• Confirm the COR is still the person in the job. Reassignments, retirements, and role changes that nobody updated in JAM are common and are always a finding.
• Pull the Status Reports for the review period. Look at cadence first, then content. A later section walks the patterns worth watching for.
• Check for any Contract Discrepancy Reports or Correspondence Reports the COR raised. These are the escalations, and they tell the CO whether the COR is handling routine things directly and raising real problems in writing.

Before walking any individual COR file, the contracting office has a portfolio view that makes review season manageable. SPM's Administrative Reports area runs on EDA / Advana / Kibana dashboards, and three of them carry most of the work:

• COR Document Status. A roster of every active contract with a dedicated Annual COR Review column. The CO sees at a glance which reviews are current, which are due this month, and which are overdue. Reviews already on file show the submission date.
• COR Management. The full COR roster across the portfolio with appointment dates, contract numbers, and designation letter status. This is how the CO catches appointments that belong to CORs who no longer work in the office.
• SPM COR Training. Training records by course, completion date, and certificate file. The CO can confirm baseline certification currency across the whole portfolio in one pass before drilling into individual files.

A CO with twenty active contracts can run these three reports in five minutes at the start of the month, see which three or four reviews are due, and schedule them on the calendar. That rhythm keeps the annual review from collapsing into a twenty-review sprint at the end of the year.

A year of Status Reports usually has a shape. The shape matters as much as any individual entry, and a handful of patterns show up often enough to have names.

Findings are only useful if the CO writes down what they are doing about them. The response depends on the nature and severity of the gap, and a rough proportion guide helps:

• Minor administrative gap. Missing training record, stale appointment that needs a quick update, a signature line the COR never completed. The CO notes it on the Checklist, fixes it in JAM during the review, and moves on.
• Cadence slipping. The COR started strong and drifted. A one-on-one conversation, a reset of expectations, a note in Item Reviewed, and a calendar follow-up in 60 to 90 days to confirm the cadence recovered.
• Training gap. The COR either never received the contract-specific training or needs a refresher because the contract changed. Redeliver the training, upload the new record to JAM, note the corrective action on the Checklist.
• Sustained performance gap. Empty SPM, repeated patterns, a COR who is clearly not doing the work. A written expectations reset with specific corrective actions and a deadline, copied to the COR's supervisor. The Checklist captures the finding and the action.
• Authority violation or safety issue. A COR who has been directing work, accepting unauthorized deliverables, or ignoring safety concerns does not get coaching first. The CO documents the finding, terminates the appointment in JAM, and the contracting office appoints a new COR. The Checklist records the decision.

Once the Item Reviewed narrative is written and the attachments are in place, the CO submits the form with a password, PIN, or one-time password. SPM then does several things in sequence:

• Auto-notifies the COR, the QAPOC, and the ACO that the Checklist has been submitted. This substitutes for the "I sent you the review memo" email the CO would otherwise have to write.
• Files the Checklist in the COR Documents section of the contract's SPM record.
• Updates the COR Document Status dashboard so the portfolio view flips from "due" to "submitted" with the date.
• Makes the Checklist visible in the COR Surveillance File view alongside the JAM designation letter and the SPM smart forms the COR created during the year.

Next year, the first thing to open is last year's Checklist. If last year's Item Reviewed flagged a cadence problem with a 60-day follow-up, this year's review opens by checking whether that follow-up happened and whether the cadence held. That continuity is the thing a smart form gives the review that a Word document never did.