Publish the plan crews see

By the end of this workflow your crews see the plan you chose to give them, and your own edits in progress stay out of their view until you publish again.

Who does this#

A planner with master planning: every company Admin, and anyone else a company Admin has given it (a Field-only account can't have it). Without it, you can still edit a project that is in Draft; your changes wait for someone with master planning to publish them. See Who can see and do what.

Before you start#

• Every project starts Live: crews see each save the moment it lands. You only need this workflow when you want to check changes before crews see them.
• The project is open in the editor, and your last change has saved.
• Crews see the plan through their crew links, Work, My tasks, Calendar and the Day plan (see Work, My tasks and Calendar and the Day plan). The What crews see dialog lists these views.

Steps#

Put the project into Draft#

1. 1
   Open the choice. In the editor choose Tools ▾ → What crews see…. The dialog shows Live (crews see every save as it lands) and Draft (crews see the plan you last published).
2. 2
   Switch to Draft. Choose Draft, then press Publish now and switch to Draft. Crews keep the plan as it is right now.

3. 3
   Keep working. Edit and save as usual. A second chip sits beside the save chip: ◷ Draft · published with the time, then ◷ Draft · unpublished changes once you have saved something crews don't have yet.

Publish your changes#

4. 4
   Check first. In What crews see…, See what crews see opens the published plan, read-only.
5. 5
   Publish. In the same dialog press Publish…. Publish to crews opens: Publishing replaces the plan crews are seeing with the plan you have now. Press the publish button, which says how many projects it will publish. The chip goes back to the time of this publish.
6. 6
   If someone else saved meanwhile. When a teammate saved the project after you last loaded it, nothing is published and the dialog names who saved and when. Press Include it anyway to publish the project with their change, or Cancel to leave it.

Publish several projects at once#

7. 7
   Open the master plan, tick the projects to publish and press Publish…. Every ticked project publishes together, or none do. A line in the dialog counts the scheduling conflicts in what you are publishing, such as a person booked on two projects the same day. It never stops the publish. Publish… on People opens the same dialog with the Draft projects that page shows, and is grayed out while none of them has anything to publish.

Go back to Live, or throw changes away#

8. 8
   Go Live. In What crews see… choose Live and press Go Live, or Publish and go Live when you have unpublished saves. From then on crews see every save again.
9. 9
   Discard unpublished changes. Discard unpublished changes, confirmed with Restore the published plan, returns the project to the plan crews are seeing. Ganttry keeps your current plan in History first, as an automatic save, so Restore… can still bring it back. If a teammate saved after the last publish, it refuses and names them.

Good to know#

• Crew progress goes straight through. When a crew reports percent complete, work status, remaining work, a checklist tick or an attachment on a Draft project, it reaches the plan crews see at once, without waiting for a publish.
• Bookings on People wait too. A booking on People never publishes. The first one into a Draft project says so, for example Bridge 12 is a Draft — crews see it after you publish. A stay is the exception: it reaches the person's Day plan and itinerary at once, without a publish.
• Day notes. A day note you tick for crews in Day notes… reaches them with the next publish while the project is in Draft. Unticking a note hides it from crews at once.
• Where the Draft shows. A project in Draft carries a Draft pill on Projects, Home, Crew planning and Reports, and in the legend on People. A crew link reads Published with the time, where a Live project's link reads Live · updated. A lookahead printed from a Draft says DRAFT — not published to crews in its header.
• Notifications wait. Assignment and status notifications to Field accounts wait while a project is in Draft. A blocked-task notification and a published notification always go.
• Project files are always the latest; a Draft doesn't hold them back.
• Restoring a Live project. Restoring an earlier version of a Live project from History opens with Switch to Draft first picked: the project goes to Draft with today's plan published, then the restore lands, so crews keep today's plan until you publish. Its button reads Switch to Draft and restore; Restore now shows crews the restored plan at once. A project a course uses as its template or answer key can't be switched to Draft, so its confirm offers no such choice.
• The master plan needs a wide screen. At 780 pixels wide or narrower it refuses rather than squeeze three weeks of dates side by side, so publish several projects from a laptop or desktop.