FMS EdgeFMS Edge — home

Stage 02

LOR Assessment in Foreign Military Sales

Timeline: Assessment standards per C5.2.5.2: Category A within 10 days, Category B within 10 days, Category C within 45 days of Receipt; Advisory comments are due in 10 working days; RFI cycles add time

Updated 2 November 2026Checked against the SAMM: 26 October 2026

The logs the in the Defense Management System on receipt, then assesses it against the mandatory actionable criteria ( Table C5.T4A). A request that falls short is considered insufficient, and Requests for Information go to the purchaser. One that meets the criteria is actionable, and it is complete once the Table C5.T4B criteria are also met and every Request for Information has been addressed.

What happens

Receipt and the DSAMS dates

On receiving a , the promptly enters the data in the Defense Management System () as a Customer Request and at once acknowledges receipt to the purchaser. Both the Date, which is the date on the request itself, and the Receipt date, which is the date the received it, must be entered in promptly when the arrives [SAMM ].

A Customer Request will be created in for every received, including a separate Customer Request for each document developed from a single , so that can measure accurately how long each document takes to develop. When the receiving is not authorized to offer some or all of the items on an , it will forward the to the other concerned. For example, some products, such as “S” type devices, must be offered on a National Security Agency () . When the Air Force receives an that asks for them, it will forward the to and ask it to develop a case for those items. will give the Air Force its , and the Air Force will tell the purchaser both case identifiers and how the 's details are split between the [SAMM ].

The processes the so case development can begin. The individual responsible for doing this is generally found at the headquarters element of the ’s organization. This person may be referred to as the country director, Country Program Manager (), command country manager (), or country desk officer. Normally, the country director will process all the receives for a given country or region. However, for large and complex programs, there may be more than one country director assigned.

The will send a copy of the to the 's Office of International Operations and to the applicable (; the U.S. Military Group, or , in some countries) if either or both were not on distribution. For an for or , the will also send a copy to the . should begin the activities that Section C5.2.5.1 sets out, unless they believe the raises concerns on which the , the Department of State () or both should be asked for guidance [SAMM ].

The , or both may, at any point in the -to- process, begin coordination to approve or disapprove the request, or may advise the to suspend further correspondence until that coordination is complete. If the request is turned down, the formally tells the to stop processing it, gives the rationale for the decision and issues guidance on further actions. If a (ID) has already been established in , the will cancel it [SAMM ].

The actionable criteria

The assesses each to determine whether the request meets the actionable criteria defined in Table C5.T4A. The assessment period begins at “ Receipt” and closes at “ Insufficient” or at “ Actionable”, whichever comes first, for Categories A, B and C. Its is 10 days for Category A, 10 days for Category B and 45 days for Category C [SAMM ]. The standard applies only to the first determination that an is actionable or insufficient, and the tells the partner promptly of that outcome and records the date of the notice in [SAMM ].

Insufficient, actionable, complete

An that does not meet the mandatory requirements in Table C5.T4A is considered insufficient, and no case development activity may begin until more information has been obtained from the purchaser or clarified with it [SAMM ]. Once the contains all the information needed to complete case development, and every Request for Information has been addressed, an Complete milestone must be entered in [SAMM ].

The “ Insufficient” date is the date on which the assessment process finds that the falls short of the mandatory actionable criteria in Table C5.T4A. Before case development starts, Requests for Information will be sent to the purchaser to cover what is needed. The tells the partner promptly of an insufficient determination and records the date of that notice in . It also logs the reason the is insufficient in , using reason codes based on the Table C5.T4A criteria [SAMM ].

Once an , with any additional information the purchaser has provided, meets the mandatory requirements in Table C5.T4A, it is considered actionable, and the may go ahead with case development actions. For Category A, B and C documents, the “ Actionable” milestone must be entered in before any case development activity may begin. The milestone is the date on which the assessment process found that the meets, at a minimum, the Table C5.T4A criteria. The case must be initialized first, so that the milestone can be entered in the Case Milestone Window. The milestone is mandatory for those three categories, since it starts their case development clock [SAMM ].

The tells the partner promptly that the is actionable and records the date of that notice in [SAMM ]. An actionable may still need more information before the document can be fully processed. Both the “ Complete” criteria in Table C5.T4B and the criteria in Table C5.T4A must be fully met before an is considered complete. To settle any remaining issues, Requests for Information will be sent to the purchaser before the “ Complete” date is entered in . The “ Actionable” milestone may be entered on a case document more than once when previously provided requirements change significantly, as Section C5.2.5.3 provides [SAMM ].

Special reviews and the LOR Advisory

In some instances, the may need to prepare an Advisory to notify the Under Secretary of War for Acquisition and Sustainment (USW(A&S)) and the Joint Chiefs of Staff of certain proposed sales. Section C5.2.6 of the describes Advisories and how they are processed. Table C5.T6 of the identifies the types of defense articles requiring either an Advisory or some other type of special review. Each entry in the table provides a hyperlink to either a specific form or to a specific section of the explaining the unique review process for that item. An Advisory does not replace required disclosure or releasability actions being worked by the Military Departments () [SAMM , ]. Examples of the types of items requiring an Advisory or unique review include the following [SAMM , , ]:

  • First introduction of into the international partner’s country
  • that is expected to require congressional notification [SAMM ]
  • Coproduction or licensing agreements for
  • that has not yet completed Operational Test and Evaluation (OT&E)
  • Night Vision Devices ()
  • Ballistic Missile Defense capability
  • Command, Control, Communications, Computer, Intelligence, Surveillance, and Reconnaissance ()
  • equipment
  • Nonstandard
  • Integration of non-U.S. subsystems
  • Other defense articles and services of a sensitive nature

The Weapons Directorate in 's Office of International Operations ( (/WPN)) prepares the Advisory in the format at Figure C5.F5 and sends it to the Joint Chiefs of Staff and to USW(A&S). The advisory should include a copy of the purchaser's request and, when one is required, the . sends the Advisory as soon as possible after it receives the with every required attachment, to ensure consistency with Theater objectives and policy. The 's recipients then have 10 working days, counted from the date of the advisory, to give their comments for consideration. will refer any non-concurrence to an appropriate level within the Office of the Under Secretary of War for Policy for resolution. An Advisory is no substitute for an Exception to National Disclosure Policy () process, nor for the releasability requirements that the work [SAMM ].

Key players at this stage

Partner nation

  • Foreign Liaison Officer (FLO)Partner nation military or civilian representative stationed in the United States, often at a U.S. Implementing Agency (AFSAC, USASAC, NAVSUP WSS, or a SYSCOM)

Embassy — Security Cooperation Organization

DSCA

Service international affairs office

Case manager

Program office

Industry

Common pitfalls

  • and (TSFD) release reviews start late; the partner learns months into development that a capability will not be released
  • RFI cycle drags because the partner's technical expert is not available at the
  • Parallel reviews fall out of step: the service supports the sale while or the Department objects

What to watch for

Information for evaluating can be found in C5.2.5 and Tables C5.T4A and C5.T4B. Questions that bear on the assessment of an include the following:

  • Did copies of the go to the proper U.S. Government () organizations for action/review?
  • Is the complete, and does it comply with policy?
  • Does the contain an identifiable international partner reference or serial number?
  • Is the a result of a foreign solicitation?
  • Are there additional references, such as a or pre-negotiated conditions?
  • Is the request for a valid military requirement?
  • Is this a sensitive technology request?
  • Is the request for missile-related technology or classified information?
  • Will production be in-country?
  • Will any production be used for third-country sales?
  • For standard U.S. materiel, was a valid provided?
  • If the request is for nonstandard materiel, has a military specification (MILSPEC) package or engineering data description been included?
  • What initial spare parts need to be delivered with the end items?
  • Is sufficient information included to process a sole source request?
  • Was the request screened to determine if there is a concurrent commercial bid?
  • Does a quality inspection team need to inspect materiel upon delivery?
  • Does the international partner need any special or contractor services such as an in-country logistics officer?
  • Does the international partner request a not-to-exceed () or firm-fixed-price () response?
  • Does the contain unique international partner budget or requirements?
  • Is a required?
  • Does the request indicate that Foreign Military Financing will be used as a method of financing?
  • Has a negative response been coordinated with ?

Guides on this stage

References

SAMM

  • SAMM C5.2.5.2: Letter of Request Assessment.
  • SAMM C5.2.5.2.1
  • SAMM C5.T4A: Mandatory Criteria Before Letter of Request Actionable (Before Case Development Activities)
  • SAMM C5.T4B: Mandatory Criteria Before Letter of Request Complete
  • SAMM C5.2.6.1: Letter of Request Advisory Memoranda.
  • SAMM C5.F5: Standard Letter of Request Advisory Format
  • SAMM C5.T6: Defense Articles or Services that Require Item-specific Letter of Request Advisories or Review
  • SAMM C5.2.5.1: Letter of Request Receipt and Acknowledgement.
  • SAMM C5.2.5.2.2: Letter of Request Insufficient.
  • SAMM C5.2.5.2.3: Letter of Request Actionable.
  • SAMM C5.2.5.2.4: Letter of Request Complete.
  • SAMM C5.1.5.2
  • SAMM C2.1.4.2: Country Team Assessment.
  • SAMM C5.T1: Country Team Assessment - Common Required Elements
  • SAMM C5.7.6.1: Implementing Agencies Prepare and Submit Initial 36(b) Congressional Notification Package to the Defense Security Cooperation Agency.
  • SAMM C5.2.4: Defense Security Cooperation Agency and Department of State Letter of Request Review.
  • SAMM C5.2.5: Implementing Agency Letter of Request Review.
  • SAMM C5.2.6: Letters of Request Requiring Letter of Request Advisory Memoranda and/or Unique Review.
  • SAMM C5.2.6.1.1: Preparing Letter of Request Advisories.

Public authorities

  • DSCA 24-61: DSCA Policy Memo 24-61 (SAMM E-Change 707)