[Return to ReadyIndy_EOP] [Go back to your personal 'bookmoves'.]
"Pray the Lord of the Harvest will send forth workers into His harvest field."
Under construction: we're re-writing. Pardon our dust.
In the meantime, follow our published EOP pdf Alerts/Telecon/Zello section.
*** ALSO REFERRED TO AS OUR 'CALL-OUT' ***
This is only the written narrative re our "Rollcall/Alerts/CheckIn/Assignments" Process.
(See 'Assignments' sheet to actually see the process in motion, during an activation.)
Alerts: Goal: During an activation, everyone should know immediately (and check-in quickly) when the initial Alert is tweeted @ReadyIndy, Send ALERT via @ReadyIndy and @IndyPrayer. "Emergency Alert. We're activating our Incident Action Plan .. http://cityreaching.pbworks.com/ReadyIndy_EOP
Do YOU know how to get set-up to receive tweets as immediate texts to your phone?
Easy: Just text the phrase ON readyindy ...to 40404.
The following process should be accomplished during an activation while en route to the designated EOC.
(Please check-in even if you CAN'T participate -- so that we know you're unaccounted-for, but available.)
Check-in Process ,...
- Easy. Just check-in by leaving a COMMENT in the main incident post, within our Facebook Core Group. Be sure and note your preferred ROLE.
Still under-constuction below...
Everyone should already have a printed-roster of contact info... in your emergency GoKit... and on your lanyard's thumbdrive.
LEADERS: |
Leader Calls/Recruits an Ops Officer (next section below). Then alert ReadyChurches and affiliated network(s).
|
|
Send ALERT via @ReadyIndy and @IndyPrayer. "Emergency Alert. We're activating our Incident Action Plan .. http://cityreaching.pbworks.com/ReadyIndy_EOP
|
|
|
|
|
OPERATIONS: |
Ops Officer Calls/Recruits 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.
|
|
|
|
|
|
|
PLANNING/PIO: |
Planning/PIO Officer Calls/Recruits a PCS officer. Initiate contacts re Planning/PIO below... and hoping to recruit a PIO so we can split the combined-role into separate roles. Then similarly, the PIO will hope to recruit a ReadyVOST leader to recruit digital workers throughout the internet. Below, each person should 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. |
|
Ensure ALERT was sent @ReadyIndy and @IndyPrayer.
|
PIO |
|
VOST |
|
|
|
PCS: |
PCS Officer Calls/Recruits 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. |
|
|
Prayer |
|
Care |
|
Share |
|
|
|
|
|
LOGISTICS: |
Logistics Officer initiates contacts of Logistics people below... Then takes responsibility for Volunteers Triage (section below). Meanwhile, Logistics team continues calling the next person listed below. 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. |
|
|
|
|
|
|
SUVs TRIAGE
(volunteers)
|
Logistics Officer takes responsibility for staging all 'resources', including human resources = example: Sudden Untrained Volunteers (SUVs). We have a specific process for volunteer-triage, to quickly get them ID'd and into their best roles... click here. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
************* FORMER PAGE CONTENTS -- DELETE SOON ***********
Document Purpose: It describes how everyone in our 'Tier 1' group (see ROSTER) gets notified and accounted-for quickly, and slotted into role Assignments. Here's how...
Anyone MAY be the very first to know! Follow your personal 'bookmoves', including texting/tweeting/posting your status. Therefore others may/will know about an emergency before we officially 'activate the team'. [BUT... IMPORTANTLY... Please do not give the impression we're 'activating' yet -- please leave that decision to our leaders. See below.] As anyone becomes aware of the emergency, he/she may comment via our FB group -- thus the calling-tree order (below) may be accelerated because of the advance tip-off.
Activating our ReadyIndy team? Anyone can and SHOULD contact our leader(s) to determine if activating is appropriate. Do NOT self-deploy -- at least not under the ReadyIndy banner. Only our leaders can initiate our activation.
Then... Our ReadyIndy rollcall-tree goes like this:
- Leader (MikeBoler) confers with Operations Officer (see below) regarding hazards, our available inventory of resources (including people-resources), and together determine activation. After Operations Officer has been empowered to activate the RollCall, the Leader can Check-In (via our FB group) and begin carrying out his own role by issuing the initial alert in the FB group, and then @ReadyIndy and also the mobile alert via @IndyPrayer). (Or he may delegate the ALERT responsibility to the Planning/PIO Officer.)
(Here's some typical verbage to cut/paste... Not too much, not too little. Link to details. Best #tag to use, and which Twitter accounts to follow.)
"Emergency Alert. We're activating our Incident Action Plan ..
http://cityreaching.pbworks.com/ReadyIndy_EOP / #readycity @ReadyIndy @ChristEmNetwork "
These public alerts make it possible that anyone could immediately know about the emergency, even as we're going through the entire rollcall to ensure everyone is accounted for, and status known. After sounding these alerts, the Leader then begins scaling everything through partner collaboration, notably reaching his 'network' of other leaders:
- CEN (national hqtrs)
- ReadyChurch leaders,
- Ready Hispanic Chaplains leader (Gerson Cardona)
- Leader of neighborhood church closest-to-incident. (see map?)
- Local community affiliates: @INOFBCI, @DHSIndianapolis, @IndyMNLs, county(s) CERT leader(s), etc.
- Other personal network leaders, eg CBMC leaders who can in turn alert all their Pauls/Timothys throughout the city.
- Operations (BenMcCann) -- CHECKS-IN (via FB group) and then contacts/delegates the RollCall responsibilities to the Planning Officer (who has Roster, etc) -- and then immediately starts carrying out his Operations Role, contacting his various networks and recruiting...
- Safety/Security Officer (Steve Pappas may at times need to serve a dual role, Logistics/Security -- see Logistics role in order below.)
- Planning (NeilCox) -- CHECKS-IN (via FB group) and starts ASSIGNMENTs Form203 (and fill in your name there as Planning Officer) and then contacts PCS Officer & Logistics Officer -- see below. Then starts Planning/PIO role by contacting all Tier1 planning/pio people on the roster and recruiting...
- PIO -- CHECKS-IN (via FB group) and starts their PIO Role, ensuring the Alert (above) has gone out, recruits ReadyVOST Leader and County PIOs. Then connects with key Media contacts.
- ReadyVOST Leader. responsible for social-media, notably our public page on Facebook,
- Ensure that all key ReadyVOST roles have been filled. See ROSTER for available staffing.
- Recruit a virtual-buddy for each established role 'on the ground'. Follow same tree as this RollCall tree. Good practice, and it makes sense!
- County PIOs (when we have some) -- CHECKS-IN (via FB group) and begin their role, contacting their area churches (and updating church-markers on the Metro Ministry Map).
- ResourcesUnit -- notably, to quickly take over the Assignments function.
- Other Planning Section-Leaders: SituationUnit, DocumentationUnit, DemobilizationUnit, FinancialUnit, and other Technical Specialists -- They CHECK-IN (via FB group) and immediately begins their roles.
- Lastly, the Planning Officer reviews the entire ROSTER and ensures that all 'Tier1' team-members have been accounted-for. (This responsibility may have been delegated already to the ResourcesUnit or ReadyVOST member). [How so? Is out RollCall bullet-proof yet, re Tier1 folks?] Planning Officer updates the Incident_EOP re numbers contacted, etc.
- Logistics (NancyBuening or Steve Pappas) -- CHECKS-IN (via FB group) and contacts their team and begins their role, contacting & delegating:
- Hospitality (Food, Shelter, Clothing)
- Transportation
- Financial (see Financial Info & Controls role above, included in Planning section).
- Volunteer Mgmt -- As you triage volunteers, remember: Trained role folks above are NOT considered 'volunteers.
- SUVs -- Remember, our objective is to provide just-in-time training at the point of enlistment. Do not simply write down their names/contact info; ACTUALLY PROCESS THEM IMMEDIATELY... even if assigned to a reserve-role in the coming hours. [If our processing power hasn't yet scaled, assign newly-trained vols to help process more vols.]
*********
Remember: As we grow 9 county-teams (each with 5 core roles)... you will have a great number of people from which to select backup/reserves. So it's vitally important that we continue pressing forward to scale by building more & more teams throughout the metro area.
And let's all recruit a Virtual-Buddy in addition to our regular 'buddy'! Especially consider those who are digitally adept, and those who might otherwise not be able to participate 'on the ground'.
Ref: LA CERT Call-out Process.
Comments (0)
You don't have permission to comment on this page.