How to Plan Deep Work Around Claude's 5-Hour Window

The Window Starts When You Do

Anthropic's help center describes the session limit simply: the period starts when you send your first message, and the limit resets in full five hours later. That has two consequences most people miss.

• A throwaway message starts the clock. A quick question at 8:00 means your window ends at 13:00, even if your deep work starts at 10:30. You get only two and a half hours of that window for the real task.
• Unused time does not carry over. If you stop at 11:00 with budget left, the window still ends at 13:00. The remaining allowance is not banked.

If you are on a verified Ultra account, there is no 5-hour limit, but the weekly limit still applies. Everyone else should treat the first message of the day as a scheduling decision.

Three Scheduling Patterns

The two-window day is tempting and often a mistake. Two full sessions a day, five days a week, is the pattern that most often runs into the weekly limit. Use it for crunch days, not as a default. See Claude weekly limits explained for how the two limits interact.

Batch the Expensive Work Early

Not every task costs the same. Large uploads, long-document analysis, web research, extended thinking, and Claude Code runs consume far more than editing or short questions. Put those at the start of the window, when you have the most room and the freshest thread.

1. Prepare before you send anything. Gather files, trim them to the relevant pages, and write your first prompt outside Claude. Preparation does not start the clock.
2. Front-load the heavy asks. Document analysis, research, and complex reasoning go first.
3. Move to light work as the session fills. Editing, formatting, and short follow-ups fit in the last part of a window.
4. Keep unrelated questions out of the deep thread. A side question in a long, file-heavy thread pays for the whole thread's context. Ask it in a fresh chat or save it for later.

This also improves output quality. A fresh thread with a focused brief tends to produce better first answers than message 60 of a meandering one.

Checkpoint Before the Reset

The costly moment is not hitting the limit; it is hitting it mid-thought, with the plan only in the thread. A checkpoint is a short, structured summary you can paste into a fresh chat after the reset. Create it when you see the session getting close, not after you are blocked.

Before we stop, write a checkpoint I can paste into a new chat.
Use exactly these headings:

GOAL: one sentence.
DECISIONS MADE: bullet list, with the reason for each.
CURRENT STATE: what is finished, what is half-done.
OPEN QUESTIONS: what we have not resolved.
NEXT 3 STEPS: in order, specific enough to start immediately.
KEY FACTS: numbers, names, constraints I must not lose.

Keep it under 300 words. No preamble.

The checkpoint does two jobs. After the reset, you start a new chat with a compact brief instead of a heavy thread, which saves usage. And if you come back the next day, you remember where you were. For the full method of moving work across chats, see moving a Claude conversation to a new chat.

When not to checkpoint: short, self-contained tasks. If the work fits comfortably in one sitting, a checkpoint is overhead.

Worked Example: A Proposal Day

A Pro user needs to write a 10-page client proposal in one day, using two source PDFs and a call transcript.

• 7:45-8:30, offline prep: extract the relevant 18 pages from the PDFs, trim the transcript to the client's stated goals, draft the outline. No messages sent.
• 8:30, window 1 opens: analysis of sources and outline review with thinking on. Then section drafting.
• 11:45: the usage meter is getting high. Run the checkpoint prompt. Save it. Continue light edits until blocked or done.
• 12:00-13:30: step away or edit the draft manually.
• 13:30, window 2 opens: new chat, paste the checkpoint and the current draft only (no source PDFs). Finish remaining sections and a final review.

Window 2 starts lean because it carries a 300-word checkpoint and a draft instead of 18 pages of sources plus three hours of conversation. This is the difference between finishing in the afternoon and being blocked again by 15:00.

Pace the Week, Not Just the Day

The weekly limit resets at a fixed time assigned to your account, shown in Settings > Usage. Knowing that time is half the planning.

• Schedule the heaviest work (big analysis, long Claude Code runs) in the first half of your weekly cycle.
• Keep the last day or two before the reset for lighter work, with buffer for surprises.
• Remember that Claude Code shares the same limits as claude.ai, so coding sessions count in your weekly plan.
• If a deadline lands right before your reset, consider whether usage credits are cheaper than reshuffling the week. Anthropic says that with credits enabled, work continues instead of stopping.

If you find yourself rationing every week despite good habits, that is a plan question; see Claude Pro vs Max.

Mistakes That Waste a Window

If you do get blocked mid-task without a checkpoint, do not waste the wait. Write down from memory what you were about to ask and what you had decided, then use the break for work that does not need Claude: reviewing the draft, checking numbers, or preparing the files for the next window. When the session resets, your first message should be a compact brief rather than "where were we?" in the old heavy thread.

The common thread is that the window is a resource you schedule, not a timer you react to. Ten minutes of planning at the start of the day usually saves more usage than any single prompt trick.

ClaudeKit Workflow Note

Planning around the window requires knowing where you are in it. ClaudeKit's usage circle sits in the bottom-right of claude.ai; hover it to see session and weekly limits with reset times, so you can decide when to checkpoint without opening settings. It appears when Claude returns usage data, and nothing is stored or sent to ClaudeKit.

For checkpoints, ClaudeKit's Handoff Brief turns a long conversation into a compact brief to continue in a new chat (free users get two per day), and the checkpoint prompt above can be saved to the prompt library for one-click reuse. Pinning key decisions to the Workspace panel keeps them findable while you work. For handling the moment of reset itself, see protecting your work at session resets.