> ## Documentation Index
> Fetch the complete documentation index at: https://docs.officeridge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Readiness

> Compliance deadlines, IT system readiness and backup power, and weather monitoring.

These tabs cover your current state of readiness: what is due, whether your systems will survive an
outage, and what the weather is doing.

## Compliance Calendar

Regulatory compliance deadlines, events, and milestone tracking.

**Columns:** Title · Type · Due · Priority · Status · Completed

The same calendar surfaced in [Quality and audits](/compliance/quality), shown here because
preparedness obligations have deadlines too — drill frequencies, plan reviews, and continuity
attestations.

## IT Systems

IT system readiness for emergencies including backup power availability.

**Columns:** System · Readiness · Backup Power

| Field            | What it records                         |
| ---------------- | --------------------------------------- |
| **System**       | The system in question                  |
| **Readiness**    | Its assessed readiness for an emergency |
| **Backup Power** | Whether it has backup power available   |

<Warning>
  A system without backup power is unavailable during an outage, which matters most for anything your
  staff need in order to reach members. Record this honestly — an optimistic assessment here becomes
  a failure during an actual event.
</Warning>

Recovery targets for these systems are set in [Plans and procedures](/emergency/plans) as RTO and
RPO values.

## Weather

Weather observations for emergency monitoring with temperature and conditions.

**Columns:** Time · Temp F · Condition

Weather monitoring supports operational decisions during developing events — whether to reschedule
visits, activate a plan, or contact members early.

<Tip>
  Extreme heat is a genuine risk for home care members, not just storms. A member without working air
  conditioning during a Texas summer needs the same attention as one in a flood zone.
</Tip>

## Assessing IT readiness

<Steps>
  <Step title="List every system staff depend on">
    Including anything needed to contact members or access their information.
  </Step>

  <Step title="Assess readiness for each">
    Consider what happens during a power loss, an internet outage, and a full site loss.
  </Step>

  <Step title="Record backup power availability">
    Honestly.
  </Step>

  <Step title="Compare against your recovery targets">
    A system with no backup power cannot meet a short RTO.
  </Step>

  <Step title="Review after any infrastructure change">
    New systems and changed arrangements both invalidate a previous assessment.
  </Step>
</Steps>

## During a developing event

<Steps>
  <Step title="Monitor conditions">
    Track the weather tab alongside official sources.
  </Step>

  <Step title="Identify at-risk members">
    Use [Maps](/maps) to see who is in the affected area.
  </Step>

  <Step title="Activate the relevant plan">
    See [Plans and procedures](/emergency/plans).
  </Step>

  <Step title="Contact members early">
    Before conditions prevent it.
  </Step>

  <Step title="Consider contingency coverage">
    If you may not be able to deliver care. See [Continuity](/operations/continuity).
  </Step>
</Steps>

<Warning>
  Weather observations in OfficeRidge support your decisions; they are not an official forecast or
  warning service. Always rely on National Weather Service and state emergency management advisories
  for evacuation and warning decisions.
</Warning>

## Troubleshooting

| Problem                                              | What to check                                                                     |
| ---------------------------------------------------- | --------------------------------------------------------------------------------- |
| A system shows ready but failed during an outage     | Reassess **Backup Power** and **Readiness**. The prior assessment was optimistic. |
| The compliance calendar shows nothing due            | Preparedness deadlines need adding with **Due** dates.                            |
| I need to know which members are in an affected area | Use [Maps](/maps) for geographic distribution.                                    |
| Weather data looks stale                             | It supports monitoring, not real-time warning. Use official sources for warnings. |

## Related

<CardGroup cols={2}>
  <Card title="Maps" icon="map" href="/maps">
    Where your members and staff are.
  </Card>

  <Card title="Continuity" icon="life-buoy" href="/operations/continuity">
    Backup agency coverage.
  </Card>
</CardGroup>