Time Blocking by Energy Levels for Multiple Jobs: Exact System with Templates and Adjustments

Time blocking by energy levels means assigning tasks to specific times based on your natural cognitive peaks—not a rigid schedule. For people juggling multiple jobs, clients, or projects, this method prevents burnout and maximizes output by matching task complexity to your available energy. The system has three core steps: (1) track your energy patterns for at least 5 days, (2) classify tasks by cognitive demand, and (3) design flexible blocks that adapt to your rhythm. Below, we break down each step with exact templates, rules for adjustments, and tools to implement it without friction.

1. Track Your Energy Patterns: The Only Way to Avoid Self-Deception

Most people assume they know their energy peaks—morning, afternoon, or night—but real data often contradicts intuition. For example, a developer might believe they’re most productive at 11 PM, but tracking reveals their focus drops after 9 PM, even if they keep working. To identify your true peaks:

• Log your energy hourly for 5-7 days on a 1–5 scale (1 = exhausted, 5 = in flow). Include the task type and its difficulty (low/medium/high). Example: "9:00 AM – Energy 4/5 – Writing client proposal (high demand)".
• Use a spreadsheet with columns for time, energy level, task, and difficulty. Color-code rows (e.g., green for 4–5, yellow for 3, red for 1–2) to spot patterns visually. Avoid apps with automatic tracking unless they correlate activity with self-reported energy (e.g., Toggl Track + manual notes).
• Look for consistent trends: Do you hit 4/5 energy at 8 AM but crash by 2 PM? Or do you start slow but peak after lunch? Ignore outliers (e.g., a single high-energy night after coffee). Focus on repeated patterns.

Example: Energy Log for a Freelance Designer

• Monday: 7:00 AM (2/5), 9:00 AM (4/5), 12:00 PM (3/5), 3:00 PM (2/5), 6:00 PM (1/5).
• Tuesday: 8:00 AM (3/5), 10:00 AM (5/5), 1:00 PM (3/5), 4:00 PM (2/5).
• Trend: High energy 9–11 AM, medium 12–2 PM, low after 3 PM. Evenings are unproductive.

2. Classify Tasks by Cognitive Demand (3 Tiers)

Not all tasks require the same mental effort. Group them into three tiers to assign them to the right energy blocks:

• High-demand (Tier 1): Tasks requiring deep focus, creativity, or decision-making. Examples: writing a technical report, designing a wireframe, coding a new feature, or strategizing for a client. Reserve these for your peak energy windows.
• Medium-demand (Tier 2): Repetitive but attention-heavy tasks. Examples: editing documents, client meetings, reviewing feedback, or organizing project files. Schedule these for moderate-energy periods.
• Low-demand (Tier 3): Mechanical or automatable tasks. Examples: sending invoices, replying to short emails, updating spreadsheets, or social media scheduling. Use these for low-energy moments.

Example: Task Classification for a Consultant with 3 Clients

• Client A (Marketing): High-demand = drafting campaign strategy; Medium-demand = reviewing analytics; Low-demand = scheduling posts.
• Client B (Development): High-demand = debugging code; Medium-demand = team sync; Low-demand = updating Jira tickets.
• Client C (Finance): High-demand = financial modeling; Medium-demand = client call; Low-demand = reconciling expenses.

3. Design Flexible Time Blocks: Templates and Rules

Templates for 3 Energy Profiles

Use these templates as starting points, then adjust based on your tracked data. Each template includes buffer time (10–15 minutes between blocks) to reset and handle transitions.

• Morning Peak (High energy 7–11 AM):
• - 7:00–9:00 AM: High-demand task (e.g., coding for Client A).
• - 9:15–10:30 AM: Medium-demand task (e.g., client meeting for Client B).
• - 10:45 AM–12:00 PM: Low-demand task (e.g., emails for Client C).
• - 2:00–4:00 PM: Medium-demand task (e.g., reviewing reports).
• - 4:15–5:30 PM: High-demand task (e.g., designing a proposal).
• - 5:30 PM onward: Buffer or rest.
• Afternoon Peak (High energy 2–6 PM):
• - 9:00–11:00 AM: Low-demand tasks (e.g., organizing files).
• - 11:15 AM–1:00 PM: Medium-demand task (e.g., editing content).
• - 2:00–4:00 PM: High-demand task (e.g., writing a blog post).
• - 4:15–6:00 PM: Medium-demand task (e.g., team follow-up).
• - 6:00–8:00 PM: High-demand task (e.g., programming).
• Night Peak (High energy 8 PM–12 AM):
• - 10:00 AM–12:00 PM: Low-demand tasks (e.g., social media updates).
• - 12:15–2:00 PM: Medium-demand task (e.g., invoicing).
• - 4:00–6:00 PM: High-demand task (e.g., client strategy).
• - 6:15–8:00 PM: Medium-demand task (e.g., sync meeting).
• - 8:00–11:00 PM: High-demand task (e.g., technical documentation).

Rules for Effective Blocks

• Variable durations: Use 25-minute blocks (Pomodoro) for short tasks or 90-minute blocks for deep work. Example: A 90-minute block for coding, followed by a 25-minute block for emails.
• Buffer time: Leave 10–15 minutes between blocks to stretch, hydrate, or review notes. This prevents mental fatigue when switching contexts (e.g., from Client A to Client B).
• Weekly review: Every Friday, compare your planned blocks to what actually happened. If a high-demand task was consistently postponed, reassess its priority or your energy allocation. Example: If you planned to write a report at 9 AM but kept pushing it to 3 PM, move it to a lower-energy slot or break it into smaller chunks.
• Limit high-demand blocks: Cap Tier 1 tasks at 2–3 per day to avoid burnout. Example: If you have 5 high-demand tasks, split them across 2 days.

4. Implement Time Blocking with Tools: Calendar and Task Apps

To apply this system with multiple jobs, use a tool that lets you:

• Color-code by job/client: Assign a unique color to each job (e.g., blue for Client A, green for Client B). This lets you see at a glance which blocks belong to which project. Example: In a calendar view, blue blocks = Client A’s tasks, green = Client B’s meetings.
• Block time visually: Use a calendar view to drag and drop tasks by duration and priority. If a task runs long, adjust the following blocks without losing structure. Example: If a client call overruns by 30 minutes, shorten the next block or move it to your buffer time.
• Sync with reminders: Set alerts 5–10 minutes before each block to mentally prepare. This is critical when switching between jobs (e.g., from a design project to a finance report).

Example: Time Blocking for a Consultant with 3 Clients

A consultant with high energy in the morning, medium in the afternoon, and low at night might structure their Monday like this:

• 8:00–10:00 AM (High energy): Data analysis for Client A (blue).
• 10:15–11:30 AM (Medium energy): Meeting with Client B (green).
• 11:30 AM–12:30 PM (Low energy): Replying to Client C’s emails (red).
• 2:00–4:00 PM (Medium energy): Preparing report for Client A (blue).
• 4:15–5:30 PM (High energy): Strategy for Client C (red).
• 5:30–6:30 PM (Buffer): Pending tasks or rest.

For dynamic adjustments, tools like Foco’s calendar view let you drag and drop tasks while maintaining color-coding. If you need to unify tasks from multiple apps (e.g., Notion, Jira, GitHub), this guide explains how to centralize them without migrating data.

5. Common Mistakes and How to Fix Them

• Mistake 1: Overloading energy peaks. Assigning too many high-demand tasks to your best moments leads to burnout. Fix: Limit Tier 1 tasks to 2–3 per day. Example: If you have 5 high-demand tasks, split them across 2 days or delegate one.
• Mistake 2: Ignoring transitions. Switching between jobs without breaks causes stress. Fix: Use 10–15 minutes between blocks to reset. Example: After a client call (Client A), take a walk before starting a design task (Client B).
• Mistake 3: Not prioritizing by importance. Filling blocks with urgent but unimportant tasks delays critical work. Fix: Use the Critical Power List method to identify 1–3 must-do tasks per day before blocking time.
• Mistake 4: Forgetting rest. Productivity isn’t about working nonstop. Fix: Include active rest (e.g., walking, meditating) or passive rest (e.g., doing nothing) in your blocks. Example: Schedule a 30-minute walk after lunch to recharge.

6. Adjusting Blocks for Real Life: Handling Overlaps and Delays

Even the best-planned blocks can derail. Here’s how to handle common disruptions:

• Overlapping tasks: If two high-priority tasks collide, ask: Which one moves the needle most for my goals? Example: If a client meeting (Client A) conflicts with a deadline (Client B), reschedule the meeting or delegate the deadline task.
• Unexpected tasks: Use your buffer block (e.g., 5:30–6:30 PM) to handle urgent requests. If no buffer exists, shorten a low-demand block or move it to another day. Example: If a client emails an urgent request at 4 PM, adjust your 4:15 PM block to accommodate it.
• Energy crashes: If you’re exhausted during a high-demand block, swap it with a low-demand task. Example: If you planned to write a report at 9 AM but feel sluggish, switch to emails and move the report to your next high-energy slot.

7. Time Blocking for Multiple Jobs: Advanced Tactics

Avoiding Context-Switching Fatigue

Switching between jobs (e.g., from coding to design to finance) drains mental energy. To minimize this:

• Batch similar tasks: Group tasks by job or type. Example: Schedule all Client A’s tasks in the morning, Client B’s in the afternoon.
• Use color-coding: Assign a unique color to each job in your calendar or task app. Example: Blue = Client A, green = Client B. This reduces cognitive load when scanning your schedule. For a manual alternative, see Bullet Journal for Multiple Jobs.
• Limit job switches: Aim for no more than 2–3 job switches per day. Example: If you have 3 clients, dedicate mornings to Client A, afternoons to Client B, and evenings to Client C.

Time Blocking with Parkinson’s Law

Parkinson’s Law states that work expands to fill the time available. To use this to your advantage:

• Set artificial deadlines: Assign shorter blocks to tasks to force focus. Example: If a report usually takes 3 hours, block 2 hours and use the pressure to work faster. For more on this, see Parkinson’s Law for Multiple Jobs.
• Use time constraints: For low-demand tasks, set a timer. Example: "Reply to emails for 25 minutes, then stop." This prevents tasks from ballooning.

8. How to Apply This with Foco

If you manage multiple jobs, Foco can streamline time blocking by energy levels. Here’s how:

• Color-coded containers: Create a "work" container for each client or project (e.g., "Client A – Design" in blue, "Client B – Development" in green). Tasks inherit the container’s color, so you can see at a glance which job they belong to in the Panorama view.
• Calendar view: Drag and drop tasks into time blocks using the execution date field (set the time and duration). Example: Block 9:00–10:30 AM for a high-demand task like "Write proposal for Client A." If the task is recurring (e.g., weekly meetings), set the recurrence to auto-populate future blocks.
• Voice capture: Dictate tasks on the go. Example: Say, "Review Client B’s report tomorrow from 2:00 to 3:30 PM," and Foco will create the task with the time block pre-filled. For multiple tasks, use Ráfaga to dictate a list (e.g., *"Call Client A at 10 AM, draft email to Client C by 11 AM") and review them before saving.
• Adjusting blocks: In the List view, filter by execution date to reorganize tasks. Example: If a client meeting runs long, drag the next task to your buffer block. Use the Kanban view to track task status (to do, doing, done) for each job.

FAQ

How long should my time blocks be?

Block duration depends on the task and your energy. Use 25-minute blocks (Pomodoro) for short tasks, 50–90 minutes for deep work, and 10–15 minutes for buffers between blocks. Example: 90 minutes for coding, 25 minutes for emails.

What if my energy levels change day to day?

Track your energy for at least 5 days to identify patterns. If your energy fluctuates, design flexible templates (e.g., morning/afternoon/night) and adjust blocks daily based on how you feel. Example: If you’re exhausted on Tuesday, swap a high-demand block for a low-demand task.

How do I handle tasks that take longer than planned?

Use your buffer block (e.g., 5:30–6:30 PM) to absorb overruns. If no buffer exists, shorten a low-demand block or move it to another day. Example: If a report takes 3 hours instead of 2, adjust the next block or move it to tomorrow.

Can I use time blocking with other methods like the Eisenhower Matrix?

Yes. Use the Eisenhower Matrix to prioritize tasks before blocking time. Example: Label tasks as urgent/important, then assign them to energy-appropriate blocks. For a step-by-step guide, see Critical Power List.

How do I avoid feeling guilty when I adjust my blocks?

Time blocking is a tool, not a rigid rule. If a block isn’t working, adjust it without guilt. Example: If you’re not in the mood for a high-demand task, swap it with a low-demand one and revisit it later. The goal is productivity, not perfection.