Owner's Engineer and PMC roles get contracted separately often enough, and defined vaguely often enough, that accountability gaps between them are one of the more common and more genuinely avoidable sources of project dysfunction on Indian projects that engage both.
| Role | Typical core scope | Common overlap zone with the other role |
|---|---|---|
| Owner's Engineer | Technical review, design verification, quality assurance on behalf of the owner/lender | Site supervision and progress certification |
| PMC | Overall project management - schedule, cost, contractor coordination, delivery | Technical/design review and quality oversight |
Where Accountability Actually Breaks Down in Practice
When both roles are contracted with overlapping quality-oversight responsibility but neither has final sign-off authority clearly assigned in writing, a genuine gap can open where each party assumes the other caught a specific defect, and it turns out neither actually did - not through negligence exactly, but through a genuine and entirely foreseeable ambiguity about whose job it specifically was. Owner's Engineer is more commonly engaged specifically on lender-financed projects precisely because financial institutions want independent technical verification kept separate from the entity actually managing project delivery, and a PMC's general project management scope, however competently executed, doesn't satisfy that specific independence requirement lenders are looking for.
A Scenario Showing Exactly How This Gap Opens Up
Picture a lender-financed project where both an Owner's Engineer and a PMC are engaged, with both parties' contracts referencing "quality oversight" in fairly general terms without a specific RACI-style breakdown clarifying which party has final sign-off authority on any given quality decision. A structural defect emerges during construction that both parties later claim, in good faith, they assumed the other was specifically monitoring for - the PMC assumed the Owner's Engineer's technical review would catch it as part of design verification, while the Owner's Engineer assumed the PMC's site supervision function would flag it during routine progress inspection. This isn't a story about either party failing to do their job as they understood it - it's a story about a contractual ambiguity that made this exact gap entirely foreseeable, and entirely avoidable with a clearer upfront breakdown of specific decision rights.
Why a Written RACI Breakdown Is the Actual Fix
The fix is a written RACI-style breakdown agreed at contract stage, specifically naming who has final sign-off on quality decisions, schedule decisions, and cost decisions respectively, rather than assuming the general scope documents for each role implicitly resolve this overlap on their own - general scope language, however carefully drafted, tends not to anticipate every specific situation where the two roles' responsibilities genuinely intersect.