Emergency Scanning Is Not Processing

Emergency scanning is a quick check for imminent trouble, not a substitute for processing an in-basket. The rule preserves the difference between looking for a particular urgent signal and systematically deciding what every incoming item is, what action it requires, and where it should go.

Purpose and Limits

An emergency scan can be appropriate when time is short and a specific risk must be checked. The example is returning from an off-site meeting with a long conference call due to begin in fifteen minutes: a brief look can establish whether a serious problem is developing or whether a client has approved a major proposal. Such a scan answers an immediate question; it does not settle the status of the whole in-basket.

The distinction is especially important in knowledge work, where projects may have no clear edges, information is abundant, and communication crosses organizational divisions. A quick search for urgent messages may help with a near-term contingency, but it cannot by itself manage the many incoming requests and agreements that must be tracked. The broader system has to accommodate both high-level priorities and small open details, rather than mistaking momentary visibility for completed handling.

Processing Requires an Order

During actual processing, items should be handled one at a time, starting at one end of the in-basket and continuing through it in order. Processing does not mean spending time completing every item; it means identifying what an item is, deciding what action is required, and dispatching it accordingly. That distinction allows a person to move quickly without leaving the contents undecided.

The temptation to choose only the most urgent, enjoyable, or interesting material undermines this method. Once processing follows preference rather than an orderly pass, less attractive items remain untouched. The in-basket then stops functioning as a reliable funnel: unresolved material accumulates on the desk and across the office, and the apparent search for urgency helps perpetuate the backlog it was meant to control.

Backlogs and Sequence

The rule does not require one universal direction for processing. In theory, the first item received could be handled first; in practice, either end can work if the person proceeds all the way through within a reasonable period. The crucial point is completion of the pass, not the abstract superiority of first-in, first-out or last-in, first-out.

A large backlog of email can make last-in-first-out more efficient because later messages may sit on top of accumulated discussion threads. Even there, the sequence is a practical choice within deliberate processing, not permission to scan selectively. The in-basket is a processing station rather than a storage bin: emergency scanning may briefly inspect it, but only systematic decisions clear it.

Reliability Beyond the Individual

The same distinction has consequences for shared work. Requests and relevant information may arrive through voicemail, email, conversation, or written notes; for others to rely on a communication, it must enter the recipient’s system, be processed and organized, and become available for review as a possible action. If someone manages only one medium, colleagues are forced to restrict themselves to that channel, and communication gaps can weaken the whole arrangement.

An organization cannot dictate each person’s private method, but it can hold people accountable for tracking what comes to them and for outcomes. When people collect commitments reliably, they can renegotiate what they will not do; without a record, they may forget the very agreements that need renegotiation. Emergency scanning addresses what might need attention immediately. Processing and reliable collection make it possible to know what remains, act on it, and coordinate with others without depending on constant supervision.