AI Agents Are Lining Up at the Schedule's Door
In eight days in October, Oracle, Procore and Planera announced ways for outside AI agents to reach project and schedule data. For planners, the question is no longer whether AI can read the programme, but who gets to change it.
On 21 October, as Procore's Groundbreak conference opened in Orlando, a scheduling start-up called Planera launched an AI agent with a narrow, almost modest job. It reads the open RFIs in Procore, checks them against the critical path and the look-ahead in Planera, and reports which ones could stall work in the coming weeks. The example output in the press release is one line long: "You have 4 open RFIs that could delay work in the next 21 days."
The agent itself is small. What it plugs into is not.
In the space of eight days, Oracle, Procore and Planera each announced ways for AI agents, including general-purpose ones like Claude and ChatGPT, to reach directly into project and schedule data. For three decades the programme has been a file that only scheduling software could open properly. It is turning into a live data source that any approved agent can query. For planners, the question is shifting from whether AI can read the schedule to who, or what, is allowed to change it.
Eight Days in October
Oracle went first. On 21 October it announced AI Agent Studio for Industry Applications, a no-code and low-code environment for building agents on top of its industry software, including engineering and construction. Oracle's own construction example is an agent that identifies risks to schedule milestones, finds the related field issues and proposes mitigation steps. It supports MCP (more on that below), lets customers choose among models on Oracle's cloud, and tracks "AI-unit consumption" so that someone, somewhere, can see the bill coming. The fine print matters: the studio is planned to arrive within the next 12 months, in the US first.
A day later Procore opened its Agent Marketplace with 15 partner-built agents. They cover reality capture, safety, payroll, prequalification and document checks, plus Planera's schedule-risk scanner, the only entry filed under "Schedule Risk & Project Controls". Usage draws on Procore AI credits. Procore's own illustration of the idea starts in a site trailer: a user reviewing the schedule realises they need temporary power, asks Procore AI for a generator, and a partner agent checks equipment specifications against the schedule before handing the decision back to the human. By the end of the conference, Procore was also promising Procore AI MCP, which lets companies connect their enterprise Claude environment to Procore, with other AI providers to follow in 2027.
On 28 October Planera announced upcoming support for the same protocol, so that teams can query live CPM schedules from inside Claude or ChatGPT.
Every System Gets a Socket
The common thread is the Model Context Protocol, or MCP, which Planera's release describes as "an open standard" for connecting AI assistants to enterprise applications and databases. Think of it as a universal socket. Instead of exporting an XER file and pasting chunks of it into a chatbot, an agent asks the scheduling system a question and gets an answer back from the system itself.
Procore's AI chief put the strategy plainly in Planera's announcement. "The future of AI isn't one agent doing everything," said Thiago da Costa, Procore's SVP of AI and data. "It's an ecosystem of specialized agents working together." Procore describes the marketplace the same way: agents "reach across systems instead of copying them", with each side keeping its own data and security model.
For project controls this is a bigger shift than another chatbot. RFIs, submittals and daily logs already have agents of their own, as the launches above show. The schedule, the one artefact every other workflow eventually points back to, is now being wired into the same network.
Bring Your Own Agent
The platforms are not the only ones building sockets. Consultancy RPC said it would show AI agents built inside Oracle Database 26ai that let users interrogate Primavera P6 EPPM data in plain language, at a Primavera user event in London on 15 October. Open-source projects such as pyp6xer-mcp already expose XER parsing, float and schedule-quality checks to any MCP-capable agent. They are community-built and unvalidated, but they show how low the barrier has become.
Autodesk is moving more slowly. At Autodesk University in September it showed construction agents for document search, submittal review, bid proposals and spoken daily logs. Its broader next-generation assistant, which works across projects, is due to begin rolling out in 2027.
For three decades the programme has been a file that only scheduling software could open properly.
Permission Slips
If agents can reach the schedule, the controls around that reach become the product. Every vendor in this round leads with them.
Procore says marketplace agents use per-user OAuth, so an agent "never sees more than what that person already has access to". An admin approves each agent and chooses the projects it applies to, and a new Control Tower gives admins visibility of AI usage. Oracle's studio promises guardrails tied to roles and permissions, plus testing, tracing and monitoring before and after deployment. Planera says its scanner writes a note on the affected activity but that "dates and logic change only through Planera's change controls".
That last line is the one schedulers should underline. Reading the programme is one thing. Writing to it is where baselines, claims and contractual dates live, and where an unaudited change can cost far more than the time it saved.
The Case for Caution
There are good reasons not to get carried away. Much of what was announced is not yet generally available. Oracle's studio is up to a year away, Autodesk's assistant starts rolling out in 2027 and Planera's MCP support was announced as upcoming. Marketplace agents are, by design, built by third parties whose accuracy the platform does not guarantee.
The vendors also say little about how well these agents perform. Newforma, which bought the analytics start-up Lumi AI the same week, set out three tests for project AI: answers must be explainable, verifiable against source data, and accurate enough to act on when liability is in play. None of the October launches published results against tests like these. Planera's own claim, that schedulers and superintendents spend "as much as two to three days a week" matching RFIs to the schedule by hand, is a vendor figure, not a measured one.
And an agent that reads a bad schedule fluently is still reading a bad schedule.
What It Means on Monday
For a project controls team, the practical consequences arrive before the products do. Someone has to decide which agents may connect to the scheduling system, whose permissions they run under, and whether any of them may write. Someone has to own the audit trail. If your organisation already has an enterprise Claude or ChatGPT licence, expect a colleague to ask why it can't just talk to P6.
The safest early pattern is the one the vendors themselves are advertising: agents that read widely, flag specific activities and leave every change to the scheduler. The riskier pattern is quieter. It is a growing web of connections that nobody in project controls signed off.
Planera's press release contains the most honest sentence of the month. When its agent cannot match an RFI to an activity with confidence, it reports it as unmatched instead of guessing, "because a false match in a schedule is worse than a miss". As the agents line up at the schedule's door, that is not a bad rule for letting them in.
Method. Sources were checked on 1 November 2026. Product capabilities and availability dates are as announced by each company, not independently tested. The RPC demonstration is described from the company's own LinkedIn announcement. The trend scan behind this issue is summarised on the issue page.