How to plan your week when you work several jobs

A day job and a side business. Three freelance clients. Two companies you co-own. More and more people work more than one role, and most planning tools still assume you have one job, one calendar and one task list.

The result is familiar: work calendars in different accounts, tasks spread across several tools, and the constant feeling that something in one role is being dropped because of another.

Why several roles are harder than one big one

Switching costs attention. When you move from one task to another, part of your attention stays on the first one for a while. Leroy (2009) called this “attention residue” and found it lowered performance on the next task. Switching between roles, with different people, tools and priorities, adds even more.

Calendars don’t talk to each other. A meeting in your consulting calendar doesn’t block time in your employer’s calendar, so you end up double-booked.

Every role thinks it’s the only one. Each job’s tools show only their own work, so nothing shows the real total load on your week.

One plan, many roles

The fix isn’t more tools. It’s one place where every role meets, while each role keeps its own tools for the actual work.

1. Give each role a colour and a name

Make a short list of your roles: “Company A”, “Client B”, “Personal”. Give each a colour. Use these names everywhere: in your planner, calendar and notes.

2. See every calendar together

Connect or subscribe to all your calendars in one view. You should be able to look at one screen and see every commitment, in its role’s colour.

3. Block time per role, in big chunks

Instead of switching between roles all day, give each role whole blocks: Monday and Wednesday mornings for Company A, Tuesday for Client B. Big blocks mean fewer switches and less attention residue.

4. Keep a “next actions” list per role

For each role, keep a short list of the next concrete things to do. When a role’s block starts, you open that list and begin, with no time lost remembering where you were.

5. End each block with a note to yourself

Before switching roles, write one line: where you stopped and what comes next. This “parking note” makes the next start much faster, and it helps your mind let go of the role you’re leaving.

6. Do one weekly review across all roles

Once a week, look at everything together: what’s done, what’s due next week, and whether one role is quietly eating the others. Decide where the big blocks go next week.

A sample week

Here is how a week might look for someone with a part-time job at Company A, two freelance clients and their own life:

• Monday: Company A all day, with a 20-minute parking note before leaving.
• Tuesday morning: Client B. Afternoon: Client C.
• Wednesday: Company A.
• Thursday morning: Client B. Afternoon: personal admin and bills.
• Friday morning: Client C. Afternoon: weekly review across every role, then nothing.

Meetings that don’t fit the pattern still happen, but the default shape keeps switches to two or three a day instead of twenty. Tell each client or team which days are theirs; most people respect a clear pattern.

Protect the role with no deadline: you

When every job has demands, the one that disappears first is your own life: exercise, rest, friends, admin. Treat it as a role with its own colour and its own blocks. It doesn’t send you angry emails, which is exactly why it needs protecting.

Doing this in Thendoo

Thendoo was built for exactly this. Create a Space for each role, each with its own colour. Connect Google Calendar for every account and choose which Space each calendar belongs to, so meetings from every job appear on one Today timeline in the right colour. Connect ClickUp to see the tasks assigned to you, and filter Today, the Calendar or Tasks to one Space when you want to focus on one role. The Weekly review shows each Space on its own card.

Sources

• Leroy, S. (2009). Why is it so hard to do my work? The challenge of attention residue when switching between work tasks. Organizational Behavior and Human Decision Processes, 109(2), 168–181.