How echoMike fits together

echoMike runs UK drone survey operations end to end: who you are flying for, where you are flying, who is cleared to fly it, and what evidence you keep afterwards. Almost everything you do sits somewhere in one chain of objects. Learn the chain and the rest of the app stops being a menu.

The chain

Organisation → project → flight area → job → Forms → flight clearance → records.

Your organisation is the top of everything. It owns your people, your fleet, your certificates, your templates and your settings, and nothing crosses between organisations. You belong to exactly one at a time — there is no organisation switcher in the app.

A client is the company you are working for. Clients live at /clients and get attached to projects.

A project is a delivery record: one site, one commission, one body of work that may run for months. Open one at /projects and it has six tabs — Overview, Spatial, Equipment, RAMS, Files and Billing. Files needs the View files permission; Billing needs Manage finance.

Flight areas and jobs

A flight area is the polygon you are permitted to operate in, plus its take-off and landing (TOAL) zones and its operational parameters. Flight areas are project-owned: you draw one once on the project’s Spatial tab, and every job on that project can borrow it. A job can also create its own.

A job is a single piece of scheduled field work — a visit, a day, a mobilisation. Jobs are where the crew, the aircraft, the date and the paperwork all meet. Every job carries a state: New, In progress, On hold, Completed or Cancelled. Its tabs are Overview, Spatial, Weather, Forms, Equipment, Logs and Billing.

Paperwork and the gate

The Forms tab on a job holds the operational documents: Pre-Flight Survey, RAMS, On-Site Planning, Pre-Flight Briefing, Debrief and, if something goes wrong, an Occurrence / Airprox report.

Those feed readiness — the set of automated checks behind every job. Each check comes back as Blocker, Confirm to proceed, Advisory or Met. When you are satisfied, you open Record flight clearance on the job and the decision is written down with your name on it.

What is kept

Flights land in the Logbooks (/flight-logbook for pilots, /technical-logbook for airframes and batteries). The job header’s Ops Pack button exports the whole job as a document bundle, and /organization/reports builds the CAA audit pack.

Ready to build the chain for real? Start with Set up your first workspace.