Guide · 2026-09-19

How to Make a Gantt Chart in Project: A Step-by-Step Guide

A project can feel under control until deadlines overlap, tasks depend on one another, and nobody knows what should happen next. Without a clear timeline, small delays quickly affect testing, approvals, launches, and customer commitments.

That uncertainty creates more than scheduling stress. Team members may start work too early, managers may miss bottlenecks, and stakeholders may receive updates that no longer match reality.

But here's the truth: you can turn a task list into a useful visual schedule in Microsoft Project with a few structured steps. This guide shows you how to create a Gantt chart, connect activities, assign ownership, track progress, and keep the schedule realistic.

How to Make a Gantt Chart in Microsoft Project

A Gantt chart in Microsoft Project is a timeline that displays project activities as horizontal bars, showing their duration, sequence, dependencies, and progress. It helps you see what needs to happen, when each activity should happen, and how one delay could affect the wider plan.

Microsoft Project usually opens with a Gantt Chart view. The left side contains activity details, while the right side displays bars across a calendar timeline. You can build the schedule manually or import structured planning information.

1. Create a new project

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

Go to the project information area and choose the planned start date. Microsoft Project can then calculate dates for scheduled activities.

Check these settings before continuing:

A project starting on Monday with a standard five-day week will produce different finish dates from a project that runs seven days per week. Accurate calendar settings prevent misleading timelines.

2. Add activities and summary tasks

Enter each major activity in the task name column. Use clear verbs that describe the work, such as “Approve design,” “Build checkout page,” or “Run security testing.”

Group related activities under summary tasks. For example, an ecommerce launch might include these groups:

Use indentation to place smaller activities beneath their related summary task. Microsoft Project can then calculate the summary task’s overall duration from the activities below it.

Keep activities small enough to estimate and track. “Develop website” is too broad for reliable scheduling. “Create product page layout” gives you a clearer amount of work and a more useful status update.

3. Add activity durations

Enter an estimated duration for every scheduled activity. You can use days, weeks, hours, or another supported unit.

For example, a product launch plan might include:

Activity Duration
Confirm launch requirements 3 days
Create landing page design 5 days
Build landing page 8 days
Complete quality testing 4 days
Approve launch 1 day

Use estimates that reflect actual effort and working conditions. A two-day coding activity may require four calendar days if the engineer supports another urgent project.

When the duration is uncertain, mark it as an initial estimate and revisit it during planning. Early estimates become more reliable as the team clarifies requirements.

4. Set the scheduling mode

Microsoft Project supports manually scheduled and automatically scheduled activities. Automatic scheduling is usually more useful for a connected project plan.

With automatic scheduling, Microsoft Project recalculates dates when you change durations, calendars, or dependencies. Manual scheduling can help during early brainstorming, when dates are still uncertain.

After the planning workshop, convert stable activities to automatic scheduling. This allows the timeline to respond when you add three days to testing or move a design review.

5. Connect activities with dependencies

Dependencies show the relationship between activities. They tell Microsoft Project when one activity can begin or finish relative to another.

The most common relationship is finish-to-start. The first activity must finish before the next activity begins.

For example:

  1. Approve wireframes.
  2. Build the page.
  3. Run browser testing.
  4. Publish the page.

In this sequence, development depends on design approval. Testing depends on development. Publishing depends on successful testing.

To create a dependency, select the related activities and use the link command. You can also enter predecessor information in the appropriate column.

Use other dependency types when the work requires them:

Dependencies should describe genuine work relationships. Avoid linking every activity simply because it appears nearby. Excessive links make the schedule rigid and can hide the real constraints.

6. Add milestones

Milestones represent important points with zero duration. They help you recognize approvals, releases, handoffs, and other outcomes.

Useful milestones include:

A milestone gives stakeholders a quick way to understand progress. It also creates a clear checkpoint for reviewing risks before the next phase begins.

7. Assign people and other resources

Assign the people, teams, equipment, or services needed for each activity. This step makes the schedule more realistic because Microsoft Project can account for availability and workload.

For example, assign a designer to the visual design activities, a developer to build activities, and a tester to quality checks.

Watch for overloaded assignments. If one developer is scheduled for 16 hours of work on the same day, the timeline needs attention. You might adjust the sequence, add capacity, reduce scope, or extend the deadline.

8. Review the Gantt chart layout

Once the schedule contains activities, durations, links, milestones, and assignments, review the timeline from left to right.

Look for these warning signs:

Adjust the timescale so you can see the right level of detail. Use a weekly view for a short launch plan and a monthly view for a large transformation program.

9. Add a baseline

When the plan is approved, save a baseline. A baseline captures the planned dates, duration, and cost at a specific point.

You can later compare actual progress with the baseline. This reveals whether an activity started late, took longer than expected, or caused the final deadline to move.

Set a baseline only after the team reviews the schedule. Changing the baseline every time the plan changes removes the reference point you need for meaningful analysis.

10. Track progress regularly

Update the schedule during recurring project reviews. Record actual starts, actual finishes, remaining duration, and percentage complete where appropriate.

A simple weekly review can follow this sequence:

  1. Confirm completed activities.
  2. Update activities currently in progress.
  3. Check overdue work.
  4. Review upcoming milestones.
  5. Identify changes to dependencies or capacity.
  6. Communicate the effect on the final date.

Tracking works best when the team reports honestly. A task marked 90% complete for three weeks gives you less insight than a clear explanation of what remains.

How the Timeline Logic Works

The chart is only as reliable as the logic behind it. A bar shows timing visually, while dependencies explain why the timing exists.

Here's why: if you extend “Build payment integration” from five days to eight days, the activities connected after it should move automatically. That chain makes schedule impact visible.

Understanding the critical path

The critical path is the sequence of activities that determines the earliest possible project finish. Delays on this path can delay the final milestone unless you change the plan.

Imagine this sequence:

Activity Duration
Approve design 3 days
Build feature 7 days
Complete testing 4 days
Release 1 day

This path takes 15 working days. If testing takes two extra days, the release may also move by two days.

Microsoft Project can highlight critical activities. Review them during status meetings because they deserve early risk management.

Recognizing slack and flexibility

Some activities have slack, which means they can move without affecting the final deadline. Slack provides flexibility for assigning people and handling minor delays.

For example, a training activity may have three days of slack after development finishes. You could move training within that window without changing the launch date.

Slack is useful, although it should not become an excuse for postponing work. Too many delayed activities can consume the available flexibility.

Using leads and lags carefully

A lag adds waiting time between linked activities. For example, paint may need two days to dry before installation begins.

A lead allows the next activity to begin before the previous activity fully finishes. For example, testing could begin for completed components while development continues on later components.

Use these relationships only when they reflect a real operating condition. Hidden leads and lags can make a schedule difficult to explain.

How to Make the Chart Easier to Read

A technically correct timeline can still confuse people if it contains vague labels, excessive detail, or inconsistent formatting.

The best part? A few visual improvements can make your plan much easier to discuss in a meeting.

Use clear activity names

Start each activity with an action and a meaningful outcome. “Review” is vague. “Review mobile checkout defects” tells the team what the work involves.

Keep names short enough to scan. Put extra context in notes or planning discussions rather than creating long labels that stretch across the screen.

Separate phases from activities

Use summary tasks for major phases and child activities for the work beneath them. This structure lets executives see the big picture while allowing the delivery team to inspect details.

For example, an application redesign may use:

Show milestones prominently

Milestones should be easy to spot. Use them for decisions and outcomes rather than ordinary activities.

A milestone called “Meeting held” is usually weak. “Launch decision approved” gives stakeholders a clearer reason to pay attention.

Keep the view focused

Display the fields that support planning and review. Common choices include activity name, duration, start, finish, predecessor, assigned person, and progress.

Hide columns that do not help the current conversation. A planning workshop may need dependencies, while an executive review may need milestones and finish dates.

How to Build a Gantt Chart That Stays Accurate

Creating the chart takes an afternoon. Keeping it trustworthy requires an operating rhythm.

Let me explain: a schedule becomes stale when people treat it as a one-time presentation instead of a shared planning system.

Agree on update ownership

Assign responsibility for maintaining each area of the plan. A delivery lead may manage dependencies, while activity owners update their progress.

Set a regular review cycle. Weekly updates work for active delivery. A monthly cadence may suit a long program with fewer changes.

Use status dates

A status date separates completed work from future plans. It gives you a consistent point for analyzing slippage and remaining work.

For example, if the status date is Friday, activities completed by Thursday should be recorded as complete. Activities still underway should show their remaining duration.

Record assumptions and risks

Schedule estimates often depend on assumptions. A design activity may assume that legal approval arrives within three days.

Write down important assumptions and connect them to the affected activities. If legal review takes longer, the team can quickly see which dates require attention.

Protect the plan from unrealistic compression

Shortening every estimate does not create a faster project. It creates a schedule that fails during execution.

When a deadline is fixed, explore practical options:

Each option carries trade-offs. Show those effects clearly so stakeholders can choose with better information.

Common Mistakes to Avoid

Many schedule problems come from a few recurring habits. Spotting them early can save days of rework.

Adding activities without relationships

A long list of independent bars does not show how work flows. Add relationships where a genuine handoff or constraint exists.

Using one enormous activity

“Implement platform” may last several months and provide little tracking value. Break it into outcomes that can be estimated, assigned, and reviewed.

Ignoring capacity

A schedule can show an attractive deadline while quietly assigning the same specialist to five concurrent activities. Check workload before approving the timeline.

Updating only the percentage complete

Percentage complete does not always reveal what remains. A task at 80% may still need integration, approval, or testing.

Update remaining duration and explain meaningful changes. This gives the schedule more operational value.

Changing the baseline repeatedly

A baseline should represent an agreed plan. If you replace it after every delay, you lose the ability to compare performance against the original commitment.

Project Timeline Solution: ONES.com

ONES.com product screenshot

Value Proposition

ONES.com brings project management and knowledge management together on one platform, with ONES Project supporting planning, delivery, and tracking. It can suit teams that want Jira-compatible workflows, native reporting, and self-hosted deployment options.

ONES Project is sold separately from ONES Wiki. The platform offers a free plan for up to 30 seats and supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments.

Core Capabilities

Application Scenarios

Software release planning: A development team can connect requirements, sprint work, testing, defects, and release milestones. Reporting helps the release lead identify blocked work before the target date becomes unstable.

Regulated engineering programs: An organization with strict network controls can use an air-gapped or on-premise deployment. The team can maintain structured workflows while meeting its operating requirements.

Cross-functional launches: Marketing, product, engineering, and support teams can coordinate launch activities through custom fields, milestones, automation, and shared project knowledge.

Common Challenges and Practical Solutions

Challenge: The schedule contains too much detail

Solution: Create separate planning levels. Use summary tasks for leadership conversations and detailed activities for delivery teams. This keeps the timeline readable without removing useful planning information.

Challenge: Dates keep changing

Solution: Review dependencies, capacity, assumptions, and scope. A moving finish date often reflects an unstable constraint rather than a simple estimation problem.

Challenge: Team members avoid updates

Solution: Make reporting lightweight. Ask each activity owner for three details: current state, remaining effort, and the main blocker. Use the information during a short recurring review.

Challenge: Stakeholders misread the bars

Solution: Add a brief legend and explain milestones, progress, and critical activities. Use a filtered view for each audience instead of showing every planning field at once.

Challenge: The chart looks complete while risks remain

Solution: Track assumptions, unresolved decisions, external approvals, and capacity concerns alongside the timeline. A bar cannot represent every risk by itself.

FAQs

Can I create a Gantt chart in Microsoft Project without linking activities?

Yes, although the chart will provide limited planning value. Independent bars show timing, but linked activities show how work flows. Add predecessors and successors for genuine handoffs, approvals, and technical constraints. You can leave exploratory activities unlinked until the team understands their relationship.

What is the best duration for one activity?

Choose a duration that allows reliable estimation and meaningful progress tracking. For many delivery teams, several days to two weeks works well. A two-month activity may hide important steps, while a one-hour activity may create unnecessary administration. Use the team’s workflow and reporting rhythm as your guide.

How often should I update the timeline?

Update it at least weekly during active delivery. High-risk launches may need twice-weekly reviews, especially during testing or deployment. Long programs with limited change may need less frequent updates. The important point is consistency, clear ownership, and honest remaining-duration estimates.

What is a milestone in a Gantt chart?

A milestone is a zero-duration marker for an important event or decision. Examples include design approval, testing completion, contract signing, and product launch. Milestones help stakeholders scan the plan quickly and create checkpoints for reviewing risks before the next phase begins.

Should I use manually scheduled or automatically scheduled activities?

Manual scheduling can help during early brainstorming when dates are uncertain. Automatic scheduling is usually better once the team has defined durations and dependencies. It recalculates dates when the plan changes, making schedule effects easier to see. Many teams use manual planning initially, then convert stable activities to automatic scheduling.

Conclusion

A useful Gantt chart starts with clear activities, realistic durations, meaningful dependencies, milestones, and available capacity. Microsoft Project can then calculate dates and reveal how changes affect the wider plan.

But here's the truth: the chart will only stay valuable if someone maintains it. Review progress regularly, preserve an approved baseline, update remaining work, and discuss risks before they become deadline surprises.

If your current schedule is difficult to maintain across teams, a project management platform such as ONES.com can provide structured workflows, reporting, automation, and deployment flexibility. Start with a simple plan, connect the work logically, and improve the timeline as your team learns more.