What are the steps involved in preparing an emergency response guide?

The essence of compiling emergency response guidelines is to solidify scattered emergency response experience into an operational manual that can be implemented and replicated. The core needs to go through four core links: risk base calculation, full-scenario response link disassembly, practical verification and polishing, and dynamic iterative updates. It is most taboo to copy general templates and make paper articles.

Just like making a first aid plan for a person, you must first know what basic diseases he has. The first step in making a guide is to understand the applicable scenarios. For example, to make a fire emergency guide for an old community, you must first find out how many elderly people living alone with limited mobility are in the community, which section of the fire escape is often blocked by electric vehicles, and the nearest fire station to send police. How long does it take to get there, and which corridors are piled with debris all year round? These basic information are not accurate, and the written guide is likely to add confusion - I have seen streets copying the general template before, requiring residents to evacuate to the west gate in case of fire. As a result, the west gate has been blocked by construction for half a year. The consequences of an actual danger are unimaginable.

Once you have figured out the bottom line, don’t rush to pile up the terms. You have to put yourself into the “real accident” scenario and walk through it. From who will report a danger as soon as a danger is discovered, who will notify key groups, and who will clear the disposal channel, to what tools are needed in each link, and what are the backup plans when the contact person cannot be found, all have to fall on specific people and specific operations. Don't write vague statements like "relevant personnel are responsible for handling". When an accident occurs, no one will know who the "relevant personnel" are.

The process you complete by yourself is somewhat taken for granted, and you have to run it through with all relevant people before you know where the pitfalls are. Last year, when our park was working on a rainstorm emergency guide, we initially calculated according to the regulations that 20 sandbags piled at the entrance of the underground garage would be able to block water. However, during the actual simulation, we discovered that the entrance is on a gentle slope, and the piled sandbags would leave gaps. At least 35 sandbags would be needed in conjunction with waterproof baffles to block leaks. If we hadn't practiced in advance and used them directly, the garage would definitely be flooded during a heavy rainstorm during the flood season.

The industry now has different views on the granularity of the guideline. Some people think that it should be written as detailed as possible, and even the words used when notifying residents should be clearly marked. Others think that emergency scenarios are highly variable, and that enough flexibility should be left without being too stuck. In fact, both ideas are applicable. The operation pages for front-line cleaning and security personnel must be written as detailed as possible. They do not need to make on-the-spot judgments and just follow the instructions. ； The version for on-site command can list several alternatives to facilitate flexible adjustments according to actual conditions.

Don’t just lock the guide in a file cabinet as a display after writing it. The surrounding environment changes, loopholes are discovered during exercises, or even small dangers expose problems. The content must be updated in a timely manner, just like patching a mobile phone system. The more loopholes are patched, the fewer loopholes will be used. Only when it is really needed will it be used.