| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Finally, you can manage your Google Docs, uploads, and email attachments (plus Dropbox and Slack files) in one convenient place. Claim a free account, and in less than 2 minutes, Dokkio (from the makers of PBworks) can automatically organize your content for you.

View
 

Kokomo_RollCall

Page history last edited by indychristian 7 years, 8 months ago

[Return to ReadyKokomo]

REDRAFTING THIS PAGE FOR KOKOMO USAGE  Forgive the remaining template-links herein.
Related:  Cindy is building a team ROSTER. Til then, here's a preliminary Roster.

 

Did YOU CHECK-IN VIA FACEBOOK GROUP yet?
During an activation, first do your personal bookmoves/alerts,
then check-in by leaving your COMMENT in the main incident post (even if you can't participate)!

 

This is the main Rollcall when activated and en route to the designated EOC (Emergency Operations Center).    Worst case: This plan below will effectively ensure that everyone is reached reasonably quickly.  BETTER-case scenario:  During an activation, everyone should know immediately (and check-in quickly) when they receive the initial Alert as it's tweeted at @ReadyKokomo.   Do YOU know how to get set-up to receive tweets as immediate texts to your phone?  Easy:  Just text the phrase   ON READYKOKOMO   ...to 40404. 

 

 Everyone should already have a printed-roster of contact info... in your emergency GoKit... and on your lanyard's thumbdrive.

LEADERS: Call/Recruit an Ops Officer (next section below).  Then alert ReadyChurches and affiliated network(s).
Travis Taflinger
Send ALERT via @ReadyKokomo (on Twitter) .  "Emergency Alert.  We're activating our Incident Action Plan .. http://cityreaching.pbworks.com/Kokomo 
Then contact CEN national office; then... (Then start listing your team of leaders... eg... name, name, name, name, name.)
   
   
OPERATIONS: Call/Recruit a Planning/PIO officer.  Initiate contacts re Ops below.  Everyone call the next person listed.  If they don't confirm the message immediately, move on to the next person.  Remember the best-case scenario:  it's likely that the next person already knows and has quickly checked-in.  So keep an eye on the Facebook core-group.
Jeff Newton
(Then start listing your team... eg... name, name, name, name, name.)
   
   
PIO/Planning: Call/Recruit a PCS officer.  Initiate contacts re Planning/PIO below.  Everyone call the next person listed.  If they don't confirm the message immediately, move on to the next person.  Remember the best-case scenario:  it's likely that the next person already knows and has quickly checked-in.  So keep an eye on the Facebook core-group.
Casey Cline
Ensure ALERT was sent @ReadyIndy and @IndyPrayer.  Then contact... (Then start listing your team... eg... name, name, name, name, name.)
PIO  
VOST  
   
PCS: Call/Recruit a LOGISTICS officer.  Initiate contacts of your PCS people below - Recruit at least one per Prayer-Care-Share category.  Everyone call the next person listed.  If they don't confirm the message immediately, move on to the next person.  Remember the best-case scenario:  it's likely that the next person already knows and has quickly checked-in.  So keep an eye on the Facebook core-group.
(who Kokomo?)
(Then start listing your team... eg... name, name, name, name, name.)
Prayer (Then start listing your team... eg... name, name, name, name, name.)
Care (Then start listing your team... eg... name, name, name, name, name.)
Share (Then start listing your team... eg... name, name, name, name, name.)
   

 

 
LOGISTICS: Initiate contacts of your Logistics people below.  Everyone call the next person listed.  If they don't confirm the message immediately, move on to the next person.  Remember the best-case scenario:  it's likely that the next person already knows and has quickly checked-in.  So keep an eye on the Facebook core-group.
(who Kokomo)
(Then start listing your team... eg... name, name, name, name, name.)
 

 

   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   

 

 

 

 

 

 

 

 

 

 

Comments (0)

You don't have permission to comment on this page.