This simulator turns the incident-command structure described in Apiary Emergency Response into a live network: declaring a poisoning, fire, storm or theft incident sends a notification from the incident node to a pre-designated coordinator, who then dispatches the logistics, communications and documentation roles in parallel. Each role works through its own task list β relocating hives, contacting stakeholders, logging the response β before the incident is marked resolved. Tuning team readiness and channel clarity shows directly why the two highest-leverage fixes in a real emergency plan are pre-agreed roles and a single, fast communication channel: both delays compound into the total response time.
An incident node notifies a coordinator, who dispatches three roles β logistics, communications, documentation β each carrying out its required tasks against a target: hives get secured, stakeholders get contacted, and a document log grows with every action recorded.
Pick an incident type, set team readiness and channel clarity, then click Declare incident and watch the response time, task count and resolved average update as the network works through the incident.
Formal incident command systems, borrowed from fire and emergency services, assign roles before an incident happens specifically so nobody has to decide who does what while the incident is already underway β the plan's value is almost entirely in the pre-agreement, not the paperwork.
A single hobbyist with one or two hives probably does not need a formal plan, but anyone managing multiple sites, staff, or commercial contracts benefits from at least a simple written version, since the value comes from having roles and contacts agreed before an incident, not during one.
A single pre-designated coordinator, ideally someone senior enough to authorise urgent spending or actions without checking with anyone else mid-crisis, should have clear authority to declare an incident and activate the response plan.
Record the time it was first noticed, every action taken and by whom, photographs of affected hives, any samples collected with a clear chain of custody, and communications sent to neighbours, regulators or insurers β this log underpins any later claim or investigation.
A short annual or twice-yearly review, ideally combined with a simple walk-through drill, keeps roles and contact details current and keeps the team familiar with the plan before it's actually needed.
The most common mistake is a lack of pre-agreed roles, which leads to duplicated effort, gaps in the response, and inconsistent communication going out to staff, neighbours or regulators from multiple uncoordinated sources.