Use comments for the explanation behind the plan, and history to investigate recorded changes. Both are more useful when you first select the correct activity in the correct schedule.

Add a comment

1. Open a schedule in a team workspace and select the activity.
2. Choose Comments in the toolbar.
3. Read the existing discussion and confirm the activity shown in the panel.
4. Write the relevant information and send the comment.

Adding comments requires the appropriate project access, normally Editor or Admin. A read-only schedule share does not by itself grant commenting rights. Comments are unavailable in personal workspaces.

Write enough context for someone reviewing the activity later. “Delivery moved to 14 October; supplier confirmed today” is more useful than “Delayed.” Distinguish a reported fact from a proposed date or action.

A comment does not change the activity’s dates, remaining duration, or completed status. Make the corresponding schedule edit or progress entry when the data itself needs to change.

Use comments during progress collection

Record the reason for a pushed start, a revised forecast, or a disputed actual date in the activity’s discussion. The progress fields still need to be completed; writing a comment alone does not address a Required update.

Comments give the manager context when reviewing collected progress. Follow your team’s communication process for urgent decisions rather than assuming a comment alone constitutes approval or notification.

Open activity History

Select an activity and choose History. Review the recorded field changes and their schedule context. Use the available scope controls:

• This file for changes in the selected schedule.
• Tagged files for the project’s reporting files.
• All files for the broader available history.

Load more entries when you need earlier records. Check which files are included before concluding that a field never changed.

History is an investigation tool, not an Undo control or a complete copy of every source application’s audit trail. An imported file’s prior editing history is not recreated simply because the resulting activity data was imported.

Explain a changed date

Start with the activity’s History, then compare the relevant schedule issues. Check whether the date moved because of an edited duration, relationship, calendar, constraint, actual date, or recalculation. A recorded date change can be the result of another activity’s logic change.

Use Driving Path for the current cause and Compare schedules for the differences between issued plans. Add a comment to preserve the explanation after reviewing it.

Export a review with its comments

Choose Export → Excel with comments when the recipient needs the activity data and discussion context in a workbook. Check the generated file and the intended audience before distributing it.

For repeatable review classifications, use a custom column alongside comments: a short status such as “Needs response” can be filtered, while the comment holds the explanation.