Emergency Messages covers the practical knowledge, vocabulary, decisions, and field judgment needed for emergency messages within Navigation and Signaling. This page defines the topic broadly so the wiki can accept future manuals, diagrams, checklists, and local examples without narrowing the subject around a single document.
At this level of the library, the subject should be understandable to non-specialists and usable in difficult conditions. At A0, the subject must be usable under stress with little infrastructure, little time, and uneven training.
Communications topics preserve the ability to send, receive, confirm, record, and interpret messages when ordinary channels are limited or unreliable.
For InfoPreserver, emergency messages should be treated as a working capability rather than a label. A reader should be able to understand what problem the topic solves, what conditions make it harder, what signs or measurements matter, what mistakes are common, and when the issue belongs in a more specialized folder.
An emergency message should answer, in order: what happened, where, when, who is affected, what is known, what is uncertain, what action is required, who sent it, and when it will be updated. Put the action near the beginning when delay could cause harm. Use plain language, short sentences, familiar place names, and a time zone or “local time.”
Separate observation from interpretation. “Water is rising over the east road at 14:20” is more useful than “the town is flooding,” unless the larger conclusion has been verified. Record the source and confidence so a later sender can correct an error without hiding the history of the message.
Use a small number of priority levels. For example: routine information, preparation, urgent protective action, and immediate distress. Define who may issue each level and what acknowledgment is required. A complicated priority scheme fails when people are frightened, tired, injured, or working in poor light.
The sender should request a repeat-back for critical details such as names, coordinates, quantities, medication names, and times. The receiver should repeat the message in their own words and identify any missing part. A relay should preserve the original source, time, location, uncertainty, and requested action instead of silently compressing the message.
When radio or telephone service is unavailable, use a runner, posted notice, chalk or marker, flag, lamp, whistle, bell, or prearranged signal. A written message should include the date, time, sender, intended recipient, and expiration or update time. Do not leave an urgent warning where rain, wind, darkness, or ordinary traffic can erase or hide it.
Morse code is useful for short messages when a lamp, buzzer, whistle, knock, or radio key can reach the receiver but speech cannot. The international radio spelling alphabet is useful for spelling names, map references, call signs, and serial numbers. Neither system makes an unclear message clear: transmit the plain-language meaning first, then spell the critical word or number.
Messages should reach people who cannot hear a siren, read a small screen, speak the sender's language, move quickly, or access a powered device. Pair sound with light, vibration, text, pictograms, or a person who can explain the action. Never use a false alarm as a test without clearly announcing the exercise. Repeated vague or exaggerated warnings train people to ignore the next one.
Future additions should explain emergency messages in a way that a reader can evaluate, teach, and adapt. Good candidates include field guides, checklists, illustrated procedures, training notes, safety guidance, tables of limits or warning signs, repair or maintenance examples, and public-domain or open-license manuals.
Avoid narrow documents that only mention the topic in passing. If a future PDF belongs partly here and partly somewhere else, keep one primary copy and add cross-links from the related pages. When a source is technical, add a short orientation note explaining prerequisite skills and the A-level where it becomes fully usable.
This page is currently placed in A0 Survival Baseline. If later documents prove that the topic needs simpler emergency treatment or a more advanced technical treatment, it can be split into lower- and higher-level pages without losing this broad orientation.
Path: 10_A0_Survival_Baseline/Navigation_and_Signaling/Emergency_Messages
Page type: A0 topic guide with local documents
Current direct documents: 3 documents
Documents in this branch: 3 documents
Child folders: 0 folders
Navigation: Parent