Crisis communication plan

If you have a medical emergency or other emergency call 911.

Marketing and Communications is the lead communicator in the event of a crisis affecting the wellbeing of UAF students, faculty and staff on campus and extending to UAF community campuses if applicable.  Working in concert with UAF's emergency response team, Marketing and Communications maintains the Nanook Hotline, the "UAF on Alert" website, and other communication tools to effectively communicate with UAF constituencies and the media in a timely manner.


The rapid release of accurate information regarding an accident, incident, natural disaster, emergency or controversial issue is clearly in the best interest of the University of Alaska Fairbanks. The UAF Crisis Communication Plan (CCP) plan does not change the way emergencies are initially reported at UAF. All emergencies on the Fairbanks campus and at UAF-owned and -operated facilities within the Fairbanks area should be reported immediately to the UAF Emergency Communication Center (police and fire dispatch center) at 907-474-7721.

Emergencies can occur at any time and without warning. Careful planning with an emphasis on safety will assist UAF community members in responding appropriately to crises and emergencies. Each department should have a plan for dealing with an emergency. This plan addresses media relations and communications issues and is an adjunct to the UAF Emergency Operations Plan.

The goal of UAF's CCP is to provide accurate information and visible leadership in a timely fashion. Without prescribed communication protocols in place, potentially damaging issues can negatively affect the institution's long-term image, credibility and public relations.

This plan establishes communications protocols to ensure that campus officials and communicators are familiar with both procedures and their specific roles. Details and exact procedures to be followed at branch campuses, and at other sites, should be developed and practiced locally. This plan is designed for internal use and is not intended to establish any standard of care enforceable by third parties.

Size: 138.2K bytes Modified: 24 August 2009, 13:11

Size: 43.7K bytes Modified: 24 August 2009, 13:11