# Field operations

Product design

This page describes the product model and requirements. Examples illustrate the model, not a guaranteed API or completed feature. Check the [application contracts](/stormtrust/apps/) and [dataset inventory](/stormtrust/product/platform-and-data/datasets-and-source-contracts/) for implemented scope. Use [operations guides](/stormtrust/engineering/operations/) for runnable procedures.

Field operations converts prioritized storm intelligence into accountable human activity.

## Action plans

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

## Deployment zones

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

## Territories

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

## Assignments

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

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

Suggested statuses include:

```txt
unassigned
assigned
accepted
in_progress
completed
cancelled
blocked
```

## Canvassing

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`.

## Property visits

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

## Inspections

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

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

## Outcomes

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.