Preserve operational context from requirement to field record.

Two products with clear responsibilities

Tropos Operations™ owns the commercial and accountable operational record: who requested the work, what service is required, whether the information is ready for review, which risks and controls apply, and who has authority to release or accept the work.

Tropos Field™ is the execution surface for the pilot or field team. It is designed to receive an authorised, versioned MissionPack, present the relevant site and safety context, capture observations and evidence, and return an attested record of what happened.

• Operations™: requirement and authority
• Field™: execution and capture
• One authoritative record
• No uncontrolled double entry

Operations™ begins with a governed requirement

The current Operations™ foundation supports client and contact lookup, orders and order lines, existing-site lookup, location requests, supporting evidence, documents and audit history. An order can progress through draft to READY_FOR_REVIEW with controlled numbering, service-date changes and cancellation records.

READY_FOR_REVIEW is not permission to fly. It records that the requirement is sufficiently prepared for accountable review. The current certified boundary does not yet create a Job or release work into planning.

• Client and site context
• Order and service records
• Location evidence
• Review and audit history

Readiness, RAMS and mission authority

The developing Operations™ journey is designed to connect the approved requirement with a Job, Mission Risk Assessment, RAMS, personnel and equipment readiness, operational constraints and an explicit release decision.

These records should remain versioned so the field team receives the exact authorised context rather than an informal collection of messages and attachments. RAMS and client-report integration are active development areas; the complete release-to-planning journey is not yet presented as certified or deployed.

• Mission Risk Assessment
• RAMS and controls
• Competence and equipment context
• Explicit release authority

A MissionPack carries context into the field

A MissionPack is the governed projection of an authorised mission for Field™. Its intended role is to bind the current site boundary, task, risk controls, documents, responsibilities and evidence requirements into one versioned package.

Receipt, version pinning and acknowledgement are important because field teams need to know whether they are working from the current authorised plan. The full Operations™-to-Field™ MissionPack handoff remains in development.

• Versioned mission context
• Site and boundary information
• Pinned controls and documents
• Receipt and acknowledgement

Field™ supports safe, evidence-led execution

Field™ is being developed around maps, live position and boundaries; dynamic risk and GO/NO-GO checks; personnel, equipment, vehicle, first-aid and welfare readiness; and structured capture of photographs, observations, samples and operator attestations.

Forestry is the active-first domain direction, including estate, site, compartment, plot, access, slope and terrain context. Agricultural field forms and spray execution records remain registered future capabilities rather than active production functionality.

• Maps and governed spatial context
• On-site readiness checks
• Observations and photographs
• Task completion and attestation

Evidence must return with integrity

The intended return path preserves what was observed, which task was completed, who attested it and which evidence belongs to the mission. That record can then support SilvaSense™ or AgriSense™ analysis, operational acceptance and a defensible client deliverable.

Binary evidence transfer, complete offline conflict handling, write-back, weak-device assurance and the authorised-mission-to-processing handoff remain incomplete. Tropos will not describe the full chain as operationally deployed until those controls are implemented and evidenced.

Human authority and current boundaries

Operations™ may organise readiness evidence and Field™ may present the current mission context, but neither AI nor workflow automation approves legal, safety, agronomic or operational decisions. An authorised person remains responsible for GO/NO-GO, mission release, treatment approval and acceptance.

Tropos does not claim autonomous flight approval, complete live weather, NOTAM, flight-restriction-zone or Ordnance Survey integration, unattended operations or general production deployment. Current work remains platform development with explicit certified, partial and future boundaries.

Supporting continuing operational compliance

Tropos Operations™ records Remote Pilot qualifications, competency and currency together with aircraft, equipment and maintenance information. It also preserves operational documents, readiness evidence, mission records and accountable approvals so the organisation can maintain and demonstrate the controls behind its operations.

Tropos Analytics holds a current PDRA01 Operational Authorisation. That authorisation is granted by the CAA, and legal responsibility remains with Tropos Analytics, its accountable personnel and each Remote Pilot. Operations™ supports the compliance process; it does not itself confer CAA approval.

• Pilot qualification and currency
• Aircraft and equipment records
• Maintenance and technical history
• Controlled operational evidence

For contractors and the organisations that commission them

A drone contractor can use Operations™ as the controlled home for clients, enquiries, quotations, personnel, aircraft, maintenance, risk evidence, missions and completed-work records. Field™ can stand alongside it—or be used for a defined field workflow—to give pilots and crews the current task context, boundaries, controls and evidence requirements at the point of work.

A client, principal contractor, land manager or infrastructure organisation can use Operations™ and Field™ to commission work across approved suppliers: issuing consistent, versioned task information and receiving structured photographs, observations, attestations and completion evidence from the field. This supports accountable oversight without taking operational judgement away from the contractor or Remote Pilot.

Both products can be adopted independently. Used together, Operations™ governs the requirement and authority while Field™ carries that context into execution and returns an attributable record of what happened. Each organisation and contractor retains its own legal, safety and operational responsibilities.

• Independent contractors and field teams
• Multi-crew operators
• Organisations commissioning field work
• Governed tasking and evidence return

Lone-worker and man-down support

Tropos Field™ includes man-down support for people working in remote or higher-risk environments. It can support the organisation's lone-worker arrangements by keeping the worker, task and location context connected to the agreed monitoring and escalation process.

Man-down support is one control within a wider safe system of work. It does not replace suitable communications, supervision, emergency planning, trained responders or direct contact with the emergency services, and it does not make an unsafe task safe.

• Lone-worker context
• Man-down support
• Defined escalation arrangements
• Linked field and mission record

From enquiry and quotation to invoice evidence

The wider Operations™ direction connects the commercial record with delivery: capturing an enquiry, applying controlled services and pricing, preparing a versioned quotation, and carrying an accepted scope into the governed order and operational workflow. Changes, approvals and the basis of the price should remain visible rather than being lost across separate documents and messages.

After authorised work is completed and accepted, the same evidence chain can support invoice preparation and reconciliation. Integration with external accounting packages is intended to exchange approved customer, quotation and invoice information without making Tropos a replacement accounting ledger. Connector coverage and automated exchange remain development capabilities and will be described by supported package as each integration is implemented and verified.

• Controlled services and pricing
• Versioned quotations and acceptance
• Invoice preparation from accepted work
• External accounting-package integration