PMC Consultant vs Deployed Intelligence System

What does a PMC consultancy actually deliver?

A project management consultancy provides qualified professionals to plan, coordinate, and govern a project on an owner's behalf. That means someone with construction experience making real-time decisions, managing contractor relationships, certifying progress claims, assessing variations, and carrying professional accountability for how the project is administered.

The best PMC firms bring three things that no system can replicate.

The first is judgment. Knowing whether a contractor's EOT claim is legitimate, whether a variation instruction is properly described, or whether a subcontractor's performance is heading toward a dispute requires experience. Systems can flag signals. They cannot exercise professional judgment about what those signals mean in context.

The second is relationships. NZ's infrastructure and construction market is small. The experienced CA who knows how a contractor's commercial manager operates, who has worked with the engineer to the contract before, or who has managed a consent authority's process on a similar project is genuinely valuable. That institutional knowledge lives in people, not documents.

The third is accountability. When an owner engages a PMC firm, a qualified professional is carrying PI insurance and signing off decisions. That legal accountability is a real transfer of risk from the owner to the consultant. A system gives you information. A PMC firm takes responsibility for acting on it.

The PMC fee structure reflects all three. You are paying for a qualified professional's time, attention, and judgment: on your project, available when issues arise, and accountable for the quality of their advice. That time is fully billable. The question is not whether consultants should be billing for it; they should. The question is whether the owner is getting that professional's highest-value capacity, or whether a significant portion of the engagement is consumed by systematic work that a deployed system could handle more reliably.

What does a deployed intelligence system actually deliver?

A deployed project intelligence system does something different. It runs continuously across the entire documentary record of a project and surfaces what the people managing that project need to see.

That means extracting every obligation from a contract and its special conditions, mapping them against a timeline, and alerting when action is required. It means monitoring every piece of project correspondence for claim risk signals, programme deviations, and instruction ambiguities. It means tracking payment claim cycles under the Construction Contracts Act 2002, flagging when a payment schedule is due, and generating a daily briefing on where the project's documentary record stands.

Systems do this without fatigue, across every document, on every project simultaneously. A senior CA reviewing a 250-page contract with 80 special conditions will identify the major obligations. They will miss some. They will not re-read the whole contract when a new variation instruction arrives six months later. A system does.

What a system does not do is make decisions. It surfaces information and flags risk. The professional still needs to assess it, interpret it in context, and decide what to do. The value of a deployed intelligence system is in raising the floor of what gets seen, not in replacing the people who act on it.

Provan is built on this model. Deployed on the client's infrastructure, owned by the client, and configured from 10 years of hands-on construction project management experience. It is not a SaaS subscription. It is a permanent business asset that keeps running whether or not a specific consultant is engaged on a project.

Where do the two overlap?

The overlap is in the systematic, document-intensive work that experienced PMC professionals are trained to do but that consumes time that could go toward advisory engagement.

Obligation tracking, deadline monitoring, variation register maintenance, RFI log management, payment schedule tracking, and correspondence review are all things that good PMC firms do as part of their engagement. These tasks require discipline and consistency, but they do not require professional judgment in the same way that assessing a contractor's extension of time entitlement does.

When these tasks are handled by a deployed system, two things happen. The PMC's professionals spend more of their time on advisory work, the high-value engagement that owners genuinely need qualified people for. And the systematic work gets done more consistently than any individual can manage across a full project portfolio.

This is the productive overlap: not competition between the consultant and the system, but a reallocation of where each party's capacity goes.

When is a PMC consultancy the right answer alone?

There are clear situations where a PMC firm is what an owner needs, and where a deployed intelligence system would be secondary at best.

The first is when the owner has no internal construction capability. If the owner's team has never administered a construction contract, needs someone to carry the Contract Administrator role under NZS 3910, and cannot assess contractor performance independently, they need a PMC firm first. The system provides information. The owner still needs someone qualified to act on it.

The second is complex stakeholder and interface environments. Multi-contractor projects, projects with significant design development risk, or projects involving iwi, heritage, or consent processes that require active relationship management need a human presence. These are judgment-intensive and relationship-dependent. A system is not a substitute.

The third is where the project involves specialist delivery domains outside the owner's experience. An infrastructure owner running their first large civil project, or a corporate developer managing a design and build for the first time, needs qualified professionals who have been in those situations before. Experience cannot be systematised.

For these owners, the right answer is a strong PMC engagement. The priority is getting the right firm with the right experience. A deployed intelligence system may complement that engagement, but the PMC firm is the primary investment.

When is a deployed system the right answer alone?

There are also situations where an owner has sufficient internal capability but is operating without a systematic intelligence layer, and that gap is the real risk.

Asset owners and government entities with experienced in-house project teams often have capable people who understand construction delivery. What they lack is a systematic layer that ensures their people see everything across a large portfolio. Their PMs are experienced enough to act on information. The problem is that the information is not being surfaced consistently.

In this situation, the value of a deployed intelligence system is straightforward. The existing team gets better information, faster. Obligations that were previously tracked through spreadsheets and individual vigilance are now tracked systematically. Claim risk signals that would have been buried in a correspondence file are surfaced automatically. Board reporting that previously required manual assembly is generated from live project data.

For organisations like councils, Crown entities, or corporate infrastructure owners with dedicated capital works teams, a deployed system is often the highest-leverage investment they can make. Their constraint is not professional capability; it is systematic visibility across a portfolio that is too large to manage manually.

When do you need both?

Most asset owners running programmes of more than two or three concurrent projects end up in a position where they need both. The PMC firm provides delivery leadership, accountability, and professional judgment on individual projects. The deployed system provides portfolio-level visibility, continuous documentary surveillance, and institutional memory that persists across project cycles and staff changes.

The practical dynamic works like this. The PMC firm is engaged on specific projects or programme phases. Their professionals are on-site, in meetings, reviewing contractor submissions, and making decisions. Between those moments, the system is monitoring the documentary record, tracking obligations, and flagging anything that needs attention before the next engagement. When the consultant arrives for their next review, they are not starting from scratch. They have a current picture of where the project stands and what has moved since they were last in the room.

This is where the combination generates the most visible value: the consultant's time goes further because the system is handling the systematic layer, and the system's output is acted on by people with the professional judgment to interpret it correctly.

Owners who operate this way consistently report that their PMC engagements feel more productive. The consultants are spending their time on what they are actually engaged for. The owner is getting more advisory value from the same fee.

How do the commercial models differ?

The commercial structures are meaningfully different, and it is worth understanding both before deciding where to invest.

Dimension	PMC Consultancy	Deployed Intelligence System
What you get	Qualified professionals managing delivery, administering contracts, and carrying accountability for their decisions	Continuous obligation tracking, documentary surveillance, deadline alerts, risk signals, and decision-support across every project in the portfolio
What you don't get	Continuity between engagements; systematic coverage of the full documentary record at all times	Professional judgment, relationships, legal accountability, or someone to act on the information the system surfaces
Commercial model	Rate-based (daily, hourly, or percentage of construction value). Scales with project duration and complexity.	One-time build and configuration fee plus ongoing maintenance retainer. Does not scale linearly with portfolio size.
Continuity	Project-by-project. Engagement ends when the project ends, and institutional knowledge leaves with it.	Continuous. Runs across the full portfolio, accumulates project history, persists through staff changes.
Knowledge retention	Resides with the consultant. Departs when the engagement ends or key personnel change.	Embedded in the system on the owner's infrastructure. Permanent business asset.
Capacity model	Constrained by professional headcount. Adding projects requires adding consultants.	Runs across the entire portfolio simultaneously. Capacity does not reduce as projects increase.
Decision authority	Consultant makes decisions within delegated authority and carries PI exposure	System surfaces information and flags risk. Humans retain all decision authority.
Best for	Owners who need someone else to carry delivery risk; projects requiring judgment, relationships, and professional accountability	Owners with internal capability who need systematic portfolio visibility; organisations where knowledge retention and consistency are the primary constraints

The financial comparison is not straightforward because the two investments serve different purposes. A PMC fee is the cost of having qualified professionals managing your project. A deployed system build fee is a one-time investment in a permanent business asset. The right question is not "PMC or system this year." It is: what is the total cost of the professional advisory I need, and does a deployed system make that investment go further over time?

For most owners, the answer is the latter. A deployed intelligence system does not reduce the need for qualified PMC advisory. It means the advisory time the owner is already buying is spent on higher-value work.

What about smaller programmes that cannot justify either?

Not every owner is running a $300M portfolio. A developer with one $60M project, a council with two or three capital works projects, or a corporate owner managing their first major construction programme may find that a full PMC engagement plus a deployed intelligence system is more infrastructure than their situation requires.

For these owners, there are two practical approaches.

The first is a targeted PMC engagement scoped to the highest-risk phases rather than full end-to-end delivery. A PMC firm engaged for procurement, contract formation, the first three months of construction, and project completion (with the owner managing the middle phase using clear protocols) can provide essential professional oversight at a proportionate cost.

The second is a Business Intelligence Review: a specialist reviews the contract, surfaces the obligations and risk exposures, produces a clear obligation register, and delivers a working session to brief the owner's team on what they need to manage. This is Provan's entry offer. Send one contract, get a clear picture of what matters, and understand what a systematic intelligence layer would look like deployed inside the business. No commitment. No ongoing cost. Just visibility.

For owners who grow beyond a single project, the decision point typically arrives naturally: when managing obligations across multiple projects manually becomes the constraint, and when the cost of what gets missed exceeds the cost of deploying a system.

A deployed intelligence system becomes a permanent business asset, present on the next project and the one after. Unlike a PMC engagement, which concludes with the project, the system stays. Its cost is borne once and its value compounds across every project that follows.