Consultants

Consultant 360 — empanelment, fee history, performance, deliverables — built so the same brief is not re-written every project.

What it is

engages 6–10 consultants per project across architecture, structure, MEP, façade, ID, landscape, lighting, and specialist trades. The consultant network module captures empanelment, terms, fee history, past performance, current load, and deliverable record per consultant. Project briefs reference the master record, not a fresh document. The rehiring decision sees the same data the original hiring did.

Inputs

Triggers

·New project registered in M03
·Discipline-specific consultant requirement identified by Design
·Empanelment review cycle (annual or event-driven)
·Consultant performance review prompted by project closure

Data reads

·Project record with scope, segment, location
·Existing consultant master with performance history, fees, current load
·Discipline-specific empanelment criteria from CPT
·Past project outcomes per consultant

Artefacts consumed

·Consultant credentials, registrations, past project portfolio
·Fee proposals
·NDA and IP terms
·Design Basis Reports (DBR) per discipline

Tools & Techniques

Methods

·Outcome-based performance scoring across past projects
·Current-load capacity check across all active engagements
·Discipline-specific brief generation from project record
·Concept-iteration workflow with versioned reviews

Policies

·consultant empanelment policy with discipline-specific criteria
·Fee structure policy and benchmarks
·NDA and IP policy for design work
·DBR policy per discipline

Decision rules

·Empanelment requires KYC plus reference check plus site visit
·Re-engagement informed by performance score, not relationship inertia
·Capacity above 90% on existing engagements blocks new package award
·DBR sign-off required before concept design begins

Outputs

Artefacts produced

·Consultant master record with continuously updated performance
·Empanelment contract and engagement letter per project
·Discipline-specific design brief per project
·MEP DBR and discipline DBRs per project
·Performance evaluations fed back to master record

Data writes

·Consultant record updated on engagement, performance, exit
·Project record updated with engaged consultants per discipline

Downstream triggers

·Engaged consultants begin concept and detail design in M07
·MEP DBR drives calculation work in M08
·Consultant performance signals feed into future empanelment decisions

Stakeholders

DesignIdentifies required consultants, owns brief, reviews iterations
CPTEmpanelment, fee negotiation, contract
MEP DesignDiscipline-specific MEP DBR (Design Basis Report)
ConsultantsDeliver design per brief and policy

The flow

01Identify consultants required by discipline
02Empanelment with terms, fee, NDA, IP
03Issue design brief with project record reference
04MEP DBR — loads, systems, redundancy, codes
05Concept iterations and reviews
06Performance capture fed back to empanelment record

State change

Before

Consultant engagement is one-off per project; performance is not durable data.

After

Consultant has a persistent record; engagement and rehiring are evidence-based.

Real-world example

Worli project — 8 consultants engaged. MEP consultant (Mahindra Consulting) selected based on previous performance score of 4.2/5 on three projects. Architectural concept iterates three rounds in ACC; v3 approved by MD with one comment on lobby.

Artefacts

·Consultant master record
·Empanelment contract
·Design brief per discipline
·MEP DBR per project
·Concept iteration history
·Performance evaluations

Pain today

Same brief is rewritten every project. Past performance lives in design heads, not on the record. Fees vary between projects with no visibility into why.

Integrations

No external system integrations — module operates on internal records.