The Contractor Performance Assessment Reporting System is the federal government's central database for past performance records. Every contract above the simplified acquisition threshold — currently $250,000 — is supposed to generate a CPARS evaluation at least annually and at final completion. Those evaluations are visible to source selection officials across all federal agencies. They follow your firm for three years from the date of final evaluation.
Most small government contractors understand this in theory. Fewer understand how ratings are actually assigned, what the rating categories mean in practice, or what levers they have when a rating is unfair. That gap is expensive. A single "Satisfactory" rating in a category where your competitors have "Very Good" or "Exceptional" ratings can be the difference between winning and losing a best-value evaluation.
How the rating scale actually works
CPARS uses a five-point scale: Exceptional, Very Good, Satisfactory, Marginal, and Unsatisfactory. There is also a Not Applicable category for areas where the contractor had no relevant performance obligations.
The practical reality is that the middle of this scale is not neutral. "Satisfactory" does not mean "did a good job." It means the contractor met the minimum requirements of the contract. In a competitive evaluation, a Satisfactory in any significant category — quality, schedule, cost control, management — will generally score lower than a competitor with Very Good or Exceptional in the same area. This is a mathematical reality of best-value evaluation, not a matter of opinion.
"Very Good" is the baseline competitive rating. It means the contractor exceeded requirements in some meaningful way. If you are consistently receiving Very Good ratings and some competitors have Exceptional, you are in the second tier on past performance scoring.
"Exceptional" is reserved for performance that, by the FAR definition, significantly exceeded contract requirements and demonstrated behaviors that a contracting officer would specifically want to call out. It requires justification. Not every Contracting Officer Representative will write Exceptional even for genuinely exceptional performance, because Exceptional creates additional documentation obligations. This is worth understanding.
Who writes your ratings and when
The Contracting Officer Representative (COR) assigned to your contract is typically the primary author of CPARS evaluations. On larger contracts, multiple individuals may contribute. The Contracting Officer reviews and approves the assessment before it is finalized.
Evaluations are supposed to be completed within 120 days of the end of the evaluation period (annually or at completion). In practice, they are often late. A COR who is overworked, transitioning off the program, or simply not paying attention to CPARS deadlines may submit evaluations late or with less detail than they should contain.
You will receive an automated notification when a CPARS evaluation is submitted for your firm. You have 14 calendar days to review the evaluation and submit a contractor comment. This window is critical. If you miss it, you can still submit a comment later, but you lose the ability to flag the evaluation for review during that initial window.
The categories you will be rated on
Standard CPARS evaluations cover five areas, though not all apply to every contract type:
Quality of product or service. Whether the work met the technical requirements of the contract and the quality standards specified in the statement of work. This is the most weighted category in most source selections.
Schedule. Whether deliverables were provided on time and whether the contractor managed schedule risks proactively. A single late deliverable that was communicated in advance and mitigated is treated very differently from a pattern of missed deadlines discovered by the COR at the last minute.
Cost control. Primarily relevant on cost-reimbursement contracts. Whether the contractor managed costs against the approved budget, identified overruns early, and managed the contract to completion within negotiated amounts.
Business relations. The quality of communication, responsiveness to contracting officer requests, accuracy of administrative deliverables (invoices, reports, certifications), and general professionalism. This category is more subjective than the others and more dependent on the relationship your day-to-day team has built with the COR.
Management of key personnel. Applicable when the contract designates key personnel by name. Whether the contractor maintained the approved personnel, managed substitutions according to the contract requirements, and ensured continuity of knowledge during transitions.
How to position for a strong rating during performance
The time to manage your CPARS rating is not after the evaluation is submitted. It is throughout the period of performance. Several behaviors reliably produce stronger ratings.
Document everything that exceeds requirements. When your team delivers something ahead of schedule, captures a cost savings the government wasn't expecting, or solves a technical problem that wasn't in scope, write it up and send it to the COR. A concise summary email — "This week the team completed X ahead of the October milestone. I wanted to flag this in writing" — creates the paper trail that a conscientious COR will reference when writing the evaluation. A COR who has to reconstruct twelve months of performance from memory will produce a less accurate evaluation than one who has your summary emails to refer to.
Surface problems before the government finds them. A problem you disclose early, with a plan to resolve it, is a business relations positive. The same problem discovered by the COR is a quality or schedule negative. The difference in the CPARS record can be significant.
Ask for interim feedback at six months on annual contracts. A brief meeting with the COR to ask "how are we doing and is there anything we should be doing differently" accomplishes two things: it gives you time to correct course before the evaluation period closes, and it signals a level of professionalism and accountability that CORs notice.
What to do when a rating is unfair
CPARS provides a contractor comment mechanism specifically because COR assessments are not always accurate. If you receive a rating that you believe is wrong — factually incorrect, inconsistent with prior feedback, or based on requirements that were never clearly communicated — you have options.
First, submit a contractor comment. This is visible to every source selection official who reads the evaluation. A well-written contractor comment that cites specific facts — delivery dates, correspondence, approved contract modifications — creates context that any reasonable evaluator will factor into their assessment. A vague complaint does not. Be specific, professional, and factual. Do not express frustration or make accusations.
Second, within the 14-day review window, you can formally request a review of the evaluation by the contracting officer. This escalates the dispute through the CPARS system and triggers a formal response. The contracting officer can modify the evaluation if the contractor's objection is supported. This process works best when the dispute is factual — a rating of "late on deliverables" that you can rebut with documented approval of a schedule extension, for example.
Third, maintain your own documentation. Government email systems are imperfect. COR turnover happens. Having your own organized archive of performance documentation, correspondence, and COR feedback gives you the evidence base to support a contractor comment if a rating comes in that does not reflect the actual performance record.
Checking your own record
You can view your firm's CPARS record through the CPARS portal at cpars.gov using your DUNS or UEI number. Review it annually. Look for evaluations that are factually inaccurate and have not received a contractor comment. Look for evaluations where the narrative text is thin — a rating of "Very Good" with no supporting narrative is less useful to a source selection evaluator than a "Very Good" with specific examples, and some CORs default to minimal documentation.
If you find evaluations you cannot access — contracts where an evaluation should exist but does not appear — contact the contracting agency directly. Missing evaluations are more common than they should be, and an absent record for a strong contract is a missed opportunity.