The Logistics Release Point (LRP) Meeting
“THE LOST OPPURTUNITY”
Grizzly CSS Team
SFC Cedric L. Busby, SFC Henry L. Morton Jr.,
SFC Ganon McClory,
The Logistics Release Point (LRP) meeting is conducted daily before the Task Force (TF) Logistics Package (LOGPAC) arrival to its designated location. This meeting allows the Task Force to gather key CSS leadership to discuss future CSS coordination. The LRP is an opportunity many units fail to use fully. The TF usually has no clear understanding of what the LRP meeting is suppose to achieve and/or fails to conduct a meeting at all. This article will discuss what an LRP meeting can accomplish and offers Tactics, Techniques and Procedures (TTP) on agenda, attendees and hard copy request flow.
WHAT CAN THE LRP MEETING ACCOMPLISH
A LRP meeting is run by the TF S4 or XO and should be held 30 to 60 minutes before the arrival of TF LOGPAC. The LRP meeting involves all of the TF’s key CSS leadership. The meeting is open discussion based and is intended to articulate the details for the synchronization of the TF CSS effort with the TF maneuver effort. The meeting is an exchange, of information and hard copy requests, between the TF’s First Sergeants, specialty Platoon Sergeants and the TF S4. The requests are given directly to the S4 and the HHC 1SG. This exchange allows for the planning of the upcoming day’s daily LOGPAC. It also provides a snapshot in time of the TF’s current state of readiness and its future anticipated requirements. Additionally, the exchange of 5988Es/2404s may be conducted under the supervision of a Unit Maintenance Collection Point (UMCP) representative and a discussion of the unit’s critical maintenance issues can be addressed. Using this technique the LRP meeting becomes more efficient, organized and a valuable asset and tool for the TF S4 and XO.
PREFACE: 71-2 CONCEPT OF LRP MEETING
Doctrine provides a general concept for the LRP meeting. However, when referencing Field Manuals covering operations at the LRP, you will find there is little specific information written. An actual agenda of an LRP meeting, which is provided in FM 71-2 page 7-16, is listed below.
FM 71-123 has a brief list of attendees, which includes a representative from the CTCP, all 1SGs and the TF XO. This attendee list is incomplete and the agenda does not provide clear guidance as to what the meeting is to accomplish. The following information will offer TTPs for the organization of the LRP meeting and enhance what is written in FM 71-2 and FM 71-123.
TFs should develop an agenda to follow at the LRP meeting.
Using an agenda will allow for a well-organized and less time consuming meeting. The importance of this and any other CSS planning is that it must become SOP and be practiced before the unit’s arrival at a Combat Training Center (CTC).
LRP meetings must have an agenda. The key is that the Agenda must meet the desired End state.
LRP ROLE CALL
The LRP meeting should be the center of gravity for all CSS coordination. Unfortunately, newly attached units and specialty platoons are key players who are rarely in attendance. One solution is for the TF to set a standard attendee list that will be in effect at every LRP meeting and to ensure all attachments are made aware of this requirement as soon as they are assigned to the TF.
TTP: LRP MEETING ATTENDEES
An example role call would involve the following key CSS leadership
HARD COPY REQUEST FLOW AT THE LRP
A key time saver at the LRP meeting is the submission of hard copy supply requests forms. There are numerous names for the supply request forms, (normally color coded), but the key is to use a four-copy system. The requesting 1SG or Specialty Platoon SGT keeps the first copy as a record for what should arrive on the following LOGPAC. The second copy is given to the S4 who maintains a copy at the Combat Trains Command Post (CTCP); this copy will give the S-4 a snapshot of the total TF requirement. The third copy is given to the HHC 1SG at the LRP meeting who in turn takes all of the copies back to Field Trains Command Post (FTCP) for the consolidation of bulk pushes. The unit’s supply sergeant, who fills all other classes other than bulk, maintains the fourth copy. Four copies of the request form will ensure the next LOGPAC will arrive with the appropriate supplies requested.
TTP: USE OF A FOUR-COPY SUPPLY REQUEST
COPY 1-UNIT SUPPLY SGT: FILLS REQUEST FOR CL I,II,IIIP,VII,IX,WATER
COPY 2-1SG/SPECIALTY PLT SGT: RECORD OF REQUEST
COPY 3-S4: GIVEN AT LRP AND TAKEN TO CTCP FOR TF OVERVIEW
COPY 4-HHC 1SG/FTCP: SUPERVISION OF EXECUTION OF SUPPORT
The decisive point for TF CSS operations at any CTC on a daily basis is the LRP meeting. Understanding the importance of the LRP meeting and what it can accomplish is the first hurdle that the S-4 must overcome during the unit’s deployment to a CTC. The concept, agenda and purpose of the LRP meeting are simple tasks to accomplish when employed. Nevertheless, few units conduct LRP meetings and most units who attempt, usually have an ineffective outcome. To overcome this pitfall, units should begin by utilizing an agenda, ensure the right participants attend, and use hardcopy requests to provide redundancy to FM request. This article will aid a unit’s future success by helping them to understand the importance of the LRP meeting and what the unit can accomplish when they use the TTPs discussed herein.