GSA published MAS Solicitation Refresh 32, along with an upcoming mass modification that Schedule contractors must accept within 30 days after issuance.
This post is provided for informational purposes only. We highly recommend reviewing the original GSA materials, including the final MAS Refresh 32 solicitation, mass modification, attachments, webinar slides, and Q&A, before accepting the mass modification, submitting an offer/modification, updating catalog files, or taking any compliance action. GSA’s final published documents control.
Key contractor takeaways
SIN-specific changes
Refresh 32 includes several SIN-level updates, including:
- retirement of SIN 311423 Non Perishable foods
- updates to SIN 532310 Rental and Leasing of Hardware Store Products
- creation of SIN 518210GM Grants QSMO Marketplace
- revisions affecting Health IT, Canine services, PACS, and Environmental Consulting SIN language
Important update: proposed Joint Venture changes have been removed from Refresh 32. GSA indicated that any JV-related updates will be addressed in a future refresh with advance notice.
End-of-Support (EOS) becomes a catalog risk area
For product contractors, GSA is adding stronger language around obsolete ICT products, EOS dates, and availability of security updates. If an item appears obsolete or has a projected EOS date of three years or less, GSA may request additional information. Contractors should be ready to support their catalog data with documentation.
Past performance / SCP-FSS-001 revisions
The draft SCP-FSS-001 narrows when offerors can substitute customer references or relevant project experience from predecessor companies or key personnel. GSA is also adding language allowing additional verification of PPQs and relevant project experience.
Contractor takeaway: Refresh 32 continues the trend toward tighter MAS compliance around contract clauses, catalog structure, product lifecycle management, FCP data quality, and documentation. Before accepting the mass mod or submitting a new offer/modification, contractors should review affected SINs, FCP files, past performance support, and EOS-related product data.
