Blog
How to Create a Gantt Chart in Microsoft Project 2024
A Gantt chart is useful only when it represents a workable plan. Entering a list of activities is the starting point, not the finished schedule. In Microsoft Project Professional 2024, you can connect tasks, define milestones, assign responsibility and compare actual progress with the approved plan.
This guide explains how to create a Gantt chart in Microsoft Project and turn it into a schedule that can support delivery meetings, resource planning and reporting. The steps apply to typical projects in construction, engineering, IT, operations, consulting and other professional environments.
1. Start a project and choose the calendar
Open Microsoft Project 2024 and create a blank project. The default view is usually the Gantt Chart view, with task information in the table on the left and the time-scaled chart on the right.
Before entering detailed tasks, define the basic scheduling context:
- Enter the project start date in the project information settings.
- Choose whether the project is scheduled from a start date or a finish date. Scheduling from a start date is the usual approach for planned delivery work.
- Review the project calendar and working time.
- Set the standard working days, daily working hours, holidays and exceptional non-working periods that affect the project.
Calendar accuracy matters because Microsoft Project uses working time to calculate dates. For example, a task with a five-working-day duration does not necessarily finish five calendar days after it starts if a weekend or non-working day is included.
Use a project calendar for general working patterns, then review individual resource calendars if some people or teams work different hours. Avoid changing calendars simply to force a desired finish date. If the date is unrealistic, identify the constraint or dependency that causes the problem.
2. Enter tasks and realistic durations
In the Gantt Chart view, enter each significant activity in the Task Name column. Start with deliverables and work packages, then break them into activities that can be assigned and reviewed.
A useful task is specific enough for someone to understand what must be completed. “Prepare design” may be too broad, while “Issue coordinated design package for review” is easier to assign and track.
Enter a duration for each activity using units such as days or weeks. Do not confuse effort with duration:
- Duration is the amount of working time between the task start and finish.
- Work is the amount of effort assigned to one or more resources.
- Units represent how much of a resource’s available capacity is assigned.
For a first schedule, estimate durations using information from previous projects, subject-matter experts or a bottom-up assessment of the work. Record assumptions outside the chart if the estimate depends on an approval, supplier response or uncertain scope.
Microsoft Project can calculate dates automatically when tasks are set to Auto Scheduled. This is generally more suitable for a connected project plan because changes to predecessors can move successor tasks. Manually scheduled tasks can be useful while collecting initial information, but they may not respond to dependencies in the same way. Check the task mode column and use one approach consistently.
Do not type dates into every task unless there is a clear reason. A schedule built mainly from hard-coded dates is difficult to maintain when the plan changes.
3. Add milestones
Milestones mark important events rather than periods of work. Examples include design approval, contract signature, first production release, client handover or completion of a testing phase.
To create a milestone, add a task such as “Design approved” and set its duration to zero days. Microsoft Project displays it as a diamond on the Gantt chart. A milestone can also have predecessors and successors, which makes it useful for communicating decision points.
Use milestones at meaningful control points. If every minor action becomes a milestone, the chart becomes harder to read and the important dates lose visibility. A project may have internal milestones for management reviews as well as contractual or customer-facing milestones.
4. Connect tasks with dependencies
Task dependencies show the order in which work can occur. They are the foundation of a useful Microsoft Project Gantt chart because they allow the schedule to respond when an activity changes.
The common dependency types are:
- Finish-to-start: the successor starts after the predecessor finishes. This is the normal relationship for sequential work.
- Start-to-start: the successor can start when the predecessor starts, subject to any lag.
- Finish-to-finish: the successor cannot finish before the predecessor finishes.
- Start-to-finish: the successor cannot finish until the predecessor starts. This relationship is less common and should be used only when it accurately describes the process.
For most schedules, use finish-to-start links first. You can create them by selecting tasks and using the link command, by entering predecessor information in the task table, or by dragging between task bars where appropriate. Review the resulting dates rather than assuming the link produced the intended logic.
Dependencies should represent real conditions, not simply the order in which tasks were typed. For example, “Prepare installation method” may need to finish before “Submit method for approval”, while “Prepare training materials” may run in parallel with installation.
Use lag or lead carefully. A lag can represent a waiting period, such as time required for curing, review or delivery. If the waiting period is a real activity that needs ownership, it is often clearer to create a separate task instead of hiding the time in a relationship.
After adding links, look for tasks with no predecessor or successor. Some are valid project start and finish activities, but unexplained gaps can indicate missing logic. Also check for circular relationships, unrealistic overlaps and dependencies that create an unintended finish date.

5. Group work with summary tasks
Large projects are easier to read when related activities are organised under summary tasks. A typical structure might include:
- Project initiation
- Requirements and analysis
- Design and approval
- Implementation or construction
- Testing and handover
Enter the detailed tasks, select the tasks that belong together and indent them beneath a summary task. Microsoft Project then shows the summary task as a higher-level bar spanning its underlying work. Summary tasks help managers review the plan at different levels without removing the detailed activities.
Use summary tasks to describe deliverables, phases or work packages. Do not assign work directly to a summary task when the actual effort belongs to its child tasks. Keep the hierarchy logical: a task should not be nested under an unrelated phase merely to improve the appearance of the chart.
Summary tasks are also useful for reporting. You can collapse the outline to show only the major phases during a steering meeting, then expand it when the delivery team needs to examine individual activities.
6. Assign resources and review workload
A schedule becomes more useful when it shows who is responsible for the work. Open the resource sheet or use the resource assignment controls to add people, teams, equipment or cost resources as appropriate for the project.
For each task, assign the resource responsible for completing it. Use names or role-based resources according to the way your organisation plans work. A role such as “Electrical design” may be suitable during early planning, while a named specialist may be needed once the team is confirmed.
Review the effects of assignments on duration, work and availability. If one person is assigned to several tasks at the same time, the schedule may show an over-allocation. That does not always mean the plan is impossible: the tasks may be intentionally shared, or the person may have enough capacity to perform both. It does mean the situation should be reviewed.
Possible responses include changing task dates, assigning another resource, reducing the assignment, splitting work, or agreeing which activity has priority. Automatic resource levelling can help identify and resolve some conflicts, but it can also move dates and extend the schedule. Review any resulting changes before accepting them.
Microsoft Project is designed for structured project scheduling and tracking. It is not a replacement for every process diagram, organisational chart or team collaboration system. Use the schedule for time, dependency, responsibility and progress information; use a suitable diagramming or document tool when the main requirement is a process map or organisation chart.
7. Set a baseline before work starts
When the plan has been reviewed and approved, save a baseline. A baseline records the planned dates, durations and other schedule values so that you can compare the original plan with the current forecast.
Set the baseline from the project controls or tracking commands. Do this only after the schedule contains the agreed scope, dependencies, resources and milestones. If the baseline is saved too early, later changes may make the comparison less meaningful.
A baseline does not freeze the project. The current schedule can continue to change as work progresses, while the baseline remains a reference point. If the scope is formally re-planned, follow your organisation’s change-control process and decide whether a new baseline is appropriate. Do not overwrite the original plan without documenting the reason.
8. Update progress and read the schedule
During delivery, update the schedule using actual information rather than moving bars manually to make the chart look acceptable. Depending on the project, record actual start and finish dates, remaining duration, percentage complete or remaining work.
Set a status date to define the point up to which progress is being reported. Then review:
- Tasks that should have started but have not.
- Activities that are finishing later than planned.
- Milestones that are at risk.
- Changes in the forecast finish date.
- Resource over-allocations caused by delays or added work.
- Tasks on the critical path or other chains that have little scheduling flexibility.
Percentage complete is not always enough. A task can be marked 50 percent complete for several reporting periods without indicating whether the remaining work will finish on time. Ask the responsible person for a realistic remaining duration and update the schedule accordingly.
Compare current dates with baseline dates to distinguish normal progress from variance. If the forecast is later, identify the cause: delayed predecessor, additional scope, unavailable resource, approval delay or an incorrect original estimate.
9. Format and share the Gantt chart
Keep the chart readable for its intended audience. Show the columns that support the meeting or report, such as task name, duration, start, finish, predecessor, resource names and progress. Hide columns that add noise.
Use the timescale controls to change the level of detail. A weekly view may work for short-term coordination, while a monthly view is easier for management reporting. Keep the outline collapsed when presenting high-level phases and expand it for planning workshops.
Highlight milestones, late tasks or key work packages with consistent formatting. Avoid excessive colours and decorative formatting because they can make status information harder to interpret.
Before sharing the schedule, check the project start and finish dates, task names, filters, print area and page layout. Export or print a focused view for stakeholders who need a report, and retain the working project file for detailed planning and updates. Make clear whether the document shows the baseline, the current forecast or a particular reporting date.
Practical checklist for a usable schedule
- Define the project start date and working calendar.
- Enter deliverables, work packages and activities.
- Add realistic durations and choose the appropriate scheduling mode.
- Create milestones for significant decisions and handovers.
- Link tasks using real dependencies.
- Group detailed activities under summary tasks.
- Assign responsible resources and review capacity.
- Check for missing logic, unrealistic constraints and over-allocations.
- Save a baseline after approval.
- Update actual progress at an agreed status date.
- Compare the current forecast with the baseline and report meaningful variance.
Microsoft Project Professional 2024 is suitable when a task list is no longer enough and the team needs a structured plan with dependencies, milestones, resource information and progress tracking. Genuine Microsoft Project licences are available from KEYFORREST with instant electronic delivery; see the current product page for the available licence and current price.
Perguntas frequentes
What is the fastest way to create a Gantt chart in Microsoft Project?
Open a blank project in Gantt Chart view, set the project calendar, enter tasks and durations, then link the tasks with predecessors. Add summary tasks, milestones and resources after the basic schedule logic is working.
Should I enter task dates manually?
Use manually entered dates only when a date is a genuine fixed requirement or while collecting initial information. For most connected project schedules, use automatic scheduling and dependencies so that dates can respond to changes.
What is the difference between a milestone and a normal task?
A milestone represents an important event or decision and normally has zero duration. A normal task represents work performed over a period and therefore has a duration.
When should I set a baseline?
Set a baseline after the scope, dates, dependencies, resources and milestones have been reviewed and approved. It provides a reference for measuring schedule variance during delivery.
Can Microsoft Project create process diagrams or organisation charts?
Microsoft Project focuses on project schedules, dependencies, resources and progress. Use a dedicated diagramming tool when the main output must be a process diagram or organisation chart.