Build a modification intake register before opening eMod

Published by Federal Bid Partners LLC · October 26, 2026 · Change planning

A modification starts with a business change, not with an upload. Someone wants a different labor category, a new address, or an updated item list. Before preparing forms, capture what is changing and why. GSA directs contractor-initiated MAS updates through eOffer/eMod and points contractors to the current modification guide and SIN-specific requirements. Those sources establish the route; your intake register organizes the work. Read GSA's modification guidance.

Write a change statement that can be checked

Use this sentence: “We propose changing [specific approved contract content] from [current state] to [requested state] because [business reason].” Include the contract number, affected SINs, item or labor-category identifiers, and desired effective date. Label that date as requested until the executed modification establishes what actually applies. Avoid vague requests such as “refresh our pricing” that hide several unrelated decisions.

For a fictional example, Harbor Technical proposes adding two service categories while also correcting its billing contact. Its intake register contains separate rows: category additions and contact correction. Both relate to one contract, but each has a different evidence owner. The operations lead supplies role descriptions; the contract administrator verifies contact details. The team asks which modification types and supporting documents apply before deciding how to package the requests.

Confirm the contract's current reporting arrangement before choosing a guide. GSA provides a TDR guide and a separate reference for contracts that remain under non-TDR clauses while awaiting transition. Record which guidance applies today and the document supporting that choice; do not infer effective contract terms solely from the newest solicitation refresh. Check GSA's guide-selection note.

Create six useful register columns

• Current authority: the executed contract or modification supporting today's position.
• Proposed difference: a precise comparison, with stable item identifiers.
• Evidence owner: a named person responsible for the underlying facts.
• Open questions: uncertainties for the contracting officer or current guidance.
• Dependencies: related catalog, entity, pricing, or customer-record changes.
• Status proof: a link to the actual document supporting the stated stage.

Use statuses that describe observable events: intake, evidence gathering, internal review, submitted, clarification requested, executed, and reconciled. A submission receipt supports “submitted.” It does not support “approved.” Keep each supporting file next to the row it explains rather than scattering documents across an email thread.

Decide what belongs in the package

Make a one-page dependency sketch. If an addition affects a catalog, note which catalog workflow the contract uses. If a company change might involve more than a routine administrative update, flag the uncertainty rather than assigning a convenient label. The current guide contains different modification checklists; use the applicable checklist instead of assuming every change follows one procedure. Consult the MAS Modification Guide.

Harbor's reviewer discovers that the proposed category names differ between the cover letter and spreadsheet. The register catches this before submission because both files point to the same change statement. The team fixes the discrepancy, records the revision date, and freezes the reviewed version. It has improved clarity without claiming that a complete internal checklist guarantees acceptance.

Finish with a defensible handoff

The intake meeting is complete when someone outside the discussion can explain the requested change, locate its evidence, identify the remaining question, and name the next owner. Save the register with the reviewed package. When questions arrive, update the same record. That gives a small contract team continuity even when people change roles or several modifications overlap.