Checklists

Checklists are your organization's own cards: a pre-flight, a post-flight, a battery-handling list, whatever your crews sign off. They live in the Checklists tab of the Pilot Logbook at https://rotorlab.app/logbook. A template is the card itself, a named, ordered list of steps. A run is one completed pass over a card, optionally filed against a flight.

The design decision that matters: a filed run stores the items as they read at the time of completion, not a pointer to the current template. A checklist is evidence. If the pre-flight card is revised next year, last year's completed run keeps saying what was actually checked, or it is worth nothing in an audit.

Templates: your organization's cards#

A new organization is seeded with two cards the first time the page loads: Standard pre-flight (eight items covering airframe, propellers, battery, links, GPS, firmware, weather and airspace, crew) and Standard post-flight (six items covering power-down, damage inspection, heat checks, battery readings, log filing, and remarks). Both are editable and deletable like anything you write yourself.

Only organization managers see the New checklist button; everyone completes the cards, managers write them. An organization can hold up to 100 templates, each with up to 200 steps.

The template editor takes:

• Name, up to 120 characters.
• When it is used, the card's kind: Before the flight (preflight), After the flight (postflight), Maintenance, After an incident, or Other.
• In use: whether the card is offered to pilots. A card switched off keeps its filed runs but stops appearing as something to complete.
• The steps themselves, one row each. Drag the handle to reorder, press Enter in a step to add the next one, or use Paste a list to import one step per line from an existing document.

For a new card, Start from offers the two standard cards, a Blank card, or Copy one of ours to duplicate an existing template.

Editing a card changes it from here on; runs already completed keep the wording they were signed off against. Deleting a template also keeps its filed runs, because they are the record and it was only the form.

Completing a card#

Press Complete on any active card. Each step gets a three-way answer: pass, fail, or not checked. Pass is preselected; anything you leave alone is recorded as not checked rather than dropped, so a run always accounts for every item on the card.

Below the items you can attach the run Against flight (pick from your recent flights, or leave it unattached) and add Notes. File this checklist saves the run.

A run is marked complete only when every item was answered either way. A card with an unanswered item is a card that was not finished, and the record says so.

Filed checklists#

The Filed checklists table lists completed runs newest first: when it was completed, which card, what it was filed against, and the pass, fail, and unchecked counts, plus the source (manual for runs filed in the app, gc for runs sent by a ground station). Open any run to see every item as worded at the time of sign-off, with a check, cross, or dash per item and any per-item notes. An item answered against an older version of the card is kept and labeled "Not on the current version of this card."

In the Flights tab, a flight with a filed checklist shows a checklist pill in its row: the pill reads "checklist", "checklist part-done" if a run was incomplete, or the failure count in red if anything failed. That is the thing you actually want to see next to a flight on an audit.

Managers can delete a filed run; the confirmation warns that the record of what was checked goes with it.

Related#

• Pilot Logbook
• Ops Manual
• Maintenance
• RotorLab GC