Excel for project managers on Mac: trackers, Gantt charts and status reports in 2026

Most project managers on Mac use Excel for three jobs. They keep a task tracker, draw a timeline, and write a status report for a sponsor or client. Excel handles each job well at small scale. It starts to fight you as the project grows and more people touch the file.

What project managers build in Excel on Mac

A typical tracker looks the same from project to project. Teamwork's guide to Excel project management lists task name, owner, start date, due date, status, priority, estimated hours, actual hours and notes. Start with that list. Add a column only when a real decision needs it.

The rest of this page uses those columns. You will set up a table, a Gantt chart, a dependency check and a status pivot. Microsoft's Gantt support article names Microsoft 365 for Mac, Excel 2024 for Mac and Excel 2021 for Mac. Check your version under Excel > About Excel before you follow the chart steps.

Set up a task tracker that survives a week of changes

Start with an Excel Table. Select your header row and the data under it, then press ⌘ T. The table grows when you add a row. Formulas fill down on their own, and charts pick up new rows. A plain range does none of this.

Name the table as soon as you create it. Microsoft's October 2026 What's New in Excel post says naming tables at creation is now available for Excel on Mac. Pick a short name like tblTasks, so formulas stay readable months later.

Use a dropdown for Status

Select the Status column. Go to Data > Data Validation, set Allow to List, and type your options separated by commas. Everyone now uses the same spelling. A filter for Done misses a cell that says Done with a trailing space.

Flag overdue tasks with a formula and conditional formatting

Add a column named Overdue. In the first data row, enter =AND([@Due]<TODAY(),[@Status]<>"Done"). Excel fills the formula down the table. A late task that is not Done returns TRUE.

TODAY() recalculates each time the file opens, so the flag stays current. The risk is a copy someone pasted as values. That copy freezes the flag on the day of the paste, and nobody notices until a client does.

Next, highlight the late rows. Select the table, go to Home > Conditional Formatting > New Rule, then choose Use a formula to determine which cells to format. Enter =$H2=TRUE, replacing H with the letter of your Overdue column. A light red fill works well.

Blank Due cells count as zero, so they read as earlier than today. Add a blank check to the formula, such as =AND([@Due]<>"",[@Due]<TODAY(),[@Status]<>"Done"). The FAQ below covers this case.

Build a Gantt chart in Excel for Mac, step by step

Excel has no built-in Gantt chart type. Microsoft says so in its support article on Gantt charts. You build one from a stacked bar chart, then hide the start dates. The article covers Microsoft 365 for Mac, Excel 2024 for Mac and Excel 2021 for Mac.

1. Add a Duration column with =[@Due]-[@Start]+1. The plus one counts the first day, so a task due the day it starts lasts one day.
2. Select the task name, Start and Duration columns. Go to Insert > Recommended Charts, choose Stacked Bar, then confirm the chart.
3. Click the Start series, the bars that carry the start dates, and choose Shape Fill > No Fill. Only the duration bars stay visible.
4. Control-click the vertical axis, choose Format Axis, then tick Categories in reverse order. Without this step, the first task sits at the bottom.

Microsoft's support page also links free Gantt chart templates on create.microsoft.com for Microsoft 365 subscribers. Start from a template when you need color-coded categories quickly. Build your own when you need a column the template lacks, such as Predecessor.

Two problems break Gantt charts in practice. The first is text dates. A Start cell that Excel reads as text sits in the wrong place or does not show at all. Real dates align right in the cell. The second is a row typed under a plain range. Inside a table, a new row joins the chart. Outside one, it does not.

Handle dependencies without pretending Excel has a dependency engine

Excel does not know that design must finish before build starts. Teamwork says dependencies in Excel are usually text notes. A date change then means finding every affected task by hand, and reminders depend on memory. A small check column helps, though it does not solve the problem.

Give every task an ID in a Task ID column. Put the ID of the task it waits for in a Predecessor column. Then add a Check column with this formula: =IF([@Predecessor]="","",IF([@Start]<=INDEX([Due],MATCH([@Predecessor],[Task ID],0)),"Check predecessor","OK")). Rows that start too early now say so.

The test uses <=, so a start on the same day the predecessor is due gets flagged. Change the test to < if your team starts the day after a finish. Decide the rule once, and keep it in a cell note so the next person knows it.

Say design is due on a Friday and build starts that same Friday. The check flags the build row. You then decide whether the overlap is real or whether the dates need to move. Excel points at the problem, and the decision stays with you.

Build a status report with a pivot table, and check the totals

A status report is mostly counting. How many tasks are Done, In progress or Blocked, grouped by owner. A pivot table does this without extra formulas. Put Owner in Rows, Status in Columns, and Task ID in Values set to Count. Our guide to making a pivot table in Excel on Mac covers each menu.

Refresh the pivot after each change. Go to Data > Refresh All to update every pivot in the workbook. Teamwork lists stale pivots and weekend rebuilds as common pain points, so make refreshing part of your routine.

Check totals before anything leaves your Mac. A 2016 paper by Ray Panko states that large spreadsheets very likely contain at least one incorrect bottom-line value. The abstract gives no percentage, so do not quote one. Compare the pivot count with =COUNTA(tblTasks[Task ID]) instead.

A second check takes seconds. Filter the table to one owner, then compare the pivot row for that owner with what you see. Two numbers that disagree tell you something broke before a client does.

Keep one copy of the file, not five

Teamwork lists version chaos as one of Excel's main limits for project work. Shared files pile up as copies with names like Project_v3_FINAL_revised. Overwrites happen. Comments end up in cells or side threads, and there is no audit trail.

Keep one file in OneDrive or SharePoint, and have everyone open that copy. Mac users often save to Desktop out of habit. Move the file into the cloud folder before the first share, then send a link instead of an attachment.

Use the file's version history when you need an older state. A new file name is not version history. Put the date in the name if your team likes it, such as a status file dated for each Friday, but keep one live copy.

How much time project reporting really takes

Two figures circulate, and they do not match. Wellingtone's research summary says 72% of respondents spend half a day or more every month collating reports. Teamwork cites 42% for the same report, phrased as one or more days. Secondary summaries place the 42% figure in an earlier year. Quote the 72% with its exact wording.

Lucid Software's blog says the average project manager spends 13 to 16 hours a week on status reporting. It names only industry research and cites no study. Treat it as a vendor estimate, not a benchmark.

The practical lesson is simple. Time your own report from start to finish for one cycle. Write down the step that took longest, which is often formatting and pulling numbers together. Fix that step first, before you buy anything.

When Excel stops being enough

Teamwork says Excel maintenance rises steeply at roughly 30 to 50 tasks, several concurrent clients, or a larger team. That is the author's own guidance, not a survey result. Use it as a warning sign, not a rule.

Watch for three signs. You spend Friday rebuilding the report. Two people keep different versions they both call current. Inserting a row breaks something, and you cannot say what. When two or three of those show up, a dedicated project tool may save more time than Excel does.

Excel still works well for the reporting layer. Many teams keep their tracker in a dedicated tool, then export the numbers to Excel for the sponsor deck. Check your tool's export options before you rebuild anything by hand.

Where Lazur helps in Excel on Mac

Lazur is a voice assistant for the Mac. Hold ⌥ ⌘ and ask about anything on screen, and Lazur answers out loud. It listens and looks at the screen only while you hold the shortcut. It does not click buttons or edit your file for you.

Three kinds of ask fit this job. Ask where something is, and Lazur draws a circle and a label around it. Ask how to do something, and Lazur guides you one click at a time, waiting for each click. Ask for text, and Lazur drafts it for you to edit.

• Where is Recommended Charts? Lazur circles it on screen.
• Walk me through the Stacked Bar steps. Lazur waits for each click.
• Why does this cell show a number, not a date? Lazur explains the format.
• Draft the status note from these rows. You edit it before it goes out.
• Research Gantt templates. Lazur runs the search in its own Chrome tabs.

Dictation fits status notes well. Hold fn, speak, and clean formatted text lands at the cursor in any app, Excel included. Snippets and a personal dictionary help too, so project names come out spelled the way you expect.

Lazur keeps a memory of what you asked and did, and that memory stays on your Mac. It runs on macOS, on Apple silicon and Intel. Windows is planned, not available. The Pro trial lasts 3 days, needs no credit card, and starts when you first open the app.

Mistakes project managers make in Excel on Mac

• Typing dates as text. Real dates align right in the cell. Text often aligns left and breaks charts.
• Inserting rows inside a plain range. Formulas can point at the wrong cells. A table avoids most of that.
• Pasting the Overdue results as values. The flag stops updating on that day.
• Merging cells in the tracker. Sorting and filtering get messy, and merged cells cause chart trouble.
• Keeping five copies of the file. Teamwork ties overwrites and lost comments to this habit.
• Trusting one total. Check counts with a second formula before you send anything.

Most of these mistakes come from a plain range that grew past its first draft. Convert it to a table early, and most of them go away.

A weekly routine that takes less time

1. Update Status and Actual hours on the same day each week, before the status meeting.
2. Refresh the pivot with Data > Refresh All before you read it.
3. Check the Overdue flag and the Check predecessor column.
4. Copy the pivot counts into the status note. Dictate the risks with fn.
5. Save to the shared folder, then send the link, not an attachment.

Set the weekly update as a reminder. Ask Lazur to add it to Apple Reminders by voice, so the update does not depend on memory. The routine then runs without you deciding each Friday.

Start with one live project this week

Pick one project that is live today. Build the tracker, add the Overdue flag, and draw one Gantt chart. Note how long the report takes. Then run next week's report the new way and compare. If the new way saves real time, build the next project the same way.

You can download Lazur for Mac and start the 3-day Pro trial, or read pricing first. The Excel page shows more of what Lazur does inside the app. Lazur works in any app on screen, so Excel is one place it helps, not the only one.