What’s new

There is a bell at the foot of the sidebar. When a task becomes yours to do it is waiting there — named, with its checklist, linking straight to the task. Flightplan can also email you and send you a Slack direct message, so you find out with the app closed. One message per batch: six tasks at once is one email, not six.

Email is on. Slack is off until somebody turns it on, and your Slack account is matched to your Flightplan one by email address. Both channels have a switch on the new Settings page, and every email has an unsubscribe link at the foot. Tasks that are open to anyone tell nobody — they are on My work instead. See Notifications.

Schedules, rebuilt

New schedule is a page of its own now. Start from a preset — Every weekday, Nightly, Quarterly — or open the full builder for anything else. The cron box takes day names (MON-FRI), the last day of the month (L) and the third Saturday (6#3), and every cadence reads back as a sentence with the next four fire times beside it.

The One-off tab schedules a single run for a date and time, then closes itself. Start one now instead generates the checklists immediately and leaves no schedule behind. Every schedule you already have is unchanged. See Schedules.

Connections moved

Connections has left the sidebar for a card on Settings. Connecting and disconnecting is still limited to organization admins. See Connections.

Flightplan is open. Write down a process once, generate a checklist from it every time you run it, and keep the record of what happened.

This is the first entry in the changelog, and it stands in for everything built up to today. What follows is what the app does.

Write the process down once

A workflow is the process: the tasks it contains, the order they have to happen in, and who each one is for. You build it on a canvas, connect a task to the tasks it waits on, and publish it. A workflow is never worked directly — it is the thing you make copies of.

A task can be assigned to a person, to a group like Site leads or Night shift, or to anyone at all. A group is resolved when the task is worked, so adding somebody to the team is one edit rather than an edit to every workflow they touch.

A task can also ask for an answer while it is done — a reading, a photo, a box to tick. Pick from single-line text, rich text, number, checkbox, choice list and file upload. Mark one required and the task cannot close without it.

Read Building a workflow and Fields.

Run it as a checklist

Generating a checklist takes a snapshot of the workflow as it stands right then. Improve the workflow today and the checklist somebody started yesterday still shows yesterday's version.

Each task is blocked until the tasks before it close, then ready, then complete or skipped. Nobody has to hold the sequence in their head, and nobody can jump it by accident. A skip asks for a reason and keeps it.

My work is every open task that is yours across every checklist, and it is where most people spend the day. A bar at the top generates a new checklist without going anywhere else. A task the workflow left open to anyone tells you how long it has sat there, and Assign me makes it yours.

Read Running a checklist and My work.

Say what the form never asked

Every task takes comments — on the checklist page and in My work, on your tasks and everybody else's, blocked or complete or skipped. Fields collect the answers a process expects every time. A comment is for the once: the vendor who did not call back, the part that came in the wrong size, the reason a task sat for two days.

A comment changes nothing. Nothing unblocks, no automation fires. It goes on with your name and the time, and it stays.

Read Comments.

Keep the record

A finished checklist becomes a read-only account of itself: every task, its final status, who closed it and when, what they answered, and every file they attached. Tasks closed by somebody they were not assigned to are on the record as well — not flagged as a problem, just visible.

Times read on your own clock, with the zone named, wherever in the world you open them.

Read The checklist summary.

Have checklists start themselves

A schedule generates checklists on a cadence — daily, weekdays, weekly, monthly, quarterly, or a cron expression — so the first person in on Monday finds the work already waiting.

A schedule is its own thing rather than a setting on one workflow, because recurring work is usually several workflows at once. "Monday morning open" can be a walkaround, a till count and a safety check under one cadence. Each schedule reads its cadence in its own time zone, so 9:00 AM stays 9:00 AM in January and in July, and an overlap rule decides what happens when the last checklist is still open.

Read Schedules.

Connect it to the rest of your tools

Connect a Slack workspace and a task announces itself when it becomes ready — in the channel you pick or as a direct message, with a message you write and a link straight to the task.

A task can also belong to a machine. Mark it external and Flightplan sends a signed step.ready webhook to an endpoint you own when its prerequisites clear. The payload carries a callback token that closes that one task and nothing else, so a deploy, a backup or a test suite can close its own task and the checklist waits for it exactly the way it waits for a person.

Read Connections.

Ask Claude about your work

Add https://flightplan.run/mcp as a connector in Claude and it reads your workflows and checklists and acts on them. "What are my tasks?" is answered from your actual work. "Start the onboarding for Acme Corp" starts it. A procedure pasted out of a document comes back as a workflow, laid out and ready to look at. When a task collects information, Claude shows you the form in the conversation, and closing it there records the same completion the page would.

Ask for a write-up of a finished checklist and Flightplan hands over the whole record so Claude writes the document — a handover note, an incident report, a compliance record, whichever you say. You pick the workspace when you approve the connection, and grant reading only if you want answers without changes.

Works with anything that speaks the Model Context Protocol, not only Claude. Read Claude and other AI.

And the manual

Everything above is documented at flightplan.run/docs, in plain language and public, so you can send an article to somebody who does not have an account yet. Every page has Copy markdown at the top, for pasting into whatever coding agent you use.

The help center has a new last page: Talk to a human. When none of the articles answered the question, that page says what to send us and hands it to support@flightplan.run.

It has a form on it. Pick what the message is about, write a line and a paragraph, add your organization and the page you were on, and it composes the email and opens it in your own mail app — subject filled in, nothing sent until you send it. On a device with no mail app, Copy the message puts the same text on the clipboard for webmail.