Publish and Update a Client Schedule

Before you start

• A project with phases, calendar work, or sold scope to draw from

Why it is a separate draft

• Your internal schedule is a working tool and moves constantly.
• The client schedule is a deliberate, simplified statement you control.
• Nothing internal reaches the client on its own — only publishing changes what they see.

Building the draft

1. Open the project and go to the Schedule tab.
2. Set up the client schedule if the project has not used one yet.
3. Add project phases, chosen calendar events, or sold-scope items — SiteView copies the label and dates and never edits the original.
4. Reword titles and descriptions into plain client language, and set each item's status.
5. Untick anything that should stay private for now.

Choosing how much detail to show

• Layout: timeline, plain list, or grouped by month.
• Content: phases only, item detail, or both.
• How far ahead the client can see: two weeks, four weeks, eight weeks, or everything.
• Date precision: exact days, week of, month, or milestone only — useful when you do not want to commit to a day.
• An optional Completed section so the client can see what is already finished.

Previewing before it goes out

1. Use Preview as Client on the Schedule tab to render the client view from the current draft.
2. Compare it against the version that is published today — the header line tells you whether one is live and when it went out.
3. Open the project portal preview to see the same schedule in place on the client page.

Drift: when internal dates move

• Moving an internal phase, calendar event, or approved scope line never changes a published version.
• SiteView flags the affected draft rows instead, so you can see exactly what has moved since you last published.
• Refresh a flagged row from its source to pull the new dates into the draft, then publish again when you are ready.
• Until you publish, your client keeps seeing the dates from the last published version.

Publishing and republishing

• Publishing takes a fixed snapshot of the ticked items and makes it the live version.
• Later internal changes never alter a published version, so the client is not watching dates shift.
• Republishing adds a new version; earlier versions are kept exactly as they were shown.
• Publishing sends no email or text; share or re-share the portal link yourself.
• Every published version is kept, so you can always tell what the client was shown and when.

Hiding it again

• Turning off portal visibility removes the schedule from the client page and deletes nothing.
• Removing a draft item never touches the internal phase, task, or calendar event it came from.

Troubleshooting

Related guides

• Client Links, the Portal, and What Clients Can See
• How to Use Project Costing
• How to Create, Send, and Approve Estimates