Submit a progress update
Use this guide when a project manager asks you to update your activities. You need Editor or Admin access to the Premium team project, and its cycle must still be Collecting.
You are reporting what happened through the stated cutoff and what remains. You are not expected to recreate the schedule or publish the project update yourself.
Open the active update
Open the project’s Progress page, or use an update/to-do entry from Home or workspace Updates. Check the project, source schedule, Updates Through cutoff, and Due Date.
Use My Tasks or the assignee filter to find your work. Use Remaining to focus on entries that still need an update. A filter changes what you see; it does not remove your responsibility for other assigned activities.
If the activity list is unexpectedly empty, clear filters, check assignments, and confirm the cycle is still collecting.
Understand the update fields
The collection sheet shows the existing schedule alongside the update inputs. Enter the dates you intend to report; do not assume that a displayed fallback/planned date has already been confirmed as an actual.
| Field or action | What to enter or check |
|---|---|
| Update Start | Actual start for work begun by the cutoff, or a forecast start beyond it |
| Update Finish | Actual finish for completed work, or forecast finish for work remaining |
| Update status / Required | Whether the date/status inputs have adequately addressed the activity |
| % Complete, when shown | Manual physical progress for work underway |
| Push | Report that the activity has not started for this update |
Start cannot be after finish. Milestones use their relevant start-side or finish-side date. Date entry uses the activity calendar’s start/end working-hour boundaries, so the cutoff’s time can matter as well as its day.
Report completed work
Enter the actual start and actual finish that occurred on or before Updates Through. Check the resulting completed status and physical percent.
Entering a finish can fill or infer a start if one has not been entered. Review that start and correct it to the actual date rather than assuming the suggested value is historical fact.
Do not enter a planned finish before the cutoff unless the work actually finished. A finish at or before the cutoff can mark the activity completed.
Report work still in progress
Enter or confirm the actual start, then enter a realistic forecast finish after the cutoff. Check that the activity is treated as started/in progress.
Where available, the finish-date picker offers:
- Push End: projects remaining duration from Updates Through for work that began by the starting data date.
- Reforecast: projects a finish from the entered start date using the activity’s duration/calendar information.
These are date suggestions. Use them when their assumption matches the work; otherwise enter the forecast you can support. They do not prove the current remaining-duration estimate is correct.
If physical percent is enabled, enter your assessment separately. Physical percent does not determine the remaining duration. Setting it to 100 does not substitute for reporting actual completion.
Report work that did not happen
For an activity that did not start by the cutoff, use Push when offered, or enter a forecast start beyond the cutoff with the appropriate forecast information. Push marks the update as not started; it does not record an actual start or a completed task.
Add a comment explaining the reason and any known next step. “Awaiting access; expected start next Wednesday” is more useful than an unexplained pushed date.
For work that already started but did not finish, keep the actual start and report a future finish. Do not use a not-started response to describe unfinished work that is already underway.
Review Required rows
A row may remain Required when you have entered only part of the necessary information. For example, entering a start without the relevant finish or status can leave the task awaiting a response.
Check the date pair, activity type, and cutoff. Do not mark a task complete merely to clear the Required indicator. If the correct information is unknown, ask the project manager and explain the uncertainty in a comment.
Some prior actual information can be carried into the sheet. Still review it: a date shown in the collection is not a reason to skip a known correction.
Submit and check remaining work
Commit your entries and resolve any save error, then choose Submit. The dialog shows the addressed count and outstanding activities.
If it says This update can’t be submitted yet, use the link to your remaining tasks or view the other outstanding and unassigned work. Your personal list can be complete while the whole update still has gaps; contact the manager about work outside your responsibility instead of inventing values for it.
When the required reporting is complete, the dialog allows submission and confirms that the update window has been addressed. 100% updated means the reporting tasks have responses, not that construction is 100% complete.
Your committed inputs are part of the collection. Submit does not calculate the project’s final forecast or publish a schedule; the manager reviews and applies the cycle separately.
Correct an entry
While the cycle is collecting and the field remains editable, correct the input and review any resulting status changes. Clearing a start can clear related finish/status input, so recheck the entire row afterward.
If collection is closed because the manager moved to Editing or completed the cycle, contact the manager. Returning to collection has consequences for applied schedule edits; contributors should not work around the closed cycle by changing a different schedule.
For the manager’s next steps, see Run a progress update.