Air Force Mentor Logo


AFMentor | Bookmark | Search | Mail Page | Comment


Appendix A: Commander's Call Action Plan

Shop at

Table of Contents

Getting to Know Your Boss Time Management The Schedule Suspense Tracking & Following Up Correspondence
The Boss’ Quick Reference Book
Protocol and Special Events Staff Meetings Technical Issues The Staff Car The Typical Day
A: Commander’s Call Action Plan B: Sample Background Paper C: Sample Protocol 3X5 Cards D: Sample Commander’s Reference Book E: Sample Exec Continuity Book
Example Desk Layout


This appendix is written to serve as a reference source on Commander’s Call requirements. It is designed to help organize a Commander’s Call and conduct pre-meeting steps. This document is not meant to be all-inclusive. Note that the intent of this document is a reference source and the Commander may direct modifications.

1. Establish a date for Commander’s Call (based on every 60/90 day cycle). The Exec and secretary should coordinate date and place for Commander’s Call. The Exec will develop checklists and task Action Officers (AOs) to perform the functions of protocol and visual information support for the event. Because each Commander’s Call may have different requirements, the Exec will issue guidance to AOs as necessary.

2. Request “Potential Topics” (3 weeks prior). The Exec or designated person will put an E-mail requesting “Potential Topics” from key staff members and Additional Duty Representatives. The Exec will establish a suspense for topic inputs. These inputs will be used to develop a Read-Ahead for the Commander.

3. Develop “Commander’s Call Read Ahead” (3 weeks prior). Exec will prepare and send a Read-Ahead to the Boss. The Read-Ahead will have three sections: agenda, potential topics, and discussion. The agenda will be a proposed schedule showing events from the beginning to the end of Commander’s Call. Potential topics should include topics the Commander previously requested and issues relevant to upcoming events. The Discussion section will contain questions or topics requiring the Commander’s input such as dry-run schedules, etc.

4. Commander’s Call Review (2 weeks prior). The Exec will meet with the commander to discuss the Read-Ahead. The purpose of this meeting is to finalize topics and issues presented in the Read-Ahead.

5. Approved Agenda (2 weeks prior). Following the Commander’s Call Review, the Exec or designated representative will finalize the agenda and build slides for the event. Additional Duty Personnel and others are responsible for building their slides using the template created by the Exec.

6. Finalize Material (1 week prior). At least seven days before Commander’s Call, all material is given to the Commander for his/her preparation.

7. Commander’s Call. Commander’s Call Held.

Click here to submit your information.
Send me Comments and Suggestions

Page Added on: 23 January 2006