How to Add a Subtask in Microsoft Project

You open Microsoft Project. You’ve got a list of tasks. And somewhere in the back of your head, you know that dumping everything into a flat list is a disaster waiting to happen.

Deadlines blur together. Dependencies get missed. No one knows who owns what.

Subtasks fix that. They let you break big, ambiguous work into concrete, assignable steps — and Microsoft Project makes this surprisingly powerful once you know where to look.

This guide walks you through every method to add subtasks in Microsoft Project, plus the tips that separate organized project managers from the ones firefighting every week.

What Is a Subtask in Microsoft Project?

A subtask is a child task nested beneath a parent (or summary) task. Together, they form a Work Breakdown Structure (WBS) — the backbone of any well-run project.

Here’s the hierarchy in plain terms:

• Summary Task — the big bucket (e.g., “Website Redesign”)
• Subtask — the individual pieces of work (e.g., “Write copy,” “Design mockups,” “QA testing”)

When you indent a task beneath another task in Microsoft Project, the upper task automatically becomes a summary task. Its duration, cost, and completion percentage roll up from the subtasks below it — automatically.

According to the Project Management Institute (PMI), projects that use a formal Work Breakdown Structure are significantly more likely to meet scope, schedule, and budget targets than those that don’t. Yet studies show that only 46% of organizations prioritize the use of structured project management practices consistently.

That gap is expensive. PMI research estimates that $122 million is wasted for every $1 billion invested in projects due to poor project performance — much of it tied directly to unclear task structures.

Subtasks in Microsoft Project are your first line of defense against that waste.

Why Subtasks Matter More Than Most Teams Realize

Before jumping into the how, it’s worth grounding yourself in the why. Here are the numbers:

• 77% of high-performing projects use dedicated project management software with structured task hierarchies (Wellingtone, State of Project Management)
• The Standish Group CHAOS Report consistently shows that only 35% of projects are completed on time, on budget, and with full scope — a figure that improves dramatically with proper WBS use
• Teams using hierarchical task structures report up to 28% less rework compared to teams using flat task lists
• 71% of project managers say unclear task ownership is the single biggest contributor to missed deadlines (Asana Anatomy of Work report)
• Organizations that apply structured project planning practices waste 28x less money than those that don’t (PMI Pulse of the Profession)
• 80% of project managers feel their organizations don’t use project management software to its full potential (Wellingtone, 2023)

Subtasks solve the ownership problem. Every piece of work gets a name, a duration, an owner, and a place in the overall structure.

How to Add a Subtask in Microsoft Project: Step by Step

There are three main methods. Use whichever fits your workflow — the result is identical.

Method 1: Using the Indent Button on the Ribbon

This is the most visual method and the easiest to learn.

Step 1: Open your Microsoft Project file and go to the Gantt Chart view (the default view when you open a new file).

Step 2: Enter your parent task in the task list. For example, type “Phase 1: Discovery” in a task row and press Enter.

Step 3: In the next row, type the name of your first subtask — for example, “Stakeholder interviews.”

Step 4: With your cursor on the subtask row, go to the Task tab in the ribbon at the top.

Step 5: In the Schedule group, click the Indent Task button (it looks like a right-facing arrow with lines).

Your subtask immediately moves one level down. The parent task above it turns bold, signaling it is now a summary task.

Step 6: Repeat for any additional subtasks under the same parent.

Pro tip: You can create multiple levels of subtasks by indenting further. Microsoft Project supports up to 10 levels of hierarchy in a single project file.

Method 2: Keyboard Shortcut (Fastest Method)

Once you know this shortcut, you will never go back to the ribbon.

Step 1: Type your parent task and press Enter.

Step 2: Type your subtask name in the row below.

Step 3: Press Alt + Shift + Right Arrow to indent the task.

To outdent (move a task back up a level), press Alt + Shift + Left Arrow.

That’s it. Two keystrokes per subtask. If you’re building a detailed WBS with dozens of subtasks, this shortcut alone will save you significant time across every project you manage.

Method 3: Right-Click Context Menu

Step 1: Enter your tasks in the task list — parent task followed by the task you want to make a subtask.

Step 2: Right-click on the task row you want to indent.

Step 3: From the context menu that appears, select Indent Task.

The task moves down one level and the row above becomes a summary task.

How to Add Subtasks to an Existing Summary Task

You may already have a project set up with summary tasks, and now you need to add new subtasks inside them.

Step 1: Click on the last subtask currently under the summary task where you want to add a new one.

Step 2: Press Enter to create a new row below it.

Step 3: Type your new subtask name.

Step 4: Press Alt + Shift + Right Arrow to indent it to the correct level.

Microsoft Project will automatically include it under the summary task and recalculate the summary task’s duration and cost.

What if the new task ends up at the wrong level? Use Alt + Shift + Left Arrow to outdent or Alt + Shift + Right Arrow to indent further until it sits at the right level.

How to Add Multiple Subtasks at Once

Building out a full WBS from scratch? Here is the efficient approach.

Step 1: Enter all your tasks in the task list first — parent and subtask names — without worrying about indentation. Get everything into the list.

Step 2: Select multiple consecutive rows by clicking the first task row number, then holding Shift and clicking the last one.

Step 3: Press Alt + Shift + Right Arrow to indent all selected tasks simultaneously.

This is far faster than indenting one task at a time, especially for larger projects. According to the Project Management Institute, project managers spend an average of 54% of their time on planning activities — batching your WBS setup like this is one of the simplest ways to reclaim hours every week.

How to Collapse and Expand Subtasks

Once you have subtasks set up, Microsoft Project gives you clean controls to focus on the right level of detail.

To collapse a summary task (hide its subtasks):

• Click the small triangle/arrow to the left of the summary task name, or
• Click on the summary task row and press Alt + Shift + Hyphen (–)

To expand a summary task (show its subtasks again):

• Click the triangle/arrow again, or
• Press Alt + Shift + Plus (+)

To collapse or expand all summary tasks at once:

• Go to View tab → Outline → Select your desired outline level

This is especially useful for reporting. Collapse everything to Level 1 to show only summary tasks in a clean, high-level view. Expand all for a full drill-down during team standups.

How to Move and Reorganize Subtasks

Projects change. Subtasks move. Here is how to handle it without breaking your structure.

To move a subtask to a different position:

Step 1: Click the gray row number to the left of the subtask (this selects the entire row).

Step 2: Hover over the row number until your cursor changes to a four-directional arrow.

Step 3: Click and drag the row to its new position.

Microsoft Project will automatically adjust task IDs, predecessor links (where applicable), and summary task rollups.

To move a subtask from one summary task to another: Use the drag method above, then check its indent level after moving. Use Alt + Shift + Right/Left Arrow to re-indent if needed.

Common Mistakes That Undermine Your Subtask Structure

Even experienced users make these errors. Knowing them upfront saves painful rework.

Creating summary tasks manually instead of using indent. Some users type “(Summary)” into a task name thinking that creates the rollup. It doesn’t. The only way to create a true summary task in Microsoft Project is by indenting a task beneath it.

Over-nesting subtasks. More levels don’t always mean more clarity. A WBS with 6+ levels of nesting for a 3-month project creates confusion, not control. A common rule of thumb: no more than 3–4 levels for most projects.

Skipping the 100% rule. Your subtasks should collectively account for 100% of the parent task’s work. If your “Phase 1: Discovery” summary task has only two subtasks but actually requires five distinct deliverables, you have gaps in your plan — and gaps become schedule risk.

Assigning resources to summary tasks. Always assign resources to subtasks, not summary tasks. Summary tasks are containers. Assigning hours to them creates double-counting and inaccurate resource loading.

Not linking subtasks with dependencies. Subtasks under the same summary task often have a finish-to-start relationship. If “Draft report” must happen before “Review report,” link them. Unlinked subtasks do not warn you when one slips and cascades into another.

According to Gartner, poor requirements management — which includes poorly defined task breakdowns — is cited in 37% of project failures as a primary contributing factor.

Tips for Building a Subtask Structure That Actually Works

These principles separate functional project plans from plans that collect dust after week one.

Name subtasks as deliverables, not activities. “Homepage wireframe complete” is clearer than “Work on homepage.” Deliverable-based naming makes completion obvious and removes ambiguity about when a task is done.

Keep subtask durations between 8 and 80 hours. This is the classic WBS rule of thumb. Too short and you’re micromanaging. Too long and you lose visibility. The sweet spot gives meaningful progress tracking without administrative overhead.

Use milestones to mark key handoffs. Milestones are zero-duration tasks that mark the completion of a phase or a key deliverable handoff. Set them after your summary tasks as checkpoints. In Microsoft Project, set a task’s duration to 0 to convert it to a milestone.

Build your WBS before assigning durations. Get the full task structure locked first, then add durations. Doing it the other way around causes structural changes that break your timeline repeatedly.

Use task notes to document assumptions. Right-click any task → Notes → add context about scope, assumptions, or dependencies. This context is invisible in the Gantt view but critical for anyone who picks up the project later.

Conclusion

Adding subtasks in Microsoft Project is one of the most straightforward ways to transform a chaotic task list into a clear, controlled project plan.

The mechanics are simple: enter your tasks, use Alt + Shift + Right Arrow to indent, and let Microsoft Project handle the rollup calculations automatically. Use the Indent button on the ribbon if you prefer visual navigation, or right-click for a quick alternative.

The harder part — and the more valuable part — is designing a WBS that genuinely reflects how the work unfolds. Name subtasks as deliverables. Keep durations in a manageable range. Link dependencies. Assign resources to subtasks, never summary tasks.

Do that consistently, and Microsoft Project stops being a tool you update for status meetings and starts being the single source of truth that actually runs your project.

Given that organizations using structured project management waste 28 times less money than those that don’t, the time you invest in getting your subtask structure right pays dividends far beyond any single project.

Now go build something worth managing.