Skip to content
GSA11 min readUpdated June 6, 2026

GSA MAS Refresh 31: TDR Expansion, Mass Mod A909, and Contractor Action Items

A source-backed guide to MAS Refresh 31, why it matters, what GSA says about mandatory TDR for all MAS SINs, and how contractors should think through reporting ownership.

Built for
MAS contractors trying to understand Refresh 31 and the TDR transition without losing the operational thread
By the end
Understand the Refresh 31 signal and the practical reporting questions to resolve internally.
Field guide

Refresh 31 action board

Read the source
Do not rely on secondhand summaries for live contract actions.
Signal
The contract team sees Refresh 31 or Mass Mod A909.
Response
Read GSA's TDR help and official TDR page, then save the source links in the contract file.
Accept and sequence
Clicking without notes makes future audits and handoffs harder.
Signal
A system-generated mass modification is available.
Response
Confirm who is authorized to act and document the acceptance/timing process.
Assign TDR ownership
TDR data quality is a process problem, not just a portal problem.
Signal
Monthly line-item reporting becomes part of the contract rhythm.
Response
Name the data owner, reviewer, submission owner, and backup.
Reconcile IFF
Late cleanup is harder than monthly hygiene.
Signal
Sales reporting and fee payment must stay aligned.
Response
Tie reporting cadence, IFF payment timing, and sales records together.
Part 1

What changed with Refresh 31

GSA's TDR help page states that Refresh 31 was released on April 2, 2026, and that TDR is mandatory for all MAS SINs as of that refresh.

That makes Refresh 31 a major anchor for the GSA library because it affects how contractors think about sales reporting, line-item data, and IFF reconciliation.

Part 2

Mass Mod A909 is not just a click

GSA describes a system-generated Refresh 31 Mass Modification A909 and a follow-on Participate in TDR modification. Contractors should treat that sequence as a contract administration event with notes, source links, and an owner.

The goal is not to scare anyone. The goal is to avoid a future scramble when someone asks who accepted what and what changed afterward.

Part 3

The real work is monthly data discipline

TDR shifts attention toward monthly transactional reporting. That means the company needs to know what sales count, where the data comes from, how exceptions get reviewed, and how reporting ties to fee payment.

A strong internal process makes TDR feel like recurring contract hygiene instead of a surprise compliance project.

Part 4

Where older refresh pages fit

Refresh 31 should be the first detailed refresh page because it is current and operationally important. Older refresh pages can be added later as historical context if they explain meaningful changes, but they should be clearly dated.

Examples

What this looks like in practice

Operating modelA clean monthly TDR rhythm

A contractor exports sales tied to the MAS contract, checks line items against internal records, reviews exceptions, submits TDR data, and reconciles the Industrial Funding Fee. That rhythm should have an owner and a backup before the first deadline feels urgent.

  • Export sales.
  • Check line items.
  • Review exceptions.
  • Submit and reconcile.
Team handoffWrite the note future-you will need

When the mass mod is accepted, record the date, user, source page, affected contracts, reporting owner, and next reporting checkpoint. That note is small, but it turns a system action into institutional memory.

Frequently asked questions

Is TDR mandatory for all MAS SINs after Refresh 31?

GSA's TDR help page states that, as of Refresh 31 released on April 2, 2026, TDR is mandatory for all MAS SINs.

Should this page replace official GSA instructions?

No. Use this page to understand the workflow, then verify live contract actions and deadlines on the official GSA source pages.

What should the company do internally?

Assign reporting ownership, identify data sources, define review steps, record modification acceptance, and reconcile reporting with IFF payment timing.