PMC firms built around one city's site-supervision process increasingly work outside it — through partner networks, associate engineers, or periodic site visits rather than a permanent local office. That's not automatically a problem, but it changes what you should be asking before you sign, compared to hiring a firm headquartered in your own city.
Ask How Site Presence Actually Works
"We serve your city" can mean anything from a dedicated site engineer physically present daily, to a principal who visits periodically and reviews reports remotely in between. Neither is inherently wrong for every project, but the answer should change what you expect week to week — and it should be stated plainly before you sign, not discovered once the project is underway.
Ask What Local Compliance Knowledge Actually Transfers
A PMC process built on one city's development authority — HIDCO and NKDA norms in New Town, for example — doesn't automatically transfer to a different one, whether that's GDA in Ghaziabad, the NOIDA Authority, or a different municipal corporation entirely. What should transfer is the underlying discipline: independent site supervision, BOQ verification, quality inspection cadence. The specific approval and compliance path has to be rebuilt for the new authority through a local associate or partner. Ask directly how that local knowledge is sourced, not assumed.
Ask for the Escalation Path Before You Need It
If your site engineer is a local associate rather than a firm employee, who do you actually call when something goes wrong — the associate, or the firm's principal? Get this answered in writing before the first site issue, not after, because that's exactly the moment an unclear reporting line costs you the most time.
A PMC operating outside its home city isn't a red flag by itself. Vague answers to these three questions are.