A rejected FCP Catalog Baseline is not something you redo. The fix runs through a separate correction modification, and until that correction is accepted it is the only modification you can file on the contract. The goal is to recover in one cycle, which means diagnosing the actual defect rather than patching the symptom GSA reported.
Why can't you just resubmit a rejected baseline?
Because the baseline is a one-time migration action, not a recurring filing. Once it has been submitted and processed, the record exists. Changing it is a correction to that record, which is its own modification type — and the freeze on all other modifications stays in force until the correction clears.
This is the structural fact that makes a rejection expensive. With an ordinary modification, a rejection costs you the fix and a new queue position. With a baseline, it costs you that plus continued paralysis on everything else.
- You cannot: withdraw the baseline and start over as though it never happened
- You can: file a correction modification addressing the specific defects
- You still cannot: file anything else — SIN additions, price increases, new services — until the correction is accepted
How do you read what GSA actually rejected?
Separate the reported error from the underlying defect. The validation engine reports where it stopped, which is often downstream of what actually went wrong. Patching the reported field without finding the cause produces a second rejection on a different field.
A worked example. The engine reports a rate mismatch on one labor category in option year three. The instinct is to correct that one cell. But if the cause is a pricing workbook built from an internal rate sheet rather than the award document, that same drift is sitting in every other category — and the engine only reported the first one it hit.
Fix the cell and you resubmit into a second rejection. Fix the source and you resubmit once.
- Read the full error report, not just the first line. Multiple errors often share one root cause.
- Categorize each error as structural (formatting, precision, missing periods) or substantive (rates or names that disagree with the award).
- For every substantive error, check whether the same defect exists elsewhere in the file. It usually does.
- Rebuild from the award document rather than editing the rejected file, when more than a couple of substantive errors appear.
When I was a Contracting Specialist at GSA reviewing these, the corrections that came back clean were the ones where the contractor had clearly gone back to source. The ones that bounced twice were always spot-fixes to the specific cells we had flagged.
What belongs in the correction modification package?
The corrected file, and a short narrative that tells the reviewer exactly what changed and why. The narrative is optional in the sense that nothing requires it, and valuable in the sense that it routinely saves a review cycle.
| Element | Purpose |
|---|---|
| Corrected Services Plus File | The substantive deliverable |
| Change narrative (one page) | Tells the reviewer which fields moved and on what authority |
| Reference to the award and modifications relied on | Shows the corrected rates trace to the actual award |
| Confirmation the defect class was swept | Preempts the question of whether the same error remains elsewhere |
That last row is the one that earns its keep. If GSA flagged a precision error in three categories, say explicitly that you corrected precision across all categories, not only the three flagged. Otherwise the reviewer has to check, and checking takes time you are paying for in freeze days.
What are the most common causes of a baseline rejection?
Almost always a mismatch between the file and the award as modified. The file is internally consistent and plausible — it simply does not match what GSA awarded.
- Rates from an internal price list rather than the award plus every accepted modification.
- Decimal precision carried at two places instead of four.
- Missing option periods, particularly unexercised out-years.
- Labor category names that were tidied up somewhere between award and workbook.
- Live formula cells that display a number and carry an expression.
- SCLS coverage flags inconsistent with the award's wage determination matrix.
Across our 70+ proven GSA contract awards, I have never seen a baseline rejected for a reason that could not be traced back to the file disagreeing with the award document. The engine is not arbitrary. It is comparing two things, and one of them is wrong.
How do you keep a rejection from becoming three rejections?
Reconcile the entire file against the award before resubmitting, not just the flagged fields. A rejection is evidence that your source data is wrong somewhere. Treat the reported errors as a sample, not a complete list.
The discipline that works:
- Pull the award document and every accepted modification into one stack.
- Build a single reconciled rate table from that stack — this becomes the source of truth.
- Rebuild the pricing file from the reconciled table rather than editing the rejected file.
- Convert all pricing cells to static values.
- Verify precision, option-year coverage, name matching, and SCLS flags across every row.
- Submit the correction with a narrative naming what changed.
Step three is the one people resist, because editing feels faster than rebuilding. It is faster, right up until the second rejection.
What Should You Do Now?
- Read the entire error report and group errors by root cause, not by the field GSA named.
- Assume every substantive error is systemic until you have checked the rest of the file and proven otherwise.
- Rebuild from the award document when you find more than a couple of substantive errors. Spot-fixing the flagged cells is how one rejection becomes three.
- Include a one-page change narrative stating which fields moved, on what authority, and that you swept the whole file for the same defect class.
- Do not queue anything else behind it. Until the correction is accepted, it is the only modification you can file.
- Work the correction in catalog.gsa.gov and keep the GSA Vendor Support Center guidance open alongside it.
- Fix the source, not just the file. If your internal rate sheet drifted from the award, update it — otherwise the next modification repeats the problem.
I spent eighteen years in federal acquisition as a Contracting Specialist and Contracting Officer at GSA, IRS, DoD, DOI, HHS, FTC, and Energy, with FAC-C Level III certification and a Master of Liberal Arts from Harvard University. If your baseline came back rejected and you would rather not spend another cycle guessing, Blackfyre's flat-fee FCP Baseline service takes the file and works it through to acceptance. If you are on the ongoing GSA Maintenance plan, baseline work and the modifications that follow it are included.
Frequently Asked Questions
Can I withdraw a rejected FCP Baseline and start over?
No. The baseline is a one-time migration action, so once it has been processed the record exists. Changes run through a separate correction modification rather than a fresh submission.
Can I file other modifications while the correction is pending?
No. Until the baseline is accepted, the correction modification is the only filing permitted on the contract. SIN additions, price adjustments, and new services all continue to wait.
Does GSA tell me everything that is wrong with the file?
It tells you what the validation engine flagged, which is not necessarily everything that is wrong. If a defect is systemic, the engine may report it on the first rows it encounters. Treat the report as a sample and check the whole file.
Should I edit the rejected file or rebuild it?
Edit it for one or two isolated structural errors. Rebuild from the award document when you find substantive rate or naming errors, because those almost always indicate the source data was wrong rather than a single cell.
Is a change narrative required with the correction?
Nothing requires it. It routinely saves a review cycle, because it tells the reviewer which fields changed, on what authority, and whether you swept the rest of the file for the same defect — questions they would otherwise have to answer themselves.
What is the most common cause of rejection?
The pricing file disagreeing with the award as modified. Usually the rates came from an internal price list that drifted from the award over several modifications, so the file is internally consistent but does not match what GSA actually awarded.