The review before the document is written

← All Insights

1. A review held before the paperwork starts moving

Most work on a case travels on paper. An implementing agency drafts the agreement, then sends it to the office that writes and countersigns it. Errors found there are expensive, because the correction sends the document back through offices that have already read it.

For a small set of cases the manual inserts a meeting before any of that begins. "DSCA may conduct a Pre-Case Review (PCR) with the IAs and other stakeholders on new LOAs during case development and before the IA submits the case to DSCA (IOPS/GEX/CWD) for processing" (SAMM C5.6.10). The stated aim is to find the problems early and cut the rework later.

It is deliberately not a standard step. "A PCR is not appropriate or necessary for all LOAs, but should be considered for cases meeting the criteria in Section C5.6.10.1" (SAMM C5.6.10). Nor is the decision the drafting agency’s to make. "The (Office of International Operations, Regional Execution Directorate (IOPS/REX)) Regional Division leadership is the final decision authority for whether or not a PCR should be held" (SAMM C5.6.10).

2. Which cases are candidates

Five triggers are listed. The first is size relative to what the partner already runs, a new sale representing an increase of more than 15 percent to the purchaser’s current active program. The second and third are tied to the congressional notification thresholds. One is a sale that crosses them and introduces a capability the partner has not held before. The other crosses them and involves articles that are not a program of record. The fourth is any sale forming part of an international weapon competition. The fifth is a catch all for sales with unique aspects warranting a look before the document is finalized (SAMM C5.6.10.1).

Those thresholds are the same ones described in congressional notification of arms sales. The competition trigger connects to a different pressure, since a case being drafted against a live competition has a commercial deadline attached to it.

The list is not exhaustive in practice. "DSCA (IOPS/REX) Regional Division leadership may also mandate a PCR for cases not requested by the IA or DSCA (IOPS/WPN)" (SAMM C5.6.10.1.1).

3. Asking for one, and being turned down

The request runs through the country portfolio director rather than direct to the reviewing office, and it has a deadline measured backwards from submission. The agency gives notice at case initialization and no later than 30 calendar days before the document goes forward, naming a point of contact, the case designator, and why the case qualifies (SAMM C5.6.10.1.1). For competitions the weapons division raises it instead.

Once a review is approved, the clock starts on the other side. "The PCR Lead will notify the IA and DSCA (IOPS/WPN) within 10 calendar days with a proposed date for the PCR" (SAMM C5.6.10.1.1).

A refusal is also documented rather than simply communicated. If leadership decides a review is not required, "the CPD will notify the requestor and enter the justification for why a PCR is not necessary in the case remarks in the DSAMS within 10 calendar days" (SAMM C5.6.10.1.2). The record sits with the case. "A requestor may appeal a decision to deny a PCR by providing the CPD additional justification for why a PCR is necessary" (SAMM C5.6.10.1.2).

4. Who sits in the room

The lead decides the attendance list from a wide pool. It runs across the international operations offices, the financial policy and regional execution offices, the case writing division, the strategy and policy side and the general counsel. The implementing agency and the relevant program office are on it too (SAMM C5.6.10.3). Mandatory attendees are named well ahead. "Attendance is optional for all other stakeholders" (SAMM C5.6.10.3).

Optional does not mean silent. "Stakeholders who cannot attend must review the documents and provide any changes and input to the PCR Lead 48 hours prior to the scheduled meeting" (SAMM C5.6.10.3).

Industry gets a narrow, supervised slot. "Prime contractors will be included in the discussion when necessary and only for the portion that requires their participation" (SAMM C5.6.10.3.1), and while they are present the papers go away: "The LOA and other supporting documents should not be visible when the contractor is in the meeting" (SAMM C5.6.10.3.1). Anyone uneasy about a contractor attending can say so in reply to the invitation, and the lead decides. The related limits on what a government office may say to a company are covered in what a security cooperation office may do for industry.

5. The package and the two clocks

Two deadlines bracket the meeting. Scheduling happens "within 10 calendar days after the receipt of request from the IA or DSCA (IOPS/WPN)" (SAMM C5.6.10.4), and the meeting itself sits clear of the submission date: "The meeting should occur no later than ten work days before the LOA document is sent to DSCA (IOPS/GEX/CWD) for action to allow the IA time to correct deficiencies identified at the PCR" (SAMM C5.6.10.4).

The reading material arrives earlier still. "The IA will provide a complete LOA package to the PCR Lead seven work days prior to the meeting" (SAMM C5.6.10.5). The listed contents are the whole file rather than the agreement alone. They run from the request and the cover memorandum through missile technology approvals, congressional notifications and excess article approvals. Also listed are the manpower sheet, nonrecurring cost waivers, approval to sell letters for communications security, two system approval memoranda, and the pricing and case remarks reports (SAMM C5.6.10.5).

A case waiting only on long lead waivers or a notification does not have to wait for the meeting. The review can run while those finish (SAMM C5.6.10.5). If anything changes after the package goes in, "the IA must provide the updated version of the document to the PCR Lead for distribution to the group" (SAMM C5.6.10.5.1).

6. What the meeting cannot do

Minutes are due "within 3 work days after the meeting" (SAMM C5.6.10.6), and the actions in them are not closed by the person who raised them. "All actions must be approved/adjudicated by the supervisor of the designated office before the LOA document is sent to DSCA (IOPS/GEX/CWD) for action" (SAMM C5.6.10.6). The minutes then travel with the package, action items marked complete.

The limit on the meeting is stated flatly. "The PCR Lead is not authorized to give exceptions to policy or approve policy changes during the PCR or through the PCR minutes" (SAMM C5.6.10.7). Anything that needs a departure from policy goes through the separate exception route, described in the approvals a case must carry.

7. What a supplier can take from this

A pre-case review is a signal about the case rather than about the company. It usually means the sale is large relative to the partner’s program, crosses a notification threshold with something new in it, or sits inside a competition. Any of those implies a longer runway before an agreement exists to be performed against.

The narrow contractor slot is worth noting. A prime may be asked in for one technical question with the documents off the screen, which is not an opportunity to discuss scope or price. The useful preparation is to have the technical answer ready in a form that does not require seeing the agreement.

Key terms

Pre-case review	A meeting held with stakeholders on a new case before the document is submitted for processing.
PCR lead	The person designated to schedule the meeting, run it, assign actions and circulate minutes.
Country portfolio director	The route through which a review is requested, and who records a refusal in the case remarks.
Complete LOA package	The request, agreement, cover memorandum, approvals, waivers and reports due seven work days before the meeting.

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 case that attracts extra review is usually large, sensitive or contested, which lengthens the runway before delivery. Sentfore works at the delivery end of defense programs in difficult environments, providing secure movement, protective security, facilities and life support around equipment and people once they arrive. Requirements can be sent through the contact page.