Generate
The operator describes the drone, the area and the mission. Hespoire drafts the SORA and the operations manual from those structured inputs. Nobody starts from a blank page.
More on generateFrom a description of the job to an authority-ready file.
The operator describes the drone, the area and the mission. Hespoire produces the file, tests it against the rules and keeps it true afterwards.
- GenerateThe operator describes the drone, the area and the mission. Hespoire drafts the risk assessment and the operations manual from those structured inputs.
- CheckHespoire checks every claim and mitigation against the current EASA rules and flags gaps before the authority does.
- MaintainA new drone, a new location or a rule change updates only the sections it touches. The rest of the file stays as approved.
- ReuseApproved work carries forward. Your second authorisation builds on your first, so a new mission no longer means a new document cycle.
Follow one file through the platform.
Check
Every claim and mitigation is checked against the current EASA rules. A gap comes back as a specific question, long before an authority could raise it.
More on checkMaintain
A new drone, a new location or a rule change touches some sections and leaves others alone. Only the affected sections are updated.
More on maintainReuse
Approved work carries forward. The operator’s second authorisation takes a fraction of the first.
More on reuseAuthorisation file
Example operator · ILT · SORA 2.5
Example operator · ILT · SORA 2.5
Drafting1 gap open3 of 8 sections changedSecond file · 2 sections new
- 1Concept of operations
BVLOS dyke inspection, ZeelandAMC1 Art. 11 · Step 1✓ AMC1 Art. 11 · Step 1UnchangedReused - 2Intrinsic ground risk
3 m, 35 m/s · density < 500 · iGRC 5Step 2✓ Step 2Updated: new droneReused - 3Ground risk mitigations
M1(B) medium · M2 medium · final GRC 3Step 3Gap flaggedUpdated: new droneRevised: new area - 4Air risk
Below 150 m, uncontrolled, rural · ARC-bSteps 4–6✓ Steps 4–6UnchangedReused - 5SAIL
SAIL IIStep 7✓ Step 7UnchangedReused - 6Containment
Flight geography, contingency, bufferStep 8✓ Step 8Updated: new droneRevised: new area - 7Operational safety objectives
Evidence mapped per objectiveStep 9✓ Step 9UnchangedReused - 8Operations manual
Procedures, roles, emergency responseStep 10✓ Step 10UnchangedReused
Question for the operator
You claim M1(B) at medium robustness. How is access to the flight area restricted during the operation, and who enforces it?
Illustrative file with example values. Not a real application.
One rule check, one fix loop.
What we hold ourselves to.
People stay accountable
AI drafts. The operator reviews and signs. A safety case is a claim that a person stands behind, so nothing in Hespoire is designed to remove that person.
Traceable by design
A language model on its own is a poor safety tool, because it can sound right while being wrong. That is why our checks run against a rule model built and owned by a co-founder who works on the regulation, and each one links back to the rule it enforces.
Your file is yours
Operator data is commercially sensitive. It is used to serve that operator. We will set out exactly how customer data is handled in the customer agreement and data processing agreement before anyone uploads a file.