Guide · 2026-09-11

How to Create a Gantt Chart in MS Project: 7 Easy Steps

Building a Gantt chart in MS Project can feel harder than the project itself. You may have tasks, deadlines, dependencies, and team assignments scattered across notes, yet still lack a clear visual plan. That confusion creates real problems: missed handoffs, unrealistic dates, and progress updates that take too long.

But here’s the truth: you do not need advanced project-management skills to create a useful Gantt chart. You need a clear task list, realistic durations, and a logical sequence. In this guide, I’ll walk you through seven practical steps in Microsoft Project, from starting a blank plan to tracking progress. You’ll also learn how to fix common scheduling issues and when another project management platform may suit your team better.

How to Create a Gantt Chart in MS Project: 7 Steps

To create a Gantt chart in MS Project, start a project, enter tasks and durations, link dependencies, assign resources, set a baseline, and track progress. The chart updates automatically as your schedule changes.

Here is the complete workflow:

  1. Start a new project and set the calendar.
  2. Build the task list.
  3. Organize tasks into phases.
  4. Enter durations and milestones.
  5. Link tasks with dependencies.
  6. Assign people or resources.
  7. Save the baseline and track progress.

1. Start a New Project and Set the Calendar

Open Microsoft Project and choose a blank project. Before entering activities, set the project start date and confirm the working calendar.

Go to Project and open Project Information. Select the planned start date, then choose the calendar that matches your team’s working pattern.

For example, a standard calendar may use Monday through Friday with eight working hours per day. A construction team may work weekends, while a global team may need regional holidays removed from its schedule.

Here’s why: an incorrect calendar changes every finish date. If MS Project assumes a five-day week while your team works six days, the chart may show a later completion date than your team expects.

2. Build the Task List

Enter the work required to complete the project in the Task Name column. Start with broad activities, then add the specific actions needed to finish each one.

For a website launch, your first entries might include:

Keep each task meaningful. “Build website” is too broad because it hides research, design, development, and testing. “Create homepage layout” gives you a clearer unit of work and a more useful progress signal.

You might be wondering: how detailed should the task list be? A task should usually represent work that one person or one small group can complete within a few days or a couple of weeks.

3. Organize Tasks into Phases

Long task lists become easier to read when you group related activities under summary tasks. In MS Project, these groups create a hierarchy without removing detail.

For example, you could create these phases:

Place the relevant activities below each phase, then use the Indent Task command to make them subtasks. MS Project displays the phase as a summary task and calculates its overall duration from the activities underneath it.

Use phases to explain the project structure, rather than adding unnecessary levels. If every activity has several layers of sub-activities, the schedule may become difficult to maintain.

4. Enter Durations and Milestones

Enter an estimated duration for each task in the Duration column. You can use days, weeks, hours, or minutes, such as 5d, 2w, or 16h.

MS Project uses these durations to calculate the schedule. With automatic scheduling enabled, the application places each activity on the timeline and adjusts dates when dependencies change.

Add milestones for important points that have no meaningful duration. A milestone may represent:

Set a milestone’s duration to zero. It will appear as a diamond on the chart, making major approvals and delivery points easy to spot.

The best part? Milestones give stakeholders a fast way to understand progress. They can see whether the project has reached a meaningful checkpoint without reading every activity.

5. Link Tasks with Dependencies

Dependencies show the relationship between activities. They tell MS Project when one task can begin relative to another task.

The most common relationship is Finish-to-Start. The next activity starts after the previous activity finishes. For example, development may begin after the design is approved.

To create a link, select the related activities and click Link Tasks. You can also enter predecessor numbers in the Predecessors column.

Common dependency types include:

Use dependency links instead of manually typing dates wherever possible. If testing depends on development, linking those activities allows MS Project to move testing when development takes longer.

Let me explain: manually entered dates can make a schedule look precise while hiding its logic. Dependencies reveal what actually controls the timeline.

6. Assign People or Resources

Assign resources to show who is responsible for each activity. Select a task, open the Resource Names column, and choose the relevant person, team, or equipment.

For example, a website project might assign:

Resource assignments help you spot overloaded team members. If one designer is assigned to three activities during the same week, the schedule may need adjustment.

MS Project may change task durations when work, availability, and effort interact. Review those changes instead of accepting them without checking the real situation with the assigned person.

7. Save the Baseline and Track Progress

Once the schedule is realistic and approved, save a baseline. A baseline records the planned dates and gives you a reference for measuring actual performance.

Go to Project, choose Set Baseline, and save the baseline for the entire project. Later, you can compare planned dates with actual dates and see where the schedule has shifted.

During regular updates, enter actual starts, actual finishes, remaining durations, or percentage complete. The Gantt chart will show progress bars and schedule variance.

For example, if a five-day design activity is only 60% complete after five working days, the project may need a revised forecast. That information helps you discuss corrective action before the delay reaches development.

How the Gantt Chart Works in MS Project

A Gantt chart combines a task list with a timeline. Activities appear as horizontal bars, while the position and length of each bar represent timing and duration.

Summary tasks show project phases, milestones appear as diamonds, and dependency lines connect related activities. The left side explains the work; the right side shows when it happens.

Chart element What it tells you
Task bar When an activity starts, how long it lasts, and when it ends
Summary task The overall span of a phase or workstream
Milestone An important checkpoint with zero duration
Dependency line How one activity affects another
Progress shading How much of an activity has been completed
Baseline bar The approved plan compared with the current schedule

The chart is most useful when it reflects real relationships. A polished visual with weak estimates can mislead the team, while a simple chart with realistic dependencies can guide daily decisions.

Manually Scheduled Versus Automatically Scheduled Tasks

MS Project supports manually scheduled and automatically scheduled activities. Manual scheduling gives you more control over displayed dates, while automatic scheduling lets the application calculate dates from durations, calendars, and dependencies.

Automatic scheduling is usually better for a connected project plan. Suppose design takes three extra days. With linked automatic tasks, development and testing can move with it. A manually scheduled plan may leave later activities unchanged until someone notices the conflict.

You can still use manual scheduling during early planning when dates are uncertain. After the team agrees on the logic, convert the schedule to automatic scheduling and review the results.

How to Make the Schedule More Accurate

A Gantt chart is only as reliable as its assumptions. Use estimates from the people doing the work, then identify activities that could delay the rest of the project.

Consider three questions for every major activity:

For example, a legal approval may take one day in a simple project but two weeks during a regulated launch. Recording the shorter estimate without checking the approval process creates false confidence.

Here’s why: project delays often come from waiting, rework, and unavailable specialists rather than active work. Add realistic waiting periods when they affect the schedule.

Use the Critical Path to Focus Attention

The critical path is the sequence of activities that controls the earliest possible completion date. A delay on this path can delay the entire project unless you change the plan.

In a product launch, the path might run from requirements approval to design, development, testing, and release. A separate marketing activity may have extra flexibility and therefore less immediate schedule risk.

Use the Gantt Chart view and critical path formatting to identify activities with little or no slack. Then focus status meetings on those activities first.

This does not mean ignoring other work. It means spending attention where a small delay could create the largest effect.

How to Format and Share a Clear Gantt Chart

Formatting helps people understand the schedule quickly. Keep the timeline readable, use consistent names, and show only the information your audience needs.

Useful adjustments include:

For a weekly team meeting, you might show activities planned for the next two weeks. For a steering committee, you may show phases, milestones, major risks, and the forecast completion date.

Avoid placing every available field on the screen. Too much detail makes the chart harder to scan and can hide the schedule’s most important signals.

Choose the Right View for Each Conversation

Use the standard Gantt Chart view for planning and status reviews. Use a task sheet when you need to inspect durations, predecessors, constraints, or assigned resources.

Timeline view can work well for presentations because it shows major phases and milestones in a simplified format. A network diagram may help when the team needs to examine dependency logic rather than calendar placement.

Think of each view as a different lens. The underlying plan stays connected, but the presentation changes according to the decision you need to make.

Natural Project Scheduling Solution: ONES.com

ONES.com product screenshot

Value Proposition

ONES.com combines project management and knowledge management in one platform. It can help teams coordinate schedules, work items, requirements, and project guidance without relying on a collection of separate tools.

For teams comparing project management platforms with Microsoft Project or looking for a Jira alternative, ONES Project provides structured planning with Jira-compatible workflows and self-hosted deployment options.

Core Capabilities

Scheduling complexity → Custom workflows and fields → More precise planning

When every project follows a different process, fixed task structures create friction. ONES Project lets you configure workflows and custom fields so teams can capture the information they actually need.

Scattered project guidance → ONES Wiki → Easier knowledge access

Teams often lose time searching for requirements, decisions, and operating guidance. ONES Wiki provides a connected knowledge management space, serving as a Confluence alternative for teams that want project context near their work.

Manual progress reporting → Built-in reporting → Faster status visibility

Preparing weekly updates can consume hours. Built-in reporting helps teams view progress, workload, and project trends without assembling every update manually.

Complex sprint planning → Sprint management → Clearer short-term execution

Agile teams need a practical way to plan upcoming work. Sprint management supports iteration planning, prioritization, and review of completed activities.

Repeated administrative work → Automation → Fewer routine handoffs

Notifications, status changes, and recurring actions can slow delivery. Automation reduces repetitive coordination and helps activities move through agreed workflows.

Plugin-heavy project setups → Native capabilities → Lower configuration overhead

When essential functions depend on many extensions, maintenance becomes harder. ONES Project includes core planning, workflow, reporting, field, sprint, and automation capabilities in the platform.

Restricted deployment requirements → On-premise, private cloud, or air-gapped deployment → Greater infrastructure control

Some organizations cannot place project information in a public cloud. ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with full feature parity between cloud and self-hosted versions.

Small-team budget pressure → Free plan for up to 30 seats → Lower barrier to adoption

Small teams can begin with up to 30 seats on the free plan, then evaluate whether the platform fits their planning and knowledge management needs.

Application Scenarios

A software team can use ONES Project to manage backlog items, sprint work, dependencies, and release reporting while keeping technical guidance in ONES Wiki.

An organization with restricted network requirements can use a self-hosted deployment for project coordination while maintaining control over its operating environment. A distributed team can use workflows and reporting to coordinate handoffs across departments.

Common Challenges When Building a Gantt Chart

Challenge: The Schedule Has Too Much Detail

Problem: The chart contains hundreds of small activities, making it difficult to identify major deadlines or risks.

Solution: Group related activities into phases and keep the main view focused on work that affects timing, ownership, or delivery. Move highly detailed planning into lower-level tasks when necessary.

Challenge: Dates Keep Moving Unexpectedly

Problem: A small change causes several later dates to shift, and the team does not understand why.

Solution: Review dependency links, calendars, constraints, and task types. Look for hard date restrictions that prevent MS Project from recalculating the schedule logically.

Challenge: Team Members Are Overloaded

Problem: One person appears assigned to several activities at the same time.

Solution: Use resource views to identify conflicts. Move work, adjust timing, add capacity, or split activities after discussing the change with the team member involved.

Challenge: Progress Updates Are Inconsistent

Problem: Some people report percentages while others report dates, making the project status difficult to interpret.

Solution: Define a weekly update routine. Ask each owner to report actual progress, remaining effort, risks, and any dependency that could affect the next milestone.

Challenge: The Plan Looks Accurate but Is Not Realistic

Problem: The chart has precise dates, yet estimates do not reflect review time, waiting periods, or rework.

Solution: Validate the schedule with the people performing the work. Add contingency where uncertainty is high, and record assumptions in the project notes so they remain visible.

FAQs About Creating a Gantt Chart in MS Project

Can I create a Gantt chart in MS Project without entering every task?

You can create a basic chart with only a few activities, but the result will have limited planning value. Enter the major work packages first, then add enough detail to show ownership, dependencies, milestones, and realistic timing. You can refine the schedule later as the team learns more. Start with the project structure rather than trying to predict every minor action on day one.

Why are my tasks not moving when an earlier activity is delayed?

The tasks may be manually scheduled, disconnected from the earlier activity, or restricted by date constraints. Check the scheduling mode, predecessor column, and constraint type. If the work should move automatically, connect the activities with the correct dependency and use automatic scheduling. Then review the updated dates to confirm that the result matches the team’s actual workflow.

Should I use hours or days for task durations?

Use the unit that matches how your team estimates work. Days are usually easier for planning business activities, while hours may help with short technical tasks or capacity calculations. Avoid false precision. An estimate of “2 days” may be more honest and useful than “13.5 hours” when the work includes reviews, interruptions, or coordination.

What is the difference between a milestone and a task?

A task represents work that takes time, while a milestone marks an important event or checkpoint. A milestone usually has zero duration, such as “Design approved” or “Launch completed.” Milestones help stakeholders scan the schedule quickly and make it easier to discuss whether the project has reached a meaningful stage.

How often should I update a Gantt chart?

Update the schedule at least once a week during active delivery. High-risk projects may need updates several times per week. Record actual progress, remaining duration, new risks, and changes to dependencies. Updating only when a deadline is missed reduces the chart’s value because it hides early warning signs.

Conclusion

Creating a Gantt chart in MS Project comes down to seven practical actions: set the calendar, list the work, organize phases, estimate durations, link dependencies, assign resources, and track progress against a baseline.

But here’s the truth: the chart will not solve unclear ownership or unrealistic estimates by itself. It becomes valuable when the team reviews its assumptions and updates it regularly.

If your current schedule feels confusing, start with a small project and build one phase at a time. If you need connected project and knowledge management, configurable workflows, reporting, automation, or self-hosted deployment, ONES.com is another platform worth evaluating alongside Microsoft Project.