In branch network programmes, the biggest procurement risk is not choosing a poor designer. It is choosing a firm that can design one beautiful flagship but cannot deliver repeatable, compliant, cost-controlled outcomes across a full network. This article looks at the questions procurement teams should ask before the shortlist becomes a delivery problem.
Stephen Voyle, Managing Director, Context Architects
Outline
- Why every shortlisted firm can show a flagship
- The shift from design firm to delivery firm
- Seven structural questions every tender should ask
- Sub-consultant liability, internal QS and single PO
- Test-fit speed and Premise Condition Reporting
- Live kit-of-parts manuals and lifecycle thinking
- Red flags hiding in confident tender language
- Weighting criteria for network versus flagship
Key Takeaways
Most bank branch tenders are evaluated on creative design strength and historical experience. Those criteria are necessary but insufficient. For a network-grade programme, the decisive question is not "who designs the best single branch?" but "who can deliver fifty branches at network scale, on time, on budget, with single-point accountability and a maintainable specification?" This article offers a seven-question evaluation framework grounded in that distinction.
- Design talent is necessary but not sufficient at scale
- Most tenders test flagship craft, not deployment capability
- Seven questions expose how a firm will really perform
- Sub-consultant liability and internal QS are decisive tests
- Rapid test-fit separates delivery firms from design firms
- A live kit-of-parts manual signals lifecycle readiness
- Fragmentation hides in confident-sounding proposal language
- Network programmes deserve different weighting to flagships
Introduction
If you have ever sat through a beauty parade of architecture firms presenting their bank branch portfolios, you will recognise the pattern. Each presentation opens with the same hero image. Each firm walks the panel through the same Pinterest-perfect flagship. Each emphasises its creative process, research methodology, and depth of bank-sector experience. And by the end of the day, the differentiation that mattered when you wrote the tender brief has quietly dissolved into a wash of indistinguishable competence.
This is the central problem with how bank branch design and delivery is typically procured in New Zealand. The shortlist process is optimised to identify the best designer of a single branch, when the actual challenge in front of you is the deployment of a coherent, compliant, cost-controlled programme across dozens of sites. Those are not the same problem. The skills that produce an award-winning flagship are not the same skills that produce predictable, repeatable, maintainable outcomes at network scale. If you are about to issue a tender, evaluating responses, or sitting on a shortlist panel for a multi-branch programme, the seven-question framework below is designed to expose how each firm will perform once the creative phase ends and the real work of network deployment begins.
The Shortlist Problem: Every Firm Can Show You a Beautiful Flagship
New Zealand's leading retail bank design firms have invested decades in compelling, award-winning case studies. Visit any practice website and you will find a curated reel of urban signature branches in Queen Street, Lambton Quay or Cashel Street. Most firms on your shortlist will arrive with comparable books. The flagship is the entry fee, not the differentiator.
The risk is that your evaluation panel mistakes design ambition for delivery capability. A firm that can render a striking single flagship can still struggle to roll out forty regional sites on a coordinated specification, on time, against an FM-friendly kit of parts. The two capabilities sit in different parts of the building lifecycle, and they are very rarely co-resident in the same firm. The shortlist that survives a flagship-led beauty parade is not necessarily the shortlist you want carrying out your network programme.
From Design Firm to Delivery Firm: Why the Distinction Matters
A pure design firm sells creative thinking and documentation. A delivery firm sells outcomes: on-budget, on-programme, on-specification, repeatable across many sites. At network scale, the second is what determines whether your business case survives contact with reality. Construction Industry Institute research, summarised in the Building Knowledge Base, shows that direct rework alone averages around 5 per cent of total construction cost and as high as 12 per cent on industrial projects, with most root causes traceable to design coordination breakdowns rather than site execution. Multiplied across a multi-branch programme, fragmentation becomes the single largest variable in your lifecycle cost.
Seven Questions Every Procurement Framework Should Include
1. How fast can the firm produce a defensible test-fit and Premise Condition Report?
Speed is not vanity in property work. A 48-hour rapid test-fit gives your Head of Property the data to negotiate landlord contributions before the head lease is signed. A Premise Condition Report identifies base-build defects that should sit with the landlord, not your CapEx. Ask each firm to demonstrate a recent example, with dates, deliverables and the negotiating outcome it enabled.
2. Does the firm take legal liability for sub-consultant technical design?
This is the most exposing question in a banking branch tender. Does the firm engage structural, fire and electrical engineers under its own purchase order and accept liability for their work, or does it pass that risk back to you? Many practices quietly assume the latter. The answer materially changes your insurance exposure across a programme.
3. Who carries the internal Quantity Surveyor function, and when?
In the conventional model, QS sits outside the design team and arrives late. The New Zealand Institute of Quantity Surveyors and equivalent international bodies have long argued that early-stage cost planning is the single highest-leverage cost intervention available. Ask whether QS capability sits inside the design team from feasibility, or arrives only after drawings are nearly complete. The difference shows up in variation claims twelve months later.
4. Is there a single purchase order and a single accountable contact?
Either one party absorbs architecture, design management, project management, contract administration and site observation under one engagement, or you are running a coordination layer. Both can work. Only one of them is defensible at network scale.
5. How does the firm manage long-lead procurement and direct supplier engagement?
Bank branches depend on specialist trades: vault doors, transaction counters, security systems, brand fixtures. Firms that procure these directly bypass main-contractor Preliminary and General margins. Firms that pass procurement back to a main contractor add a markup and a coordination risk. Ask which model is actually on the table.
6. Does the firm maintain an active, written network specification manual?
A live "kit of parts" specification is the strongest predictor of network-grade outcomes. Without it, every site becomes a bespoke project, and every component becomes a future Facilities Management problem. With it, FM teams can source replacements from a catalogue rather than reverse-engineer a one-off.
7. What is the firm's evidenced delivery timeline against industry benchmarks?
Integrated delivery research, summarised by the Associated General Contractors of America, consistently shows that integrated approaches compress programme by 30 to 50 per cent versus segregated traditional approaches. Ask each firm for evidenced average delivery cycles from feasibility to handover, not their best case.
Red Flags in Tender Responses
Watch for three recurring patterns. First, "we will appoint a project manager on your behalf" usually means the PM is still a separate contract you carry. Second, "we will recommend specialist sub-consultants for you to engage" means liability is bouncing back to your in-house team. Third, "we use industry-standard cost rates" without an internal QS function means cost engineering is happening after design lock, not before. None of these phrases is automatically disqualifying, but each shifts coordination risk back to the bank, and the cumulative effect of three or four such phrases is a tender response that promises a flagship and delivers a fragmented programme.
How to Weight the Criteria for a Network Programme
For a single flagship, weight creative expression highly. For a network programme of ten or more sites, that weighting will under-serve you. A defensible network weighting places roughly 40 per cent on delivery capability (single PO, internal QS, sub-consultant liability), 30 per cent on speed-to-market (test-fit, procurement, programme compression), 20 per cent on lifecycle and FM standardisation (kit of parts, digital twin documentation), and 10 per cent on creative track record. Most banks evaluate in roughly the inverse proportion, and most banks then overspend in years two and three. The framework is not the only answer, but it is a more honest reflection of where network risk actually sits.
Next Steps
The next post in this series moves from evaluation criteria to delivery model itself, examining what integrated, single-provider branch design deployment looks like in practice and why a growing number of New Zealand banks are choosing it over the fragmented multi-consultant approach. For further reading on long-cycle banking network deployment in New Zealand, the Context Westpac Network case study and the broader Context services overview offer practical reference points. If you would like to discuss your current tender process or shortlist confidentially, the Context team is available via https://context.nz/contact/.
Jump to the other blogs in this series here:
Why the New Zealand Bank Branch Is Being Repositioned (Not Retired) in 2026
The Hidden Costs in Bank Branch Programmes: Why Lifecycle Cost (Not CapEx) Determines Network ROI
Blog Author Bio - Stephen Voyle
Stephen Voyle is Managing Director, FNZIA at Context Architects, with more than 30 years of experience in the New Zealand construction industry. His perspective is shaped by the practical realities that sit behind major property decisions: governance, commercial performance, customer experience, compliance, delivery risk and long-term asset value.
In the retail banking sector, Stephen brings a clear view of why branch networks can no longer be assessed as simple refurbishment programmes or isolated design projects. The challenge for New Zealand banks is now more strategic: how to create physical environments that support trust, advisory conversations, accessibility, operational efficiency and repeatable network delivery.
Through these articles, Stephen explores the decisions property, procurement and customer experience leaders must make as bank branches are repositioned for a more digital, regulated and customer-led banking market.
Stephen Voyle, Managing Director, Context Architects