video1.0<iframe src="https://www.loom.com/embed/cced3df1ae2942cc955aadb8af3beed6" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/cced3df1ae2942cc955aadb8af3beed6-e94c9b5418e61adc.gif867.536This Loom explains optional Step 4: pre-populating CrisisWorks with priority fire prevention properties before patrol inspections begin. It covers two approaches: importing properties from a council property database or importing properties from the previous season’s Fire Prevention Notices event, using filters like “Hazards Exist Status Ever” and “Request Clearing Status Ever,” then exporting an Asset Code CSV. It also walks through preparing the CSV, ensuring case-sensitive and space-sensitive column headings match CrisisWorks field mappings, deduplicating on asset code, and using status codes such as 3 for draft inspection or 10 for first inspection required. The video recommends testing in a test event first and then completing the full import into the live event after verifying event ID, locations, inspection status, and officer assignments.