The Progress Update module collects the team’s activity progress, applies it to a schedule, and supports review before publication. It is available on Premium projects in team workspaces.

Project Editors can contribute updates. Project Admins can initiate and manage the cycle. Premium status does not replace the need for the appropriate role.

The update cycle

Stage	What happens
Collecting	Contributors record progress against the selected source schedule
Editing	A manager applies the collected changes and reviews the resulting schedule; contributors can no longer submit new updates
Completed	The manager publishes the cycle, optionally making its resulting schedule current

1. Initiate collection

Open the project’s Progress page and initiate an update. The wizard asks you to select:

• Source Schedule: the schedule on which the team will collect progress.
• Status Date (From): the source schedule’s reporting date.
• Updates Through: the cutoff for progress being reported.
• Due Date: when contributors should submit their updates.
• Update Tag: a recognizable label for the cycle.
• Completion Threshold and Due Date Reminder: settings used for reminder notifications.

Review the settings and initiate the cycle. The reporting cutoff and the submission deadline serve different purposes: a team might report progress through Friday while submitting it on Monday.

2. Collect activity progress

Contributors open the active cycle and review the activities in the update window. Use the assignee and update filters to focus on the relevant work, then record its status, dates, and physical percent as appropriate.

Review the completion indicator and any outstanding activities before using Submit. An update window showing 100% updated means its activities have been addressed for reporting; it does not mean the construction work is 100% complete.

Physical percent is separate from completion status. Setting an active activity’s physical percent to 100 does not automatically complete it. Record actual completion explicitly when the work is finished.

3. Move to editing

A Project Admin chooses Move to editing to apply the collected updates. The dialog offers:

• A new copy of this schedule: the recommended default, preserving the original collection schedule.
• An existing schedule: applies the changes to another selected schedule in the project. The collection schedule itself cannot be selected as the in-place target.

Activities without updates carry forward unchanged. Check the dialog’s count of activities with no update before continuing.

Choose how to handle the status date:

• Move schedule status date and recalculate moves the reporting date to the cutoff and recalculates remaining work.
• Keep the current status date applies the collected changes without moving that date or triggering recalculation through this action.

During editing, contributors cannot submit new updates. A manager can return the cycle to collecting when more input is needed.

4. Review and publish

Review the applied schedule’s actual dates, remaining work, milestones, and calculated results. Then choose Publish update.

The Set as current schedule option makes the resulting schedule the project’s current schedule and removes that designation from the previous current schedule. Publishing marks the cycle completed, ending collection for that cycle.

Publishing is distinct from applying progress and recalculating. Finish the schedule review before marking the cycle complete.

Troubleshoot access

If the module says Premium project required, ask a Workspace Owner or Admin to allocate a Premium slot. If you can contribute but cannot initiate or publish, check your Project Admin access. If entry is unavailable during an existing cycle, check whether it has moved to editing, been locked, or been completed.

See Premium projects and Roles and access.