How to share a project plan with a stakeholder who doesn't have MS Project

You've built the plan. Now you need to send it to a stakeholder — an executive sponsor, a client, a team lead, an auditor — someone who needs to see the schedule but doesn't have Microsoft Project installed and isn't going to install it for one file.

There are four common ways to share it. They differ in three dimensions that matter:

• Friction for the recipient (do they have to download, install, or sign up for anything?)
• Fidelity of what they see (Gantt + dependencies + status, or just text?)
• Update workflow (when the plan changes, what do you re-send?)

Option 1 — Email the .mpp file (don't)

Tempting because it's one click in Outlook. Doesn't work for the reasons covered in the previous guide: the recipient can't open it without paid software they probably don't have.

What actually happens: the stakeholder sees the attachment, double-clicks, gets a "no application available" error, replies asking for a PDF. You're now in two-round-trip territory and you've trained them to expect that every plan update will involve back-and-forth.

Don't do this.

Option 2 — Screenshot the Gantt

A small step up. Open the plan in MSP, screenshot the timeline, paste into an email or Slack message.

Fidelity is low. The recipient sees:

• Task bars and approximate dates
• The general shape of the schedule

The recipient doesn't see:

• Dependencies (the arrows are usually too small to read in a screenshot)
• Per-task status, % complete, or assigned resources
• Anything below the visible scroll position
• The critical path

Updates are painful — every change means a new screenshot. The stakeholder can't search, filter, or click into a task to ask questions about it.

Use for early-stage informal updates ("here's where we are at a glance"). Don't use as the primary communication channel for an ongoing project.

Option 3 — Export to PDF

In MSP, File → Save As → PDF produces a landscape Gantt PDF. This is the workplace standard for project status reporting and for good reason: PDFs are universally readable, render the same on every device, and survive forwarding through any email client.

Fidelity is decent — the dependencies render, the task table is searchable text, the timeline shows critical path if you've configured MSP to colour it.

Trade-offs:

• Static. Every update means re-exporting and re-sending. Stakeholders who get three PDFs over three weeks end up with stale data and confusion about which one is current.
• Hard to read on phones. PDFs of wide Gantt charts pan-and-zoom on mobile, which most stakeholders won't bother with.
• No analysis layer. The PDF shows tasks and dates; it doesn't tell the stakeholder what to pay attention to.

PDFs are right when the artefact itself is the deliverable — an attachment to a steering committee pack, a record for an auditor, something filed for later. They're wrong as the day-to-day stakeholder view of a living plan.

Option 4 — A web share link (read-only)

Best fit for most ongoing stakeholder communication. You upload the plan once to a web service that hosts it; the service gives you a URL; you send the URL.

The stakeholder clicks the link and sees the plan in their browser — no install, no signup, no friction. When the plan changes, the URL stays the same; the content behind it updates the next time you re-upload.

This is what PlanSight AI does:

1. Upload your .mpp to plansight.aisolutionmaven.com
2. PlanSight parses it into a task table, Gantt chart, and analysis view in seconds
3. Copy the Stakeholder share link from the workspace and paste it into your status email or Slack
4. Anyone with the link can view the plan, critical path, risks, and AI-generated summary in their browser

The recipient doesn't need an account. The link works on phones. If you have Pro, the link never expires — re-upload the updated plan and the same URL serves the new version. Free signed-up users get one persistent plan (replacing on each upload). Anonymous uploads work for 24 hours.

Other tools that produce stakeholder share links: Smartsheet, Wrike, and Project Online all support read-only sharing once you've imported the .mpp. They differ from PlanSight in cost (paid, $10-25/user/month) and complexity (full PM platforms with their own learning curve). For PMs whose source of truth is already MS Project and who just want to communicate, a focused viewer-and-share tool is usually less overhead.

What makes a good stakeholder share

The best share artefact:

• Loads instantly. Stakeholders won't tolerate more than a few seconds — they're busy and the alternative is asking you for a status update.
• Renders on mobile. Executives read on phones. If the share view requires pan-and-zoom, half your audience never reads it.
• Shows the critical path. This is the single piece of analysis most stakeholders want — what's the longest chain, where does the project end?
• Stays current. Either the URL is live (web share), or you commit to a cadence (weekly PDF). Don't mix the two.
• Is read-only by design. A share link that allows accidental edits creates risk. Read-only by default is the right safety property.
• Captures status, not just data. Tasks + dates are the data. RAG status, late tasks, tasks at risk, recent slips — that's what the stakeholder needs to act on.

Update workflow matters more than people think

When you pick a sharing mechanism, you're really picking an update workflow. Stakeholders don't read the first artefact carefully — they read the third, fourth, and fifth ones if your project runs for months. Anything that requires you to manually re-export and re-send every week will get skipped during busy stretches, and stakeholders will quietly assume the plan hasn't changed.

A web share link with a stable URL solves this. Your weekly status email keeps the same line — "Current plan: [link]" — and stakeholders learn that clicking the link always shows the truth.

Pro tip: pair the share link with a short narrative

The link is the data. The two-sentence narrative in your email is what makes the stakeholder care.

Bad: "Plan attached, see link."

Good: "Two milestones slipped this week — vendor delivery on Task 47 and stakeholder review on Task 71. Critical path still hits Sep 30. Plan: [link]."

The link lets them verify. The sentence tells them what to think about.

Related guides

• How to open an .mpp file without Microsoft Project
• Critical path explained for project managers