Running 30 projects at once - the operating system of a multi-site EPC
Anyone can run one project well. The test of an engineering company is whether the thirtieth project gets the same discipline as the first. Notes on the system that makes that possible.
A single project is a test of competence. Thirty projects running at the same time is a test of system. The difference between the two is the single most important thing an engineering company learns as it grows - and the place most of them quietly fail. The first project gets the founder's full attention; by the tenth, attention is a scarce resource, and the only thing that scales is the system you put in its place.
Attention does not scale - systems do
When you run a handful of sites, the promoter can hold every one of them in his head. Past a dozen, that stops working - not because the promoter got worse, but because human attention is finite. The companies that survive the transition replace heroics with a system: a weekly planning rhythm, a single source of truth for every site's status, a clear owner for every project, and an escalation path that surfaces a problem before it becomes a crisis.
The system is unglamorous. A standard project dashboard. A Monday review where every site reports the same five numbers. A resource calendar that shows where the cranes, the crews and the senior engineers are this week and next. None of it is exciting. All of it is the difference between a group that runs 30 projects and one that runs 5 and drops the other 25.
The scarce resource is senior judgement
Steel can be bought. Crews can be hired. The thing that does not scale on demand is senior engineering judgement - the person who can look at a foundation, a stringing plan or a substation layout and know, in a minute, whether it is right. A multi-site business has to ration that judgement deliberately: deploy it to the riskiest stage of the riskiest projects, and build standard procedures so the routine work does not need it.
The mistake is to let every site pull the same three senior people in every direction. The discipline is to decide, every week, where senior judgement is actually needed - and to trust the system everywhere else.
What the thirtieth project should feel like
The goal is simple to state and hard to reach: the thirtieth concurrent project should get the same quality of engineering, the same safety discipline and the same commissioning rigour as the first. If it does not - if quality is visibly a function of how much promoter attention a site happens to get - the company has not built a system, it has built a bottleneck wearing the founder's name.
Running 30+ projects at a time is not a boast about volume. It is a claim about repeatability. The volume is only worth anything if every one of them holds the standard.
This essay is an in-house first draft, prepared for Mr. Paresh Ardeshna's review. It expresses general operating opinions on themes within his domain, but no specific event, customer, year or biographical claim has been verified. To be edited, signed off, or replaced before publication.
Got a question on what you have just read - or on power transmission EPC, transformer technical services, renewable energy SPV structuring, or the Indian engineering ecosystem? Write directly to the office.
First-generation Indian industrialist and engineer. Promoter and Director of Hi-Tech Transpower Pvt. Ltd. (est. 2005), a pan-India engineering and EPC services company in power transmission and renewable energy.