An Execution Scope is the bounded area of work that In Parallel tracks — the team, project, program, or account that gets its own Living Execution Plan.

Every Execution Scope in In Parallel has one Living Execution Plan, one Execution Memory — the accumulating record of decisions, commitments, and ownership changes — and one place where your team stays aligned over time. Getting the scope right means the plan stays relevant and the signals In Parallel captures from meetings are meaningful. Getting it wrong means the plan feels noisy or disconnected from how the work actually runs. Most teams start with one scope, prove the value, then add more.

The Managing section in the left nav shows all your Execution Scopes and lets you switch between them or create new ones. Click Managing to expand it, then click the + icon in the Managing header.

Click the + icon to open the creation form. The name should match how people already talk about this work. The description is labeled optional, but filling it in directly improves the quality of AI-generated priorities and plan summaries — In Parallel uses it to understand what this scope covers.

Fill in the name, add a description of what this scope covers, then click Create.

Note: The product UI uses "team" in this flow. In In Parallel, the result is an Execution Scope — which can be a team, project, program, or any other bounded area of accountability.

In Parallel creates the scope and takes you straight to its dashboard — a default set of Living Execution Plan widgets is configured automatically. You don't need to set up the dashboard manually.

Note: Add at least one goal before your first meeting — even a rough milestone gives In Parallel the context it needs to surface accurate priorities from day one. The dashboard can be customised with additional widgets, but that's covered separately.

Getting the scope boundaries right matters more than most other setup decisions. A well-scoped area stays coherent and useful. A poorly scoped one fills with noise.

Ask yourself: "What outcomes am I accountable for executing?"

If the answer spans multiple unrelated cadences, owners, or success metrics, you're looking at multiple scopes — not one. A good scope has:

In Parallel can be used to manage many types of scopes depending on the user's need. There are no specific scopes that can only be used. Here are some examples of the types of scopes In Parallel has been used to manage:

Naming seems like a small decision but it affects adoption — people need to recognize the scope instantly and connect it to a real meeting or work rhythm.

Good names: - Match how people already talk about the work - Imply execution responsibility, not aspiration - Are easy to say in meetings and updates

Examples: "Platform Migration", "Product Weekly", "Q2 Growth Program", "Revenue Operations", "Customer X Delivery"

Names to avoid: - Vague: "Everything", "Company", "Ops Stuff" - Overly strategic: "Transformation", "Innovation", "Future" - Disconnected from any cadence

If you can't explain the scope in one sentence, it's probably too broad.

How many Execution Scopes should I create? Start with one — whichever team or initiative you most need to keep aligned. Add more once the first one is working well. There's no hard limit, but each scope works best when it has a clear owner, a real meeting cadence, and at least one goal.

Can I rename or edit a scope after creating it?

If you want to change the name of an Execution Scope, please ask your Customer Success contact to help.

What's the difference between an Execution Scope and a project in my project management tool? An Execution Scope is about execution reality — the decisions made, priorities shifted, risks surfaced, and ownership established in real meetings. It's not a task list or a project tracker. Think of it as the layer that keeps a team aligned on what matters and why, updated automatically from meetings rather than by manual input.

Can one person own multiple scopes? Yes. A team lead might own a Team scope for their group and a Project scope for a specific initiative. The Personal Dashboard aggregates tasks and goals across all your scopes, so nothing falls through the gaps.

What if I set up the scope incorrectly? Nothing is permanent. Update the name, description, and goals at any time. The history of decisions and meeting captures stays attached to the scope regardless of edits.