Refresh 32 offer-package check
What Refresh 32 means for the working file
For offer teams, Refresh 32 is less about memorizing every clause change and more about making sure the working package is current. The supplied solicitation and SF30 attachment identify Refresh Number 0032, with a June 4, 2026 creation date.
That matters because the document set, templates, and required checklist are the materials the team will actually touch. A good Refresh 32 workflow starts by downloading current files and retiring old copies from active drafting folders.
FCP is now the pricing center of gravity
GSA's required-template page lists the FCP Product File and FCP Services Plus File as required price proposal templates. In practical terms, the old phrase 'price proposal template' still helps people understand the job, but the actual current work depends on whether the offering is product, service, or both.
For products, the workbook centers on item identity, manufacturer data, SIN, descriptions, options, accessories, unit of measure, and commercial/GSA pricing. For services, the Services Plus File centers on labor/service titles, descriptions, qualifications, geographic and performance assumptions, prices, and reporting identifiers.
Do not skip the narrative inputs
The official GSA required-template page notes that certain technical proposal factors are completed in eOffer narrative fields, not by uploaded documents. That means a beautiful upload package can still be incomplete if the narrative responses are thin.
The practical move is to build a two-column map: upload documents on one side, eOffer narrative inputs on the other. Both sides need ownership before submission.
What this looks like in practice
Offer roomTreat Refresh 32 like a clean-room package build
Start a fresh working folder for the current refresh, even if you have older templates from a prior attempt. Put the solicitation, SF30 attachment, required-template page, checklist, FCP files, pricing terms, and category attachments in one place.
Then mark each file as current, conditional, or not applicable. This avoids the classic GSA problem: a team works hard from an old workbook and only discovers the mismatch when eOffer review starts asking questions.
- Current official source
- Owner
- Required or conditional
- Matches pricing story
- Ready for upload
Reviewer lensThe upload tab is really a proof table
The document list is not random. Financial documents prove responsibility, pricing files prove the offer, letters prove supply-chain authority, past performance proves delivery history, and compliance documents prove the offer can be awarded and maintained.
Frequently asked questions
Should I reuse older GSA offer templates for Refresh 32?
Use older files only as references. For active drafting, download current files from GSA or SAM.gov so the workbook structure, instructions, and required tabs match the current refresh.
Does Refresh 32 replace the Refresh 31 TDR changes?
No. Refresh 31 remains the key TDR expansion anchor. Refresh 32 sits after it, so the offer team should understand both the current template package and the TDR operating model.
What should I check before uploading documents in eOffer?
Check that each upload has a proof role, current source, owner, clean filename, correct required/conditional status, and no contradictions with pricing or narrative entries.