Intelligence Readiness Score

About You

What best describes your organisation?

Project management consultancy or construction advisory

We manage projects on behalf of clients — RCP, Greenstone, Octa, boutique PMCs

Engineering or multidisciplinary consultancy

Design, engineering, and advisory — Beca, WSP, GHD scale or similar

Main contractor or head contractor

We build — managing subcontractors, variations, and commercial risk

Asset owner, corporate, or utility

We own and operate assets — Fonterra, councils, port companies, infrastructure owners

Developer or project owner

We commission and fund projects — property developers, iwi entities, private investors

Government or Crown entity

Public sector capital works — ministries, crown entities, SOEs, local authorities

Construction or infrastructure law practice

We advise on contracts, disputes, and compliance

Pipeline — Question 01

How long does it take your team to prepare a tender proposal from scratch?

Weeks — we are pulling information from all over the place every time

CVs, project references, methodology, pricing — scattered across drives, emails, and people's heads

Days — we have templates but still spend significant time assembling content

The structure exists but the data is not centralised

Hours — team profiles, project experience, and pricing are in one system ready to assemble

The proposal is mostly configuration, not creation from scratch

Contracts — Question 02

How does your team track obligations and deadlines across your agreements?

Memory, email threads, and calendar reminders

Key dates live in people's heads or scattered across inboxes

Spreadsheets and shared documents

Tracked manually but requires someone to keep it updated

A system that maps and tracks obligations continuously

Deadlines are surfaced without anyone having to chase them

Projects — Question 03

How quickly could you identify every deadline across your active projects in the next 30 days?

It would take days of asking around and checking files

No single view exists

A few hours — we would need to pull together several spreadsheets

Data exists but it is scattered

Minutes — we have a live view across the portfolio

All deadlines surfaced in one place, updated continuously

Projects — Question 04

How does your team start each day on a live project?

Check email, open last week's minutes, figure out what is urgent

The day starts with searching, not acting

A task list or to-do board guides the day

Better structure but still manually maintained

A daily brief surfaces the top priorities, deadlines, and actions required

Every morning, the team knows exactly what matters without having to search for it

People — Question 05

If your most experienced person was unavailable tomorrow, what happens to their projects?

The project effectively pauses until they return

Critical knowledge lives in their head

Someone can cover the basics, but important details get missed

Handover notes exist but they are incomplete

The system holds the project memory — anyone can step in

Context, obligations, and deadlines are captured independently of individuals

People — Question 06

How much time do your senior people spend on administrative tasks versus the work clients are paying for?

More admin than advisory — most of their time is spent chasing information

Senior expertise is consumed by data entry, searching, and follow-ups

Roughly even — admin takes up a significant chunk but they still do productive work

Not operating at full capacity but getting by

Mostly productive — routine tracking and data work is handled by systems

Senior people focus on judgement, relationships, and strategy

Finance — Question 07

How do you track payment deadlines and variation exposure across your projects?

We find out when a payment is missed or a variation dispute surfaces

No systematic view of what is owed, what is claimed, or what deadlines are approaching

We track payments and variations per project but pulling a total picture takes effort

Data exists but is scattered — variation registers, payment schedules, and claims are in different places

We have a live view of payment deadlines, variation status, and total financial exposure

Nothing is unassessed, nothing is overdue, and the total position is always visible

Risk — Question 08

How do you identify emerging risks before they escalate?

We find out when something goes wrong

Risk management is reactive — problems surface as incidents

Regular meetings and reviews catch most things

Periodic check-ins work, but gaps between meetings can hide issues

Continuous monitoring flags risks as patterns emerge

Overdue actions, communication gaps, and deadline pressure are surfaced before they compound

Risk — Question 09

How do you track communication patterns and relationship health across your projects?

We do not — relationships are managed informally

No visibility into response gaps or escalation signals

We notice when things feel tense but there is no systematic tracking

Relationship issues are caught by instinct, not information

Communication gaps and response patterns are tracked and flagged

The system tells us when to pick up the phone before silence becomes a problem

Overall — Question 10

How consistent is the quality of delivery across your team and projects?

It depends entirely on who is assigned

Some projects run well, others have gaps — same firm, different outcomes

We have templates and processes, but compliance varies

The tools exist but not everyone uses them the same way

A system enforces consistency regardless of who is on the project

The standard is built into the workflow, not dependent on individuals

Your answers

Want to see what this looks like in practice?