Field operations

Field operations converts prioritized storm intelligence into accountable human activity.

An action plan specifies an event, objective, prioritized geography, property count, crew capacity, assignments, campaign recommendations, and constraints.

A deployment zone is a work-oriented geography derived from storm intensity, property density, road accessibility, service area, territory ownership, and operational capacity.

A territory supports assignment, ownership, overlap rules, time scope, geometry, and event scope.

An assignment connects an actor to a target and expected action:

User or team
    ↓
Territory, property, or task
    ↓
Expected action

Suggested statuses include:

unassigned
assigned
accepted
in_progress
completed
cancelled
blocked

A canvassing record captures property, salesperson, territory, attempt, result, next action, timestamp, permitted location data, and notes.

Suggested statuses include not_visited, no_answer, contacted, not_interested, follow_up, inspection_requested, customer, and do_not_contact.

A visit retains actor, property, event, permitted arrival and departure data, notes, observations, photos, result, and next action.

Inspection workflows may capture the inspector, time, observed damage, roof facets, materials, photos, recommendations, and approved acknowledgments.

Inspection results remain distinct from radar-derived impact assessments.

Field evidence may include images, videos, notes, measured hailstones, roof observations, signed documents, and inspection results. Every item retains acquisition metadata.

Field activity can progress from visit to contact, inspection, opportunity, quote, contract, and revenue. An integrated customer relationship management (CRM) system may remain the final source for external outcomes.