Step-by-step instructions for incident logging, reporting, office duty, equipment, training, personnel, and admin tasks. Use this page as the operational checklist; use the navbar for daily navigation.
Incident Response Log is the running record of all incidents. Incident Report is filed after the event, from a specific incident’s page.
/incident/<id>/report/) to submit narrative and upload media.
Inventory Management tracks what each unit holds. Maintenance records service and faults. Overdue maintenance is the escalation queue.
Office duty is recorded per volunteer per calendar month (days in office) through a hub under Personnel: download template, upload CSV, and (for admins) track submissions and nudge UICs. Training tracks programmes and attendance coverage. Personnel detail management includes roster changes (de-roster / reinstate) from a volunteer’s page, plus unit and profile upkeep.
/personnel/office-duty/) — Admin or Unit In-Charge with an assigned unit (also linked from the Personnel menu).
/personnel/office-duty/email-uic/) when you want the system to mail the template; if a unit has no UIC email on file, nothing is sent — download the template from the hub and contact them manually.
These links are for superusers and admin role users. They cover Django’s admin interface and bulk management of users and units.
Vehicles are assigned during incident dispatch. Day-to-day fleet records:
Office duty started/ended correctly → glance at open incidents → scan overdue maintenance → confirm training instances on the calendar match ground reality.
Incident report filed → equipment status updated → volunteers’ duty records accurate → any follow-up training or admin notes captured in Admin if required.