Operations™ perspective · 20 August 2026

A flight log is not the whole operational story.

Accountable drone work begins before take-off and continues after the aircraft lands.

01

Compliance is demonstrated through connected records

Pilot currency, competence, aircraft status, maintenance history and operational documents all influence whether work is ready to proceed. Keeping each record in a separate folder or spreadsheet makes it harder to understand the complete position at the point of decision.

Tropos Operations™ is being developed to connect those records to the client requirement, site, mission and responsible people.

  • Pilot currency and competence
  • Aircraft and maintenance records
  • Current operational documents
  • Mission-specific authority

02

Software supports responsibility; it does not replace it

A system can make missing, expired or incompatible information visible and preserve who reviewed it. It cannot confer CAA approval, certify a flight as lawful or remove the responsibilities of the UAS operator and Remote Pilot.

The distinction matters: operational software should support the management and demonstration of compliance while keeping formal authority with the appropriate people and regulator.

  • Readiness visibility
  • Fail-closed controls
  • Named reviewer
  • Human go or no-go authority

03

Field™ evidence completes the record

The plan approved in the office is only part of the story. Conditions, observations, photographs, checks, tracks, samples, exceptions and attestations created on site need to return with their original mission context.

Tropos Field™ is the developing operational edge for that work, including offline-aware capture and lone-worker or man-down support directions. These safety-support features do not replace emergency planning, communications or supervision.

  • Versioned mission context
  • On-site checks
  • Attributable evidence
  • Exceptions and attestations

04

From enquiry to closure

Operational work also has a commercial lifecycle: enquiry, scope, quotation, pricing, order, delivery, acceptance and invoicing. Operations™ is intended to connect that business journey with the governed delivery record and, where appropriate, integrate with external accounting packages.

The aim is not simply administration. It is a defensible chain showing what was requested, what was authorised, what happened and what was accepted.

  • Quoting and pricing
  • Work orders
  • Acceptance and invoicing
  • Accounting integration direction

05

Useful alone, stronger when connected

Operations™ can support contractors or organisations managing contractors as a focused product. Field™ can provide structured evidence capture independently. Connected together—and with SilvaSense™, AgriSense™ or Intelligence™—they can preserve more context across the complete journey.

That is the platform advantage: synergy through governed links, without forcing every organisation to adopt every product.