The Progress page manages a reporting cycle from collection to completion. Use it when several people need to report work against a common cutoff and a manager needs to review the result before issue.

Progress cycles require a Premium project in a team workspace. Project Editors can contribute. Project Admins initiate, apply, return, cancel, and complete cycles. See Premium projects and Roles and access.

If you are only supplying dates for your work, start with Submit a progress update.

Understand the three stages

Applying progress, calculating the schedule, and completing the cycle are distinct actions. A collection that is 100% addressed is not a project that is 100% built.

1. Prepare the source schedule

Choose the working schedule that represents the starting plan. Check its status date, activity assignments, calendars, and important actual dates. Preserve a version if you need an explicit pre-update reference.

Use an eligible working schedule. Child versions must be copied or moved out of their parent before starting a progress cycle. Resolve any file-state or permissions message before initiating collection. The project needs a plan the contributors can recognize, with useful activity names and IDs.

2. Initiate collection

Open the project’s Progress page and start an update. Review the wizard’s settings:

A team might report through Friday night and submit by Monday morning. The due date is not the same as the reporting cutoff.

Review the setup and initiate the cycle. During collection, Update Options provides the settings that can be changed, including whether to Show % Complete. Check the effect of changing a cutoff after people have already entered dates.

3. Monitor collection

Use the collection sheet’s Assign column to review responsibility, and use the assignee controls, My Tasks, and Remaining filters to see what still needs attention. Confirm that unassigned work has an owner or an agreed reporting approach.

Contributors enter update start/finish dates, use Push where appropriate, and provide physical percent when enabled. Review the contributor guide for how dates determine reported status.

The completion indicator measures addressed reporting tasks. A forecast date or a pushed task can satisfy reporting without saying that the underlying construction is complete. Read comments on unusual movement and confirm actual dates before applying them.

The Submit dialog identifies remaining work across the update, including other assignees and unassigned tasks. A contributor can have no personal tasks remaining while the cycle still has outstanding entries.

4. Move to editing and apply updates

Choose Move to Editing. The Apply updates dialog applies collected progress to this working schedule and captures a collection snapshot before the transition. It does not ask you to choose another schedule as the target.

Review the number of activities with no update. Those activities carry forward unchanged. A manager can continue with incomplete collection, but should do so knowingly; missing input is not evidence that the planned work happened.

The dialog has two independent choices:

• Move status date to the collection cutoff.
• Recalculate schedule after applying the progress.

Both are selected by default. You may apply progress without recalculating, or choose the date movement separately. Make the choice that matches the review process; without recalculation, do not assume the forecast fully reflects the newly applied inputs.

Choose Apply updates. The cycle enters Editing and contributors can no longer add collection input.

5. Review the working schedule

Check actual start/finish dates, activity status, remaining duration, physical percent, milestones, constraints, and logic. Calculate when required and inspect the changed forecast, Quality results, and driving paths.

Compare with the prior issued schedule or your preserved pre-update version. Resolve missing or inconsistent input before completing the cycle. A high reporting-completion percentage does not guarantee the dates are correct.

Return to collection when more input is needed

Return to Collection restores the collection snapshot. It undoes applied progress and subsequent editing changes, while keeping comments and submitted update inputs.

This is not just a switch that reopens the input fields while preserving every edit made during Editing. Preserve a separate version or copy of any editing work you need to keep before returning. Then let the team correct the collection and apply it again when ready.

6. Complete the reviewed update

Choose Complete and review the dialog:

1. Give the saved version a clear Name and ID.
2. Decide whether to mark this version as Current.
3. Decide whether to assign the next Update #.
4. Choose Complete update.

Completing the cycle saves a child version. Its schedule logic is read-only while it remains a version; copy it or move it out of its parent to edit. The parent schedule stays editable. The Current and Update choices are optional and can be changed later in Files.

If you mark the saved version Current, project navigation opens that issued version. Return to the editable parent when preparing future changes. Use a copy if you need to develop an alternative from the saved result.

After completing the cycle, check Files and the dashboard to confirm the intended version, tag order, and reporting dates. Share the preserved issue when a fixed record is required.

Cancel an update

Cancel Update discards the cycle’s submitted progress inputs and cannot be undone. It is different from closing the options dialog with Cancel, and different from returning to collection.

Use it only when the cycle itself should be abandoned. Read the confirmation and preserve any information the team still needs before continuing.

Resolve common blockers

If Progress requires Premium, ask a Workspace Owner or Admin about allocating a slot. If you can contribute but cannot move to editing or complete the cycle, check Project Admin access. If entry is unavailable, inspect the cycle stage and source file state.

For date entry and “Required” rows, use Submit a progress update. For a surprising forecast after applying, use Calculate a schedule.