The Tender Submission That Looks Like Everyone Else's
I have sat in tender debriefs where the client told us they scored three firms within two points of each other. The CVs were comparable. The methodology sections were near-identical. The track records overlapped on similar projects. The fee proposal was the tiebreaker, which meant the cheapest firm won, not the best one.
This is the reality for most PMC firms submitting on NZS 3910 projects in the $30M to $200M range. You are competing against firms with equally qualified people, equally relevant experience, and equally polished submissions. Your people section lists the same registrations. Your methodology section describes the same reporting cycles. Your risk management approach uses the same language.
When every firm says "our people are our differentiator," nobody is differentiated. The evaluation panel is left comparing CVs line by line, and the decision comes down to price or personal relationships.
What Evaluation Panels Actually Want to See
Evaluation panels do not score on claims. They score on evidence. There is a meaningful difference between a firm that writes "we have a robust methodology for contract administration" and a firm that shows a live dashboard with every obligation from a comparable contract mapped, tracked, and colour-coded by urgency.
One is a sentence. The other is proof.
The shift happening right now in NZ construction procurement is that clients are beginning to ask harder questions about how firms actually deliver. Not what they will do, but how they will do it. Not which people they will assign, but what systems those people will use. This is a direct response to too many projects where the promised methodology existed only in the tender document and never made it to site.
If your tender submission cannot show the panel something tangible, something that proves your methodology is real and operational, you are competing on words against firms that are also competing on words.
The System Is the Differentiator
The firm that can demonstrate a live obligation tracking system during a tender interview has a differentiator that no CV can match. It is tangible, visible, and impossible to fake.
Consider what this looks like in practice. You walk into the tender interview. The panel asks how you will manage contract administration on a project with 180 Special Conditions amendments. Instead of talking about your team's experience, you show them:
- Every obligation from a comparable NZS 3910 contract, mapped and categorised by party, deadline type, and risk level
- Automated tracking for every Construction Contracts Act payment deadline, with zero tolerance for missed windows
- A daily priority view showing exactly what needs attention today, not buried in a spreadsheet but visible at a glance
- A full audit trail of every notice, instruction, and correspondence linked to the relevant contract clause
The panel can see that this is real. It is not a promise. It is a working system. They can ask questions about it. They can see how their specific contract would be managed. The other four firms in the room are still talking about their methodology.
More clients are asking "what technology do you bring to this engagement?" in tender interviews. If your answer is "Microsoft Project and email," you are already behind. Read more in Why Construction Clients Are Asking About Technology.
Why CVs Are Necessary but Not Sufficient
Let me be clear. People matter. Your senior PM with 15 years of NZS 3910 experience is genuinely valuable. Their judgement, their relationships, their commercial instinct cannot be replaced by any system. The tender submission absolutely should feature strong CVs.
But here is the problem: your competitor has a PM with 15 years of NZS 3910 experience too. Possibly the same one who used to work for you. The CV arms race has reached a point where everyone has comparable people, and the evaluation panel knows it.
The firms that are growing their capacity without simply adding headcount are the ones that combine strong people with strong systems. The system does not replace the PM. It ensures that the PM's expertise is captured, their obligations are tracked, and their project can survive if they are reassigned, promoted, or (let's be honest) headhunted by the client halfway through.
That message resonates with evaluation panels because they have all experienced the problem. They have all had a PMC firm's star PM leave the project and watched the quality drop. A system that prevents that outcome is worth scoring higher.
What This Looks Like in a Tender Submission
The tender document itself needs to change, not just the interview. Here is how to restructure the methodology section:
- Section 1: Project Intelligence. Describe how you ingest and map every obligation from the head contract, including all Special Conditions. Show a sample obligation register from a comparable project. Include a screenshot of the live tracking dashboard.
- Section 2: People + System. Present your team not as standalone individuals but as professionals operating within a system. Explain what the system does for each role. The PM gets daily priorities. The contract administrator gets automated CCA deadline tracking. The project director gets a weekly risk digest.
- Section 3: Continuity. Address key person risk directly. Explain that the contract knowledge lives in the system, not in one person's head. A replacement PM can pick up the project at full capacity because the obligation register, correspondence history, and commercial context are all accessible from Day 1.
- Section 4: Reporting. Show sample outputs. A daily obligation summary. A weekly contract health report. A monthly risk dashboard. Make the panel see what their project director will actually receive.
The strongest tender submissions do not describe a methodology. They demonstrate one. The gap between "we will track obligations" and "here is how we track obligations, live, right now" is the gap between losing and winning.
Before your next tender submission, ask: "Could we show the evaluation panel a live demonstration of how we would manage their contract?" If the answer is no, you are competing on words. If the answer is yes, you have something most of your competitors do not.
The Firms That Move First Win
Right now, in early 2026, most PMC firms in New Zealand are still submitting tenders the traditional way. That means the window is open. The firm that moves first, that demonstrates a working project intelligence system in their next tender interview, takes a position that is very difficult for competitors to match quickly.
Building a credible system takes time. Configuring it with real domain knowledge takes experience. The firms that start now will have a demonstrable track record by the time their competitors realise they need to catch up. That is how market position is built: not by claiming to be better, but by being visibly, provably better in the room where the decision is made.
Your people are still your greatest asset. The system makes them visible.
Provan builds AI-powered operating systems for infrastructure and engineering businesses, covering six domains: Pipeline, Contracts, Projects, People, Finance, and Risk. The Pipeline and Contracts domains give PMC firms a tangible system to demonstrate in tenders, turning methodology claims into live capability that evaluation panels can see and score. Built from 10 years managing projects from $10M to $750M.
This article provides general commentary on tender strategy for construction project management firms. It is not legal, procurement, or financial advice. For specific tender or business development decisions, consult qualified professionals relevant to your situation.
Win More Tenders
Book a working session and we will show you what a live project intelligence system looks like in a tender interview.
Book a Working Session →Or email stephen@provan.ai