Skip to content
GSA9 min readUpdated June 6, 2026

GSA MAS Refreshes: What Contractors Should Watch After a Solicitation Update

How GSA MAS refreshes work, why mass modifications matter, how Refresh 32 affects the offer-template package, and why Refresh 31 remains the TDR expansion anchor.

Built for
MAS contractors tracking solicitation refreshes, mass mods, reporting changes, and clause updates
By the end
Know how to read a refresh without missing operational changes.
Cluster map

Keep going inside this topic

All guide clusters →
Field guide

Refresh reading checklist

Part 1

Refreshes are how the MAS program changes over time

A MAS refresh updates the solicitation and can change clauses, templates, reporting requirements, SIN instructions, or program rules. Existing contractors often see those changes through mass modifications.

The right habit is not panic. The right habit is to read what changed, decide what applies, assign an owner, and update internal contract administration notes.

Part 2

Refresh 31 is a major anchor page

Refresh 31 has its own child guide because GSA states that Transactional Data Reporting became mandatory for all MAS SINs with Refresh 31. That has real operational consequences for reporting cadence, sales data, and IFF handling.

Refresh 32 deserves its own child guide because it is the current Refresh 32-era offer package branch, with FCP files, required templates, and eOffer uploads. The refresh archive should eventually cover Refresh 31 down through Refresh 25, but each older page should be framed as history unless the official material is still current.

Part 3

Do not turn refresh pages into stale instructions

Refresh pages should explain what changed, why it mattered, and what contractor teams should check. They should also link to official current GSA resources so readers do not rely on old summaries when filing live submissions.

Recommended URL format: /guides/gsa/refresh/31, /guides/gsa/refresh/30, and so on.
Examples

What this looks like in practice

Refresh 31TDR became a daily-business issue, not a footnote

GSA's TDR help says Refresh 31 was released on April 2, 2026, and made TDR mandatory for all MAS SINs. That is not just a clause-reading issue. It changes reporting behavior and timing for contractors moving into the TDR model.

The useful contractor question is: who owns the monthly report, who checks data quality, and how does IFF payment get reconciled?

Frequently asked questions

Should this library use /refresh31 or /refresh/31?

Use nested URLs like /guides/gsa/refresh/32 and /guides/gsa/refresh/31. The format gives us a clean refresh index and a natural archive for older refresh pages.

Does every refresh need a page?

Only if it gives readers useful context. Refresh 32 is useful for the current offer-package layer, and Refresh 31 is useful because TDR expansion is a large operational change.

Should contractors resubmit anything just because a guide mentions a refresh?

No. Contractors should review official GSA instructions, their contract, and the relevant mass modification before taking action.