Skip to content

Mitigation and drying

Draft · new in v3

Mitigation is often the first contractor activity on a claim and the one with the richest field data: moisture readings, equipment placed, hours run, rooms affected and decisions about what to dry versus remove. TRP records it as structured, evidence-linked events so it can be reviewed, reconciled with the estimate and reused in later decisions.

A MitigationEvent records one observed unit of mitigation work.

Minimum data:

  • job_id, claim_id, event_time, reported_by
  • activity: inspection, water_extraction, equipment_placement, equipment_removal, moisture_reading, cleaning, antimicrobial_application, containment, demolition_for_drying, other
  • area: structure, level, room, and an optional free-text description
  • loss_context: peril and, where relevant, water category and class. Vocabulary is source-defined; record the classification system used
  • equipment: type, count, identifier, placement and running hours where applicable
  • readings: material, measurement method, value, unit and reference or dry standard
  • evidence_ids, verification_status

A reading is an observation. “Dry” or “drying goal met” is a judgment tied to a stated standard and a person. Record both, and record who made the judgment.

Flag these for review:

  • equipment billed for days with no placement or reading evidence;
  • rooms with estimate lines for drying but no moisture readings;
  • demolition for drying with no corresponding waste event;
  • readings above the stated dry standard at closeout.

Equipment running hours and metered or modeled energy feed an EnergyEvent. Declare whether energy is measured or estimated, and avoid counting the same electricity in both a utility record and an equipment record.