Sign A909 First: MAS Refresh 2026 Week by Week for U.S. Contractors

MAS Refresh 2026 makes Transactional Data Reporting mandatory for every MAS SIN and forces contractors to accept new system-generated mass modifications within tight windows. Refresh 31 and Refresh 32, both tracked by GSA, require you to sign the mass mods in sequence, map your sales data to the new TDR fields, and start reporting on schedule. Gsascheduleservices helps contractors handle exactly this kind of modification and reporting work, and the MAS Modification Guide spells out the acceptance order you need to follow. Start the mapping work today, not after the deadline hits.

TL;DR:

• All MAS contractors must accept the system-generated mass modifications in sequence, including A909 and A917, to ensure timely TDR reporting and avoid blockages on contract changes.
• The reporting requires mapping specific data fields, such as order date, ZIP code, UCID, and worksite location, and testing uploads early to prevent formatting issues during official submission periods.
• Acceptance windows are tight, with the A917 mod needing signing within 30 days, and delays may prevent future price changes, contract extensions, or modifications.
• TDR data collection is now mandatory for all SINs, with the government projecting up to $50 million in annual cost savings from full rollout, emphasizing the importance of compliance.
• Contractors can reduce onboarding time by leveraging expert support from Gsascheduleservices for readiness assessments, mod management, field mapping, and building a repeatable reporting process before deadlines.

Table of Contents

• What Changed in MAS Refresh 31 and Refresh 32
• How Long Do You Have to Accept the Mass Mods?
• What Data Does TDR Actually Require?
• Your Compliance Checklist for This Quarter
• Category-Specific Changes Worth Reviewing Closely
• Getting Your Systems Ready Before the Deadline Hits
• What This Refresh Cycle Really Tests
• How Gsascheduleservices Keeps You Ahead of These Deadlines
• Where to Verify These Requirements Yourself
• Sources
• FAQ

What Changed in MAS Refresh 31 and Refresh 32

Refresh 31, issued April 2, 2026, and Refresh 32, released June 5, 2026, reshape several parts of the MAS solicitation at once. Here’s what actually shifted:

• TDR is now mandatory for all SINs. Every schedule holder, regardless of category, must accept the Transactional Data Reporting mass mod and begin submitting monthly sales data with new required fields.
• Mass mod acceptance windows got shorter. Refresh 32’s DEI-related modification requires acceptance within 30 days, tighter than prior cycles.
• A new DEI clause reflects Executive Order 14398, while a companion AI clause remains partially in draft, with GSA deferring parts of that language to a future refresh.
• End-of-Support requirements now apply to IT and ICT products, forcing vendors to disclose end-of-life dates and security update commitments.
• SIN churn continues: grants management gets a new home under SIN 518210GM, while SIN 311423 for non-perishable foods is being retired.

How Long Do You Have to Accept the Mass Mods?

You’ll see at least two mass modifications land in your eMod queue over this cycle: A909 for Refresh 31 and A917 for Refresh 32. Each carries its own signature and its own clock.

1. Accept Refresh 31’s A909 mod first. This unlocks the “Participate in TDR” modification, which you must accept before you can report any sales data.
2. Accept “Participate in TDR” promptly. Reporting obligations begin the first day of the quarter after acceptance, so a delay pushes your entire reporting timeline back a full quarter.
3. Sign Refresh 32’s A917 mod within 30 days of receipt, per the Significant Changes attachment for Refresh 32.
4. Verify your authorized negotiator is current in eMod and that your FAS ID has multi-factor authentication enabled before you attempt to sign anything.
5. Call your contracting officer or contract specialist immediately if a mod looks wrong or if your CO/CS contact info in eLibrary is outdated.

Unsigned mass mods don’t disappear. They roll forward and can block later modification requests, including price changes and option-year exercises, until you clear the backlog.

Pro Tip: Set a calendar reminder the day a mass mod lands, not the day it’s due. Contracting officers see a wave of last-minute signatures right before deadlines, and any error in your submission at that point has no time left to fix.

What Data Does TDR Actually Require?

TDR isn’t a vague reporting gesture. The Significant Changes attachment for Refresh 31 lists specific fields you must capture for every reportable transaction:

• Order date and ship date
• ZIP code shipped to
• Federal customer or Treasury Account Symbol
• Cloud Service Type (for applicable cloud SINs)
• Unique Contract Identifier (UCID)
• Order type and order discount
• Worksite location

Some fields apply only to services, others only to products, so check your SIN-specific instructions before building your extraction process. Reporting cadence works on a monthly capture, quarterly submission basis: you log transactions as they happen, then upload them through the FAS Sales Reporting Portal (SRP) once your official reporting period opens. GSA has flagged a grace period for a handful of newer data elements running from July through December 2026, giving contractors extra runway to get those fields right without immediate penalty.

Why this matters: GSA reports that TDR pilots have already produced $20.2 million in annual cost avoidance, and the agency projects up to $50 million once TDR is fully rolled out across MAS. That’s the government’s stated rationale for making this mandatory instead of optional.

Accurate TDR data also interacts with your price list. Under TDR, you’re generally relieved from the older commercial sales practice disclosures, but the Price Reductions Clause still governs how price changes get evaluated, and sloppy transaction data makes future price negotiations harder to defend.

Your Compliance Checklist for This Quarter

Work through these in order, and document each step with a date and a name attached, since contracting officers may ask for evidence during a contract review.

1. Sign outstanding mass mods in sequence: A909 first, then “Participate in TDR,” then A917. Log the acceptance date for each.
2. Map every required TDR field to your internal order system. If you use an ERP or CRM, identify which fields already exist and which you’ll need to add manually.
3. Run a test upload through the SRP before your official reporting period starts, so any formatting errors surface while there’s still time to fix them.
4. Inventory catalog items for End-of-Support exposure. Anything with a manufacturer end-of-life date inside the next three years needs a documented mitigation or replacement plan.
5. Update subcontracting plans and joint venture documentation if your JV structure or small business subcontracting commitments changed since your last modification.
6. Confirm your CO or CS contact in GSA eLibrary and keep a running modification compliance log with every mod, acceptance date, and outcome.

Pro Tip: Assign one person as the TDR data owner, not a committee. TDR compliance dies from diffusion of responsibility more often than from any technical problem.

Category-Specific Changes Worth Reviewing Closely

Not every change hits every SIN the same way. If you sell in these categories, look past the general summary and check your own attachment language.

• IT and ICT products face the new End-of-Support requirement directly: contracting officers can require replacement items or remove products from your contract if you can’t document security update availability. Cloud SINs also pick up the new Cloud Service Type reporting field.
• Human Capital SINs got updated instructions on past performance documentation, worth a careful read if you’re bidding task orders that weight experience heavily.
• Facilities and Food categories lose SIN 311423 for non-perishable foods, and related Order-Level Materials guidance was refreshed alongside it.
• Grants management gets a dedicated home under the new SIN 518210GM, with its own instructions for eligibility and pricing structure.
• Joint ventures should double check FASt Lane eligibility constraints, since some JV structures face additional documentation requirements under the refreshed solicitation language.

Getting Your Systems Ready Before the Deadline Hits

Readiness for TDR isn’t a paperwork exercise, it’s an operations project with a hard deadline attached.

1. Name a TDR owner and a mass-mod signer. They can be the same person at a small business, but both roles need to be explicit.
2. Enable MFA on your FAS ID and confirm your authorized negotiators are current, since an expired negotiator designation can stall a signature at the worst possible moment.
3. Map your ERP or order management fields to the TDR data elements and build a repeatable monthly extraction process rather than a manual one-time export.
4. Collect End-of-Support statements from your manufacturers now, before you need them for a contracting officer review.
5. Run a test SRP upload and reconcile it against your accounting records to catch mismatches before they become a reported discrepancy.

Pro Tip: Treat your first TDR reporting cycle like a dress rehearsal. Submit early in your window, not on the last day, so GSA has time to flag problems before they compound into your next quarter’s data.

What This Refresh Cycle Really Tests

TDR doesn’t just ask for more data, it tests whether a small contractor has the internal discipline to track transaction-level detail the way larger primes already do. That’s the real shift here. Contractors who treat mass mod acceptance as a formality rather than a sequenced process are the ones who end up blocked on a later price modification or option exercise. An orderly plan this quarter, mapped fields, tested uploads, signed mods in order, prevents a pricing or delivery disruption six months from now.

— Josh

How Gsascheduleservices Keeps You Ahead of These Deadlines

Mapping TDR fields, sequencing mass mod acceptance, and rebuilding a price list under new reporting rules eats real hours you don’t have if you’re also running the business. Gsascheduleservices exists for exactly this gap: readiness assessments, mass-mod acceptance management, TDR field mapping and reporting support, and price-list updates, all handled by people who track these solicitation refreshes for a living instead of once a year. Contractors working through GSA paperwork on their own typically spend over two years and face multiple rejections; utilizing expert support can often reduce the process to several months with minimal client time investment. If your existing schedule needs modification support, the maintenance plans cover ongoing mods, and if you’re still working toward your first award, the proposal packages start with a readiness assessment. Get a free eligibility check to see exactly where your contract stands against Refresh 31 and Refresh 32 before your next deadline arrives.

Where to Verify These Requirements Yourself

• Help with Transactional Data Reporting — TDR mandate and mod sequence
• MAS Modification Guide — mod acceptance order
• Save your contract’s CO/CS contact from GSA eLibrary for direct questions

Sources

• Significant Changes for the GSA Multiple Award Schedule (MAS) Solicitation (Refresh 32)
• Help with Transactional Data Reporting | GSA
• Significant Changes for the GSA Multiple Award Schedule (MAS) Solicitation (Refresh 31)

FAQ

What Is MAS Refresh 2026?

MAS Refresh 2026 refers to Refresh 31 and Refresh 32, the two solicitation updates that made TDR mandatory for all SINs and introduced new DEI and product lifecycle clauses. Both refreshes require contractors to accept system-generated mass modifications within specific deadlines.

Do I Have to Accept the TDR Mass Modification?

Yes. TDR became mandatory for every MAS SIN under Refresh 31, and accepting mod A909 followed by “Participate in TDR” is required to stay compliant. Skipping acceptance can block later contract modifications, including price changes.

How Long Do I Have to Accept the Refresh 32 Mass Mod?

Refresh 32’s mass modification requires acceptance within 30 days of receipt. That window is shorter than earlier refresh cycles, so check your eMod queue regularly rather than waiting for a reminder.

What Happens if I Don’t Accept a Mass Mod on Time?

Overdue mass mods can block other modification requests, including price list updates and option-year exercises, until you clear them. There’s no grace period built into the sequencing, so unsigned mods simply accumulate.

Can Gsascheduleservices Help With Mass Mod Acceptance and TDR Mapping?

Yes. Gsascheduleservices offers maintenance plans covering ongoing modification support and readiness assessments that include TDR field mapping. Current pricing for maintenance packages is listed on the maintenance plans page.

When Does TDR Reporting Actually Start?

Reporting begins the first day of the quarter following your acceptance of the “Participate in TDR” modification. Delaying acceptance pushes your entire reporting start date back by a full quarter.