Planner Integration with Loop Tasks

Hi Jim,

You’re not alone in running into this, the current Loop + Planner integration is great for capturing tasks quickly, but it’s not designed yet for a “single master plan with everything in it,” which is what you’re aiming for.

A key detail is that Loop task lists and Collaborative meeting notes create their own Planner plans automatically. When you add a Loop task list in a meeting or Loop page and it syncs to Planner, Microsoft creates a separate “lightweight” plan for that task list and keeps them in sync. There’s no setting today to say “send these tasks to my existing main plan instead”.

That’s why you’re seeing tasks scattered into different plans instead of all landing in your 10-bucket master board. It’s frustrating, but at the moment it’s by design, and Microsoft hasn’t announced anything on the public docs/roadmap that would let you point Loop tasks straight at an existing plan.

For now, the realistic options are workarounds:

1. Use your main Planner plan directly in Loop (where possible)
• In “regular” Loop pages (not meeting notes), instead of inserting a Task list, use the Planner component and connect it to your existing plan. Tasks created there go straight into that plan, so everyone can still work in Loop but you keep a single board.
• This works well for ongoing project spaces where you want to keep using the Grid view (for subtasks) but still capture tasks in Loop.
2. Treat meeting/Loop task lists as an “inbox” and move tasks into the main plan
• From the meeting notes or Loop task list, click Open in Planner and move or copy the tasks into your main plan/buckets. Just be aware: if you move a task out of the auto-created plan into another plan, it’s removed from the meeting notes view (the task still exists in Planner, just not in the notes).
• Some teams keep those meeting-specific plans as “capture boards” and only move the tasks that really matter into the central plan.
3. Automate consolidation with Power Automate
• You can build a flow that triggers when a task is created in the auto-generated Loop plans and then creates a matching task in your main plan (optionally tagging it with the meeting name or source).
• It’s not as clean as being able to choose the plan up-front, but once configured it prevents tasks from spreading across lots of separate boards.

On your second point: today, subtasks are best managed from the Grid view in the new Planner, the Kanban board still focuses on the “main” task card, so you don’t see the full hierarchy in the same way you do in Grid. That’s a current limitation of how sub-tasks/summary tasks are surfaced across views.

If you’re exploring these features for a larger rollout, we share a lot of practical examples of Planner and Loop in real project scenarios on our MLPro YouTube channel:

https://www.youtube.com/@MLProPPM