Emergency Preparedness

Emergency Preparedness tracks the people and activities that keep your site ready to respond to an emergency: designated first aiders, fire marshals, emergency contacts, and evacuation drills — each as its own record with a last-done date and a next-due date.

Emergency readiness decays silently if it isn't tracked on a schedule: a first aider's certification lapses, a fire marshal leaves the organisation and isn't replaced, an evacuation drill hasn't run in over a year. Because every item type shares the same last-done/next-due structure, the register gives one place to see everything that's coming due for renewal or re-doing, regardless of what kind of readiness item it is.

Each record is one of four item types — Evacuation Drill, First Aider, Fire Marshal, or Emergency Contact — tied to a person or location, with a last-done date and a next-due date. There's no separate "expired" status; a record whose next-due date has passed is simply a record whose date field is in the past, visible to anyone sorting or filtering the list by that field.

The list page shows every item with its type, the associated person or location, and both dates, filterable and sortable. The detail page shows the full record; create and edit forms share the same fields.

• Item type — required. One of Evacuation Drill, First Aider, Fire Marshal, Emergency Contact.
• Person or location — required. Who holds this responsibility (for a First Aider or Fire Marshal) or where it applies (for a drill).
• Last date — required. When this was last done or last confirmed.
• Next due — required. When it needs to be done or reconfirmed again.

Creating or editing a record requires both dates to be set — there's no way to log an item without a next-due date, since an emergency-preparedness item with no future check-in date defeats the purpose of tracking it at all.

Reviewing upcoming emergency-preparedness due dates is a natural standing item for an H&S Committee meeting, though the two registers aren't linked by a relational field in the current version — cross-reference manually when preparing a meeting's agenda.

Can one person be recorded as both a First Aider and a Fire Marshal? Yes — create two separate records, one per item type, since each type tracks its own independent last-done/next-due cycle.

Does an overdue item block anything else in the product? No — it's a visible signal in this register only; it doesn't currently gate any other module or workflow.