Start with the file and its supported scope
An MPP plan contains more than the task names shown in a Gantt chart. Resources, dependency types, calendars, saved baselines and many application-specific structures can affect how the originating application presents it. A useful reader should identify which records it extracts and make the remaining coverage visible.
Project File Desk accepts supported unencrypted MPP14 files and Microsoft Project XML. It reads stored task fields locally and provides a review table rather than opening a cloud scheduling account. The uploaded source is never modified. Older binary formats or password-protected files need an appropriate export from the originating application before this bounded reader can use them.
Treat stored dates as observations
A task’s stored start and finish are not a promise about what a fresh scheduling calculation would produce. Different calendar rules, missing external dependencies or resource leveling can change a recalculated plan. This workbench deliberately shows the stored values and does not substitute new dates for absent ones.
Inspect the date coverage and dependency diagnostics before sharing the result. Undated named tasks remain in the table. Reversed dates, unresolved references and dependency cycles are review signals. They are not repaired automatically, because a file reader cannot safely infer the planner’s intended correction from those records alone.
Choose a review artifact for the recipient
Use the workbook when the recipient needs task, dependency, assignment and resource tables. Use the Gantt PDF for a compact visual review of stored dates and a selected baseline. The JSON export includes the supported data and omission report, while CSV provides a simple task table.
These files are review copies rather than replacements for the original MPP. Notes, costs, timephased work and other excluded structures are not recreated. Keep the source file separately and use the originating planning application whenever you need to edit, reschedule or verify behavior that depends on the full project model.