farm resilience / Farm owners, managers, workers, livestock and crop teams, contractors, safety coordinators, local advisers, emergency planners, utilities, veterinarians, and technology providers
Farm severe-weather readiness drill
Run a safe tabletop drill from one authoritative weather message through farm location and exposure mapping, delivery and acknowledgement, approved actions, fallback communications, continuity and after-action correction.
See the whole mission
Orient before entering the field.
Connect the intended outcomes, operating stages, stop conditions, and supporting technology concepts before opening the detailed action sequence.
- 01Distinguish official alerts, forecasts, local observations and farm decisions
- 02Map exposed people, animals, crops, structures, mobile equipment and critical services
- 03Test recipient routing, acknowledgements, escalation, alternate channels and shift handoffs
- 04Close plan, contact, map, device, training and continuity gaps without simulating dangerous field action
- 01Choose a bounded tabletop scenario
A useful exercise needs one event, time, farm operating state and decision boundary rather than a vague discussion of bad weather.
3 field actions ↓ - 02Test geographic and operational matching
A valid alert can still be routed to the wrong site, old field, absent crew, stale phone list or asset that has moved.
3 field actions ↓ - 03Exercise delivery and approved response
A notification icon does not prove receipt, understanding, authority or execution of a site plan.
3 field actions ↓ - 04Close the warning and recovery handoff
Readiness erodes when all-clear authority, restoration checks, missed recipients and plan changes are not reviewed.
3 field actions ↓
- G01
This is a tabletop readiness guide, not a forecast, evacuation, shelter, rescue, animal movement, crop protection, machinery or emergency procedure.
- G02
Never create live danger, move people into exposed areas, disable systems or delay response to test a warning workflow.
- G03
Follow current National Weather Service messages, local emergency authorities and approved site-specific plans.
Choose a bounded tabletop scenario
A useful exercise needs one event, time, farm operating state and decision boundary rather than a vague discussion of bad weather.
- 01Select a fictional or historical weather scenario, premises and fields, season, shift, crews and visitors, livestock groups, crops, structures, equipment, transport, power, water and communications state
- 02Use an example authoritative message with issuer, event and message identity, geography, sent and effective times, status and update lifecycle; label all exercise data clearly
- 03Identify emergency authority, farm plan owner, facilitator, observers, stop conditions, excluded live actions and the exact questions the drill will test
Test geographic and operational matching
A valid alert can still be routed to the wrong site, old field, absent crew, stale phone list or asset that has moved.
- 01Compare alert area with current premises, field and facility boundaries, forecast zones where applicable, access routes and mobile asset locations without claiming site impact
- 02List exposed workers, lone workers, visitors and contractors; animals and groups; crop or stored-product areas; structures, machinery and critical services with responsible roles
- 03Mark unknown, stale, outside-area, near-boundary and conflicting locations separately and identify who can resolve them
Exercise delivery and approved response
A notification icon does not prove receipt, understanding, authority or execution of a site plan.
- 01Send only clearly labeled test messages through approved channels and record dispatch, delivery, acknowledgement, failure, escalation and alternate-contact timing
- 02Walk through protective actions only as a tabletop using current public guidance and the approved farm plan; do not improvise evacuation, shelter, equipment movement or electrical work
- 03Test after-hours coverage, language and accessibility, poor connectivity, dead battery, power loss, unavailable supervisor, visitor accountability and emergency-services handoff
Close the warning and recovery handoff
Readiness erodes when all-clear authority, restoration checks, missed recipients and plan changes are not reviewed.
- 01Identify who can declare each transition under the plan, what site verification is required and which animal, crop, utility, structure or access concerns need qualified review
- 02Record what worked, failed, arrived late or remained unknown across data, devices, contacts, roles, maps, channels, plans, training and dependencies
- 03Assign owner, due date, temporary control and evidence of closure for each action; version the plan and set a retest trigger
Continue through the operation
See where this field guide fits.
Move beyond one task into the complete evidence, technology, operating, and review sequence around it.
Run the farm disaster resilience chain
Move from authoritative hazard information and farm exposure mapping through warning delivery, accountability, continuity, critical-load review, safe damage evidence, authorized reporting, recovery acceptance and governed records.
- 01 / RECEIVEUnderstand agricultural hazard alertsTechnology→
- 02 / DRILLExercise the severe-weather warning chainField guide→
- 03 / MAP CONNECTIVITYUnderstand farm coverage mappingTechnology→
- 04 / SURVEYSurvey one farm workflowField guide→
- 05 / ARCHITECTUnderstand IoT connectivity dependenciesTechnology→
- 06 / REVIEW CHAINReview one connected endpointField guide→
- 07 / CONTINUEUnderstand communications continuityTechnology→
- 08 / EXERCISE OUTAGERun a connectivity outage tabletopField guide→
- 09 / COORDINATEUnderstand farm emergency coordinationTechnology→
- 10 / HAND OFFRun the communication and continuity drillField guide→
- 11 / KEEP ALIVETest farm critical-load resilienceField guide→
- 12 / DOCUMENTUnderstand disaster damage evidenceTechnology→
- 13 / AUDITAudit the post-disaster evidence packageField guide→
- 14 / DEFINE TECHNOLOGYUnderstand technology requirementsTechnology→
- 15 / WORKSHOPRun the requirements workshopField guide→
- 16 / PILOTUnderstand pilot acceptanceTechnology→
- 17 / TESTDesign the pilot evidence planField guide→
- 18 / COSTUnderstand lifecycle cost evidenceTechnology→
- 19 / REVIEW COSTReview the lifecycle modelField guide→
- 20 / RETAINReconnect the operational historyTechnology→
- 21 / GOVERNGovern sensitive incident evidenceTechnology→
- 22 / CONTROL ACCESSUnderstand identity and access lifecycleTechnology→
- 23 / AUDIT ACCESSTrace one role end to endField guide→
- 24 / ASSURE RECOVERYUnderstand backup and recovery assuranceTechnology→
- 25 / TEST RESTOREReview restore readinessField guide→
- 26 / CONTROL CHANGEUnderstand technology change controlTechnology→
- 27 / REVIEW CHANGEPrepare one bounded changeField guide→
- 28 / EXPORTUnderstand agricultural data portabilityTechnology→
- 29 / AUDIT PORTABILITYTest one representative exportField guide→
- 30 / GOVERN EXITUnderstand vendor exit governanceTechnology→
- 31 / REVIEW EXITBuild the supplier exit registerField guide→
- 32 / RETIREUnderstand secure decommissioningTechnology→
- 33 / VERIFY RETIREMENTReview one connected assetField guide→
- 34 / TRANSFERUnderstand ownership-transfer assuranceTechnology→
- 35 / HAND OVERRun the connected-equipment transfer reviewField guide→
- 36 / IDENTIFYUnderstand master data and identifiersTechnology→
- 37 / CROSSWALKReconcile one entity classField guide→
- 38 / ORDER TIMEUnderstand event-time integrityTechnology→
- 39 / REVIEW TIMEReconstruct one farm timelineField guide→
- 40 / REFERENCE SPACEUnderstand geospatial assuranceTechnology→
- 41 / REVIEW SPACEAudit one spatial handoffField guide→
- 42 / TRACEUnderstand data provenance and lineageTechnology→
- 43 / AUDIT LINEAGETrace one agricultural recordField guide→
- 44 / GOVERN AIUnderstand agricultural AI governanceTechnology→
- 45 / REVIEW AIReview one proposed AI use caseField guide→
- 46 / EVALUATE AIUnderstand performance evidenceTechnology→
- 47 / AUDIT CLAIMAudit one AI performance claimField guide→
- 48 / MONITOR AIUnderstand model drift assuranceTechnology→
- 49 / REVIEW DRIFTReview one deployed modelField guide→
- 50 / HAND OFFUnderstand human–AI decision handoffTechnology→
- 51 / EXERCISERun the human–AI handoff tabletopField guide→
- 52 / DESIGN TRIALUnderstand on-farm trial designTechnology→
- 53 / REVIEW TRIALReview one treatment protocolField guide→
- 54 / ASSURE MEASUREMENTUnderstand measurement assuranceTechnology→
- 55 / CHECK REPEATABILITYAudit one measurement chainField guide→
- 56 / GOVERN DEVIATIONSUnderstand deviation governanceTechnology→
- 57 / AUDIT EXCLUSIONSAudit deviations and exclusionsField guide→
- 58 / SYNTHESIZEUnderstand evidence transferTechnology→
- 59 / REVIEW TRANSFERReview multi-site evidenceField guide→
- 60 / BOUND AUTONOMYUnderstand autonomy operating domainsTechnology→
- 61 / REVIEW DOMAINReview one autonomous missionField guide→
- 62 / COVER PERCEPTIONUnderstand robot perception coverageTechnology→
- 63 / AUDIT VISIONAudit one perception claimField guide→
- 64 / SUPERVISEUnderstand autonomous mission supervisionTechnology→
- 65 / EXERCISE CONTROLRun the supervision tabletopField guide→
- 66 / FALL BACKUnderstand robot fallback and recoveryTechnology→
- 67 / REHEARSE RECOVERYRun the fallback and recovery tabletopField guide→
- 68 / AUDIT POLICYAudit the crop-insurance registerField guide→
- 69 / AUDIT ACRESAudit the acreage reportField guide→
- 70 / AUDIT PRODUCTIONAudit production historyField guide→
- 71 / AUDIT NOTICEAudit loss notice and inspectionField guide→
- 72 / AUDIT CLAIMAudit claim settlementField guide→
- 73 / REVIEW SUPPLIERReview input supplier resilienceField guide→
- 74 / AUDIT ORDERAudit the input orderField guide→
- 75 / AUDIT DELIVERYAudit input receivingField guide→
- 76 / RECONCILE INVENTORYAudit input custodyField guide→
- 77 / CLOSE PAYMENTAudit procurement paymentField guide
Exercise the severe-weather warning chain
Test location matching, people and asset exposure, delivery, acknowledgement, escalation, alternate communication, plan action and recovery handoff.