Case Changes and Reviews · 2 of 3
A case can run for a decade. Nobody remembers in year six what was agreed in year one, and the people who agreed it have moved. Reviews exist to stop that drift. They are "an excellent opportunity for ensuring prompt issue resolution, data integrity, and accurate accountability" (SAMM C6.5.1).
The manual sets out what makes one necessary: "The following items influence a decision about the need for a case review: USG resources, desires or requirements of the FMS purchaser, political visibility or sensitivity, political-military changes in a region, and the size and complexity of the program" (SAMM C6.5.2).
Two of those are worth noticing. The partner's own requirements count, and so do political conditions in the region. A partner whose domestic law obliges it to report on the status of its accounts can say so, and the manual expects that to be accommodated: "The preferences and desires of the purchaser regarding the conduct of reviews should be accommodated to the greatest extent possible" (SAMM C6.5.2).
The commitment is meant to be written down in advance. "The number and type of reviews should be documented in the Letter of Offer and Acceptance (LOA)" (SAMM C6.5.2). Reviews consume manpower, and manpower on a case is priced.
Reviews are layered, and the layer decides who attends and what gets discussed. "Each review type has a corresponding scope of what is typically covered" (SAMM C6.5.5).
The fifth is different in kind. A case-level review is prepared annually by the implementing agency, gives financial, acquisition and logistical status for every line, and reviews the payment schedule. It is delivered on paper or electronically, and "There is no in-person meeting associated with this review" (SAMM Table C6.T6).
That is the review most partners actually receive most years, and it arrives as a document. Treating it as routine correspondence is how discrepancies survive to become closure problems.
There is a floor rather than a timetable. "FMS case reviews should be conducted at least once per calendar year, but they can be done more frequently if needed" (SAMM C6.5.4). For anything involving the partner, frequency and timing are coordinated with it.
The published matrix says country-level and service-level reviews are usually annual, and notes that timing "May be driven by purchaser funding and budgeting timelines" (SAMM Table C6.T5). A partner whose budget is set in a particular month has a strong argument for scheduling around it. Program-level reviews follow the milestone plan set out during case development and refined over time.
Practical constraints are named. Holidays on both sides, weekends and personnel changes are to be considered, and "Because FMS reviews for a specific purchaser or program often involve many of the same people, reviews should be consolidated whenever practical" (SAMM C6.5.4).
Seniority is matched rather than maximized. "The rank of the lead USG review participant should be equivalent to that of the lead purchaser participant" (SAMM C6.5.6). Sending a more senior figure than the other side is not a courtesy in this setting.
Seniority alone will not carry a review. Senior officials can co-chair, but "detailed discussions require the participation of the managers who are responsible for the day-to-day operations of the program or weapon system under review" (SAMM C6.5.6). The manual also asks for restraint on numbers while insisting the right specialists are present, and expects the chair to ensure everyone in the room has a distinct, active role.
Unanswered questions come with a clock. Where issues cannot be resolved during the review, participants are to research solutions afterwards and "follow-up appropriately to all within a week" (SAMM C6.5.6). A week is short enough to be worth holding people to, and it is the single most useful line in this section for a partner chasing an answer.
When the partner hosts, the security cooperation office in country handles lodging, transport and support for the visiting team.
Standard formats are preferred because they make reviews comparable. Deviations are accepted where other critical program or financial information has to be discussed, with requests going to the agency's business operations office (SAMM C6.5.7).
One agenda item is governed in unusual detail. A cultural day is a day built into a review to give American personnel an appreciation of the host nation's culture, through touring, events or other activities. It is not at the host's discretion alone. "Cultural days for USG security cooperation community personnel must include attendance by both the USG and the partner nation" (SAMM C6.5.3). Approval is needed from both the implementing agency and the partner before it goes on the agenda.
The boundary is drawn hard. "A day with no scheduled activities (that is not a travel day as permitted by the Joint Travel Regulations (JTR)) is not authorized" (SAMM C6.5.3). Personnel may take leave alongside authorized travel, which is a separate matter and paid for differently.
General case reviews sit alongside two other things that look similar and are not. Annual case reviews and reconciliations belong to the closure machinery and are governed separately, and financial management reviews belong to the financial chapter (SAMM C6.5).
The distinction matters when an issue is raised in the wrong forum. A discrepancy on a delivered shipment is handled through the discrepancy report process, described in supply discrepancy reports, and raising it at a program review does not start that clock. A case that should be closed is dealt with through reconciliation, set out in how a case is reconciled and closed.
A review is where status is confirmed and decisions are made. The mechanisms that actually change a case, or end it, are separate documents with their own rules.
| Case-level review | An annual written status report on every line, with no meeting attached. SAMM Table C6.T6. |
|---|---|
| Country-level review | An agency-chaired review of a partner's whole program, usually annual. |
| Program-level review | A review of one system or case cluster, driven by milestones. |
| Cultural day | An agenda day requiring approval and attendance on both sides. |
| SCO | Security cooperation organization, the American office in the partner country. |
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.
Reviews confirm status, and status is set by what actually happened in the field. Sentfore supports defense programs at the delivery end, providing secure movement, protective security, accommodation and site support in complex environments. Requirements can be sent through the contact page.