Download signNow app
4.7 / 5 rating on

University Emergency Action Plan

Use a University Emergency Action Plan 2019 template to make your document workflow more streamlined.

What the university emergency plan does

The University Emergency Action Plan is a campus document that records how university personnel respond to identified emergencies, including assigned responsibilities, contacts, locations, and approval requirements. It is not a federally standardized form with one national filing deadline or issuing agency. A university prepares its own content, identifies authorized reviewers, and updates the plan under institutional policy and applicable state law. With signNow, an administrator uploads the plan, reviews detected fields, sends signature requests, collects approvals, and stores the signed document with its audit trail.

Which institutions use the plan

The University Emergency Action Plan helps education organizations coordinate safety responsibilities across departments, buildings, and campuses.

  • A small college can reuse a controlled emergency-plan template, route signatures to its safety coordinator and president, and archive each approved campus-specific version with its audit trail.
  • A multi-campus university can coordinate facilities, public safety, student services, and administrators through assigned roles, shared templates, and delegated sending for location-specific emergency procedures.
  • A state university system can connect plan records to Microsoft 365, Google Drive, or Box while preserving signer activity and access controls for institutional review.

These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.

Who uses this university plan

Campus safety

Campus safety and emergency management teams use the plan to document response roles, facility procedures, emergency contacts, and approval workflows across university locations.

University administration

University administrators and department leaders use it to coordinate signatures, distribute approved procedures, and maintain a current record for faculty, staff, and responders.

Complete the university emergency plan

Use this sequence to prepare the University Emergency Action Plan and preserve a complete, reviewable record.

  • Upload the plan:

    Upload the completed campus plan and let signNow detect fillable fields.
  • Check the fields:

    Review emergency contacts, locations, responsibilities, and signature fields.
  • Assign reviewers:

    Assign university administrators, safety staff, and approvers in order.
  • Complete and store:

    Send the plan, collect signatures, and store the completed record.

How the plan moves to approval

The signNow workflow follows the document from university preparation through assigned review, electronic signing, and controlled record storage.

  • Upload: Upload the campus emergency plan.
  • Prepare: Review detected fields and assignments.
  • Send: Send signature requests to responsible officials.
  • Archive: Store the completed plan with its audit trail.
be ready to get more
Get legally-binding signatures now!
  • Best ROI. Our customers achieve an average 7x ROI within the first six months.
  • Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
  • Intuitive UI and API. Sign and send documents from your apps in minutes.

Review the plan audit trail

The audit trail records how the University Emergency Action Plan moved from invitation to signed, retrievable institutional record.

01

Authenticate signer:

The signer follows the assigned authentication path before opening the plan.
02

Capture timestamps:

signNow records the signing event time and related document activity.
03

Record document integrity:

The completed document receives an integrity record for later comparison.
04

Seal the document:

The signed file is sealed against undetected content changes.
05

Preserve activity history:

The audit trail preserves signer actions, access events, and completion history.
06

Export the record:

Authorized administrators retrieve or export the completed plan and evidence.

Connect campus emergency workflows

Connect university emergency planning with Salesforce, Microsoft 365, Google Drive, Box, NetSuite, or Procore to route records through existing institutional workflows.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Find and fill out the correct university emergency action plan

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

VersionsForm popularityFillable & printable
CSU Chico Emergency Action Plan 20194.8 Satisfied (1610 Votes)
CSU Chico Emergency Action Plan 20104.8 Satisfied (2685 Votes)

Configure the campus signing workflow

Configure the University Emergency Action Plan around institutional access, accountable signing, protected transmission, and a documented retention decision.

SettingRecommendation
Authentication methodEmail verification with SMS authentication
Signature typeElectronic signature with recorded intent
Audit trailCapture signing events and export evidence
Retention and encryptionApply campus policy with TLS and AES-256
User provisioningAssign administrators through controlled team access

Protect the emergency plan

Data in transit:

TLS 1.2/1.3

Data at rest:

AES-256 encryption

Security certification:

SOC 2 Type II

Information security:

ISO 27001

Protected health data:

HIPAA with BAA

Electronic signature law:

ESIGN and UETA

Retain the plan as institutional evidence

A University Emergency Action Plan should remain usable, traceable, and accessible to authorized campus personnel after signing.

Set a documented retention rule

Set a campus retention rule before collecting signatures. The federal framework does not create one universal retention period for every university emergency plan, so align the schedule with state law, institutional policy, and any records category involved.

Preserve the audit trail

Export the completed plan and audit trail together after final signing. Keep the evidence showing signer identity, timestamps, actions, and document history so administrators can explain how the approved version was created.

Limit access by responsibility

Restrict access to approved safety, facilities, and administrative personnel. Use shared templates for controlled reuse, delegated sending for authorized staff, and role-based permissions to reduce untracked edits to emergency contacts and procedures.

Review and archive approved versions

Review emergency contacts and response assignments on a scheduled institutional cycle. Replace outdated copies, record the new approval event, and archive superseded versions separately so responders can identify the active plan.

Choose the applicable retention period

The University Emergency Action Plan has no single federal retention period; use the record category, university policy, and applicable authority to set one.

01

University policy period

No federal retention period is specified for this campus emergency plan; apply university policy and state records law.
02

Six years for HIPAA records

If the plan contains HIPAA-covered records, retain them six years from creation or last effective date under 45 CFR 164.530(j).
03

Three years for tax records

If the plan includes federal tax records, retain them three years from filing under IRC §6501(a), subject to longer exceptions.
04

Three years or one year

If the plan includes employee Form I-9 records, retain three years after hire or one year after termination, whichever is later, under 8 CFR §274a.2(b)(2)(i)(A).
05

Thirty years for exposure records

If the plan includes OSHA exposure records, retain them 30 years under 29 CFR §1910.1020.

Protect plan privacy and access

  • Listing personal phone numbers or medical details in broadly shared plan copies can expose sensitive campus information.
  • Collecting signatures without documenting electronic consent may weaken evidence that participants agreed to use electronic records.
  • Leaving completed plans in personal inboxes can prevent authorized administrators from locating the current approved version.
  • Granting every contributor editing access can allow unauthorized changes to emergency contacts, locations, or response responsibilities.

Why the plan matters legally

A signed University Emergency Action Plan gives campus administrators a documented record of assigned responsibilities, approvals, and emergency procedures. Under the federal ESIGN Act and applicable state UETA or New York ESRA rules, electronic signatures can carry legal effect when intent, consent, attribution, and reliable record retention are established.

Why teams look for DocuSign alternatives
ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

28M+Documents signed
13+Years in business
4.6/5Average G2 rating

Questions about completing the plan

These answers address specific signing, access, retention, and compliance questions for the University Emergency Action Plan.

Upload the source document again in a supported file format, then review signNow’s detected fields before assigning campus officials. Auto-detection can reduce manual placement, but university-specific responsibilities and emergency contacts still require human review.

Confirm that every signer has the intended role and email address, then resend the signature request. signNow’s templates and delegated sending can standardize recurring university plans without changing the approved field assignments.

Use signNow’s audit trail to review timestamps, signer actions, and completion history. For institutional evidence, export the completed plan with its audit trail and retain both under the university’s records policy.

Business includes legally binding eSignatures, audit trails, templates, and mobile apps at $8 per user per month with annual billing. Business Premium is $15 and adds bulk send and kiosk mode.

signNow lists HIPAA compliance with a business associate agreement. FERPA obligations depend on the university’s education-record practices, access controls, and institutional policies; the platform’s HIPAA status does not determine FERPA compliance.

Electronic signatures can have legal effect under ESIGN and applicable state law when intent, consent, attribution, and record retention are established. This does not replace requirements for documents excluded from ESIGN, such as wills or court orders.

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.