How to update a P6 schedule without a P6 license

On many construction projects, the Primavera P6 schedule is maintained by a dedicated scheduler or project controls team. But project managers and superintendents are the ones closest to the work. They know which activities started, what's falling behind, and what needs attention next.

The problem is that they often don't have access to P6. So field updates travel through emails, spreadsheets, marked-up PDFs, and phone calls, and the scheduler has to interpret them and enter them into the master schedule.

There are several ways to handle this without giving every project manager a P6 license. Here's how they compare.

What "updating the schedule" actually means

A schedule update usually involves four things:

1. Actual dates. Recording when activities actually started and finished.
2. Progress. How far along in-progress activities are, as percent complete or remaining duration.
3. The data date. Moving the schedule's "as of" date forward to the update date.
4. Recalculating. Running the schedule (critical path method) so remaining work, float, and the completion date reflect the new reality.

PMs supply most of the information for steps 1 and 2. Steps 3 and 4 are normally the scheduler's job in P6.

Option 1: Send updates to your scheduler

The most common approach is to send your scheduler a list of what's changed. It can be an email, a marked-up lookahead, or a spreadsheet export of the activities.

Works well when: the project is small, updates are infrequent, and your scheduler has time.

Watch out for:

• Updates get delayed or lost when the scheduler is busy.
• You don't see the impact of your changes until the scheduler runs the update.
• Free-text notes ("concrete slipped a few days") have to be interpreted, which leads to mistakes.

Tip: use activity IDs, not just names, and give exact actual start and finish dates rather than descriptions.

Option 2: A spreadsheet round-trip

Your scheduler exports activities to Excel, you fill in actual dates and progress, and the scheduler imports the file back into P6.

Works well when: you need a structured format and your scheduler is comfortable with P6's spreadsheet import.

Watch out for:

• Imports can overwrite data if columns are mismatched.
• You still can't see how your changes affect the critical path or the completion date before sending them.
• Version control gets messy when several people edit copies of the same file.

Option 3: Use Flotillo to update a P6 schedule without a P6 license

Instead of sending progress through spreadsheets and emails, Flotillo gives project managers a place to work with a copy of the scheduler's P6 schedule. PMs record actual progress, track delays, and see the likely impact of changes before sending an updated file back to the scheduler. You can try it with a sample schedule before reading on.

1. Get the XER file. Your scheduler exports the project from P6 as an XER file and shares it with you.
2. Upload it to Flotillo. Flotillo reads the activities, logic, and dates and calculates the schedule. Your original XER file is never changed.
3. Update actual dates and progress. Enter what happened in the field, from your desk or from a phone.
4. See the impact before you save. Flotillo shows how a change affects the completion date and which activities move onto the critical path, before you commit it.
5. Export the update. Download an updated XER or P6-compatible XML file.
6. Your scheduler imports it into P6. The scheduler reviews the changes, imports them, and stays in control of the official schedule.

Works well when: you want to keep the schedule current between scheduler updates, understand the impact of field changes yourself, and hand your scheduler a clean, structured file instead of notes.

Good practice, whichever option you use

• Agree on an update cycle with your scheduler, for example every Friday with a Monday data date.
• Update actuals, not logic. Leave relationship and duration changes to the scheduler unless you've agreed otherwise.
• Record reasons when work happens out of sequence or slips, so the scheduler and owner understand why.
• Keep one source of truth. The scheduler's P6 project stays the official schedule. Everything else feeds into it.

Frequently asked questions

Can you update a Primavera P6 schedule without owning P6? Yes. You can send updates to the scheduler, use a spreadsheet round-trip, or work from the XER file in a tool like Flotillo. In every case, someone with P6 imports the update into the official schedule.

Can you open a P6 XER file without Primavera? Yes. An XER file is a text export of a P6 project, and several tools can read it, including Flotillo.

Can an updated file be imported back into Primavera P6? Flotillo exports XER and P6-compatible XML files for import into P6. As with any import, your scheduler should review the changes before accepting them into the official schedule.

Does every project manager need a P6 license? Not necessarily. Project managers can contribute updates through their scheduler, a spreadsheet round-trip, or a tool like Flotillo without working in P6 directly. Licensing depends on how your organization manages P6.

Try updating a P6 schedule yourself

Open Flotillo's sample construction schedule and try it: change an activity's dates and see what happens to the completion date and critical path. No upload or account is needed to explore. To save changes or use your own schedule, request access.