Conditional Formatting in Microsoft Project: What Works

Microsoft Project desktop does not have Excel’s familiar Conditional Formatting command, but you can still make tasks stand out as their data changes. Use custom fields and graphical indicators for rule-based flags, and use bar styles or text styles to control how tasks appear in a Gantt Chart.

What conditional formatting means in Project

Project is a scheduling application, not a spreadsheet. Its task table may look like a grid, but it does not offer Excel features such as color scales, data bars, or a general rule that fills any cell red when its value is below a threshold. The formatting tools are designed around project concepts: tasks, milestones, critical work, summary tasks, progress, and Gantt bars.

The closest equivalent depends on what you want to emphasize. A graphical indicator can show a symbol beside a task field when a condition is met. A bar style can change the appearance of a task’s Gantt bar. Text Styles can change the font or color for built-in categories such as milestones or critical tasks. These are different tools, and none is a universal cell-formatting rule.

For example, to flag tasks with less than 25 percent progress, you could use a custom field and a graphical indicator. To make critical tasks easier to see on the timeline, use a bar style or the built-in critical-task display. To distinguish milestones in the task list, adjust the milestone text style.

Choose the right Project formatting tool

Before changing a view, decide whether the signal belongs in the task table, on the timeline, or in both. That choice helps avoid building a complicated workaround when a built-in view option already does the job.

Use a custom field and graphical indicator when a rule should evaluate task data, such as progress, duration, deadline, or a manually assigned category.
Use a bar style when the key information is how a task or category appears in the Gantt Chart, including its bar color, shape, or label.
Use Text Styles when you want to change the appearance of a built-in task category, such as critical tasks, milestones, or summary tasks.
Use a filter or group when the goal is to isolate or organize matching tasks rather than change their appearance.

A filter answers “which tasks should I see?” Formatting answers “how should these tasks look?” A filter can be useful alongside a visual rule, but it does not itself recolor cells. Similarly, sorting tasks to the top is not conditional formatting; it changes their order, not their visual treatment.

Flag tasks with a custom field

For a rule that depends on a value you define, start with a spare custom field. In Project desktop, open the Project tab and choose Custom Fields. Select whether the field applies to tasks or resources, then choose an available field of a suitable type. For instance, use a flag field for a simple yes-or-no result, or a text field for labels such as Watch, At risk, and On track.

Choose a field you are not already using, then use Rename to give it a clear name, such as Review Flag.
Choose Formula if the result should be calculated from other task fields, or enter values manually if a project manager will assign the category.
Use Graphical Indicators to set the conditions and select an icon for each result.
In the task table, insert the custom field as a column so the result is visible. You can also inspect the Indicators field where applicable.

A formula-based field can update as its source values change, which makes it more useful than manually coloring individual tasks. A manual category can still be appropriate when the judgment is qualitative—for example, when a project lead assigns a risk level after considering information that is not recorded in the schedule. In that case, document what each label means so different people apply it consistently.

Custom fields are project data, not just decoration. If a field is used for a formula, indicator, report, or later export, give it a stable name and avoid repurposing it halfway through a project. A field that looks unused may already be referenced in a view or calculation.

Set up graphical indicators

Graphical Indicators turn field values into icons according to conditions you define. Depending on the field type, conditions can compare values or test categories. A flag field might show a check mark for tasks requiring review; a number field could use different icons for ranges of remaining work. The exact choices depend on the selected field and the installed Project version.

In the Custom Fields dialog, select the relevant field and open Graphical Indicators. Define the conditions from the most specific cases to the general ones, choose an icon for each result, and confirm how the rules should apply to summary rows if that option is available. Then show the field in a task table and check that the displayed icons make sense for real tasks.

For example, a project team could assign a manually maintained text field called Health with values Green, Amber, and Red, then map those values to distinct symbols. This is useful when health is a management judgment rather than a number Project can calculate. If it is possible to define an objective rule—for example, a date comparison or progress threshold—a formula-based field is usually more consistent than asking each person to choose a color by hand.

Indicators are compact signals, not explanations. A red symbol does not tell a reader whether the cause is a missed deadline, a dependency, or a resource shortage. Include a meaningful field value, note, or project status explanation so the icon does not become a mysterious warning.

Change Gantt bar appearance

If you want to highlight work on the timeline, use bar styles rather than trying to recolor a task-table cell. In a Gantt Chart view, open the Format tab and choose Bar Styles. The dialog controls the appearance of different bar types and the conditions under which those styles are used. Available settings include visual properties such as the bar shape, pattern, and color, with fields for where a bar begins and ends and how it is labeled.

Project already distinguishes common schedule elements, including summary tasks, milestones, and critical tasks. You can adjust a relevant style or create a separate style for a useful task category. Review the Show For… Tasks criteria carefully: the style needs to apply to the intended tasks, and styles that overlap can affect which bar is most noticeable. Make a small change first, then inspect the chart at a useful timescale.

Bar styling is especially useful when the task list is crowded but the schedule pattern matters. For example, a team may want a different color for a special workstream so its timing is visible among other bars. However, a chart color does not replace the task’s underlying status or change its dates. It is a visual cue, not a scheduling calculation.

Format task text and built-in categories

To change the font, size, or color for a built-in category, use Format > Text Styles while working in a suitable view, such as Gantt Chart. In the Text Styles dialog, choose an item to change—such as critical tasks, milestones, or summary tasks—and set the appearance. The formatting applies to that category in the view; it is not a rule that can be freely written for every custom field value.

This distinction matters when someone expects to say, “make every task with Health equal to Red have red text.” Text Styles is aimed at predefined task types, not arbitrary conditional cell formatting. For a custom value, use a graphical indicator, or consider whether a bar-style rule can communicate the distinction more clearly in the chart.

Also distinguish task text formatting from cell shading. A table view can display fields and indicators, but Project does not provide Excel’s full collection of conditional cell-fill options. If a highly customized color-coded table is essential, exporting or copying schedule data to Excel may help with presentation, but that creates a second representation that needs to be kept in sync with the schedule.

A practical example: show overdue work

Suppose a coordinator wants to spot incomplete tasks whose finish dates have passed. First confirm that the schedule’s status date and task dates are maintained correctly; otherwise, an overdue signal may be misleading. Decide whether Project can evaluate the rule using the fields available in the chosen custom-field formula, or whether the team needs to assign an overdue category manually. Then configure a custom field and indicator, add the field to the task table, and compare the results with several known tasks.

Check at least three cases: a completed task with a past finish date, an incomplete task with a future finish date, and an incomplete task with a past finish date. The first two should not be confused with the genuinely overdue case. Also consider summary tasks: their dates and progress summarize subordinate work, so a summary-level warning may be useful but can duplicate warnings on individual tasks.

Finally, decide how often the schedule is updated and who owns the status date, progress, and exception fields. A rule is only as reliable as its inputs. If task progress is stale, a polished icon can create false confidence rather than improve project control.

Common problems and limitations

The rule does not update: Check that the field is formula-based if it should calculate automatically, and confirm that the formula refers to the intended task fields. A manually entered category will not change by itself.
The icon is missing: Confirm that the custom field column is visible, that the condition matches the stored value, and that the selected field type supports the condition you configured.
The wrong tasks are colored: Review the bar-style criteria and any overlapping styles. Also check whether the view contains summary tasks or other categories that have their own styles.
The schedule looks different for a colleague: Views, tables, custom fields, and formatting may not be presented identically in every Project environment. Share the project file and explain which view or field is intended to be used.

Project’s formatting is also less flexible than Excel’s for decorative dashboards. A color scale across a numerical range, conditional fill based on a neighboring cell, or a large icon set may require a different reporting tool. Do not use color as the only way to convey urgency; use a label or symbol as well, and choose colors with enough contrast to remain readable.

Desktop Project, Planner, and Excel

These instructions refer to Project desktop for Windows, where the ribbon includes the Project and Format tabs described above. The exact ribbon layout can vary between releases and views. Microsoft’s former Project for the web experience has transitioned into Planner, so browser-based users should not assume that the desktop dialogs or commands are available there; use the options provided in their current Planner plan experience.

Excel is a reasonable alternative when the main task is to create a color-coded table or dashboard from exported schedule data. Its Conditional Formatting tools are designed for cell-based rules. But an export is not the live schedule: changes made in Excel do not automatically update the original Project plan, and schedule behavior such as dependencies and resource assignments is not preserved as a functioning Project model in a simple table. Keep the source of truth clear, and refresh any exported report after the schedule changes.

Frequently Asked Questions

Does Microsoft Project have conditional formatting?
Not in the same general-purpose form as Excel. Project desktop offers related tools—custom fields with graphical indicators, Gantt bar styles, and Text Styles—but each serves a more specific purpose.

Can I make a task row turn red when it is overdue?
You can create a custom field and graphical indicator to flag an overdue condition, provided the needed schedule data and rule are available. Project does not provide a universal Excel-style rule to fill the entire task row red based on any field.

Can I color Gantt bars based on task status?
Bar Styles can format bars for task categories and defined criteria. Configure the relevant style in a Gantt Chart view, then verify the criteria and result on actual tasks; overlapping styles can make the outcome less obvious.

Can I use conditional formatting for a custom field?
Use Graphical Indicators on a custom field to associate conditions with symbols. This is the closest built-in option for visually flagging custom values, but it does not provide all of Excel’s cell-fill and color-scale features.

Will the formatting appear in Excel or Planner?
Do not expect Project desktop formatting to transfer as an equivalent live rule. An Excel export may contain schedule data but needs its own formatting rules, while Planner has a different interface and feature set.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.