What does it mean that pre-flight checks?

Reviewing key conditions before starting a task catches errors before they propagate.

Example: You are about to send a major client proposal. You have proofread the document, but you have not verified that the pricing matches the latest rate sheet, that the client's company name is spelled correctly in every instance, that the scope section reflects the changes discussed in last Thursday's call, or that the attachment is the final version rather than the draft with tracked changes. You hit send. The client notices the wrong pricing within five minutes. A pre-flight check — a deliberate, structured review of key conditions before execution — would have caught every one of these errors. Not because you are careless, but because the human brain under time pressure defaults to confirming what it expects to see rather than verifying what is actually there. The check externalizes verification so your assumptions cannot hide.

Try this: Identify one recurring task you perform at least weekly — sending a report, publishing content, deploying code, running a meeting, submitting an invoice. Write a pre-flight checklist of 5-7 conditions that must be true before you execute. These are not steps in the task itself; they are conditions you verify before beginning. For example, before sending a weekly report: (1) data source updated within 24 hours, (2) all charts reflect current period, (3) summary matches the data, (4) recipient list is correct, (5) subject line includes the correct date. Run this checklist before your next execution of the task. Time the checklist — it should take under two minutes. Note what, if anything, the checklist caught that you would have missed.