Someone sent you a Microsoft Project plan and you don't have Project

A contractor emails you a programme. You double-click it and macOS shrugs, or Windows offers to buy you a Project licence you didn't want. You just need to read the thing and put it in front of a client. Here's the honest way to open a Project schedule in your browser and present it — including the one thing you need to know about .mpp files before you start.

Microsoft Project is a fine scheduling engine and a terrible sharing format. The people who build plans have Project; the people who have to read them — clients, sponsors, subcontractors, the commercial team — almost never do. So a plan arrives as a .mpp attachment and immediately becomes a hostage: locked inside a licensed desktop app that half the recipients can't open.

The usual escapes are all bad. Buy a seat for a file you'll read once. Beg a colleague to screenshot it. Paste a blurry crop into a slide and retype the dates underneath. None of that is necessary — but there's one detail nobody tells you up front, so let's be straight about it.

If you have the Project XML: drag, drop, done

This is the happy path, and it's genuinely this short. A Project .xml is the full plan — tasks, summary tasks, milestones, dates, durations, % complete, the outline structure — written out in text. Sketchedule reads it end to end.

Drop the .xml onto Sketchedule and it parses in your browser — nothing is uploaded, the plan never leaves your machine, and it works offline. What you get back isn't a flat list: the Project outline arrives intact. Summary tasks become section bands with a grey summary bar spanning their children, ordinary tasks become bars on the Gantt, and zero-duration tasks become milestone diamonds — reading straight off the fields Project already wrote.

If you only have a raw .mpp: one export, then the same path

A raw .mpp is a binary file — the export you can't do without Project touching it once. The good news: that "once" doesn't have to be your Project, and it takes about ten seconds. Here's the whole workflow, honest about which step needs what.

1. Check what you actually have. Look at the extension. A .xml is a Project XML — skip to step 4. A .mpp is the raw binary and needs converting first.
2. Get it exported to XML. The cleanest move is to ask the sender to send the XML instead — in Project it's just File → Save As → Save as type: XML (*.xml). If you can't reach them, run that same export from any copy of Project you can borrow for a minute — a colleague's machine, a shared workstation. You need Project open for this one step, not a licence of your own.
3. Save the .xml somewhere you can find it. That single file is now the full plan in a format that travels.
4. Drag the .xml into Sketchedule. Drop it on the app. It parses locally, in your browser — nothing uploaded. The tasks, summary tasks and milestones arrive as a proper outline (Fig 2).
5. Read it and roll it up. Scan the grid, expand and collapse the outline, and collapse to summary level for a cleaner picture — Sketchedule draws an automatic summary bar over each phase. Filter out anything that isn't part of the story, and promote the key dates to milestones.
6. Present or share it. Add a header, footer and logo, then export a landscape PDF or PowerPoint — or send a read-only link that rebuilds the whole picture in the recipient's browser, no Project and nothing installed. The client sees the plan, not a screenshot of it.

What it looks like once it's in

Here's a Project plan — a small office fit-out — after its XML lands in Sketchedule: the task grid on the left with start / finish / % columns, section bands for each phase, summary bars, task bars on a month axis, milestones and the data-date line. This is the view you hand to a client, not the licensed desktop they can't open.

Why present it here instead of buying a seat

Because opening the file was never the real job — showing it was. Even people who own Project rebuild its output for the boardroom, because a desktop Gantt print isn't a client deliverable. Here's where a browser presentation layer earns its place:

• Anyone can open the result. The client, the sponsor, the subcontractor — none of them need Project. A read-only link rebuilds the whole picture in their browser, nothing installed.
• Present, don't screenshot. Branded landscape page, logo, header/footer, RAG stoplights, a status line, clean typography — a real one-page PDF or PowerPoint slide instead of a blurry crop pasted into a deck.
• Nothing leaves your machine. The XML parses locally in the browser; the plan isn't uploaded to a server. For a schedule you were trusted with, that matters.
• Refresh next period. When an updated plan lands, re-import the new XML and Sketchedule shows what changed — dates moved, tasks added, tasks dropped — before you accept it.

The honest one-liner: Microsoft Project computes the plan; Sketchedule presents it. The engine stays with whoever built the schedule — Sketchedule is the presentation front-end for the plan Project already produced, a companion to it, not a replacement for it.

Microsoft Project is a trademark of Microsoft Corporation; Primavera and P6 are trademarks of Oracle Corporation. Sketchedule is an independent product and is not affiliated with, endorsed by or sponsored by Microsoft or Oracle. Figures are illustrative, drawn in Sketchedule; Fig 3 is a faithful redraw of the app view of an imported Microsoft Project plan.