Disaster recovery operations

Coordinate people, assets, work, and reporting during recovery.

Recovery is where most operations lose visibility. MX holds the whole cycle together — intake, assignment, field work, evidence, dashboards, audit, and reimbursement-ready reporting.

Discuss your recovery operation ↗Explore MX for emergency operations

↳ The platform for the long phase.

mx.recovery / day 18 · OPS-EAST-2026

recovery phase

OPERATION PHASES

Response

Assess

Recover

Close + audit

Work intake

3,420

2,108 closed

Contractors

188 crews

Spend

$1.42M

projected $2.61M

RECOVERY WORK · TODAY

WO-R-9821Pole replacement · Sector 7Crew D · vendor V-12● in-progress

WO-R-9819Substation 14 · breaker resetCrew B● in-progress

WO-R-9802Debris haul · Rt 22Vendor V-22 · 4 trucks● complete

§ 01 · Recovery operations cycle

From intake to reimbursement.

Recovery is where most operations lose visibility. The work spreads across crews and contractors, the evidence scatters, and the audit trail fractures. MX is built to hold it together.

Intake

Damage reports, vendor work, public submissions — captured and triaged into recovery work orders.

Assignment

Crews and contractors assigned by skill, certification, geography, and capacity.

Field work

Crews complete work via MX+, capturing photos, geotag, narrative, signatures, and time.

Verification

Supervisors verify completion. Exceptions surface to dashboards. Photos and evidence retained.

Cost & audit

Cost lines generated by rule. Audit trail per work order, per crew, per asset, per cost line.

Reimbursement

Reporting and exports formatted for the funding authority — federal, state, vendor, or internal.

§ 02 · Recovery capabilities

A platform for the long phase.

Response is intense. Recovery is long. The capabilities below are what keeps operations coherent across weeks, months, and sometimes years of work.

Recovery work intake

Multi-channel — phone, vendor, public, internal — into a single triage queue.

Field assignments

By crew, contractor, capacity, certification, geography, and zone availability.

Asset deployment

Equipment, trailers, vehicles tracked by location, condition, and availability — and what is packed inside them. Pallets in a trailer, tools in a sea container: the contents of any container or camp, by place rather than reconstructed item by item.

Site status

Live view of zones, sites, and crews — what is open, what is blocked, what is closed. Weather and geofence alerts by push, SMS, or email: who is inside a zone when the warning comes.

Contractor activity

External crews on the same platform — credentialing, scope, evidence, completion.

Photos and evidence

Every work order carries its evidence record. Geotagged, timestamped, retained.

Mobile reporting

Field crews report via MX+ — offline-capable, synced when the connection returns.

Dashboards & SITREPs

Live operational views. Daily SITREP packages generated and dispatched.

Executive reporting

Roll-ups by zone, work type, contractor, or funding stream — formatted for command.

Operational history

A complete record of who did what, where, when — preserved beyond the operation.

Auditability

Reimbursement-ready audit packages. Document, photo, geotag, and timestamp on every line.

Finance & projections

Cost lines generated automatically from operational activity. Projected to operation end.

§ 03 · Audit-ready by construction

The record exists because the work was done in MX — not generated afterwards.

Every cost line ties back to a work order. Every work order carries its photos, geotag, narrative, and crew. Every crew action is recorded with its permissions and timestamps. Reimbursement packages assemble from this — they do not have to be reconstructed from spreadsheets and email threads after the fact.

The same holds at the end. Demobilisation is loads, hauliers and bills of lading — each load assigned to a haulier, tracked from pickup to delivery, and reconciled into its purchase order at day end — so the movement out is as accounted for as the work that came before it.

Logistics & haulage in the platform →

§ 04 · Related solutions

Where else MX is configured.

Recovery rarely happens in isolation. These solution patterns commonly run alongside it.

Recovery operations