- Aconex is the system of record for project documents. It stores, routes, and tracks. That is what it is designed to do, and it does it exceptionally well.
- Provan is the intelligence layer above the document layer. It reads from Aconex and surfaces what those documents mean for your contract obligations, your claim exposure, and your project risk.
- Aconex alone tells you what exists. Provan tells you what it means.
- On large NZ infrastructure projects, Tier 1 contractors and asset owners almost always run Aconex. Provan is designed to sit alongside it, not replace it.
- Smaller projects without Aconex can still run Provan. The intelligence layer works with whatever document system you are using.
What is Aconex and what does it do well?
Aconex is Oracle's construction and engineering document management platform. It has been the dominant document control system for large NZ infrastructure projects for well over a decade, and for good reason. When you are managing a project with dozens of organisations, hundreds of subcontractors, and tens of thousands of documents flowing between them, you need a purpose-built system of record. Aconex is that system.
The platform handles document management with version control and audit trails, transmittal workflows between project parties, RFI management and correspondence tracking, approval and review workflows, and access control across multi-organisation project teams. It is cloud-based, built for the construction industry, and deeply embedded in how Tier 1 NZ contractors and major asset owners manage project documentation.
For any large NZ infrastructure project, Aconex solves a real and important problem. Without a document control system of this calibre, projects of any scale face document version confusion, audit trail gaps, and transmittal disputes. When adjudication or litigation arises, the Aconex record becomes the project's documentary evidence. That matters enormously on NZS 3910 contracts where the timing and form of notices, claims, and approvals can determine the outcome of disputes.
Oracle's acquisition of Aconex in 2018 has expanded its enterprise integration capabilities and brought it into Oracle's wider portfolio of construction technology. The platform is now also part of the Oracle Construction and Engineering suite, which includes scheduling, contract management, and analytics tools.
Best-in-class document control for large multi-party projects, deep integration with NZ's Tier 1 contractor and asset owner workflows, robust audit trail for dispute resolution, and long track record on major NZ infrastructure. If your project is $50M+ and involves multiple organisations, Aconex is likely already in play or will be required by your owner.
What does Provan do that Aconex doesn't?
Aconex stores and routes. It does not interpret. That distinction is where Provan operates.
The documentary record on any large NZ infrastructure project contains the full story of the project's commercial health. Every RFI that was left unanswered too long. Every instruction that wasn't confirmed in writing. Every variation notice that didn't follow the NZS 3910 timeframe. Every payment schedule that was issued a day late. The signals are in the documents. Aconex stores them all faithfully. But it does not tell your contract administrator what they mean.
Provan reads that documentary record and surfaces the intelligence your team needs to act on it. The system understands NZS 3910 and the Construction Contracts Act 2002 natively. It maps every obligation in your contract, tracks the deadlines associated with each, and monitors the documentary record for signals that obligations are approaching or have been missed.
Specifically, Provan surfaces things that Aconex does not:
- Obligation deadlines approaching. Clause 19.2 payment schedule response deadlines. Clause 7.1 variation approval timeframes. Practical completion notice periods. These are tracked against the contractual clock, not just filed as documents.
- Claim risk signals in the correspondence trail. An RFI that went unanswered for three weeks can be the foundation of a delay claim. A pattern of late instructions buried in the transmittal register can tell a commercial story. Provan reads that pattern and flags it before it becomes a formal claim.
- Cost reconciliation across the broader data stack. Most projects run Aconex for documents but Excel for cost. Provan integrates both layers, reconciling what the documentary record shows against what the cost reports say.
- Document compliance gaps. Where the contract requires written confirmation and none exists. Where a notice form was not followed. Where the approval workflow shows a decision was made but the formal record is absent.
Your contract administrators and project managers already do this work. They read the documents, make judgements, and raise concerns. Provan does not replace that judgement. It makes sure they see everything they need to see to make it well.
Where do Aconex and Provan overlap?
The honest answer is: less than you might expect.
Both systems deal with project documents. Both can surface information about what is happening on a project. But they approach this from fundamentally different directions. Aconex is organised around the document as the unit of work. Its purpose is to get the right document to the right party with a clean audit trail. Provan is organised around the contract obligation as the unit of work. Its purpose is to surface whether those obligations are being met.
There is some functional overlap in reporting. Aconex produces transmittal registers, RFI logs, and approval status reports. Provan produces obligation status dashboards, deadline alerts, and risk summaries. A senior project manager reviewing both would see some of the same underlying data presented in different ways. But the analytical layer is different, and so is the action it drives.
One area where overlap creates a genuine decision point is in RFI and correspondence tracking. Aconex tracks every RFI: who raised it, when, who it was sent to, when it was responded to. Provan reads that record and interprets the commercial significance of what it shows. You need Aconex to create and maintain the reliable record. You need Provan to understand what that record means for your exposure.
When is Aconex alone sufficient?
For some teams and some project situations, Aconex alone is sufficient, and it is worth being honest about this.
If you have highly experienced contract administrators who deeply understand NZS 3910, read the documentary record regularly, and have reliable systems for tracking obligations manually, Aconex gives them an excellent platform to work from. The intelligence is there in the documents. Experienced people can extract it without a dedicated intelligence layer.
The gap tends to emerge at scale. One experienced contract administrator running a single $40M project can hold a great deal of the obligation picture in their head and in their own tracking spreadsheets. The same person running three concurrent projects at once, or a senior contract administrator mentoring junior staff, or a PMC managing obligations across a portfolio of eight projects for different clients, starts to find the manual approach breaks down. Not because the person is less capable. Because the volume and complexity exceeds what any individual can reliably track without systematic support.
Aconex alone is also sufficient when the project is relatively short, simple in its contractual structure, and does not have a commercially aggressive counterparty. The more complex the project, the more parties involved, and the more money at stake in unresolved variations and claims, the more the gap between "we have the documents" and "we understand our exposure" starts to cost real money.
When does adding Provan make sense?
The decision to add Provan alongside Aconex is almost always driven by one of three situations.
The first is scale. Projects above $50M running for more than 18 months accumulate a documentary record that becomes genuinely difficult to manage manually. Variation registers run to hundreds of rows. RFI logs contain thousands of items. Correspondence threads across dozens of parties span years. At that scale, having a system that reads the record and surfaces what needs attention is not a luxury, it is a risk management decision.
The second is commercial aggression. Some contracts, and some counterparties, are inherently more commercially aggressive than others. On a project where the contractor is an experienced claim preparer and the owner knows it, having an intelligence layer watching the documentary record for early signals of a building claim position is worth far more than its cost. The signals are usually visible months before a formal claim arrives. Provan surfaces them when there is still time to act.
The third is capability gaps. Not every project team has a deep NZS 3910 expert reviewing the documentary record regularly. Many NZ asset owners, government agencies, and smaller PMC firms have capable project managers who are not specialist contract administrators. Provan is designed to support those teams, making sure the obligation picture is visible even when there is no resident expert monitoring it full time.
A missed time bar on a variation claim can extinguish the right to recover costs that are genuinely owed. A payment schedule issued even a day late under the Construction Contracts Act can turn a disputed amount into an immediately payable debt. The documentary record is in Aconex. But nothing in Aconex alerts you when the clock is about to expire.
Can Provan read from Aconex?
Yes. Aconex provides an API that allows authorised third-party systems to read project data. Provan is designed to connect to Aconex through this integration layer, pulling documents, transmittals, RFI records, and correspondence into the intelligence layer for analysis. Your data does not leave your project environment. Provan reads what Aconex holds and runs its analysis on the data it receives.
The practical scope of the Aconex integration is confirmed during the Discovery phase of each Provan engagement. Different projects have different Aconex configurations, different module sets, and different access structures. Some clients have Aconex administered by their owner and need to request API access as part of the project setup. Others control their own Aconex environment and can configure the connection directly. Discovery is the right place to scope this, not a product brochure.
What the integration enables is this: rather than your contract administrator downloading a transmittal register from Aconex and manually cross-referencing it against the obligation register, Provan does that work continuously. The intelligence layer reads from Aconex, interprets the record against the contractual framework, and surfaces what needs attention. Your administrator makes the decisions. The system makes sure they see everything they need to.
What about smaller projects without Aconex?
Most NZ projects below $30M-$40M do not use Aconex. The platform's cost and complexity are justified by the document volumes and multi-party structures of large infrastructure projects. Smaller projects typically manage documents through Procore, SharePoint, structured shared drives, or a mix of email and filing conventions.
Provan is not Aconex-dependent. The intelligence layer is designed to read from whatever documentary record your project maintains. If you are running documents through Procore, Provan can connect to Procore's API. If you are on SharePoint, Provan can read from the SharePoint structure. If you are managing documents through a conventional shared drive and email, Provan can ingest from those sources too.
The intelligence Provan surfaces is not contingent on what document control system sits underneath it. It is contingent on having a reliable documentary record to read from. If your document management is organised and consistent, Provan can work with it. If it is chaotic, Provan's first contribution is usually helping establish the structure the intelligence layer needs to operate.
This means that for a $25M NZ project without Aconex, running on Procore and Excel, Provan still surfaces the same obligation tracking, the same deadline alerts, and the same risk signals. The document control layer is different. The intelligence layer works the same way.
Aconex vs Provan at a glance
| Aconex (Oracle) | Provan | |
|---|---|---|
| Primary purpose | Document control and project communication | Intelligence layer above the document record |
| What it stores | Documents, transmittals, RFIs, approvals, correspondence | Obligation registers, risk signals, deadline alerts, intelligence outputs |
| What it surfaces | Who has the document, its status, its version history | What the documents mean for your contractual obligations and commercial exposure |
| NZS 3910 understanding | Not built in. Documents stored but obligations not interpreted | Native. Purpose-built obligation mapping for NZS 3910, NZS 3916, CCA 2002, FIDIC |
| Who uses it | Document controllers, project teams, all project parties | Project directors, contract administrators, senior PMs, PMC principals |
| How it integrates | Central system — other tools connect to it | Connects to Aconex, Procore, Excel, SharePoint, and other existing systems |
| Deployment model | Oracle cloud, subscription via Oracle sales | Deployed on client infrastructure, owned by client |
| Pricing model | Contact Oracle for current pricing | Value-based. Contact Provan for details |
| Best fit | Large multi-party infrastructure projects ($30M+) requiring rigorous document control | Any project where obligation visibility and risk intelligence matter |
Oracle does not publicly publish per-project or per-user Aconex pricing. If you need a current quote, contact Oracle directly. Provan pricing is based on project scope and the value the intelligence layer delivers. Contact us for details on either. Published per-user figures from third-party comparison sites are frequently outdated and should not be relied on.
Why Aconex's position in NZ infrastructure is well earned
This article is a comparison, not a sales pitch against a competitor. Aconex is a genuinely excellent platform that has earned its dominant position in NZ infrastructure for good reasons. It is worth being clear about that.
The construction industry is notoriously conservative about technology, and with good reason. Projects are long, contracts are complex, and the cost of a failed tool implementation mid-project is significant. Aconex has been in the NZ market for over a decade. Tier 1 contractors, government agencies, and major asset owners have built their document control workflows around it. The institutional familiarity with the platform is itself a value driver. Your document controller knows it. Your subcontractors know it. Your counterparty's team knows it. That shared familiarity reduces friction significantly.
Aconex also has a serious track record in dispute resolution. When claims go to adjudication or litigation in New Zealand, the Aconex record is frequently the primary evidentiary source. The audit trail it creates is comprehensive, tamper-evident, and structured in a way that courts and adjudicators find navigable. That is a genuine capability that should not be taken lightly.
Oracle's backing means the platform continues to develop. The integration with Oracle's broader construction suite, and the ongoing development of its analytics and reporting capabilities, means Aconex is not standing still. For large projects, it remains the platform against which others are measured.
The honest framing is this: Provan is not positioned against Aconex. It is positioned to do what Aconex does not do. That is a collaborative positioning, not a competitive one. Aconex stores your project's documentary record with rigour and reliability. Provan reads that record and tells you what it means. Both layers matter. The right question is not which one to choose. It is whether you have both layers covered on your project.
See What the Intelligence Layer Looks Like in Practice
Send us one contract from a live project. We surface the obligations, the deadlines, and the risk exposures your team should know about. Then show you what a systematic intelligence layer looks like deployed inside your business. No commitment. No obligation.
Book a Working Session Or email stephen@provan.ai