Professional pilots use checklists two fundamentally different ways, and knowing which to use when is the difference between a checklist that makes you safer and one that just keeps your head down at the wrong moment. Read-do means reading each item off the card and performing it one at a time — the right method when workload is low or the procedure is unfamiliar. Flow-then-verify means configuring the aircraft from a memorized sweep of the cockpit, then picking up the card to confirm nothing was missed — the right method when the airplane is moving or the phase is busy. Airlines and the military settled this question decades ago. General aviation training, for the most part, never got the memo.
Most student pilots are handed a checklist on day one, but almost no one is taught how to use one. Here’s the difference between reading a checklist and flying with one.
The Read-Do Method: One Item at a Time
Read-do is exactly what it sounds like. You read an item off the card, you do it, and you move to the next line. Read “Fuel selector — BOTH,” reach down, confirm, next item.
This is how nearly every student pilot is taught to use a checklist, and for good reason: in your first hours, you don’t know the airplane. Read-do is methodical, complete, and hard to get wrong. It’s the right tool when the procedure is unfamiliar, when the configuration is complex, or when the consequences of a missed item are severe and immediate — which is why even airline crews use read-do for abnormal and emergency procedures, after any memory items are complete.
The problem is what happens when read-do becomes the only method a pilot knows. A read-do checklist demands eyes and attention. Run one during taxi and you’re heads-down in a moving aircraft. Run one on downwind and you’re reading a card while the pattern fills up around you. So pilots start skipping it — not because they’re careless, but because the method they were taught doesn’t fit the phase of flight. The checklist becomes something you use when it’s convenient, which is precisely backwards.
The Flow-Then-Verify Method: Pattern First, Paper Second
A flow is a memorized sweep of the cockpit that follows a logical physical path — left to right across the panel, top to bottom down the pedestal, or whatever pattern fits your aircraft. You configure the airplane from the flow, by feel and habit, with your eyes available for taxiing, traffic, and the runway environment.
Then — and this is the part that makes it a checklist method rather than just memory — you pick up the card and verify. Each item gets a glance and a confirmation: already done, already done, already done. The checklist stops being a to-do list and becomes what it was always meant to be: a backstop that catches the one item your flow missed.
This is how airline crews run normal operations, and it’s why a two-pilot crew can configure a jet for approach in busy airspace without anyone reading a novel at 250 knots. The flow does the work; the checklist checks the work.
Familiar GA mnemonics are really just pocket-sized flows. GUMPS — gas, undercarriage, mixture, prop, seatbelts — is a flow for the pre-landing phase. CIGAR before takeoff is the same idea. If you’ve ever run GUMPS on final, you’ve already flown a flow. The step most pilots skip is the verify: backing up the mnemonic with the printed card once the workload allows.
Which Method, When
The practical rule is simple: read-do when workload is low or the procedure is unfamiliar; flow-then-verify when the airplane is moving or the phase is busy.
On the ground before engine start, read-do costs you nothing — take the time. Same for the runup, where you’re parked and the whole point is deliberate verification. But for taxi, before-takeoff cleanup, climb, descent, and pre-landing, a flow keeps your eyes where they belong, with the card confirming afterward that the flow was complete.
Emergencies deserve their own line: memory items first, from memory, immediately — then the printed checklist to verify and continue. An engine failure at 500 feet is not the moment to start reading. It is, however, exactly the moment where a verified flow you’ve practiced fifty times pays for itself.
What Examiners Actually Want to See
Applicants sometimes assume the examiner wants to see the checklist physically in hand at all times, read line by line. That’s not what the Airman Certification Standards ask for. The ACS requires appropriate checklist use — and examiners routinely note that a pilot who configures by flow and then verifies with the card is demonstrating better airmanship than one who taxis heads-down or, worse, recites a checklist from memory while pretending to read it.
A useful way to think about it: the examiner isn’t testing whether you can read. They’re testing whether you have a system — one that guarantees completeness without stealing your attention from flying the airplane. Flow-then-verify, done visibly and consistently, is that system.
Learning Your Flows
Flows are learned on the ground, not in the air at $180 an hour. Three things make them stick:
Build the flow from your aircraft’s checklist, in physical order. Take the before-landing items and re-sequence them as a sweep across your actual panel. The motion should feel geographic — your hand travels a path, and the path is the procedure.
Chair fly it. Sit with a cockpit poster or photo, run the flow with your hands, then verify against the card. Ten minutes a day for a week beats an hour once.
Say it out loud. Verbal callouts (“gear down, three green”) turn a private habit into a verifiable one — and they’re exactly what your examiner wants to hear.
Your CFI should be part of this. If your instructor has only ever shown you read-do, ask them to teach you flows for the busy phases — any experienced instructor will know them, and the conversation itself signals the kind of judgment that checkrides reward. If you’re still looking for an instructor who teaches this way, that’s exactly the kind of thing worth asking about in an intro flight.
Why the Card Itself Matters
One quiet advantage of the flow-then-verify method: it changes what you need from the physical checklist. A verify-card gets glanced at, not studied — so layout, grouping, and phase-of-flight organization matter more than exhaustive detail.
This is where purpose-built checklists earn their keep over the photocopied POH pages floating around many rental fleets. CheckMate Aviation — the laminated checklist maker that’s been a GA fixture for over 30 years and covers more than 350 aircraft models — redesigned its current CheckMate+ line specifically around this idea, arranging items to follow the logical flow of tasks in each phase of flight rather than the POH’s legal-document ordering.
The company’s newer Pro line takes it a step further for flight schools and clubs, customizing cards to a specific fleet with tail numbers and local procedures — which is exactly what a verify-card should be: an exact mirror of the airplane you’re actually flying, readable in a two-second glance.
Whatever card you fly with, the principle is the same: the checklist is the backstop, the flow is the skill, and the pilot who has both stops choosing between safety and looking outside.
Frequently Asked Questions
What’s the difference between a flow and a checklist? A flow is a memorized sequence of actions following a physical path through the cockpit; a checklist is the printed reference that verifies the flow was completed. They work together: the flow configures the airplane, the checklist confirms it.
Is it okay to do a checklist from memory on a checkride? Memory items for emergencies, yes — that’s what they’re for. For normal procedures, examiners want to see the printed checklist used to verify, even if you configured the aircraft by flow first. Reciting a normal checklist purely from memory is a common checkride mistake.
What does GUMPS stand for? Gas (fuel selector on the proper tank/both), Undercarriage (gear down), Mixture (set for landing), Prop (set for go-around), Seatbelts/Switches. It’s a pre-landing flow — back it up with your printed checklist when workload allows.
Should student pilots learn flows, or is that only for advanced pilots? Students should learn flows for the busy phases — taxi, before takeoff, and pre-landing — as soon as they’re comfortable with the aircraft, typically within the first 10–15 hours. Read-do remains the right method for pre-start and runup at every experience level.
Do airline pilots use read-do or flow-then-verify? Both, deliberately: flow-then-verify for normal operations, read-do for abnormal and emergency procedures after memory items are complete. That split — matched to workload — is the model GA pilots should copy.
Sources:
One thought on “Flows vs. Do-Lists: How to Actually Use a Checklist”