# Meetings and  Briefings

## Briefings

### Operations Order Brief

The OPORD briefing provides information, specific instructions, and a thorough overview of the mission. The briefing is usually presented by a single briefing officer, who may be the commander, an assistant, a staff officer, or a special representative depending on the nature of the mission or the level of the headquarters. See FM 5-0 for more information on orders production and briefings.

In an operational situation or when the mission is of a critical nature, individuals or smaller units may need more specific data, which may be provided by a mission briefing. The mission briefing reinforces orders, provides more detailed requirements and instructions for each individual, and explains the significance of each individual role.

The briefing should be organized to follow the written order’s format.

### **Air Mission Brief**

The AMB is a focused adjunct to the OPORD where the ARB commander approves the plan. The term AMB is used to mean both the written product and the briefing itself. The AMB should not be a working meeting. An OPORD should have already been published. Therefore, the AMB is essentially a backbrief to the commander. All units involved in the operation should attend and receive a copy of the order.

The AMB should focus on attack reconnaissance concepts, sequence of events, and the reasons the staff developed the sequence for the mission. The slightest change in route selection, ABFs/SBFs, or other elements of the mission can significantly affect the rest of the plan. The CAB staff will play a pivotal role in the AMB process.

Changes to the mission after the AMB must be approved by the commander. It is very difficult to resynchronize the different combat systems in the short time that remains between the AMB and mission execution. Unit personnel attending should bring:

* Air mission checklist.
* Maps.
* Execution matrix.
* ANCD for receiving frequency set changes/updates.
* AMPS DTC for receiving changes/updates to routes.

Briefing products produced may include:

* Mission.
* Friendly graphics.
* A2C2 procedures.
* Communication card (frequencies/call signs).
* Execution matrix.
* Routes (AMPS cartridge).
* ANCD frequency set load.
* Risk assessment/mission brief/mission schedule.

### **Team Brief**

Team briefs can occur at different levels. The team can be briefed by the battalion or company for specific missions or missions in larger operations. An example of this is teams being briefed by battalion for missions supporting battalion PR or QRF operations. Information and products reviewed during the brief include:

* PPC.
* FS card.
* Actions on contact.
* Contingency planning.
* Scheme of maneuver.
* Battle handover (BHO) procedures.
* Weather, NOTAMs, and hazards briefs.
* Flight plan/mission brief/risk assessment.
* IIMC recovery plan.
* Threat risk assessment.

### **Crew Mission Brief**

The PC briefs the mission and flight requirements demanding effective communication and proper sequencing and timing of actions according to a unit approved crew mission brief checklist. The appropriate aircraft type aircrew training manual (ATM) contains an example of a detailed crew mission briefing checklist and instructions for completing this task. Unit SOPs should address crew briefing checklists.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://229.gitbook.io/229-hub/knowledge/attack-reconnaissance-helicopter-operations/command-and-control/meetings-and-briefings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.