Convert PDF Schedule to Excel on Mac: Rosters, Gantt, Timetables

To convert a PDF schedule to Excel on a Mac, decide first what one row should be: one shift, one event, or one activity. Then drag the PDF into a converter that reads what the schedule means rather than copying its grid, ask for that row with the columns you need (who or what, date, start, finish), and export to Excel. Check the row count against the schedule before you build anything on it.

The Mac app that does this is ignitai. It reads each page with Apple’s on-device text recognition, and an AI builds the table your plain-English instruction describes. That instruction can ask for a weekly roster as one row per shift, for shift codes spelled out from the legend, or for only the activity table from a Gantt chart. The page images stay on your Mac; only the recognized text goes to ignitai’s servers, where the spreadsheet is built.

Schedules arrive as PDFs because PDF is what scheduling software prints: next month’s ward roster, a contractor’s 90-page baseline programme, the league fixtures, a lender’s amortization table. All of them are laid out for reading on paper, not for sorting, totalling hours or importing into a calendar.

In this guide11 sections

Four kinds of schedule, four kinds of row

The printed layout rarely matches the row you need. A roster prints people down the side and days across the top, so one line of the PDF holds seven shifts. A Gantt chart prints activities in a table and their timing as bars. A month calendar puts events inside day boxes. Turning the layout into rows is the job.

Why schedules break PDF-to-Excel converters

1. The grid is the wrong way round. A roster converted cell for cell is readable, but you can’t filter it: there’s no asking “who works Saturday nights?” of a cell that says 22:00–06:00. Counting hours, checking cover and importing into a calendar all need one row per shift.
2. Codes stand in for times. Many rosters print E, L, N or D in the cells and explain them in a legend at the bottom: E = 06:00–14:00. A grid tool copies the letter; the times are in the legend.
3. Night shifts cross midnight. A shift that starts at 22:00 on Friday ends on Saturday. Any hours calculation that ignores the date change returns negative hours.
4. Gantt pages mix text with drawing. The dates sit in the table columns; the bars are drawn shapes. Band rows for each WBS level or summary task sit between the activities and look like activities.
5. Dates are local and compressed. Microsoft Project prints dates like Mon 10/5/26; Primavera P6 prints 05-Oct-26, adds an A after actual dates and an asterisk next to constrained ones. Sort by those strings and you get alphabetical order, not dates.

Convert a PDF schedule to Excel on Mac with ignitai

1. Take the pages you need. For a long programme, open the PDF in Preview, choose File ▸ Print, set the page range, and choose Save as PDF from the PDF menu. A page that carries only bars, with no activity columns, has nothing to read, so leave it out.

2. Drag the PDF onto the ignitai window, open it with ⌘O, or right-click it in Finder and choose Open With. Born-digital and scanned PDFs can go in the same batch. A photo of a roster pinned to a noticeboard runs as its own batch, because a drop that mixes PDFs and image files imports only the PDFs.

3. Describe the row. A prompt is required, so the Convert button stays disabled until you type one. Start from the Table starter or write it out. For a roster:

   “One row per shift. Columns: employee, role, date, start, end, end_date, shift_code, location. Employees are the rows of the grid and dates are the column headings; take the month and year from the page title. Spell out shift codes using the legend on the page. If a shift ends after midnight, end_date is the next day; otherwise it equals date. Skip OFF, leave and blank cells. Dates as YYYY-MM-DD, times as 24-hour HH:MM.”

   For a P6 or Microsoft Project PDF:

   “One row per activity from the table beside the bars. Columns: activity_id, activity_name, wbs, original_duration, start, finish, actual, total_float. wbs is the nearest band or summary heading above the activity; skip the band and summary rows themselves. Dates as YYYY-MM-DD. If a date ends in A, set actual to yes and drop the A; drop asterisks. Durations and float as bare numbers of days.”

   Save the instruction, and it’s one click away when next month’s roster or the next update arrives.

4. Check the page count, then Convert. Before the run starts, ignitai shows how many pages it will use and how many you have left. Each file shows its status as it runs, and a notification arrives when the spreadsheet is ready. On macOS Tahoe, Apple’s table-layout recognition sharpens how tables are read; the same flow works back to macOS 14.4.

5. Check the table in ignitai. Rows are numbered, so a twelve-person roster with five shifts each should land near sixty rows. Original Pages keeps the schedule a click away to compare against. If a column came back empty (end_date on a roster with no night shifts, say), ignitai says so.

6. Export to Excel or CSV. Excel for working with the schedule, CSV for a calendar import. Durations, float and payment amounts are real numbers in the Excel file, so they add up the moment it opens; the header is bold and the columns fit their content.

Long programmes and the page allowance. The plan includes 80 pages a week, up to 320 a month; unused weekly pages don’t carry over. A baseline programme for a building job can run past 80 pages, so prove the instruction on an excerpt of four pages or fewer first, then read the page count ignitai shows before the full run, and buy extra pages while subscribed if the week’s allowance doesn’t cover it. Packs run from 5 pages to 1,050, and bought pages never expire. Cancelling a run while it’s still going charges nothing.

Get ignitai on the App Store — free download; your first document (up to 4 pages) converts free with Sign in with Apple, and one subscription covers iPhone, iPad, Mac, and Vision Pro.

Shift rosters: hours, cover and the calendar

With one row per shift, the roster answers questions:

• Hours per shift. =MOD(end-start,1)*24 gives the hours whether or not the shift crosses midnight. Subtract unpaid breaks if the roster prints them.
• Hours per person per week. A pivot with employee down the side and week across the top shows who is rostered over contract. Actual hours come from timesheets, and the timesheet guide turns those into the same kind of rows, so rostered and worked hours sit side by side. When the hours feed pay, the payroll register workflow closes the loop.
• Cover. =COUNTIFS(C:C,G2,B:B,"RN") counts the nurses rostered on the date in G2. A day with too few shows as a low number instead of a gap someone notices at handover.

Your own shifts in a calendar. Staff who just want their shifts on their phone can run a second, smaller conversion:

“Only shifts for Dana Ruiz. Columns named exactly Subject, Start Date, Start Time, End Date, End Time, Location. Subject is the role and shift code. Dates written like 10/06/2026, times like 7:00 AM.”

Choose CSV. Then, on a computer, open Google Calendar, click Settings, choose Import & export, select the file and click Import. Google requires English column headings and needs only Subject and Start Date; the rest are optional. If a heading comes out slightly different, rename it in the spreadsheet app and save as CSV again. Apple Calendar imports .ics files, not CSV, but it shows the shifts once your Google account is added to it.

Project schedules: what a Gantt PDF gives you

The activity table turns into a working list:

• A three-week look-ahead. Filter start to the next 21 days: a list instead of a 90-page plot.
• Critical and near-critical work. Filter total_float to 5 days or less.
• What slipped between revisions. Convert the baseline and the latest update in separate runs, since batch output has no filename column. Add a revision column to each after export, then XLOOKUP finish dates by activity_id; =finish_update-finish_baseline gives each activity’s slip in days.
• Trade packages. Filter by wbs to send a subcontractor just their activities, the scheduling counterpart of splitting a bill of quantities into packages.

What a PDF can’t carry is the scheduling engine. You may get a predecessors column, since Microsoft Project’s default table prints one, but change a duration in Excel and nothing downstream moves. For delay analysis or re-sequencing, ask for the native file: P6 exports XER or XML, and Microsoft Project saves MPP or XML. Microsoft Project’s desktop app and P6 Professional both run on Windows, so on a Mac the PDF is often what you actually have.

Timetables, calendars and payment schedules

• Timetables and fixtures. A league fixtures list, a conference agenda, a term timetable: one row per event with date, start, end, title and location. The calendar import above works the same way for a team’s fixtures.
• Month-view calendars. The hardest layout, because each event sits inside a day box and the date is a small number in its corner. Ask for “one row per event; the date is the day box it sits in; month and year from the page title”, prove it on one month, and compare a busy week against the page before you convert the year.
• Amortization schedules. A lender’s payment table converts to one row per payment: number, date, payment, principal, interest, balance. It checks itself: each balance should equal the previous balance minus that payment’s principal, and principal plus interest should equal the payment (plus escrow, where it’s listed). For the monthly statements on the same loan, see the mortgage statement guide.

Other ways to get a schedule into Excel

• Export from the source. Most rostering and scheduling software can export to a spreadsheet or calendar format directly. If you have access, or can ask the scheduler, that beats any PDF.
• Excel for Mac’s Get Data. Power Query is under Data ▸ Get Data, but Excel for Mac has no From PDF connector; that one is Excel for Windows only. Even there it reproduces the grid: a roster stays seven shifts to a line, the Gantt band rows come along, and a scan returns nothing.
• Acrobat’s Export PDF to Excel. It keeps the printed layout, which is the problem: roster grids stay grids and shift codes stay codes.
• Copy and paste from Preview. Fine for one line; on a full page the columns collapse into one.

On iPhone and iPad

• iPhone. The roster went up on the noticeboard or arrived in a group chat as a PDF. Share it to ignitai or scan the printout with the camera, use the calendar instruction for your own shifts, and choose CSV. Progress shows on the Lock Screen and in the Dynamic Island. The Google Calendar import itself needs a computer.
• iPad. A site manager with the programme in Files can pick it from the file picker or send it through the share sheet (there’s no external drag-and-drop into the app on iPad). Sort the finished table by start date, select the next three weeks of activities and copy them into an email before exporting anything.

One subscription covers iPhone, iPad, Mac and Vision Pro, and finished files open on your other devices after Sign in with Apple.

When not to use this

• The native file or a direct export exists. Take it; it carries logic and history the PDF leaves out.
• The schedule lives in an app everyone checks daily. A converted PDF is a snapshot that goes stale. This workflow is for schedules that only exist as PDFs or paper.
• The roster is handwritten. A rota filled in by pen is outside what this guide promises; typed and printed schedules are the case it covers.
• The names or the programme are confidential. The page images stay on your Mac, but the recognized text (names, dates, activity descriptions) goes to ignitai’s servers, where the AI builds the sheet, and the finished file stays in your ignitai account until you delete it. Check that against your employer’s or the contract’s terms first.

Bottom line

To convert a PDF schedule to Excel on a Mac, pick the row first (one shift, one activity, one event, one payment), then drag the PDF into ignitai and describe that row in plain English: unpivot the roster grid, spell out the shift codes, carry night shifts into the next day, take only the activity table from a Gantt chart. Export to Excel to work with it, or to CSV with Google’s column names to put the shifts in a calendar. Prove the instruction on four pages, check the row count and a few rows against Original Pages, and ask for the native file whenever you need logic rather than dates.

FAQ

How do I convert a PDF schedule to Excel on a Mac?

Drag the schedule PDF into ignitai, ask for one row per shift, event or activity with the columns you need (who or what, date, start, finish), and convert to Excel. The pages are read on your Mac and only the recognized text goes to ignitai’s servers, where the AI builds the sheet. Then check the row count and a few rows against the original page.

Can I convert a Primavera P6 or Microsoft Project PDF to Excel?

Yes, from the activity table printed beside the bars: activity ID, name, duration, start, finish and float. The bars themselves are drawn shapes, so a page that prints only bars has nothing to read. If the scheduler can send the native XER, XML or MPP file, that carries the logic a PDF leaves out.

How do I get a PDF work schedule into Google Calendar?

Convert it to CSV with columns named exactly Subject, Start Date, Start Time, End Date and End Time, with dates written like 10/06/2026 and times like 7:00 AM. Then open Google Calendar on a computer, go to Settings, then Import & export, and import the file. Apple Calendar can’t import a CSV, but it shows those events once your Google account is added to it.