May 13, 2026
How to share a project plan as a PDF (without screenshotting it)
Four ways to produce a stakeholder-ready PDF from a Microsoft Project plan, ranked by friction and how readable the result actually is.
A stakeholder asks for "the plan as a PDF." You open MS Project, hit Print, drop into Preview Mode — and the export is somehow worse than what you saw on screen. Dependency arrows missing. Task names truncated. The critical path that was red in MSP is now black-and-white. You consider screenshotting the Gantt instead.
Don't. Screenshots are the wrong tool for almost every reason someone asks for a PDF in the first place. This guide covers the four real options for producing a project-plan PDF, when each one is right, and what you can do to make whichever you pick land better.
If you're choosing between PDF and a web share link, read that guide first — the right mechanism depends on whether the artefact needs to be a snapshot or a living view.
Why screenshots break
A screenshot of the Gantt chart looks fine to you because you already know what you're looking at. It breaks for the stakeholder because:
- No dates anywhere readable. The date axis at the top is usually too compressed to read. The recipient can see "something starts around the middle" but can't tell whether that's next Tuesday or next quarter.
- No critical-path context. Without the colour-coding MSP gives you on screen — which usually doesn't survive a screenshot at low resolution — the recipient can't see which tasks actually matter.
- No status, no risks, no resource info. The image captures the timeline. It doesn't capture what's late, what's at risk, or who's overloaded.
- Stale within a week. Anything you send as an image is frozen the moment it leaves your machine. Two weeks later it's wrong, and the stakeholder doesn't know which version is current.
- Unreadable on phones. Wide Gantt screenshots become pan-and-zoom puzzles on mobile, which most stakeholders won't bother with.
A screenshot is fine for a quick Slack reply ("here's the rough shape"). It's not a substitute for a PDF, and a PDF is not always a substitute for a live view.
The four real PDF options
| Method | Setup time | Readability | Update cost | Best for |
|---|---|---|---|---|
| MS Project print-to-PDF | Low | Medium | High | Internal status, formal records |
| Excel-then-print | Medium | High (table only) | High | Auditors, finance teams |
| PowerPoint-then-print | High | High (curated) | Very high | Steering committees |
| PlanSight PDF export | Low | High | Low | Weekly stakeholder updates |
Option 1 — MS Project print-to-PDF
File → Print → Save as PDF. The most direct path. Produces a landscape Gantt that looks roughly like what's on screen, plus a task table on subsequent pages if your view includes one.
What works: it's free, it's one step, and the dependencies usually render correctly if you adjust the date scale before printing.
What doesn't: MSP's default page setup is rarely right. The Gantt frequently breaks across pages mid-month, the task table cuts off resource and notes columns, and the critical path colouring is hit-and-miss depending on your printer driver. Plan on 5–10 minutes adjusting the View → Timeline → Timescale, the page setup, and the columns before the export is presentable.
Right when the PDF is for internal status and you can iterate the page setup once and reuse it. Wrong as a weekly export — you'll re-tune it every time.
Option 2 — Excel export then print to PDF
File → Save As → Excel Workbook in MSP, then open in Excel, format the columns, and File → Print → Save as PDF.
What you get is a clean tabular view: ID, task name, start, finish, duration, % complete, resource. No Gantt. For some audiences — auditors, finance teams, anyone doing variance analysis on a per-task basis — this is what they actually want. The PDF is searchable, sortable in the source workbook, and uniformly readable.
What you lose: any visual sense of the schedule shape. There is no timeline, no critical-path highlighting, no dependency arrows. A stakeholder who needs to feel the project at a glance won't get it from a 14-page table.
Right when the PDF is going to someone who reads spreadsheets natively. Wrong when the audience needs to see the schedule.
Option 3 — PowerPoint paste then print to PDF
The premium option. Take the MSP Gantt screenshot or a cleaned-up timeline, paste it into a PowerPoint deck, add a slide with the top three risks, a slide with milestone status, and export the deck as a PDF.
This produces the most polished result by a wide margin — but it's also 30–60 minutes of manual work every time. Most PMs reach for this only when the stakeholder is a steering committee or board, where the formality pays back the effort.
Right when the PDF is itself the deliverable — a board pack, a kickoff document, an RFP response. Wrong as the weekly status cadence; you'll burn the budget for the polish before the project is half done.
Option 4 — PlanSight PDF export
Upload the .mpp, click Export PDF in the workspace, get back a landscape PDF that includes the task list with task ID, name, start/finish dates, % complete, resource, and notes — outline-indented the way MS Project displays it.
What this avoids: no page-setup tuning, no manual screenshot composition, no copy-paste-into-PowerPoint loop. The export is the same every time, takes seconds, and the columns are pre-tuned for stakeholder readability rather than full PM-view density.
What it doesn't include: the full graphical Gantt with dependency arrows. The intended use is a task-list PDF that pairs with the live web share link — not a replacement for the screenshot-style Gantt.
PDF export is a Pro feature. Free signed-up users export to Excel; Pro users get both Excel and PDF.
What stakeholders actually look at in a project-plan PDF
When a senior stakeholder opens the PDF you sent, they don't read the task table top to bottom. They look for four things, in this order:
- The headline status — a single red/amber/green pulse for the whole project.
- Milestones — are the dated commitments still going to hit?
- What slipped this week — what's different from last week's PDF?
- The critical path end date — when does the project actually finish?
This is exactly what PlanSight's weekly status snapshot is designed to surface in one page: top-line RAG, milestones hitting and coming, slips, risks. If you're sending a stakeholder PDF every week, the weekly snapshot is usually a better fit than a full task-list export — same data, packaged for the way a stakeholder reads.
For one-off PDFs (a kickoff document, a steering committee pre-read, an auditor request), the full task-list export is closer to what you want. For ongoing weekly communication, the snapshot.
Pair the PDF with a sentence
Whichever option you pick, attach a one-sentence narrative to the email when you send it. The PDF is the evidence; the sentence is what makes the stakeholder care.
Bad: "Status report attached."
Good: "RAG is amber this week — Task 47 vendor delivery slipped 3 days and is now blocking the integration milestone. Plan attached."
The PDF lets them verify; the sentence tells them what to think about. The same principle applies to a live share link, and to screenshots. The artefact alone has never been the message.