Docs

Search documentation

Find a page in the Runway documentation.

Log inApply for beta

The weekly flight

Running a flight

Boarding, the gate timers, moving the crew through the agenda together, and ending the meeting.

A flight is one run of the weekly meeting. One person starts it, the crew joins it, and everyone moves through the gates together while the app keeps time. Nothing about it is a separate mode: the same pages you edit on a Tuesday are the pages the meeting runs on.

Starting a flight#

  1. Press Takeoff

    The Takeoff button is in the app header, on every page. Keyboard: press t from anywhere outside a text field.

  2. Choose the crew

    If you belong to more than one crew, pick the one that is meeting. The flight takes that crew's agenda, that crew's scorecard and that crew's issues list.

  3. Check the agenda

    Runway shows the gates you are about to fly and the minutes each one has. Reorder or retime them here if this week is unusual, or leave it alone. See The agenda to change the default.

  4. Begin Boarding

    The flight opens and the clock starts. Everyone else on the crew now sees it and can join.

Joining a flight in progress#

Anyone on the crew who opens Runway while a flight is running sees Board Flight and lands on whichever gate the meeting is on. Latecomers do not have to be caught up by hand.

The header shows who is currently on board. If you leave, either deliberately with Leave Flight or by closing the tab, the meeting carries on without you and Rejoin Flight brings you back to where it has got to.

Moving through the gates#

Whoever started the flight is running it, and moving them to the next gate moves the whole crew. Everyone else can still navigate freely: if you want to look ahead at the issues list while the scorecard is being read, you can, and the app puts you back with the crew when you are done.

The clock#

Each gate carries the time it is allotted, and the timer counts the time actually spent there. Jumping back to the scorecard and on again does not reset it: a gate accumulates across every visit, so the total that lands in Flight Logs is the honest one.

Shortcuts#

KeyDoes
tTakeoff, or board the flight already running
[Previous gate (during a flight)
]Next gate (during a flight)
eEnd the flight (from the flight panel)
Cmd / Ctrl + KSearch and jump anywhere

Working the boards together#

Editing during a flight is live. Two people typing into the same rock notes or the same issue description see each other's changes as they happen, with a marker showing who is in the field. There is no save button and no last-writer-wins surprise at the end of the meeting.

  • Tick a to-do and it is done for everyone, immediately.
  • Add an issue mid-discussion and it is on the list for the crew to see before you finish the sentence.
  • An off-track rock can be turned straight into an issue, rather than noted down and retyped later.

Ending the flight#

The last gate is Baggage Claim: recap what was decided, confirm the new to-dos, and score the meeting. Then end the flight.

What gets written down when a flight ends:

Duration
Total meeting length, and the time spent at each individual gate.
The boards
The state of the scorecard, rocks, to-dos, issues and headlines as they stood at landing.
Notes
Anything the crew typed into a gate during the meeting.
The score
Each person's one to ten rating and their comments, and the crew average.

All of it lands in Flight Logs, where any crew member can read it back.

EOS®, Entrepreneurial Operating System®, Level 10 Meeting®, L10™, IDS®, V/TO®, The Accountability Chart®, Traction® and EOS Implementer® are trademarks of EOS Worldwide, LLC. Runway is EOS Compatible™. Runway is not owned by, created by, or endorsed by EOS Worldwide, LLC.

Need a certified guide for your business? Find an EOS Implementer® in EOS Worldwide's directory. Thinking of coaching full time? Become an EOS Implementer® with EOS Worldwide.