13.07.2015 Views

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

2004 US Air Force OPERATIONAL REPORTING ... - Survival Books

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

WWW.SURVIVALEBOOKS.COM36 AFI10-207 4 APRIL 20085.3.3.3.6.3. Notes. Important checklist information that helps explain procedures or providesadditional information.5.3.3.3.6.4. Lead-ins. Statements found in checklists that direct which steps should beaccomplished in a particular situation; they can also direct the use of a different checklist.Lead-ins are usually presented in an “if, then” format and are always underlined.5.3.4. The example QRC subjects listed in Attachment 4 are not all-inclusive. CP managers shoulddevelop and maintain QRCs that are based on their unit mission and/or probability of occurrence.5.3.5. Checklist Markings. The use of "read a step, do a step, mark a step” checklist discipline isrequired. Controllers will not proceed from one step to the next without appropriately marking eachstep. All steps must be annotated appropriately before a checklist is considered complete. The followingstandard markings will be used:5.3.5.1. A “v” (check) indicates an action was accomplished.5.3.5.2. An “O” indicates an action was noted or initiated but not completed. (Opening a stepprior to reading/acting on the step is not required.)5.3.5.3. An “N” indicates that the action does not apply.5.3.5.4. A “P” indicates a checklist item was previously accomplished.5.3.5.5. An “S” indicates that the checklist item is to be simulated.5.3.6. QRC Review. At a minimum, semi-annual reviews will be conducted/documented on a locallydeveloped form or promulgation letter in the applicable binders. QRCs relating to Nuclear Surety willbe reviewed by Unit Weapons Safety personnel annually IAW AFI 91-101. Safety review will be documentedon a letter of promulgation or other tracking sheet.5.3.7. Checklist Changes. The CP Chief/Superintendent must approve all new checklists, as well assignificant revisions to existing ones. The training manager will ensure all controllers are trained innew procedures and significant changes to existing procedures prior to posting. Controllers will beadvised of checklist changes by CIF. Changes to QRCs relating to Nuclear Surety must also bereviewed by Unit Weapons Safety personnel prior to posting.5.4. CP Daily Events Log. All CPs will maintain a CP daily events log using AF Form 4377, Events Logor other media prescribed by the owning MAJCOM. At minimum, CP daily events logs will be markedFor Official Use Only (FOUO) and classified according to content. The object of the CP daily events logis to serve as an official continuous record of events affecting the unit or functions of the CP. CPs must beable to reconstruct the events that occur during any given duty shift. CP management will develop andmaintain an OI governing the policies and procedures for preparing the log. A CP daily events log will becompleted for each 24-hour period. Each CP daily events log will typically be opened at 0001Z and closedat 2359Z, continuous 24-hour logs, whether web-based or not, are authorized at MAJCOM discretion.Entries will be made in chronological sequence using Zulu time. Events logs for exercises will not bemaintained with real world CP daily events logs. At a minimum, the log will document the following:5.4.1. All controllers on duty.5.4.2. Shift checklist/changeover completion.5.4.3. Significant events and notifications. The entry will include the checklist used and actions taken.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!