How to share a Gantt chart with clients
Send clients a view-only link to the live plan as the main copy, a PDF when they need something to file or forward, and walk them through it once on a call. Show phases, milestones and the tasks they own; keep internal detail out; and when dates move, tell them what changed and why before they notice.
By the NeoGantt team · Updated
Link, PDF, screen-share or slide: which to use when
Most client projects use all four at different points. Trouble starts when one of them is made to do every job.
| Format | Use it for | Watch out for |
|---|---|---|
| Live view-only link | The standing copy of the plan. Bookmark-able, always current. | Viewers needing an account, or seeing internal detail. Check both before you send. |
| Proposals, contracts, board packs, anything that gets filed, printed or forwarded to people you’ve never met. | It’s a snapshot. Put the date on it, and the link to the live plan if you can. | |
| Screen-share | The first walkthrough, and any conversation about a change. | Nothing remains after the call. Follow up with the link. |
| Slide or screenshot | A single moment in a presentation, such as the pitch or a steering meeting. | Out of date by next week, and it will still be circulating. Keep it to the phase level. |
If you only pick one, pick the live link. A client who can check the plan whenever they like asks fewer “where are we?” questions, and nobody works from last month’s attachment.
What to show a client, and what to keep internal
Clients want three things from the chart: when things happen, what they need to do, and when they’re being asked to approve something. Your internal task breakdown answers none of those, and it tends to start conversations you don’t want to spend a meeting on.
| Show | Keep internal |
|---|---|
| Phases and the main tasks in each | Sub-tasks like “set up staging server” or “internal design crit” |
| Every task the client owns: feedback rounds, content, access, sign-offs | Individual team members’ names and workloads |
| Approval milestones and the launch date | Hours, rates, budget burn |
| Public holidays and shutdowns that affect the dates | Contingency you’ve built in (let it absorb small slips) |
| Progress, once work has started | Notes about the client |
A good test: could you walk the client through every row in under five minutes? If not, the chart is too detailed for them. Twenty to forty rows is typical for a two- or three-month project. Keep the detailed task list in whatever your team uses day to day, and let the Gantt chart be the plan both sides agree on.
Make the client’s own tasks impossible to miss
Most client projects slip in the handoffs: feedback that takes two weeks instead of three days, content that arrives after the build has started, a login nobody sent. Put those on the chart as tasks with dates, and mark them as the client’s.
- Give feedback a bar, not a note. “Client feedback: 3 working days” on the chart is an agreement. “We’ll need your feedback” in an email is a hope.
- Mark ownership visibly. A different colour, a label, or the client’s logo on the bar. The client should be able to find their tasks without reading every row.
- Make approvals milestones. “Design approved” as a diamond on a date makes it clear what’s being signed off and when. Our guide to Gantt chart milestones has examples by project type.
- Say what happens if they’re late. In the kickoff, not on the chart: “if feedback takes longer than three days, launch moves by the same amount.”
Walk them through it once
Don’t let the first time a client sees the plan be an email. Share your screen at kickoff, spend five minutes on it, and point out three things: the launch date, the approval milestones, and their own tasks. Then send the link straight after the call.
Not everyone reads Gantt charts easily, and people rarely say so. How to read a Gantt chart is written for that client, and you’re welcome to send it with your link.
When dates change, tell them before they notice
Plans change. What damages trust is a client discovering it themselves by spotting a bar that moved. Handle changes the same way every time:
- Save the plan as it was before you change it, with a name you’ll recognise later (“v2: signed-off scope”).
- Make the change in the one live plan, not in a copy.
- Write down what moved and why, in a sentence or two the client could forward to their boss.
- Send a short note with the link, before the next meeting.
Quick timeline update: the content deadline moved from 14 to 21 November because the product photos are delayed. Development starts a week later as a result, and launch moves from 5 to 12 December. Nothing else changes. The live plan is at the usual link.
The note says what changed, why, and what didn’t change. That last line does the most work, because clients tend to assume everything has moved. Named versions also settle the later argument about what was agreed, since you can open the kickoff version and look. The full routine, including checking the knock-on work and keeping the agreed version, is in how to handle changes to a project timeline.
Make it look like it came from you
A client-facing plan is part of your service. Put your logo on it rather than the tool’s, use your own colours for phases, and give the chart the project’s name, not “Copy of template (3)”. For PDFs, check the chart fits one readable page. A plan split across four pages with a bar cut in half makes the project look less organised than it is.
Keep one source of truth
The worst version of client sharing is three copies of the plan: the one in the proposal, the one on the slide, and the one you keep up to date. Pick one live plan, share its link, and treat every PDF and screenshot as a dated snapshot of it. When someone forwards an old PDF, the link printed on it takes them to the current version.
Most Gantt tools and project management suites offer read-only sharing of some kind, and a Google Sheet can be shared view-only too. Before choosing one, check whether viewers need an account, whether they’ll see internal tasks or other projects, and whether your branding or the tool’s appears on what they see.
For the detail on each piece, see PDF export and version history. If you run client projects for a living, NeoGantt for agencies covers the whole workflow, and the client onboarding template is a good first chart to share.