CPARS Evaluations for Software Companies: Ratings, the 14-Day Comment Window and Disputes

A software company’s first federal contract produces two things: the work, and a written record of how the government thought the work went. That record lives in CPARS, the Contractor Performance Assessment Reporting System, and evaluators on every later competition can read it. Most first-time contractors meet CPARS the day a notice lands in someone’s inbox with a short deadline attached.

This guide covers how CPARS evaluations work under FAR subpart 42.15: when agencies write them, what they rate, what the five ratings mean, how the comment window works, and how to dispute an evaluation you disagree with. It builds on our guide to past performance, which covers how evaluators use the record once it exists.

---

When agencies write an evaluation

FAR 42.1502 requires agencies to evaluate contractor performance on contracts and orders above the simplified acquisition threshold, with some exceptions in the rule. The evaluations are entered in CPARS.

Two kinds of evaluation matter for timing:

• Interim evaluations. For contracts with a period of performance longer than a year, evaluations are prepared at least annually. A multi-year SaaS subscription or development contract will collect several interim evaluations before it ends.
• Final evaluations. An evaluation is prepared when the work under the contract or order is completed.

The practical consequence is that your record builds year by year. A strong first year on a new contract produces a rating you can point to in the next competition, before the contract is finished.

---

What CPARS rates

FAR 42.1503(b) lists the evaluation factors. Each one that applies to the contract gets a rating and a narrative:

• Technical (quality of product or service). Does the software do what the contract requires? Are deliverables accepted the first time? For a software company this is usually the factor that carries the most weight.
• Cost control. How well did the contractor forecast and control cost? This factor is not used on firm-fixed-price contracts, which covers most commercial SaaS and license buys.
• Schedule or timeliness. Were releases, milestones and deliverables on time?
• Management or business relations. Responsiveness, communication, problem resolution, and management of subcontractors and teaming partners.
• Small business subcontracting. Where the contract carries a subcontracting plan, how well the contractor met its goals.
• Other. Any other area the agency identifies as relevant.

The evaluation also describes the contract itself, so a later evaluator can judge relevance: what was bought, at what size and complexity.

---

The five ratings

FAR 42.1503 sets out a five-level scale, applied to each factor:

Rating	What it generally signals
Exceptional	Performance meets requirements and exceeds many to the government’s benefit, with few minor problems and highly effective corrective action.
Very Good	Performance meets requirements and exceeds some, with some minor problems and effective corrective action.
Satisfactory	Performance meets requirements. Minor problems, if any, had satisfactory corrective action.
Marginal	Performance does not meet some requirements, and corrective action was not yet fully effective or implemented.
Unsatisfactory	Performance does not meet most requirements, and recovery is not likely in a timely manner.

Two things follow from the definitions:

1. Satisfactory is not a criticism. It means you met the contract. Many solid contractors carry mostly Satisfactory ratings, and evaluators know it.
2. Above Satisfactory needs evidence. A rating of Very Good or Exceptional requires the narrative to describe where you exceeded requirements and how that helped the government. If you want those ratings, give the assessing official the facts during performance, not after the draft arrives.

---

The 14-day comment window

FAR 42.1503(d) is the rule that catches new contractors out. When an evaluation is ready, the contractor receives a notice from CPARS, and it has up to 14 calendar days from that notification to submit comments, rebutting statements or additional information.

What that means in practice:

• The notice goes to a named person. The agency registers a contractor representative to receive CPARS notices, usually from the contact information on the contract. Make sure that person is current, checks that inbox, and knows the deadline matters.
• The clock is calendar days. Weekends and holidays count. A notice that arrives before a holiday week can leave very little working time.
• Silence is not agreement, but it is a lost chance. The evaluation becomes available to source selection officials whether or not you comment. Your comments are part of the record evaluators read alongside the ratings.
• Comments can be positive. If the evaluation is fair, a short comment that adds a fact the narrative left out, such as an uptime figure or an early delivery, still strengthens the record.

---

Writing a comment that helps

A CPARS comment is read by evaluators on later competitions who know nothing about your contract. Write for them.

• Respond factor by factor. Address each rating you disagree with separately, and say what rating you believe the facts support.
• Use evidence, not adjectives. Cite dates, acceptance records, release notes, emails from the program office, and service levels from the contract. “Delivered all 12 sprint increments on schedule; see acceptance memos dated…” is stronger than “performance was excellent.”
• Separate cause from fault. If a delay came from a government-caused change, late government-furnished information, or a stop-work order, say so and point to the document that shows it. Our guide to contract modifications covers how changes should be documented as they happen.
• Acknowledge real problems and their fixes. If something did go wrong, describe the corrective action and its result. The rating definitions turn on corrective action, so this is often the strongest argument you have.
• Stay professional. The comment becomes part of your record. Tone that reads as combative costs more than the rating you are disputing.

---

Disputing an evaluation

Comments are the first step. If you and the agency still disagree, the rule and the courts give you more.

Review above the contracting officer. FAR 42.1503(d) requires agencies to provide for review at a level above the contracting officer to consider disagreements between the parties. Ask for that review in your comments if you want it. The ultimate conclusion on the evaluation is a decision of the contracting agency.

A Contract Disputes Act claim. The Federal Circuit has held that a contractor can challenge a performance evaluation through a claim under the Contract Disputes Act (Todd Construction, L.P. v. United States, 2011). That route starts with a claim to the contracting officer and can end at a board of contract appeals or the Court of Federal Claims. Relief usually means a revised or withdrawn evaluation, not money. Our guide to contract claims and equitable adjustments covers how claims work.

Decide early which disagreements are worth pursuing. A Marginal or Unsatisfactory rating on a factor that matters to your next bids usually is. A Satisfactory you would have liked to see as Very Good usually is better handled with a strong comment and better evidence next year.

---

Who sees it, and for how long

• Not the public. FAR 42.1503 limits release of a completed evaluation to government personnel and the contractor being evaluated while it can be used for source selection. Competitors cannot read your CPARS record.
• Source selection officials. Evaluators across agencies can read it when they assess past performance on a later procurement.
• Three years. Past performance information is not used in source selection more than three years after completion of contract performance, or six years for construction and architect-engineer contracts. For a software company, that sets the useful life of a strong rating, and the time a weak one takes to age out.

Some related records, such as terminations for cause or default, are also reported to the Federal Awardee Performance and Integrity Information System (FAPIIS). Our guide to responsibility determinations covers how contracting officers use that information.

---

A CPARS checklist for software companies

• Name the right contractor representative on every contract, and keep the contact current when people change roles.
• Calendar every evaluation. Interim evaluations recur at least annually; expect them and plan for the 14-day window.
• Keep a performance file as you go. Acceptance records, release notes, uptime reports and program office emails are your evidence when the draft arrives.
• Tell the program office what went well, during performance. The assessing official writes from what they know.
• Document government-caused delays when they happen, not when the evaluation is drafted.
• Comment on every evaluation, even the good ones, with facts the narrative left out.
• Read the current rule text. The FAR is being rewritten under the Revolutionary FAR Overhaul, so section numbers and wording may move. Check your contract and get advice from counsel on a specific dispute.

---

The short version

• CPARS is the government’s record of how you performed, and evaluators on later competitions read it.
• Agencies write evaluations at least annually on longer contracts and at completion, for contracts and orders above the simplified acquisition threshold.
• Five ratings, each with a narrative: Exceptional, Very Good, Satisfactory, Marginal, Unsatisfactory. Satisfactory means you met the contract.
• You have up to 14 calendar days to comment, and the evaluation becomes available to evaluators whether or not you do.
• Disagreements go to review above the contracting officer, and an evaluation can be challenged through a Contract Disputes Act claim.

---

Where this fits

Past performance is one of the categories federal buyers review, alongside registration, security and compliance. A strong CPARS record shows a customer was satisfied. It does not show that a self-attested compliance claim has been independently verified, and buyers treat those as separate questions. Score your company’s federal readiness to see how your company looks across the categories buyers check.

---

Related reading

• Past Performance for Software Companies: CPARS, References and Building a Record
• Contract Claims and Requests for Equitable Adjustment for Software Companies
• Contract Modifications for Software Companies
• Contract Closeout for Software Companies
• Recompetes and Incumbent Transitions for Software Companies