Three projects, all due in the same fortnight, each with a person asking "How's it going?" Every project looks manageable on its own list. Together, they don't fit. You find that out on the Wednesday before the deadline.
The fix isn't a better to-do list. It's seeing the hours, not just the dates, and deciding early what gives.
Quick answer
- List every active project with its deadline.
- Estimate the hours left for each, roughly.
- Count your real free hours before each deadline, after meetings.
- If hours needed exceed hours free, renegotiate now, not later.
- Give each project scheduled sessions on the calendar.
- Review twice a week and adjust.
Step 1: Get every project in one list
Write down every active project, including the ones you're "sort of" doing. For each, note:
- The deadline (real or self-imposed, and which one).
- Who it's for.
- The next action.
Give each active project a next action, or record what you are waiting for and when to check it. A project can be worth doing without an external deadline. Decide deliberately whether it belongs in this week's work or a later list.
Step 2: Estimate in hours, not tasks
A list of 12 tasks does not tell you how much time they need. Estimate the remaining work in hours, including review and revisions. Use previous work to choose a buffer. The example below adds 30% as a planning assumption, not a rule that fits every project. Track waiting time separately: two hours of your work may still require three days for someone else's approval.
| Project | Deadline | Base hours left | With a 30% buffer |
|---|---|---|---|
| Client website | 14 Nov | 16 | 20.8 |
| Quarterly report | 10 Nov | 8 | 10.4 |
| Grant application | 20 Nov | 12 | 15.6 |
That is 36 base hours, or 46.8 hours with the illustrative buffer. Use a range if the scope is uncertain, and replace the estimate as you learn more.
Step 3: Count the hours you actually have
Open your calendar. For each deadline, count the working hours available after meetings, travel, daily overhead and some space for interruptions. Use your actual week rather than assuming every unbooked hour is available for project work.
Check the projects together, not one at a time. In the example, 10.4 hours must fit before 10 November, 31.2 hours for the report and website before 14 November, and 46.8 hours for all three before 20 November. Those hours come from the same pool: you cannot allocate the same Tuesday morning to two projects. Include any early work a later-deadline project needs to meet a dependency.
If the report needs 10.4 hours and only 6 are available before its deadline, the shortfall is 4.4 hours. That is a reason to discuss scope, help or the delivery date now, not a certainty that the project must fail.
Step 4: Decide what gives
When hours needed exceed hours free, you have four options:
- Move a deadline. Ask early. "I can deliver the report on the 12th instead of the 10th" lands very differently a fortnight out than at 5 pm the day before.
- Cut scope. What's the version that's good enough?
- Get help. Delegate a piece.
- Drop something else. Decline a meeting, pause a lower-priority project.
Confirm the agreed change with the people affected, then update the task list and calendar. Moving a private work session alone does not change a delivery commitment.
Step 5: Schedule sessions, not deadlines
A deadline shows when the result is needed. Work sessions show when you intend to produce it. Keep both visible.
- Split each project's hours into sessions of 60 to 120 minutes.
- Leave time for review and waiting. Spread sessions where that helps, and book handoffs early enough for other people to respond.
- Order sessions by deadlines and dependencies. A later project may need an early approval request before you can work on it.
- Give each project a colour so you can see the balance of the week at a glance.
- Batch small project tasks (emails to the client, quick fixes) into a shared admin block. See task batching vs time blocking.
Step 6: Review twice a week
Monday and Thursday, five minutes:
- Did the sessions happen?
- Are the hour estimates still right?
- Does anything need renegotiating?
Your weekly review covers the bigger picture.
Tips for the messy reality
- Limit work in progress to what fits. Two large projects can exceed your capacity; several small ones may not. Use hours and dependencies to decide what stays active.
- Finish before starting. Shipping one project frees more headspace than progress on three.
- Use the Eisenhower test on project tasks: what's important but not urgent and getting ignored? (Eisenhower matrix examples)
- Write a note at the end of each session saying where you stopped and what's next. Restarting gets much easier.
Managing several projects in Dainvo
Dainvo Projects (Pro) are designed around the idea that a project needs time on the calendar, not just a due date:
- Each Project has a status and an optional deadline. Backlog, To Do, In Progress, Complete. Filter the Project tree by state to see what's active.
- Several Project blocks per Project. Add sessions on different days. Each block shows the Project's name and colour, so the week shows how your time is split between projects.
- Ordered tasks from your apps. Add tasks from Dainvo, Todoist, Microsoft To Do, Google Tasks, TickTick or Obsidian. Completing a task inside the Project completes it everywhere.
- One level of subprojects for bigger work.
- Notes per block on desktop. Associate a Markdown note with a single Project block to write where you stopped. Project Notes and local file links do not sync to mobile.
- Local file links. The project folder, the brief, the spreadsheet, one click from the Project. Dainvo stores links; it doesn't upload your files.
- All your calendars around it. Meetings from Google, Outlook, iCloud and CalDAV calendars sit next to your Project blocks, so free time is real free time.
- Account classifications and Standard hours (Pro) let you mark accounts as Work or Personal and define core hours. Calendar shading is a separate setting that starts off. These settings do not move existing blocks or automatically keep every Project session inside working hours.
Help: Use Projects to plan multi-block work. Pro is $5 a month or $48 a year at the launch price. For solo project tools in general, see the best personal project management apps.
FAQ
How do I prioritize between projects with the same deadline? Look at consequences. Which one has someone else waiting on it, money attached or a hard external date? That one goes first.
How many projects can one person manage at once? There is no reliable universal number. Compare the remaining effort and dependencies with your available hours, and pause lower-priority work when it does not fit.
How do I tell my manager I can't hit every deadline? Show the numbers: hours needed versus hours free. Offer options (new date, smaller scope, help) instead of only the problem.
What's the best tool for juggling multiple projects alone? One that shows project time on a calendar, not just task lists. Dainvo Projects are built for that.



