Past performance and CPARS

What past performance is used for

It is a risk assessment, not a reward for loyalty.

Evaluators use past performance to predict whether you will deliver this contract successfully. They look for work that is recent, relevant in scope and scale, and delivered well. Relevance usually matters more than volume: three closely comparable projects beat twenty loosely related ones.

The assessment is separate from technical merit. A strong technical approach with a weak delivery record reads as risk, and under a trade-off evaluation that can lose to a slightly weaker approach from a bidder with a clean record.

There is also a distinct concept worth knowing. Responsibility is a separate determination a contracting officer makes about whether you have the financial resources, capacity, integrity, and record to perform at all. It is pass or fail, made before award, and a poor performance history can affect it independently of how your proposal scored.

How CPARS records get made

The government writes them, and you get a short window to comment.

The Contractor Performance Assessment Reporting System holds performance evaluations for United States federal contracts above defined thresholds, with lower thresholds for construction and architect-engineer work. Assessments are prepared at least annually and at the end of the contract, by the government official responsible for the work.

When an evaluation is drafted, your designated representative is notified and has a limited window to review it and submit comments before it becomes available for source selection. That window is short, measured in days rather than weeks, and it is the main opportunity you have to put your side on the record. Missing it because the notification went to a departed employee’s inbox is a common and expensive mistake.

Ratings are assigned across areas including quality, schedule, cost control, management, small business subcontracting where applicable, and regulatory compliance, each with a narrative justification. The narrative frequently matters more than the rating word, because future evaluators read it.

• Prepared at least annually and at contract end
• Rated across quality, schedule, cost, and management
• Short comment window before the record is released
• Narrative text is read by future evaluators

What each rating level signals

Satisfactory means you did what you agreed to do.

The scale runs from exceptional through very good, satisfactory, marginal, and unsatisfactory. Satisfactory means performance met contract requirements, which is what the contract asked for and is not a criticism. Ratings above it require performance that exceeded requirements in ways the assessor can describe, which is why the higher ratings need evidence rather than goodwill.

Marginal and unsatisfactory ratings carry real consequences in future competitions and can affect a responsibility determination. They are also the ones most worth responding to in the comment window, particularly where the narrative attributes to you a delay or cost issue that arose from a government-caused change.

Aim for accuracy rather than flattery. A satisfactory rating with a specific, factual narrative describing comparable work at the right scale can be more useful in a future bid than a very good rating with two vague sentences.

Responding to a draft rating

Comment on the facts, and do it inside the window.

When a draft evaluation appears, read the narrative before the rating. Check dates, quantities, the description of what was delivered, and whether any delay or overrun was caused by a government change, a late government-furnished item, or a scope modification. Those are the correctable errors.

Write comments as a factual record, not an argument. Reference the modification number, the correspondence date, the accepted deliverable. A comment saying the rating is unfair persuades nobody. A comment noting that the schedule slip followed a stop-work order issued on a specific date, and that performance resumed and completed within the revised schedule, changes how a future evaluator reads it.

Where you and the assessing official genuinely disagree, there is a review process at a level above the assessor. Use it for material disputes rather than for wording preferences, and keep in mind that your comments become part of the permanent record alongside the rating.

Building a record from nothing

No record is not the same as a bad one.

A company with no relevant past performance generally cannot be evaluated favourably or unfavourably on it, which means you are not being penalised so much as failing to score. The strategy is to become evaluable as quickly as possible.

Subcontracting is the most direct route. Work performed as a subcontractor is real experience, and many solicitations permit past performance from subcontracted work or from proposed team members, provided the relationship is described honestly. Commercial and state or local work is often accepted where it is genuinely comparable, so read what the solicitation actually allows before assuming it does not count.

Meanwhile, run every contract as if it is being written up, because it is. Keep contemporaneous records of deliverables, acceptance, and any government-caused change. Ask for a reference letter while the work is fresh and the contact is still in post. Small contracts under the CPARS threshold produce no automatic record at all, so the reference you gather yourself is the only evidence that will exist.

• Subcontracted work counts as experience
• Commercial and state work is often admissible
• Gather references while contacts are still in post
• Below the reporting threshold, your own records are all there is

Canada and other buyers

No single national database, and more weight on your own references.

Canadian federal procurement has no direct equivalent of CPARS as a government-wide database that follows a supplier across departments. Performance is more often assessed through references supplied with the bid and evaluated against stated criteria, alongside departmental vendor performance management processes that operate within particular buying organisations.

That shifts the burden onto you. The reference contacts you name, the projects you can describe with specifics, and the documentation you kept are the evidence. Solicitations commonly set rules about how recent a project must be, what scale counts as comparable, and whether the reference must be reachable, and those rules are frequently applied as mandatory criteria.

Provincial, municipal, and broader public sector buyers vary further, and some maintain their own supplier performance records or vendor lists. In every case, the practical habit is the same: keep a current, structured library of your projects with dates, values, scope, outcomes, and confirmed reference contacts, so a bid does not start with an archaeology exercise.