These three roles get used interchangeably often enough in Indian project conversations that the actual scope and fee differences between them are worth spelling out plainly, since confusing them genuinely leads to real gaps in project oversight rather than just imprecise terminology.
| Role | Typical scope | Typical fee basis |
|---|---|---|
| Development Management | Broadest - from feasibility and land acquisition through design, delivery and often disposal/leasing strategy | Highest, often a percentage of overall development value or a structured success-fee component |
| Project Management | Delivery-focused - schedule, cost, contractor coordination from design through construction and handover | Moderate, typically a percentage of construction value |
| Construction Management | Narrowest - construction-phase execution oversight, often with the CM holding trade contracts directly rather than a single main contractor | Moderate, typically a percentage of construction value, sometimes with a fee-plus-reimbursable structure given the CM's direct trade contract holding |
Why the Confusion Between These Roles Causes Real Gaps
A project appointing a PM under the mistaken assumption it's getting Development Management's broader feasibility and strategic oversight can genuinely find gaps in pre-construction strategic decisions that fell outside the PM's actual contracted scope, discovered only once those decisions were needed and nobody was contractually responsible for them. Construction Management's distinguishing feature - the CM holding trade contracts directly rather than working through a single main contractor - carries genuine risk allocation implications that are easy to overlook if CM is casually treated as simply "PM but narrower" rather than a structurally different delivery model.
A Scenario Showing Why Explicit Scope Definition Matters
Picture a client engaging a firm at the PM level for a project's delivery phase, having previously worked with a different firm at the Development Management level on an earlier, similar project, and unconsciously carrying over an expectation of the broader Development Management scope into this new, more narrowly defined PM engagement. Clear scope definition at appointment, explicitly stating what's included rather than relying on the role title alone to convey it, is what actually prevents this kind of accountability gap from opening up between what a client assumes is covered and what the contract actually specifies.