Open this update in P7: the Flowchart's Add Fragnets step opens P7 in a new tab and hands it the Schedule Updater's .XER inside your browser. P7 asks before it imports it as a new project.
Pathizer and P7
Move each schedule update between Pathizer and P7 without retyping it
Pathizer's Flowchart runs the monthly update in five steps: Capture, Add Fragnets, Health Check, Review Meeting and Publish. P7 is where the scheduler does the schedule work between them: it opens the field's update from the Flowchart, takes the fragnets, runs the review meeting and saves the .XER that goes back.
The field enters progress in Pathizer's Schedule Updater. A Project Controller opens that update in P7 from the Flowchart, adds the period's fragnets, schedules with F9 and saves an .XER. The .XER goes on the Flowchart's Health Check step, is reviewed in P7, and Publish puts it in File Storage, where Pathizer starts the analysis.
Use P7 from Claude or Codex
Your AI app on your computer, your schedule in your browser.
Claude Desktop and Claude Code
Claude Desktop installs the connector from one downloaded file. Claude Code adds it with one terminal command.
Codex
Add the connector with one terminal command, or in ~/.codex/config.toml. Needs Node.js 20 or newer.
The cycle
Five Flowchart steps, and where P7 does the work
Capture
The field enters progress in the Schedule Updater. When it is done, the update is sent to the scheduler and the Updater locks.
Add Fragnets
Open the update in P7 from this step. Add the period's weather days, RFIs, change orders and other delays as fragnets, by hand or with your AI, then press F9.
Health Check
Export .XER from P7 and drop it on the Health Check step. Pathizer scores it as the next update and lists findings. Fix them in P7 and drop the file again.
Review Meeting
Open the Review Meeting layout in P7 and walk the remaining work by float path with the team.
Publish
Publish the checked file. It goes to File Storage, the analysis starts, and the Schedule Updater opens for the next period.
Who It Is For
For project controllers running the monthly update
Project controllersSchedulersProject managersField teams who enter progress
What moves between Pathizer and P7
Copy the prompt for your AI: the same step copies a plain text prompt that tells Claude or Codex how to add the period's time impacts as fragnets in P7.
Health Check: drop the .XER that P7 saved on the Health Check step. Pathizer scores it as the next update with the full Health Score and lists its findings, without adding it to File Storage.
Fix in P7: your AI app reads the findings through Pathizer's tools, you make the fixes in P7, press F9, export and check again.
Review Meeting: open P7's Review Meeting layout to walk the float paths with the team.
Publish: a Project Controller publishes the checked file to File Storage. Pathizer starts the analysis, and the next period opens at Capture.
Definitions
Terms used on this page.
Flowchart
Pathizer's page for Project Controllers that runs the monthly update in five steps and shows which step each project is on.
Fragnet
A small set of activities and ties added to a schedule to show one impact, such as a change order or weather days.
More in the glossary: Fragnet, Schedule update, Contemporaneous update, Time Impact Analysis (TIA), Multiple float paths, XER file.
Practical Outputs
What you get.
The field's progress in P7 with no retyping
Fragnets for the period's impacts, tied into the logic
A health check of the file before it is published
A published update that starts Pathizer's narrative, reports and delay analysis
Related Workflows
Related pages.
Pathizer homeOperationsDelay AnalyzerPricingThe monthly update cycleCPM scheduling tool for controllersSchedule UpdaterSchedule fragnet analysisMCP for construction schedulingCollaborative CPM schedulingFree CPM schedulingAI schedulingAI linked schedulingLet Claude or Codex scheduleFree toolsGlossary
FAQ
Questions about the round trip
The Flowchart fetches the .XER from Pathizer, where it already is, and hands it to the P7 tab inside your browser. P7 asks before it imports it, and sends nothing about the schedule to Pathizer.
Those who may download the Schedule Updater's .XER, which are the project's Controllers.
Yes. Download the .XER from the Schedule Updater, import it in P7 with File > Import, and drop the .XER you save on the Health Check step.
Because it is not published yet. Pathizer scores it in a place of its own, and only Publish adds it to File Storage as an update.
The analysis of the new update: Pathizer writes the narrative, files the reports and runs the delay analysis. The due date moves on by the cycle, and the Schedule Updater opens for the next period.
No. Pathizer takes .XER files and the .XML and SDEF formats File Storage lists, from whatever software saves them. P7 is the free option, and the one the Flowchart opens directly.
P7 runs in your browser with no account, and your schedule stays on your device.
Open P7 Free Scheduling