How are Priority Intelligence Requirements (PIR) developed?

How are Priority Intelligence Requirements (PIR) developed?

• A. The Intelligence Officer writes and approves the PIR list and does not present them to the commander.
• B. The commander approves the PIRs with input from the intel team and makes changes to the list as the situation changes.
• C. The collection management team approves the list of PIRs which remain in place throughout the operation and do not change.
• D. Higher headquarters assigns subordinate commander's PIRs, and the subordinate commander has no say in creating them.

Answer: (B)

Developing Priority Intelligence Requirements starts with the commander identifying what information is crucial for decision points and for guiding the operation. The intelligence officer or staff takes that intent and translates it into specific information needs, then presents them to the commander for approval to ensure they align with available collection assets and constraints. As the situation evolves, the intel team reviews new developments and adjusts the PIRs accordingly, with the commander approving changes so the requirements stay relevant. This collaborative, iterative process keeps PIRs aligned with current priorities and keeps ISR tasking flexible. Restricting approval to a single actor or forcing PIRs to remain fixed from higher headquarters would remove the essential adaptability and command-driven focus.

Developing Priority Intelligence Requirements starts with the commander identifying what information is crucial for decision points and for guiding the operation. The intelligence officer or staff takes that intent and translates it into specific information needs, then presents them to the commander for approval to ensure they align with available collection assets and constraints. As the situation evolves, the intel team reviews new developments and adjusts the PIRs accordingly, with the commander approving changes so the requirements stay relevant. This collaborative, iterative process keeps PIRs aligned with current priorities and keeps ISR tasking flexible. Restricting approval to a single actor or forcing PIRs to remain fixed from higher headquarters would remove the essential adaptability and command-driven focus.