Most calendar advice assumes you have a consistent weekly rhythm — the same types of work showing up in roughly the same proportions week to week. If your work is project-based, that's not your reality. A discovery phase looks nothing like an execution sprint. A review cycle has a different meeting-to-focus ratio than a build week. Your calendar system needs to accommodate that variability, not fight it.
The Challenge With Project Work
Standard layer setups (Deep Work / Meetings / Admin / Personal) can obscure what's actually happening in project-based roles. You can have a week that's 60% meetings and it's completely appropriate — that's a stakeholder alignment week on a major project. Or a week that's 80% deep work and zero meetings, and that's also fine. The question isn't whether the distribution is balanced; it's whether the distribution matches the project phase.
Two Layer Approaches
Option 1: Layer by Project
Create a layer per active project. Good for: understanding how much total time each project is consuming, identifying which projects are expanding beyond their intended scope, quarterly reviews of where your time actually went vs. what was planned. Works best when you have 3–5 concurrent projects with meaningful size differences.
Option 2: Layer by Work Type Across Projects
Standard work-type layers (Focus / Meetings / Admin / Personal) applied across all projects. Good for: understanding your focus-to-meeting ratio regardless of which project, tracking whether you have adequate deep work time, identifying when meeting load is too high across the board. Works best when you want to monitor your personal productivity health, not project health.
The Hybrid Approach
The most powerful setup for project-based workers: three layers by work type (Focus, Meetings, Admin) plus project tags in event titles. This gives you work-type analysis from the layers and project-specific analysis by filtering on tags. You get both views from one system.
Tag format: [PROJECT-NAME] in event title. Example: "[Atlas] Stakeholder review" in the Meetings layer.
The Quarterly Project Audit
Every quarter, run a project-level time review: which projects got your time, in what proportions, and how did that compare to what was actually planned? This surfaces the hidden pattern in project-based work — the projects that consume disproportionate time are rarely the ones with the most strategic value. They're the ones with the most friction, the most stakeholder noise, or the most ambiguous scope.
Knowing which projects are time sinks versus which are efficient is one of the most useful things you can know as a project-based worker. Your calendar data will tell you.