text: Chapter 8
  ⚫ BDAs.
  ⚫ Ongoing information collection activities.
  ⚫ Answers to intelligence requirements.
  ⚫ Impacts of friendly operations in the OE.
  ⚫ Maneuver echelon reports of enemy activity.
  ⚫ Current assessments on COAs the threat is adopting.
  ⚫ Changes or effects in the OE that may impact operations.
  ⚫ Updates from the decision support template and execution checklist to inform further
  information collection.
  8-145. The CIP must be disseminated to the lowest level possible to ensure unity of effort across a unit’s
  intelligence warfighting function capabilities and to nest intelligence with operations. The CIP informs the
  COP, and the COP influences intelligence activities; this is true at all levels of operations. Synchronizing
  operations and intelligence by using CIPs and COPs is important. These common tools assist in focusing
  efforts and ensuring a common understanding of often-chaotic and fast-paced OEs (see figure 5-10 on
  page 5-25).
  8-146. Within unit SOPs, the G-2/S-2 annotates how to develop the CIP, for which there are various
  development methods. Some units may build the CIP by extracting information from different systems and
  databases and compiling the information narratively or graphically. Other units may use a process by which
  data, information, and intelligence are extracted from systems and databases and automatically populated
  into a narrative or graphic product or a combination of both. When using this method, systems, as part of the
  intelligence architecture, are typically established with knowledge management rules and processes to ensure
  data, information, and intelligence are populated to higher and lower echelons.
  8-147. Before a mission, the G-2/S-2 must coordinate with higher and lower echelons and adjacent units to
  confirm how the CIP will be developed. A good practice is conducting rehearsals and confirmation briefs
  with intelligence staffs at each echelon to lessen the possibility of a particular echelon not receiving CIP
  updates when needed.
  8-148. Typical questions for CIP development include but are not limited to—
  ⚫ How does the commander—
  ▪ Want to view the CIP (on a digital system, analog, narratively or graphically, relevant layers
  to display)?
  ▪ Envision CIP development and content?
  ▪ Envision the CIP supporting operations?
  ▪ Envision subordinate units using the CIP?
  ▪ Prioritize the CIP, the intelligence running estimate, and INTSUM?
  ▪ Use the CIP when discussing operations with higher headquarters?
  ⚫ How does the CIP answer intelligence requirements?
  ⚫ Are intelligence analysts trained on systems and databases used to develop the CIP?
  ⚫ How will data, information, and intelligence populate the CIP?
  ⚫ How does the unit’s CIP interface with higher- and lower-echelon CIPs?
  ⚫ How are multinational and allied-partner data, information, and intelligence incorporated?
  ⚫ What CIP data, information, and/or intelligence is used for the intelligence portion of the COP?
  ⚫ Is the CIP rapidly tailorable to support new missions?
  8-149. All-source analysts typically maintain the CIP. Whether information is automatically populated onto
  a unit CIP, or an analyst uses multiple systems and databases to attain information to build the CIP, updating
  the CIP should be addressed as a battle-rhythm event, much like INTSUM and running estimate activities.
  The higher headquarters typically annotates CIP requirements, including timelines for updates, within
  Annex B (Intelligence) of an OPORD.