Print and export schedules
Choose an output based on what the recipient needs: a readable plan, a table for analysis, or an interchange schedule for another scheduling tool.
Choose the output
| Output | Use it for |
|---|---|
| PDF / Print schedule | A meeting handout or issued schedule with the chosen presentation |
| Batch print | A repeatable set of views and print layouts |
| Excel | Schedule data for tabular review |
| Excel with comments | A data review that includes the available activity comments |
| XER | Supported P6 schedule interchange |
Exports contain information from the selected schedule and output settings; they are not a backup of every workspace feature. Microsoft Project XML/MPP export is not supported. XER export has specific omissions, including resource/assignment coverage described in P6 compatibility.
Prepare the view first
Open the correct schedule. Choose the view, columns, filters, grouping, and level of WBS detail that the audience needs. Check the visible activity count and the comparison display if you intend to include one.
For a lookahead, show only useful fields and the relevant date window. For an issued full schedule, make sure a personal filter is not unintentionally hiding work. Views and filters explains how to save the presentation.
Print a single schedule
- Open Print → Print schedule. The PDF option in Export also leads to the print workflow.
- Choose Single and the intended Layout.
- Review the General, Header, and Footer settings.
- Check the preview, including the last page and any horizontal page breaks.
- Set the output filename and choose Print to generate the PDF.
The action generates a PDF download. You can then open or print the file using your normal PDF tools. If no file appears, check the browser’s downloads and whether generation reported an error.
Make the pages readable
Under General, review the timeline timescale and date window, page size, orientation, margins, gridlines, row numbers, and repeating headers. Use the available fit controls to balance the number of pages against readable text.
A print timeline can use fixed dates or dates relative to Project Start, Project Finish, Status Date, or another available anchor. A narrow window is useful for a lookahead; a full project needs enough width to show the important logic and labels.
If the preview is tiny, first reduce unnecessary columns and timeline span, then choose a suitable page size and orientation. Shrinking everything onto one page is rarely the most readable answer for a large schedule.
Configure Header and Footer with the identifying information the recipient needs. Use field tokens where available so the schedule name, reporting context, or page information stays useful when the layout is reused. The filename control also supports available field tokens.
Save a layout
Use Save to update a layout you can manage, or Save as new to preserve a variation. Name the layout for its purpose, such as “Landscape lookahead” or “Full schedule issue.”
A view determines the schedule information and organization. A layout determines the printed page setup. Saving one does not replace saving the other. Manage layouts under Assets → Layouts.
Print a report set
Choose Batch print when you need several outputs from repeatable view/layout combinations.
- Choose an existing batch or Add report.
- Expand a report card and set its Report Name, filename, View, and Layout. Save the report’s changes.
- Choose Preview on each report to check its output.
- Select the checkboxes for the reports you want to generate.
- Use Save batch to preserve a selection of two or more reports under a name. You can save a new batch or replace an existing one.
- Generate/download the selected reports using the print dialog’s output action.
Batch reports use shared project/workspace schedule views. Private views and Summary views are not offered because the report must be usable by other project members. Save an appropriate shared schedule view first if yours is missing.
A report’s comparison comes from its selected view. If that view compares with the previous update, the target schedule needs a valid earlier tagged update. Correct the view or reporting sequence when the dialog says no previous update exists.
For example, a coordination report can include a milestone view, an area lookahead, and a critical-work view with layouts suited to each. Check every entry’s selected view and layout before generating the set; a well-designed first page does not guarantee the remaining entries are correct.
Manage reusable report definitions under Assets → Reports. Keep their referenced views and layouts available in the relevant scope.
Export Excel or XER
Open Export and choose the required format. Confirm that the active schedule is the intended file before generating it. Use Excel with comments when the recipient needs that context, and the comparison dialog’s Export to Excel for a two-schedule difference workbook.
For an XER handoff, check the exported and omitted fields before relying on a round trip. Syncify’s calculation modes and supported options are not identical to every P6 configuration.
Final report checks
Open the generated file and confirm the schedule name/ID, status date, reference schedule, included work, page readability, and filename. A PDF or spreadsheet is a point-in-time output; later edits in Syncify do not update a file you already sent.
If the recipient needs to see the latest accessible schedule instead of a fixed issue, consider sharing the schedule.