How to Customize a Gantt Chart in Primavera P6: 7 Steps
A crowded Primavera P6 Gantt chart can hide the details you need most. Activity names may be clipped, bars can look confusing, and critical work may blend into routine tasks.
That creates real problems during planning meetings. You may miss a delayed activity, misunderstand a relationship, or spend valuable time explaining a chart nobody can read quickly.
But here's the truth: customizing your layout does not require rebuilding your schedule. You can improve readability by changing the timescale, bar styles, columns, labels, filters, and grouping options.
This guide shows you how to customize a Gantt chart in P6 through seven practical steps. You will also see examples of useful layouts, common mistakes, and ways ONES.com can support broader project planning workflows.
How to Customize a Gantt Chart in Primavera P6: 7 Steps
Primavera P6 lets you tailor the Gantt chart to match your planning purpose. For a weekly coordination meeting, you may need clear activity names and short-term dates. For an executive review, you may prefer summary bars and milestone visibility.
-
Open the Activity Network or Activities view
Open the relevant project in Primavera P6 and go to the Activities window. This is where you can configure the layout used for the activity list and Gantt chart.
If P6 displays a saved layout, decide whether you want to adjust it or create a separate layout. Saving a separate version protects your standard view for future work.
For example, keep one layout called Weekly Planning and another called Management Summary. Each view can show different columns, grouping, and bar styles.
-
Adjust the activity columns
Columns control the information shown beside the timeline. Right-click the column header area, then use the column configuration option to add, remove, or reorder fields.
Choose columns that support the decision you are making. A short-term planning view may include:
- Activity ID
- Activity Name
- Original Duration
- Start
- Finish
- Total Float
- Activity Status
A management view may need fewer details. You could show only the activity name, planned finish, actual finish, and percent complete.
Here's why: excessive columns reduce the visible chart area. If you need to scroll horizontally before seeing the timeline, remove fields that do not support the current review.
-
Change the Gantt chart timescale
The timescale determines whether P6 displays years, quarters, months, weeks, days, or hours across the top of the chart.
Right-click the date scale and open the timescale settings. Select a format that matches your planning horizon.
Planning purpose Useful timescale Executive progress review Months and quarters Monthly schedule update Weeks and months Two-week look-ahead Days and weeks Shift or field coordination Hours and days For a 12-month construction schedule, displaying every day creates visual noise. For a two-week installation plan, displaying only months hides too much detail.
The best part? You can often adjust the timescale without changing any activity dates. The schedule remains intact while the visual emphasis changes.
-
Customize activity bars
Bar styles control how activities appear on the timeline. Use the bar settings to change colors, patterns, height, and visibility.
Common bar categories include:
- Current project activities
- Baseline activities
- Remaining activities
- Actual activities
- Critical activities
- Milestones
- Summary activities
Use colors with a clear purpose. For example, you might use red for critical activities, blue for planned work, green for completed work, and gray for baseline dates.
Avoid assigning a different color to every activity type. Too many colors make the chart harder to interpret, especially when several teams review it together.
Let me explain: a bar color should answer a question quickly. If red means critical work in one layout and delayed work in another, people may draw the wrong conclusion.
-
Add labels to the bars
Labels can show useful details directly on the Gantt chart. Depending on the available settings, you may add activity IDs, names, dates, durations, or percent complete.
Use labels selectively. Activity names are helpful when the chart will be presented without the activity table. Dates may be more useful when the chart supports a handoff or milestone review.
For example, a procurement schedule could show the activity name above each bar. A progress report might show the planned finish and actual finish instead.
If labels overlap, shorten activity names, increase row height, or remove secondary labels. A clean chart communicates more effectively than a detailed chart that cannot be read.
-
Group and sort activities
Grouping changes how activities are organized vertically. You can group activities by WBS, responsible manager, activity code, calendar, status, or another classification.
To review a project by work package, group by WBS. To prepare a coordination meeting, group by responsible discipline or area. To study schedule risk, group by total float ranges or activity status.
Sorting controls the order within each group. You might sort by start date, finish date, activity ID, or total float.
You might be wondering: should you group by WBS or responsibility? Use WBS when the review follows the project structure. Use responsibility when people need to focus on their assigned work.
-
Apply filters and save the layout
Filters help you focus on the activities that matter for a specific review. You can filter for incomplete work, critical activities, late activities, milestones, or tasks scheduled within a selected period.
A two-week look-ahead filter could show incomplete activities with planned starts or finishes during the next 14 days. A recovery review could show activities with negative float or forecast dates beyond the approved target.
After configuring the chart, save the layout with a clear name. Include the purpose in the name, such as Critical Path Review, Two-Week Look-Ahead, or Baseline Comparison.
Before sharing the layout, test it with another person. If they cannot understand the colors, labels, or grouping without a long explanation, simplify the design.
Which Gantt Chart Settings Matter Most?
You do not need to change every available setting. Start with the controls that affect interpretation: visible columns, timescale, bar colors, labels, grouping, and filters.
For example, a project manager reviewing delay risk needs float, forecast dates, and critical bars. A site supervisor coordinating upcoming work needs activity names, dates, constraints, and a short timescale.
Here's a practical rule: customize the chart around the meeting decision. If the meeting decides what starts next week, prioritize upcoming activities. If it evaluates performance, prioritize baseline, actual, and forecast information.
Use separate layouts for separate audiences
A single layout rarely works for every audience. Senior leaders usually need a compact overview, while schedulers and field teams need more operational detail.
Consider creating these layouts:
- Executive overview: WBS summaries, milestones, major dates, and high-level progress.
- Scheduler review: relationships, float, constraints, baseline bars, and forecast dates.
- Field coordination: short-term activities, responsible teams, locations, and daily dates.
- Delay analysis: late activities, negative float, actual dates, and recovery work.
Keep visual rules consistent
Consistency matters when several people use the same schedule. If a blue bar means planned work, keep that meaning across your saved layouts whenever possible.
Write down the meaning of important colors and symbols. A small legend beside a presentation can prevent confusion during a busy review.
How to Show Critical Path and Baseline Information Clearly
Critical path and baseline comparisons are two of the most common reasons to customize a P6 Gantt chart. They also cause confusion when the visual settings are too similar.
Use a strong, easily recognizable style for critical activities. Keep baseline bars thinner or use a different pattern so planned dates remain visible behind current forecasts.
For example, a current activity bar might appear as a solid blue bar. The baseline could appear as a thin gray bar below it. If the blue bar extends beyond the gray bar, the difference becomes visible immediately.
Make variance visible
A chart should help you see schedule movement without calculating every date manually. Compare planned, actual, and forecast positions on the timeline.
If an activity was planned to finish on June 10 but now forecasts June 18, the eight-day movement should stand out visually. Pair the chart with columns for baseline finish, current finish, and variance when your review requires precise analysis.
Color alone may be insufficient for printed reports or viewers with color-vision differences. Patterns, labels, and clear legends provide additional context.
Use milestones as decision points
Milestones mark approvals, inspections, handoffs, deliveries, and contractual dates. Give them a distinct symbol and keep their labels short.
A milestone such as Equipment Delivered is easier to interpret than a generic label such as Delivery Complete Activity. Clear naming improves the chart before you change any visual setting.
How to Build a Useful Look-Ahead Gantt Chart
A look-ahead chart focuses on near-term work. It should help you answer three questions: what is planned, what may block it, and who needs to act?
Start with a date filter covering the next one or two weeks. Include incomplete activities and key milestones. Add columns for responsible party, planned start, planned finish, and status.
For a concrete example, imagine a building-services installation review. The chart may show duct installation, electrical rough-in, ceiling inspection, and equipment testing. Grouping by floor or discipline can reveal coordination conflicts.
Reduce detail outside the review window
A 500-activity schedule can overwhelm a short-term meeting. Filter the view and hide summary levels that do not support the immediate discussion.
Keep enough context to understand dependencies. Showing only one activity without its predecessor or successor may hide the reason for a delay.
Highlight constraints and dependencies
Dates alone do not explain whether work can begin. Add relevant constraint or predecessor information when the team needs to identify blockers.
For example, a finishing activity may appear ready to start, but its predecessor inspection remains incomplete. The chart becomes more useful when the relationship is visible during the review.
Common Mistakes When Formatting P6 Gantt Charts
Formatting errors usually come from trying to show too much at once. A chart can contain accurate schedule details and still fail as a communication tool.
Using too many colors
Assigning colors to every trade, team, location, and status creates visual competition. Choose a small set of meanings and apply them consistently.
Displaying an unsuitable timescale
A daily scale is difficult to read across a multi-year program. A monthly scale is too broad for daily field coordination. Match the scale to the decision window.
Leaving labels in default positions
Labels can overlap bars, dates, or neighboring rows. Test the chart at the size people will actually view or print it.
Forgetting the baseline
A current schedule without a baseline may show where work stands, but it does not show how the plan has moved. Include the baseline when performance or variance matters.
Saving over a standard layout
A quick customization can affect future work if you overwrite a shared layout. Save a new version when the chart serves a different purpose.
Project Planning Solution: ONES.com

Value Proposition
ONES.com combines project management and knowledge management in one platform. ONES Project supports structured planning, workflow control, reporting, and collaboration for teams that need a shared view of work.
It can complement Primavera P6 when your team needs to coordinate work beyond schedule visualization. ONES Project is also positioned as a Jira alternative, with self-hosted deployment options for organizations requiring more control.
Core Capabilities
-
Scattered project work → Unified project management → Keep tasks, ownership, statuses, and delivery work in one project environment instead of coordinating across disconnected tools.
-
Rigid approval paths → Custom workflows and fields → Adapt work states, required details, and approval steps to match your internal process.
-
Limited visibility into progress → Built-in reporting → Give project leads a clearer way to review status, trends, and delivery progress without relying on manual reporting routines.
-
Complex sprint coordination → Sprint management → Plan iterative work, organize sprint scope, and review progress within a structured delivery cycle.
-
Repeated manual actions → Automation → Reduce routine status changes and process steps by triggering actions through configured workflow rules.
-
Dependence on many plugins → Native project capabilities → Handle common planning and workflow needs within the platform, which can reduce the need for a large plugin collection.
-
Deployment restrictions → Four deployment options → Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment according to your security and infrastructure requirements.
-
Concerns about migration effort → Jira-compatible workflows → Teams evaluating a Jira alternative can work with familiar workflow concepts while adapting the platform to their own operating model.
-
Separate project and knowledge work → ONES Wiki integration → Connect project coordination with a knowledge base approach through ONES Wiki, which is sold separately as a Confluence alternative.
Application Scenarios
Engineering and construction coordination: A planning team can use Primavera P6 for detailed scheduling while using ONES Project to manage action items, approvals, issue ownership, and recurring coordination work.
Software delivery: A development team can organize sprint work, automate workflow changes, and track reporting needs through customized project structures.
Restricted environments: An organization with strict infrastructure rules can evaluate the Air-gapped or On-Premise deployment options. ONES.com provides full feature parity between its cloud and self-hosted versions.
ONES.com offers a free plan for up to 30 seats. Project teams can evaluate the platform at a smaller scale before deciding how it fits into their wider planning workflow.
Common Challenges and Practical Solutions
The chart looks crowded
Problem: Too many columns, labels, bars, and colors compete for attention.
Solution: Remove fields that do not support the current meeting. Use a shorter timescale, fewer labels, and one consistent color system.
The baseline is difficult to see
Problem: Current bars cover the baseline, making variance hard to recognize.
Solution: Use a thin baseline bar or contrasting pattern. Place baseline dates in the activity columns when the review requires exact comparison.
Critical activities do not stand out
Problem: Critical work uses the same appearance as ordinary work.
Solution: Apply a distinct bar style and include total float or critical status as a column. Check that the legend explains the visual difference.
Different teams interpret colors differently
Problem: A color has one meaning for the scheduler and another meaning for the field team.
Solution: Define a shared legend and keep meanings stable. Use labels or patterns when color alone could create confusion.
Short-term reviews include too much long-term work
Problem: The meeting spends time scanning activities outside the immediate planning window.
Solution: Apply a look-ahead filter and retain only the context needed to understand dependencies, milestones, and blockers.
FAQs
Can I change a P6 Gantt chart without changing the schedule?
Yes. Layout settings such as columns, timescale, bar styles, labels, grouping, sorting, and filters change how the schedule appears. They do not automatically change activity dates, relationships, durations, or logic. Still, review your settings carefully before saving a shared layout, because a filter can hide activities that other people expect to see.
What colors should I use for a Primavera P6 Gantt chart?
Use a small, consistent color system. For example, blue can represent planned work, green can represent completed work, red can highlight critical activities, and gray can show the baseline. Choose colors that remain readable when printed. Add patterns, symbols, or labels because color alone may not work for every viewer.
How do I show the baseline in Primavera P6?
Open the bar or Gantt chart settings and enable a baseline bar style. Select the relevant baseline, then assign it a thin line, muted color, or different pattern. Add baseline start or finish columns when the review requires exact dates. The current schedule and baseline should look different enough to reveal movement quickly.
Why are my activity labels overlapping?
Labels overlap when the chart contains long names, a narrow timeline, small row heights, or several label types. Try shortening activity names, removing secondary labels, increasing row height, or widening the chart area. You can also change the timescale so bars have more space. Test the result at the final presentation or print size.
Should I use one P6 layout for every meeting?
A separate layout usually works better for each meeting purpose. A management review may need summaries and milestones, while a field meeting may need daily dates, responsible teams, and near-term activities. Save layouts with clear names and preserve a standard version. This approach reduces repeated formatting work and helps each audience focus on the right details.
Conclusion
A useful Primavera P6 Gantt chart begins with a clear purpose. Choose the columns, timescale, bar styles, labels, grouping, and filters that support the decision in front of you.
Start with the seven steps: open the activity view, refine columns, adjust the timescale, customize bars, add selective labels, group activities, and save a focused layout.
But here's the truth: formatting cannot fix unclear activity names, weak logic, or outdated progress information. Pair a readable chart with disciplined schedule maintenance and clear review habits.
When your wider project workflow needs task management, reporting, automation, custom workflows, or controlled deployment, ONES.com can extend coordination beyond the Gantt chart. The result is a clearer path from schedule review to accountable project delivery.