Features › Scheduling
Print and export
Print the schedule as a PDF on the paper size you need with saved settings, and export it to Excel, CSV or MS Project XML — and what each format keeps.
Your schedule can go on paper or into another program. The PDF dialog prints the table, the Gantt chart or both on any of five paper sizes, and remembers the settings you use again. Excel, CSV and MS Project XML exports carry the schedule into other tools.
Where to find it
Export ▾ on the editor's toolbar: PDF…, Excel (.xlsx), CSV and MS Project XML (MSPDI).
The PDF
PDF… opens the export dialog, with your options on one side and a live preview of the pages on the other.
- Content — Table + Gantt chart (the default; the Grid ↔ Gantt slider and the column checkboxes set the mix), Gantt chart only (bars labeled with task names, milestones with their date), or Table only (the full-width table, no chart).
- Paper — Size is Letter, Legal, Tabloid (the default), ANSI D or ANSI E, and Orientation is Landscape (the default) or Portrait.
- Date range — leave it empty to print the whole project.
- Timescale — Fit across pages (choose how many Pages wide), or days, weeks or months.
- Table columns — tick the columns to print. These are chosen here, separately from what the grid shows.
- Show on chart — link lines, critical path highlighting, the today line, bar shading by % complete, weekend shading, and, when the project has them, the Crew histogram, the data date line, baseline bars (and which baseline), task colors and deadlines.
- Options — Gridlines, Color table rows by task color, the key (Legend page), Cash flow page when tasks have costs, and Hide subtasks of collapsed summaries to print the collapsed outline.
- Header & footer — the Schedule date, and a logo (Upload logo…).
Print… opens the PDF in a new tab with the print dialog ready; Export PDF saves it as a file.
The key
Legend placement puts the key on a Separate page (the default) or With schedule if it fits — on the last schedule page when there is room, and on its own page when there isn't. The key is a compact band of boxed sections side by side — the chart's Symbols, Task colors, the Crew trade colors and a Project summary.
The Crew histogram option prints the stacked crew band under the chart, in trade colors, with crew still needed striped, labeled gridlines, and each day's total when the scale is by day. Color table rows by task color washes each table row in its tag's color — in table-only prints too, where the key then lists the tag names.
Saved print settings
Save any mix of options under a name — "Owner monthly update" — with Save settings…, and pick it next time from Saved print settings. Signed in to a company account, your saved settings follow your account; without one, they stay in that browser.
A company admin can also press Set as company default… to make the current options the company's print layout. Everyone in the company then finds it as ★ Company default, and a company logo, when one is set, fills in on its own.
Excel and CSV
Excel (.xlsx) is one click: a styled workbook with row tints, text styles and typed columns. CSV is plain text for any program.
- Both export the columns the grid is showing — a hidden column drops out until you show it again.
- When any task has a cost, the Excel file gains a second Cash flow worksheet with the monthly planned, earned and baseline amounts, whether or not the Cost column is shown. See Cost loading and cash flow.
- Under a filter, both ask whether to export only the filtered tasks. See Filters, saved views and the 3-week lookahead.
MS Project XML
MS Project XML (MSPDI) writes the project as a Microsoft Project XML file. Microsoft Project opens it directly (File → Open; use Save As in Project to get an .mpp), and Primavera P6 imports it with File → Import → Microsoft Project XML.
It carries everything Ganttry's importer reads back:
- tasks, the outline, WBS and Activity IDs;
- durations (in each task's calendar hours) and milestones;
- all four link types with lag, and constraints and deadlines;
- % complete, actual dates, remaining work and the data date;
- notes;
- every named calendar and which tasks use it — working weekdays, holidays, and yearly shutdowns written out as dates across the schedule.
The active baseline goes out as MS Project's Baseline 0, for Project's benefit only — Ganttry doesn't read baselines back in.
Not exported: crew, equipment, assigned people and units, quantity, cost, your own columns, color tags, text styles, other baselines, and float and late dates (Project works out its own). Extra working days are written out but ignored when the file is imported again.
The XML export is always the complete project, even under a filter — MS Project needs every task and link.
Field paper
The crew handout, the itinerary and the master sheet print from their own screens — see Crew paper.
Who can use it
Admins and Editors, from the editor. Setting the company's default print layout is for company admins. See Who can see and do what.
Good to know
- File ▾ → Save a copy (JSON) (
Ctrl+S) saves the whole project as a Ganttry file you can open again later with Import file…. - The lookahead sheet: filter to the 3-week lookahead, then PDF… — see Print the 3-week lookahead.
- Weekend shading follows the project's calendar, even for tasks on their own calendars.
Describes Ganttry 1.15.0. Something wrong or missing? Tell us.