SORA is being industrialised. Good — now the other half matters more.

Dronedesk has launched what it calls the first fully automated SORA implementation: population-density analysis, ground and air risk classes, and a live SAIL rating computed inside the flight-planning workflow — supporting both UK SORA and the JARUS SORA 2.5 methodology. Work that used to take hours of specialist GIS analysis now happens in seconds as you adjust the flight geometry.

This is genuinely good news, and worth saying so plainly. Dronedesk's founder calls SORA “the single biggest hurdle standing between operators and BVLOS approvals”, and he's right — the risk assessment has been the expensive, specialist-bound front door of every application. Automating it is exactly what this industry's compliance stack needs, and it fits a pattern we've written about before: DJI now signs declarations for aircraft design, and tooling now industrialises the application itself. Approvals are getting cheaper and faster from both ends.

Which makes the other half the differentiator

A SORA submission is a promise: this is how we will operate. Everything after approval is the proof — was the aircraft actually maintained to its programme, was the airspace actually checked flight by flight, did the dock actually behave, and can you show all of it years later? No document generator can produce that half, because it isn't a document — it's a continuously accumulating record of what your operation actually did. That's the half Dock Pulse exists for: condition monitoring, auditable maintenance and battery records, airspace checks logged as they happen, and a one-click evidence pack when the question comes.

The operators who'll move fastest in the next two years will run both: an industrialised front door, and evidence that accumulates itself behind it. The application gets you flying. The record keeps you flying.