How to Share an MS Project Plan With Your Team Today

Wellingtone's 2026 State of Project Management report found that 72% of respondents spend half a day or more every month manually collating project reports. Ask why, and the pattern repeats across PMOs: the schedule everyone is reporting from lives in one file, on one laptop, open in a desktop app that nobody else on the team has installed.

The direct answer: you can share an MS Project plan with your team without a server migration, a Project Online license, or asking anyone else to install Microsoft Project. Open the .mpp or MSPDI XML file in Onplana Schedule, a free desktop app for Windows and Mac, keep editing it there the way you already do, and use Publish to turn it into a live project in Onplana the rest of the team can see and update without ever touching the original file.

The short answer. Open the schedule in Onplana Schedule, a free desktop app that reads .mpp and MSPDI XML files directly, edit it as usual with full undo support, and click Publish to create a shared project in Onplana from the file. The team gets a live plan they can see and comment on; the original file keeps working in Microsoft Project exactly as before, because Onplana Schedule saves back to MSPDI XML.

Why the schedule stays a one-person file in the first place

Nobody decides on purpose to keep the master schedule invisible to everyone but themselves. It happens by accretion: the plan started as a personal working file, MS Project itself has no concept of "share this with the team" beyond a licensed server nobody's IT department wants to stand up, and by the time thirty people depend on the dates in that file, moving it somewhere else feels riskier than emailing an updated screenshot once a week. The status report becomes the team's only window into a schedule none of them can open, and producing that report by hand is exactly the half-day-a-month Wellingtone's respondents are describing.

What Publish actually does

Publish takes the schedule you're already editing in Onplana Schedule and creates the equivalent project in Onplana directly from the desktop app, no separate export-then-import step. It carries across the same structure the app reads when it opens the file in the first place: tasks and their outline hierarchy, all four dependency types with lag, all eight Microsoft Project constraint types, milestones, and costs. The Gantt the team sees in Onplana afterward reflects the file as it actually was, not a simplified summary of it.

Before publish vs after publish

	Private .mpp on one laptop	Published in Onplana
Who can see the current plan	Only whoever has the file	Everyone added to the project
How the team learns the status	A report the owner writes by hand	Opens the live plan directly
What happens if the owner is out	Nobody can open or update it	Anyone with access can
Dependencies and constraints	Correct, but invisible to others	Same data, now visible to the team
Editing the master copy	Whoever has the file, one at a time	Comments and updates from the team, changes still made deliberately
Version control	Whichever copy was emailed last	One project, one current version

Share the plan with your team, step by step

1. Open the .mpp or MSPDI XML file in Onplana Schedule; file associations let you double-click it directly once the app is installed.
2. Review the Gantt and grid: name, duration, dates, predecessors, resources, percent complete, outline level, critical path, float, and milestones, plus baseline bars if the file carries them.
3. Make any corrections before publishing. Every change, cells, insert, delete, indent, outdent, dragged dependency links with type and lag, all eight constraint types, supports undo, and the schedule reschedules automatically as you go.
4. Run the free Schedule Health Check on the file if you want a second check for dangling tasks or constraint conflicts before the whole team can see it.
5. Click Publish to create the project in Onplana. The team now has a live plan; you keep the desktop app for the heavy editing you were already doing.
6. Add the people who need to see it. Anyone who only needs to view or comment on this one project can use a guest seat, which is included on every paid plan; someone editing the schedule regularly needs a full member seat.

When the desktop app is enough, and when it isn't

Publishing one schedule solves a specific problem: a plan that exists but that only one person can open. It is not the same undertaking as moving an entire PMO off Project Online, which means migrating resource pools, enterprise custom fields, and years of history, a project measured in weeks rather than an afternoon. If the actual goal is retiring a Project Online tenant rather than sharing one file, importing the schedule while keeping dependencies intact and the full migration path are the more relevant starting points. If all you need right now is to open the file and look at it, without publishing anything yet, opening an .mpp file without Microsoft Project covers the read-only route.

The diagram below shows the same path as a straight line: a file one person can open becomes a plan a team can see, with the health check as an optional stop along the way rather than a required one.

What the team gets that the emailed file never did

The comparison table above understates one thing: a published plan doesn't just make the current schedule visible, it removes the report as the only interface to it. Someone who wants to know whether a milestone is still on track opens the plan directly instead of waiting for the next status email, and the person who used to spend part of a day each month assembling that email gets that time back. None of this requires giving up the desktop app. The heavy editing, dragging dependencies, adjusting constraints, correcting durations, still happens there; Publish just means the result doesn't have to be re-explained to everyone else by hand.

Run the free Schedule Health Check Upload your .mpp or MSPDI XML file and get a per-finding breakdown of dependency issues, constraint conflicts, dangling tasks, and the real critical path, computed from the dependency graph, before you publish it for the whole team to see. No signup, no credit card. → Run the Schedule Health Check

Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.