The update process

The schedule is only as good as what the site tells you. Here is how to ask in one email and get dates back.

Updates: the people, the owners, the request, the status, the answers, the history. Updaters are the people you may ask. Ten come with the add-on; ten more cost five a month.

An updater is an email and a name. No PC.o account: a link, not a login. Select the activities, then Assign owners. Owners receive the update requests for their activities.

The Owner column shows who answers for what. A backup owner can stand in. Send update request: a data date, a due date, a window of dates, and who is in it.

Preview the email: the activities, the due date, one button. Each link is personal and closes on submit. Send. Update one is out, and the flash says so.

Update status says who has opened and who has answered, with a reminder a click away. This is Jordan's page: the activities, their bars, and Start and Finish boxes to fill in. No account.

Actual or estimated, a note if it helps, submit. Submitting closes the link. A dialog asks once more: submitting closes the link, and the answers cannot change.

Done on their side: thanks, the updates are with the owner, and the link is closed. Back with you: submitted, with the time.

Review updates shows each answer and its effect before anything changes. Accept, reject, or edit. Apply accepted, and the schedule reschedules: actuals become actuals, estimates become constraints and expected finishes.

Applied two responses, and the cycle closes. Mobilise is complete with its actual dates; Excavate starts on the estimate. Nothing moved until you said so.

Cycle history keeps every round, with an Excel export of the answers. Three of ten used. A pack of ten more is five dollars a month, from the plan page.

That was the update process. Next in the Guide: updating progress yourself, when you are the one on site.

Taken from the video’s English captions.