An offeror with a strong company and clean paperwork watched their GSA offer stall for months. Not over capability. Over pricing. The contracting officer kept asking for support they had not provided, and every round added weeks. Pricing review is where the most prepared-looking offers quietly die, and in 2026 the rules underneath it changed.
GSA rejects or delays pricing on Schedule offers when an offeror cannot adequately support that its proposed prices are fair and reasonable, when documentation is incomplete or inconsistent, or when labor rates lack a defensible basis. After Refresh 31 moved all MAS contracts to Transactional Data Reporting and eliminated the old Price Reduction Clause framework, the evaluation leans even more on clean, well-supported pricing data rather than legacy commercial-pricing comparisons.
What Does “Fair and Reasonable” Actually Mean to GSA?
Fair and reasonable means GSA is satisfied that the price the government will pay is justified by evidence, not just asserted by the offeror. It is the central test every Schedule offer’s pricing has to pass.
What sits behind the phrase:
- It is evidence-based, not a number you pick. GSA wants to see why your price is what it is, supported by data a reviewer can check.
- It is comparative. Reviewers look at your pricing against relevant benchmarks: your own commercial sales, comparable offerings, and market data.
- It is contract-long. GSA is approving prices you will have to defend for years, not just at award. Pricing that cannot hold up over time invites scrutiny.
- It shifted with Refresh 31. With TDR mandatory and the PRC framework gone, the supporting logic moved away from tracking a Basis of Award customer and toward clean transactional and commercial pricing support.
If you cannot explain, with documentation, why your price is justified, you have not met the standard, no matter how reasonable the number feels.
What Are the Most Common Reasons GSA Rejects Pricing?
Most pricing rejections come down to support, consistency, and defensibility, not the prices being outrageous. The number is rarely the problem. The justification is.
The recurring culprits:
- Insufficient pricing support. The offeror states prices but does not back them with the sales data, invoices, or documentation GSA needs to verify them.
- Inconsistent documentation. Numbers that do not match across the offer, between the price proposal and supporting files, or against the offeror’s own commercial records.
- Weak labor-rate basis. For services, labor category rates without a clear, defensible basis of estimate tying them to actual costs, qualifications, and commercial practice.
- Pricing that cannot be benchmarked. Offerings unique enough that the reviewer cannot find a comparison, with no narrative explaining the value.
- Stale or mismatched data. Support that does not reflect current commercial pricing or that contradicts what is in the federal systems.
Notice the pattern: every one is a documentation and defensibility failure, which means every one is preventable before you submit.
If your offer is service-based and your labor rates rest on “this is what we charge” rather than a documented basis, that is the gap reviewers catch, and an application review pressure-tests your pricing file before GSA does.
Why Is Service-Company Pricing Harder to Get Approved?
Because services lack the clean unit-price comparison that products have, so a service offeror has to build the justification that a product price carries on its face. This is where most service offers struggle.
The specific challenges:
| Products | Services |
| A unit price compares directly to commercial sales of the same item | Labor rates must be justified by category, qualifications, and basis of estimate |
| Catalog and invoices provide ready support | Support is assembled from rate build-ups, payroll data, and prior contracts |
| Benchmarking is straightforward | Comparable labor categories require mapping and explanation |
For services, the fix is a clean rate build-up: each labor category tied to a defined role, real qualification requirements, and a documented basis showing the rate reflects actual commercial practice. Reviewers approve what they can follow.
How Do You Pass Pricing Review the First Time?
You submit a pricing file that answers the reviewer’s questions before they ask them: complete support, internal consistency, and a defensible basis for every rate. The goal is zero rounds of clarification, because each round is weeks you do not get back, especially with GSA’s stretched staffing in 2026.
What a first-pass pricing file looks like:
- Every price is supported. Sales data, invoices, or a documented build-up backs each number a reviewer will check.
- Everything reconciles. The price proposal, supporting files, and your commercial records tell the same story with no contradictions.
- Labor rates have a basis of estimate. For services, each category is tied to role, qualifications, and a defensible rate derivation.
- It reflects the post-Refresh 31 framework. Your support aligns with TDR-era expectations rather than legacy PRC-based commercial-pricing logic.
- It anticipates the obvious questions. Where a price looks unusual, a short narrative explains it before the reviewer has to ask.
The contractors who clear pricing review fast are not the ones with the lowest prices. They are the ones whose file leaves nothing for the reviewer to chase.
Our Take
Pricing review is where optimism meets evidence, and optimism loses. Offerors spend weeks perfecting their capability narrative and then treat pricing as a spreadsheet to fill in at the end, which is exactly backward. Pricing is the part GSA scrutinizes hardest and the part most likely to send your offer into months of back-and-forth. After Refresh 31, the contractors who win the review are the ones who build the pricing file like a case they have to prove, support, consistency, and a defensible basis for every rate, rather than a number they hope clears. Get that right before you submit and you skip the slowest, most frustrating phase of the entire process. Building that defensible file from the start is precisely what GSA Verticalization™ is designed to do.
Frequently Asked Questions
How does GSA evaluate my pricing during the offer review?
GSA evaluates whether your proposed prices are fair and reasonable, meaning supported by evidence such as your commercial sales data, comparable offerings, and market benchmarks. After Refresh 31, the review relies on clean transactional and commercial pricing support rather than the old Price Reduction Clause framework.
What is the most common reason GSA rejects a pricing submission?
Insufficient or inconsistent support. Offerors state prices without adequate documentation to verify them, or their numbers do not reconcile across the proposal and supporting files. For services, weak labor-rate justification is a frequent cause.
What does “fair and reasonable” pricing mean for a GSA Schedule?
It means GSA is satisfied, based on evidence, that the government’s price is justified, not just that the offeror says it is reasonable. Reviewers compare your pricing to benchmarks and expect documentation that holds up over the life of the contract.
Do I still need a CSP-1 after Refresh 31?
Refresh 31 made TDR mandatory and removed the Price Reduction Clause framework, changing how pricing support works. Confirm the current commercial sales practices requirements for your specific offer, since the documentation expectations shifted with the move to TDR.
How do I support my labor rates in a GSA Schedule offer?
With a defensible basis of estimate: tie each labor category to a defined role and qualifications, and derive the rate from real cost and commercial-practice data. A clean rate build-up that a reviewer can follow is what passes review.
Pass Pricing Review Before It Costs You Months
Pricing is the slowest, most frustrating phase of getting on the Schedule, and it is the one most within your control before you submit. A file that leaves questions open invites months of clarification rounds, made worse by GSA’s stretched 2026 staffing. A file that answers them clears.
An application review pressure-tests your pricing the way a contracting officer will: checking support, reconciling your numbers, and stress-testing your labor-rate basis, so the version GSA sees is the version that passes.
→ Start Your Application Pricing Review
The cost of a weak pricing file is not rejection. It is the months you spend fixing it one CO question at a time.
