User Guide: Emergency Override Logging
Last updated: January 15, 2026
Overview
The Emergency Override Logging feature ensures all emergency capacity overrides are properly documented for compliance and audit purposes. When normal scheduling limits must be exceeded due to emergencies, the system captures:
- Who requested the override
- When it occurred
- Why it was needed
- Who approved it (when applicable)
Why Emergency Logging Matters
- Compliance - Regulatory requirements for emergency response documentation
- Accountability - Clear record of who authorized exceptions
- Analysis - Identify patterns to improve capacity planning
- Audit Trail - Complete history for internal/external audits
Understanding Emergency Overrides
What Is an Emergency Override?
An emergency override occurs when:
- Normal daily inspection capacity is exceeded
- Standard scheduling rules are bypassed
- Priority booking overrides existing assignments
- Same-day inspections are scheduled outside normal process
When Emergency Overrides May Be Needed
| Scenario | Example |
|---|---|
| Public Safety | Gas leak requiring immediate inspection |
| Weather Events | Post-storm damage assessments |
| Critical Infrastructure | Hospital, school, or government building |
| Business Emergency | Fire-damaged business needing occupancy |
| Health Hazard | Sewage failure, contamination |
For Staff: Logging an Emergency Override
Step 1: Initiate Emergency Booking
- Navigate to Calendar App
- Go to Appointments or Inspections
- Click New Appointment or Schedule Inspection
- If capacity limits are reached, you'll see a warning:
"Daily capacity limit reached. Emergency override required."
Step 2: Select Emergency Priority
- Look for the Priority or Emergency field
- Select "Emergency" priority level
- The system notes this is an override situation
Step 3: Document the Reason
When creating an emergency inspection, provide:
Required Information:
- Emergency Type - Select category (public safety, weather, infrastructure, etc.)
- Reason - Brief description of why this is an emergency
- Requestor - Who is requesting the emergency inspection
Note: The detailed reason field is planned for future releases. Currently, use the notes field or contact your supervisor.
Step 4: Complete the Booking
- Fill in remaining inspection details
- Select inspector (may require manager assistance)
- Submit the emergency booking
- System logs the override automatically
What Gets Logged
Automatic Audit Trail
Every emergency override automatically captures:
| Data Point | Description |
|---|---|
| Timestamp | Exact date and time of override |
| User | Staff member who created the override |
| Activity Type | Marked as "Emergency" |
| Priority Level | Emergency priority flag |
| Inspection Details | Property, type, scheduled time |
Activity Log Entry
Emergency activities appear in the activity log with:
| Field | Value |
|---|---|
| Activity Type | Emergency |
| Priority | High |
| Created By | [Staff Name] |
| Created At | [Date/Time] |
| Inspection | [Property Address] - [Inspection Type] |
For Managers: Reviewing Emergency Overrides
Viewing Emergency Activity
- Open Calendar App
- Navigate to Activity Log or Audit Log
- Filter by:
- Priority: Emergency
- Activity Type: Override
- Date Range
Reports and Compliance
Available Views:
- List of all emergency overrides by date
- Count of overrides by inspector
- Overrides by emergency type
- Trend analysis over time
Manager Approval Workflow
Note: Manager approval workflow for emergency overrides is planned for a future release. Currently, emergencies are logged with the creating user's information.
Future workflow will include:
- Staff initiates emergency override
- Notification sent to manager
- Manager reviews and approves/denies
- Approved overrides proceed with dual authorization logged
Best Practices
When to Use Emergency Override
Do Use For:
- Genuine emergencies affecting public safety
- Time-sensitive situations with documented urgency
- Situations directed by management
- Weather-related urgent inspections
Do NOT Use For:
- Routine inspections that missed regular booking
- Convenience scheduling
- Applicant requests without genuine emergency
- Avoiding normal queue/wait times
Documentation Standards
When logging emergency overrides:
- Be Specific - Describe the actual emergency
- Note External Factors - Weather, incident reports, etc.
- Include Contact Info - Who reported the emergency
- Timestamp Accurately - Don't backdate entries
- Follow Up - Document resolution
Compliance Requirements
Regulatory Considerations
Emergency override logs may be reviewed by:
- Internal audit teams
- External regulatory agencies
- Insurance investigators
- Legal proceedings
Data Retention
Emergency override records are retained according to county policy:
- Minimum retention: [As per county policy]
- Part of permanent inspection record
- Subject to public records requests (redacted as appropriate)
Troubleshooting
Common Issues
Q: I need to schedule an emergency but the system won't let me. A:
- Check if you have emergency booking permissions
- Contact your manager for assistance
- Managers can override capacity limits
- Document the situation for later logging if immediate entry isn't possible
Q: I made an emergency booking but forgot to mark it as emergency. A:
- Open the appointment/inspection record
- Edit the priority field (if available)
- Add notes explaining the emergency
- Contact your manager to ensure proper logging
Q: How do I know if my emergency override was logged correctly? A:
- Open the inspection record
- Go to Activity Log or History
- Look for the emergency priority flag
- Verify your name and timestamp appear
Q: Where can I see all my emergency overrides? A: Ask your manager for access to emergency override reports, or check the activity log with appropriate filters.
Future Enhancements
Planned improvements:
- Reason Field - Structured reason capture for overrides
- Manager Approval Workflow - Required approval for certain override types
- Dashboard Metrics - Emergency override statistics
- Automated Alerts - Notification when override thresholds exceeded
Related Features
- Calendar Permissions - Role-based access to scheduling
- Audit Logs & History - Tracking all changes
- Rescheduling & Bulk Actions - Managing emergencies at scale
- Inspector Assignment - Assigning emergency inspections
Technical Notes
Audit Trail Logging:
- All emergency activities logged with priority level
- Timestamp and user automatically captured
- Activity type flagged as emergency
Current Implementation Status:
- Emergency activity logging: Implemented
- Priority level tracking: Implemented
- Manager approval workflow: Planned
- Structured reason field: Planned
For additional assistance, contact your System Administrator.