The job Forms tab

Open a job and select Forms. Every document that job needs is here, in one rail, with a live figure for how much of it is filled in. If you only learn one screen in echoMike, learn this one — the readiness checks that gate a flight read their evidence straight out of it.

The Documents rail

The left-hand rail is labelled Documents and holds three groups.

Ops pack is the flight paperwork, in the order you work through it:

• Pre-Flight Survey — nine sections and two checklists, expanded as rows under the document.
• On-Site Planning — a package with six rows: Survey, the four on-site checklists (Initial on-site checklist, Pre-flight checklist, Take-off checklist, Landing checklist) and Pre-Flight Briefing.
• Post-Flight / Debrief — three rows: Post-flight checklist, Emergencies checklist and Debrief.

RAMS lists each risk assessment and method statement by its own name, with its status beside it. When the job has none, the group holds a single RAMS workspace entry; once one exists, that entry becomes New RAMS.

Safety works the same way for occurrences: Occurrence / Airprox until you file one, then Occurrence report 1, Occurrence report 2 and so on, with New occurrence report at the bottom.

Expanding a document is not the same as opening it. You can scan On-Site Planning’s checklists for a gap without leaving the Pre-Flight Survey you are typing into.

Screenshot pending

Job Forms tab: Documents rail showing groups Ops pack / RAMS / Safety, progress figures, review indicators and the Incomplete toggle. Needs a part-filled Pre-Flight Survey and at least one RAMS.

Two measures of done, kept apart

Every section carries two independent figures, and echoMike never merges them.

Filled is derived. It counts the fields with content and the checklist items ticked, so it cannot be faked — a section reading 4/11 has seven blanks in it right now. A section that defines nothing to fill in reads Nothing to fill in.

Signed off is a human assertion. Press Sign off in a section header and it becomes Signed off with a tick. That is you saying “I have looked at this and it is right”, which is a different claim from “the boxes have text in them”.

Keeping both is what makes a genuinely blank field workable. A section with fields that are legitimately not applicable can still be signed off, and the rail shows both facts rather than forcing one of them to lie.

The band above the editor rolls the whole job up into four tiles: Filled, Sections With Blanks, Signed Off, and either Awaiting Review or Changes Requested. A Pilot Currency readout sits alongside them, reading Clear or, for example, 2 below.

Finding the outstanding work

Press Incomplete at the top of the rail — its tooltip reads Show only sections with blanks. Everything already filled in disappears and what is left is the work. A document with nothing outstanding shows Nothing outstanding here.

Documents disabled by the operating authorisation

On-Site Planning and Post-Flight / Debrief exist only under PDRA01. Change the job’s operating authorisation to Open category or UK SORA / legacy OSC OA and those two documents stay in the rail, greyed, with a reason: Not required under OPEN. The reason always names the job’s own authorisation in capitals, so a legacy PDRA02 job reads Not required under PDRA02.

They are disabled rather than removed on purpose. A row that vanishes mid-interaction takes your place in the tree with it.

The Pre-Flight Survey and occurrence reports are never disabled — they apply to every authorisation.

Sending a document for review

A review bar sits above each document showing its title, its review status and its content revision as Rev 3. Select Send for review, pick a reviewer, and confirm — the dialog notes that The reviewer receives an immutable snapshot of the current document. Who appears in the list is set by your organisation’s review policy and permissions.

While a review is open the button reads Awaiting review. If the reviewer sends it back, a Reviewer changes required block appears under the bar with their note in it.

The rail mirrors this: each document carries a review indicator reading, for example, Review approved · Sam Okafor · Rev 3. On-Site Planning is reviewed as two documents — the package and the briefing — so its indicator aggregates them into 1/2 reviews approved, and worst case wins.

What the readiness checks read

Filling these in is not paperwork for its own sake. The flight clearance readiness checks read the same records.

Document	Group	Readiness check it feeds
Pre-Flight Survey	Ops pack	PDRA01_PREFLIGHT_COMPLETE, PDRA01_SITE_CONDITIONS_CURRENT
On-Site Planning — Survey	Ops pack	PDRA01_SURVEY_COMPLETE
On-Site Planning — Pre-Flight Briefing	Ops pack	PDRA01_BRIEFING_COMPLETE
A RAMS, once issued	RAMS	PDRA01_RAMS_ISSUED
Post-Flight / Debrief	Ops pack	None — it is the record after the flight
Occurrence / Airprox	Safety	None

Two of these are worth reading carefully. A RAMS satisfies its check only once a revision has been Issued, which happens when a reviewer approves it — see Create and issue a job RAMS. And PDRA01_SITE_CONDITIONS_CURRENT is satisfied by the geo snapshot on the Pre-Flight Survey, not by anything you type, so it goes stale on a clock — Complete the Pre-Flight Survey covers refreshing it.

Where clearance appears

Clearance is not recorded in Forms. The job header carries a Flight release readout, and the readiness strip beside it is headed Flight clearance with a Record clearance button. Once a clearance exists the button reads Renew clearance.

Screenshot pending

Job header showing the Flight release readout cell in the readout band and the Flight clearance strip with its Record clearance button and readiness summary. Needs a job with at least one blocking check.