Skip to main content

MitigationPlan Object

Represents a comprehensive plan to mitigate identified risks.
id
number
required
Unique identifier for the mitigation plan
description
string
required
Overview of the mitigation strategy
responsible
string
required
Person responsible for overseeing the mitigation plan
start_date
Date
required
Date when the mitigation plan was initiated
measures
MitigationMeasure[]
required
Array of specific mitigation measures to be implemented
analysis
Analysis
required
Risk analysis associated with this plan

MitigationMeasure Object

Specific action or measure to reduce risk.
id
number
required
Unique identifier for the measure
description
string
required
Detailed description of the mitigation measure
implementation_supervisor
string
required
Supervisor overseeing implementation
implementation_responsible
string
required
Person directly responsible for implementing the measure
estimated_date
Date
required
Target date for completion
execution_date
Date | null
Actual completion date (null if not yet completed)
mitigation_plan_id
number
required
ID of the parent mitigation plan
follow_up_control
FollowUpControl[]
required
Follow-up activities and verification checks

FollowUpControl Object

Tracks verification and follow-up of implemented measures.
id
number
required
Unique identifier for the follow-up control
date
Date
required
Date of the follow-up activity
description
string
required
Description of the follow-up activity and findings
mitigation_measure_id
number
required
ID of the associated mitigation measure
image
string
Path to supporting image file
document
string
Path to supporting documentation

DangerIdentificationWithAll Object

Extended view including mitigation details.
id
number
required
Unique identifier
description
string
required
Description of the identified danger
measures
MitigationMeasure[]
required
All mitigation measures for this danger
analysis
Analysis
required
Risk analysis results

Example - MitigationPlan

{
  "id": 5,
  "description": "Enhanced runway inspection and FOD management program",
  "responsible": "Safety Manager - Juan Pérez",
  "start_date": "2026-03-15T00:00:00Z",
  "measures": [
    {
      "id": 1,
      "description": "Increase runway inspection frequency to every 2 hours during peak operations",
      "implementation_supervisor": "Operations Director - María González",
      "implementation_responsible": "Ground Operations Supervisor - Carlos Ruiz",
      "estimated_date": "2026-03-20T00:00:00Z",
      "execution_date": null,
      "mitigation_plan_id": 5,
      "follow_up_control": []
    },
    {
      "id": 2,
      "description": "Install additional FOD detection equipment at runway entry points",
      "implementation_supervisor": "Facilities Manager - Ana Rodríguez",
      "implementation_responsible": "Maintenance Lead - Roberto Díaz",
      "estimated_date": "2026-04-30T00:00:00Z",
      "execution_date": null,
      "mitigation_plan_id": 5,
      "follow_up_control": []
    }
  ],
  "analysis": {
    "id": 12,
    "probability": "OCCASIONAL",
    "severity": "HAZARDOUS",
    "result": "MEDIUM"
  }
}

Example - FollowUpControl

{
  "id": 1,
  "date": "2026-03-25T10:00:00Z",
  "description": "Verified implementation of enhanced inspection schedule. All shifts are conducting inspections every 2 hours. No FOD incidents reported since implementation.",
  "mitigation_measure_id": 1,
  "image": "/storage/follow-up/2026/03/inspection-log-001.jpg",
  "document": "/storage/follow-up/2026/03/inspection-report-001.pdf"
}

Build docs developers (and LLMs) love