Skip to content

Consortium Builder

Map what a project requires

Place the project at the centre, identify every capability it depends on, then assemble the partners able to cover them.

Worked example

Consortia usually fail on the capability nobody thought to map — facilities management, equipment servicing, systems integration. Mapping requirements before partners are approached is what surfaces those gaps while they are still cheap to close.

Project

Healthcare City

A concept program. Capabilities are mapped to show what a consortium would need to cover.

Required capabilities

Master Planner

Campus layout, phasing and clinical adjacencies.

Not yet assigned

Hospital Operator

Clinical operating model and staffing.

Not yet assigned

Engineering

Structural, mechanical, electrical and medical gas systems.

Not yet assigned

Construction

Delivery of a complex phased building programme.

Not yet assigned

Medical Technology

Imaging, laboratory and theatre equipment.

Not yet assigned

Finance

Structuring and arranging long-tenor capital.

Not yet assigned

Digital Health

Records, referral and clinical systems.

Not yet assigned

Facilities Management

Operation and maintenance across the campus life.

Not yet assigned

Collaboration groups

Authorised users can create a collaboration group against a project, invite partners into specific capability slots and track which requirements remain uncovered. A group is a working arrangement — it confers no procurement advantage, and NBP does not conduct the procurement through which delivery partners are ultimately appointed.