Flightplan

Running

The checklist summary

.md

When a checklist finishes, its page becomes a read-only record of what happened. Open any completed checklist from the Checklists list to see it.

Nothing here can be edited. That is the point — it is the account of one checklist, and it stays as it was.

What it shows

The checklist name, a Complete badge, which workflow and version it ran, who started it and when, and how long it took start to finish. If any tasks were skipped, the count is here too.

Assignment overrides

Tasks closed by someone they were not assigned to:

QA sign-off was assigned to any Admin — completed anyway by Sam Ortiz

Not flagged as a problem — just on the record, so it can be looked at if anyone wants to.

Tasks

Every task, in order: its title and key, its final status, who closed it and when. Tasks closed by a connected system show that system's name rather than a person's.

Files

Everything uploaded to a file field anywhere in the checklist, in one list. If nothing asked for a file, the section says so.

Activity

Everything that happened to this checklist, oldest first: when it was generated, each task as it closed and who closed it, and the moment the checklist finished.

Dana Reyes completed "Count the till" Aug 25, 2026 - 2:18 AM CDT

The sections above say what the checklist ended up saying. This one says how it got there — the order things closed in, and how far apart. Checklists that ran before activity was kept say so rather than showing an empty list.

What it is for

Three things, mostly:

  • Handover. Somebody who was not there can read what happened without asking.
  • Evidence. Who signed off, when, in what order, and what they attached, all kept together.
  • Improving the process. Read a few summaries of the same workflow and it gets obvious which tasks take the longest and which ones keep getting skipped.

Next