My WebLink
|
Help
|
About
|
Sign Out
Home
Search
04-01-13 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2013
>
04-01-13 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/6/2014 2:33:57 PM
Creation date
3/6/2014 2:27:52 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
04/01/2013
Council Meeting Type
Work Session Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
107
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br />3 <br /> <br /> <br />It is important that communication s be cons istent . The exact format should be determined by the <br />department director or a designee. An example is attached <br />Along with a consistent printed message, the C ity website should contain a sidebar with links to <br />each department ’s Green and Yellow level commu nication, along w ith a brief description of <br />each. A Red l evel communication is signified by a red graphic that contains the emergency <br />information , which should appear at the top of all the pages in the C ity website. <br /> <br /> <br />Roles and R esponsibilities of the P rimary and Backup C ommunications C ontacts <br /> <br />Both the PC and BC should be able to produce and post every medium of communication that <br />the department produces. For example , if the department has a F acebook or Twitter account, <br />both the PC and BC should have t he skills and training necessary to post to th e se sites. The <br />p rimary c ontacts and b ackup c ontacts for each department will be included in a “Green” email <br />group. All external communications will be copied to the Green email group to ensure that <br />department s are aware of any activity in another department . When the PC and BC receive <br />information from other departments, they should determine what information should be shared <br />with in their department . U sing the PCs and BCs as a hub of citywide communication wi ll <br />reduce in formation overload. <br /> <br />The PC and BC should be adequately trained in the legal aspects of communicati on via social <br />media , which includes data privacy. <br /> <br />The PCs and BCs for each department should meet monthly to evaluate the communication <br />proces s and any upcoming events. <br /> <br />Roles and Responsibilities when Red L evel C ommunication is a nnounced <br /> <br />When a condition exists that requires immediate and urgent communication, a Red l evel alert <br />will be issued. Because an emergency condition will affect publ ic health and safety, the Public <br />Services Director or Public Safety Director will be the primary point of contact depending on the <br />specific nature of the situation. The responsible d irector or designee will prepare the alert in <br />coordination with the City Administrator. No official Red level communication should be sent <br />prior to notifying the City Administrator unless it is not practicable to do so . Once created, the <br />message will go out to the Red email group . D epartment d irector s are responsible for ens uring <br />that the message goes out on every available communication medi an . If a condition exists that <br />requires more than a notification, the responsible d irector may call for the use of an emergency <br />operations center , which would operate under the guideline s of the City’s E mergency <br />M anagem ent Plan. <br /> <br />There may be a need to update staff on Red level communications with information that is not <br />for public consumption. Any such printed or electronic communication should be prefaced with <br />the following words: “F OR INTERNAL COMMUNICATION ONLY. NOT TO BE <br />R ELEASED TO THE PUBLIC OR MEDIA.” <br />
The URL can be used to link to this page
Your browser does not support the video tag.