Cal Newport: 'Protect This Time Like a Doctor's Appointment'

Cal Newport is a computer science professor at Georgetown and the author of Deep Work (2016), A World Without Email (2021), and Slow Productivity (2024). His thesis across all three books is consistent: knowledge workers cannot do their best thinking in a continuously-interrupted environment, and the calendar is the primary battleground.

Newport has written more clearly than anyone else about the mechanics of defending blocks of time. The framework translates almost directly to lunch protection.

The Quote

From his own blog at calnewport.com, December 7, 2016, describing his "deep scheduling" practice:

"Once on the calendar, I protect this time like I would a doctor's appointment or important meeting. If you try to schedule something during a deep work block I'll insist I'm not available."

He explains the mechanic:

"I now schedule my deep work on my calendar four weeks in advance. That is, at any given point, I should have deep work scheduled for roughly the next month… This four week lead time is sufficiently long that when someone requests a chunk of my time and attention for a given week, I've almost certainly already reserved my deep work blocks for that period."

The mechanism is forward-loading. Newport claims the slots before anyone else can.

What "Deep Scheduling" Does

The Newport framework has four moving parts.

1. Block in advance

Schedule deep work blocks for the next four weeks. The blocks exist on your calendar before requests for your time arrive. By the time a colleague asks for a Wednesday afternoon slot, the slot is already taken.

This is the inverse of how most knowledge workers operate. Most people leave their calendars open by default and react to incoming requests. Newport leaves his calendar booked by default and reacts to requests by offering whatever survives.

2. Defend like a real appointment

The framing matters: a "deep work block" is treated as equivalent to a doctor's appointment. Newport explicitly says he "insists" on not being available during the block. The metaphor is intentional: a doctor's appointment is not negotiable; a "focus time" block has historically been treated as soft.

The lift in framing is most of the work. The block does not change. The seriousness with which you defend it does.

3. Triage incoming asks

When a request lands during a blocked period, Newport's options ladder is:

1. Decline the opportunity.
2. Delay the opportunity.
3. Allow it to encroach on the block.
4. Move the deep work to equally productive time.

His rule of thumb is to do 2 first, 4 second, 1 third, and avoid 3 if at all possible. The reason 3 is the worst option: it teaches both you and the requester that the block is negotiable, which compounds over future requests.

4. Don't optimize before establishing the habit

Newport explicitly warns against starting too aggressively. Begin with one 90-minute block per day. Get good at defending it. Then add. The discipline is more important than the schedule density.

The "Deep Break" Companion Concept

In a related calnewport.com post from September 14, 2016, Newport addresses the rest periods that punctuate deep work blocks:

"Anyone who regularly succeeds in long deep work sessions is almost certainly someone skilled at deploying deep breaks to keep the session going without burning out or losing focus."

His criteria for what counts as a "deep break":

• Should not redirect attention to a target that generates ongoing obligation (email, social media).
• Should not redirect to a "distraction ritual" (the chain of websites you check when bored).
• Should not redirect to a related-but-different professional task.
• Should not redirect to something complicated or stressful.
• Should not usually last more than 10–15 minutes, with exceptions for meals.

The exception for meals is the key. Newport's framework already has lunch built in as a permitted longer break. It is structurally part of the deep work day, not an optional extra.

How This Applies to Lunch Specifically

Newport's framework was written for focus time, not lunch. But the four parts translate cleanly.

Block lunch in advance

If your lunch is not on the calendar, it is not protected. Block 11:45 AM to 1:15 PM as a recurring event going forward — at least four weeks out.

Defend like a real appointment

A "Lunch" block is overridden 38% of the time within four weeks (per our internal research). A block titled like a business meeting is overridden 8% of the time. The same time, different label, dramatically different protection rate.

Newport's mental model — "this is a doctor's appointment" — is the right defense. The label-as-business-meeting is the camouflage that lets the mental model survive contact with your colleagues.

Triage with Newport's ladder

When something lands on your lunch block, the same hierarchy applies. Decline. Delay. Move the lunch. Allow the encroachment as a last resort.

Don't try to defend perfectly at first

Newport's caveat about starting small applies here too. Begin with three lunch-protected days per week. Get good at defending them. Then expand to five.

The Newport Critique of "Focus Time" as a Label

Newport has been consistently skeptical of generic "focus time" labels for the same reason CovertLunch is skeptical of "lunch" labels. The label tells coworkers the block is a personal preference.

His preferred terminology in his own work: he calls it "deep work" but defends specific projects ("write Chapter 3," "review the paper draft," "respond to the editor letter"). The block is named for a concrete deliverable, not for the activity type. This makes the block feel like a commitment to a project rather than a commitment to a vague preference for uninterrupted time.

For lunch, the equivalent move is naming the block as a business meeting (Vendor Sync, Pipeline Review). The block is not lying about being lunch — it is being honest about being a commitment to defending the time. The implied subject is what changes, not the underlying reality.

Why CovertLunch Is Newport-Adjacent

The technical implementation in CovertLunch is consistent with Newport's framework in three ways:

1. Forward-loaded. The extension writes events into your lunch window automatically each morning, before incoming requests can land.
2. Labeled as commitments, not preferences. Realistic business-meeting titles, not "Lunch" or "Focus Time."
3. Daily variation. Newport's manually-curated deep-work blocks vary day-to-day in topic and duration. CovertLunch does the same automatically for the lunch window.

Newport himself would probably recommend the manual version of this if asked — the discipline of consciously scheduling each block is part of the practice in his books. The argument for automation is purely about reducing the per-week attention cost from ~10 minutes to zero. Both approaches work.

Try CovertLunch free for 7 days →

What Newport Does Not Address

Newport's framework was developed for individual contributors and academics — populations with more control over their calendars than most corporate employees. Two gaps worth naming.

The asymmetric power problem

Newport's "I'll insist I'm not available" works in a context where his counterparties accept that as a final answer. Inside a corporate hierarchy, "I'll insist" can be the wrong move if the requester is your skip-level manager.

The camouflage technique handles this: nobody asks if the block is real because the block looks like an existing commitment. The political ask never happens.

The Slack ping

Newport's framework predates the modern density of Slack DMs. A perfectly-defended calendar block can still be interrupted by a Slack ping at 12:15 PM. The companion practice is Slack DND during the same window — not a Newport invention, but a necessary 2026 addition.

Related Reading

• Newport's full Deep Work practice: calnewport.com (primary)
• Burned Out From Back-to-Back Meetings? Here's the Calendar Fix — Newport's framework + Microsoft EEG research
• How to Block Lunch on Google Calendar (And Why a Fake Meeting Works Better) — applied playbook
• Executive Calendar Management — Newport's framework for the C-suite context

Frequently Asked Questions

Is Cal Newport against meetings?

No. Newport is against unstructured, low-leverage meeting accretion. He is in favor of clear-purpose meetings with explicit deliverables. His critique is volume and quality, not the existence of meetings.

Did Newport coin the term "deep work"?

The phrase predates Newport in narrow technical contexts, but he popularized it as a productivity framework in his 2016 book.

How long should a deep work block be?

Newport's typical recommendation is 90 minutes to start, building toward longer blocks (2–4 hours) for advanced practitioners. The minimum unit that produces meaningful output is around 60 minutes.

Does Newport recommend automation for calendar blocking?

He has not written publicly about specific calendar-automation tools. His own practice is manual: scheduling deep work blocks four weeks in advance and reviewing them weekly. The principle would translate to any tool that holds the discipline.

What's the difference between "deep work" and "focus time"?

In Newport's vocabulary, "deep work" is the cognitively demanding work that requires uninterrupted attention. "Focus time" is the calendar block name where deep work happens. Most productivity apps use the two interchangeably; Newport distinguishes them.