Changing a case, and the scope test

← All Insights

1. Two instruments, one test

A signed case is not fixed for life. Quantities change, schedules slip, prices settle, and the agreement has to be brought back into line with what is actually happening. The manual treats the documents that do this as instruments in their own right: "Foreign Military Sales (FMS) Amendments and Modifications are legal instruments that add or change requirements provided on the Basic case and must comply with the normal SAMM requirements for Basic cases" (SAMM AP9.3.1).

Everything in the drafting standard for an original agreement therefore applies again, with extra requirements on top. The division between the two instruments turns on one question of substance, and the answer decides more than the paperwork. "Changes to scope determines the use of an Amendment or Modification, and whether or not the change can be on a line with an old administrative surcharge rate" (SAMM Table AP9.T2). Which changes are allowed on the lighter instrument is set out in amendments and modifications.

The test is applied line by line, not to the document as a whole. "The case description must be very clear on whether there are scope changes to each line" (SAMM Table AP9.T2). Where a change falls outside the permitted list, the drafter has no discretion: "If not in this table, then it must be done on an Amendment or possibly Concurrent Modification" (SAMM Table AP9.T2).

2. The description does the work

On a change document the description field carries the reasoning rather than a summary of the goods. "Key components are to identify the LOA changes, reasons for the changes, and identification if the document is being processed for full case closure" (SAMM Table AP9.T2).

The manual supplies worked examples, which is unusual and useful. One shows a change driven by delay rather than by appetite: "This Modification extends the Months on support equipment line due to contract slippage and delayed delivery. There is no change in scope to this document. (F-15 Support)" (SAMM Table AP9.T2). The scope finding is stated on the face of the document rather than left to be inferred.

Another shows the closing document: "This Modification is for CASE CLOSURE, which decreases all remaining lines to the highest financial requirement (Ammunition)" (SAMM Table AP9.T2). Reducing every remaining line to what was actually needed is the last act before the work described in how a case is reconciled and closed.

The other examples in the list cover an amendment adding two further aircraft, a modification correcting the administrative surcharge, and an amendment that both supersedes an earlier offer and adds simulator support. Together they show the range: adding, correcting, extending, closing and replacing.

3. Where the reference line changes

On an original agreement the reference block lists the buyer’s requests in date order. On a modification there may be no request to point at, because the change came from the United States side. The manual accordingly directs that the field record a government review rather than a purchaser reference, with no date, unless there really was correspondence with the buyer (SAMM Table AP9.T2).

The description written for the state department has its own rule on a change document. "This field must identify added items or services, as well as the end item being supported" (SAMM Table AP9.T2), and it is required where two modifications run together because scope has moved.

4. Money and notes on a changed case

Payment schedules are not left to drift. "The IA should review payment schedules annually due to changes to delivery schedules, costs, and collections, by submitting Amendments or Modifications to DSCA (IOPS/GEX/CWD), who will update the payment schedule" (SAMM Table AP9.T2). A change document is therefore the ordinary vehicle for correcting a schedule that no longer matches the program, and the schedule itself is rebuilt centrally.

Notes behave in a way that surprises readers of successive versions. "Unless identified in Appendix 6, LOA notes from previous versions of the case will not be restated on subsequent Amendments or Modifications" (SAMM Table AP9.T2). A note missing from the latest document has not necessarily been withdrawn as a matter of substance; it simply is not repeated.

Deletions have to be tidied as well. "Lines deleted must have corresponding line-item description notes deleted" (SAMM Table AP9.T2). A note describing an item that is no longer on the case is treated as an error rather than as harmless surplus.

5. When the United States pays

A second kind of case is drafted from the same appendix but works differently. "Building Partner Capacity Letters of Offer and Acceptance (also known as (BPC) cases) are funded by USG appropriations and are used to transfer defense articles and services to a foreign partner for the purpose of building partner security force capability" (SAMM AP9.4.1). What that program is for is set out in what building partner capacity is.

One sentence captures the difference that matters most. "BPC cases are developed and managed centrally by the Security Cooperation community in accordance with statutory authorization and are not signed by the partner" (SAMM AP9.4.1). The document that governs an ordinary sale is an offer the buyer accepts. Here there is no such signature, which is why the life of these cases is described separately in how a BPC case runs and closes.

Within that program the route splits by what is being provided. Materiel cases pass through the same central case writing division as ordinary sales, with their own requirements for the request field, the state description, the release and delivery codes and indirect charges. Training cases do not: "These cases will NOT process through DSCA (IOPS/GEX/CWD) but will go directly from the Implementing Agency (IA) to DSCA Office of Business Operations (OBO) for review" (SAMM Table AP9.T3), after which they move to a proposed status for review by the state department bureau that handles arms transfers.

6. What a supplier can take from this

The instrument named at the top of a document tells a reader something about the change inside it. A modification means the change stayed inside the existing scope, which is why a modification can extend a delivery period without reopening what was bought. An amendment means scope moved.

The annual review of payment schedules is also worth expecting. A schedule that is revised without any change to the equipment is routine housekeeping rather than a sign of trouble on the program.

Key terms

Amendment	The instrument used where the change moves the scope of the case. SAMM Table AP9.T2.
Modification	The instrument used for changes that stay within the existing scope.
Case closure document	A change document that reduces every remaining line to what was actually needed.
Concurrent modification	Two modifications processed together, used where scope has shifted between them.
Building partner capacity case	A case paid for by United States appropriations and not signed by the partner.

Every statement above links to the document behind it. The full source list for this piece is on the sources page.

This page describes public United States government programs for general information. It is not legal, regulatory or procurement advice, and it does not address the facts of any particular case.

How Sentfore supports this

A change on paper becomes a change on the ground months later. Sentfore provides secure transport, protective security, facilities and life support for defense programs in complex environments. Requirements can be sent through the contact page.