How we operate
How an engagement actually runs
What happens once MZA is appointed: how the mandate is bounded, what we test before proposing anything, what you receive, and the point at which our role ends and appointed delivery parties take over.
Operating principle
Advisory work is only useful if it ends in a decision
Infrastructure programmes rarely stall for want of analysis. They stall because nobody is positioned to take the next decision: the options are not framed, the constraints are not established, or the parties whose agreement is required have never been in the same conversation.
MZA is structured around that problem. Every mandate is scoped to a decision, every output is written for the person who has to take it, and the engagement is bounded so that both sides know what has been bought. What follows is how that works in practice.
Engagement lifecycle
From appointment to handover
Indicative timings. A defined mandate may compress the first three stages into weeks; a programme mandate may run the fourth for years. The sequence holds either way.
Weeks 1 to 3
Scoping
Establishing what the mandate is, and what it is not
Every engagement opens with a written scope: the decision the client needs to reach, the boundary of MZA’s role, the counterparties involved, and what is explicitly excluded. This is where most advisory relationships go wrong, because an unbounded brief produces work nobody asked for and leaves the real question unanswered.
- Decision the mandate has to serve
- Scope boundary and exclusions
- Counterparties and conflicts check
- Confidentiality terms agreed
Weeks 2 to 8
Diagnosis
Testing the programme against how it will actually be delivered
We establish the real constraints before proposing anything: the approving institution’s decision cadence, the capability genuinely present in the delivery market, the interfaces between packages, and the conditions financiers will attach. The output is a constraint picture the client may not like, but can plan against.
- Approval chain and decision cadence
- Delivery-market capability, verified
- Package interfaces and ownership
- Financing and procurement conditions
Ongoing
Structuring
Converting the diagnosis into a route the market can respond to
Packaging, delivery model and counterparty strategy are set together, because each constrains the others. We test the resulting structure against the sponsor’s institutional capacity rather than against best practice in the abstract, since a model the sponsor cannot govern will fail regardless of how well it reads.
- Packaging and delivery model
- Counterparty and consortium strategy
- Route to market and sequencing
- Readiness tested against evidence
Through execution
Coordination
Holding the interfaces while the programme is live
Through procurement, negotiation and mobilisation we manage the commercial and institutional interfaces between sponsor, contractor, technology provider and financier. The work is unglamorous: tracking conditions precedent, keeping positions aligned across jurisdictions, and surfacing issues while they are still cheap to fix.
- Tender and submission coordination
- Negotiation positions prepared
- Conditions precedent tracked
- Issues escalated early
Standing
Boundary
Where MZA stops
MZA advises, develops and coordinates. We do not build, engineer, finance, own or operate, and we are not licensed to arrange financing or give investment advice. Delivery is carried by the contractors, engineering firms and financiers the programme appoints. Where a scope needs capability we do not hold, we say so and help appoint someone who does.
- Advisory and coordination only
- No EPC, design or construction
- No ownership or operation
- Legal work sits with appointed counsel
Engagement shapes
Three ways MZA is engaged
They differ mainly in what ends the engagement, which is usually the most useful thing to establish early.
Defined mandate
Ends at a decision
A bounded piece of work aimed at one decision: whether to proceed, which delivery model to adopt, whether a market is worth entering, whether a counterparty is credible. Scope and output are fixed at the outset.
Best where the client knows the question but not the answer.
Programme mandate
Ends at a milestone
A continuing role across a programme stage, typically development through procurement, or procurement through financial close. MZA holds the interfaces and the timetable while the client holds the decisions.
Best where a programme is live and coordination is the constraint.
Market representation
Ends by agreement
A standing role representing an international organisation in a regional market: institutional relationships, opportunity origination, positioning ahead of tender, and qualification of local partners.
Best where an organisation wants a market without opening an office in it.
Outputs
What you receive
Every output is written to be used by a specific person for a specific decision, not filed.
Options and decision papers
The realistic options with their consequences priced, written for a board or steering committee rather than for another adviser.
Constraint and readiness reviews
What is genuinely blocking the programme, what has to be true before market approach, and the evidence for each.
Packaging and delivery structures
How the scope divides into biddable units, where responsibility passes between them, and who owns each gap.
Counterparty shortlists
Organisations qualified against the programme’s actual technical and financial requirements, not a directory extract.
Procurement and tender workplans
The sequence, documents and approvals required, set against the approving institution’s real decision cadence.
Interface and risk registers
Named owners for every interface and open issue, maintained through execution rather than produced once.
Working together
The practical terms
The questions that come up in every first meeting, answered here instead.
- Who you actually deal with
- The people who scoped the mandate run it. MZA is deliberately senior-led and compact, so there is no handover from the team that won the work to a team that delivers it.
- Reporting cadence
- Agreed at scoping and matched to the client’s own governance, typically a written position ahead of each decision point rather than activity reporting on a fixed calendar.
- Confidentiality and conflicts
- Conflicts are checked before scope is agreed and re-checked when counterparties change. Most mandates run under an NDA, and published project records are written to a confidentiality-appropriate level.
- Working alongside your advisers
- MZA coordinates with appointed legal, technical and financial advisers rather than replacing them. Where legal drafting or a licensed opinion is required, that sits with counsel.
Discuss an engagement
Tell us the decision you need to reach and we will tell you whether MZA is the right adviser for it.