A client with operations in five states has forty three live matters. Nine in the courts at Delhi, eleven around Mumbai, seven in Bengaluru, a cluster of consumer and cheque matters in smaller towns, and a handful before tribunals. You are the coordinating counsel. You will personally appear in perhaps six of them. For the rest, your knowledge of what is happening is entirely a function of what other people tell you, and when.
This is a common and badly served position in Indian practice. The conventional response is relational: build good local relationships in each city and rely on them. Relationships matter and they are not sufficient. A first rate local advocate who reports irregularly, in a format nobody can consolidate, on a matter whose documents live only in his office, still leaves you unable to answer the question the client will actually ask, which is what is our total exposure and what is happening about it.
The determinant of quality in multi-city litigation is information architecture. Who reports what, in what format, on what cadence, into what single record. Get that right and ordinary local counsel produce good outcomes. Get it wrong and excellent local counsel produce an unmanageable portfolio.
Where Coordination Actually Breaks
The failures are consistent across practices and they are worth naming precisely, because each has a specific fix.
In a scattered portfolio your knowledge is not what you know. It is what somebody else remembered to tell you, in a format you could use.
The Structural Constraints You Are Working Within
Two features of Indian practice shape why local counsel exist at all, and understanding them helps in briefing well rather than resenting the arrangement.
The Advocates Act 1961 confers on an enrolled advocate the right to practise throughout India, so there is no general bar on appearing in another state. What varies is filing practice. Many courts require filings to be made by an advocate on the roll of that court or with a local address for service, and the Supreme Court operates the advocate on record system under its own rules, which is the sharpest version of the same principle. Vakalatnamas must be executed in the form and with the stamps the local rules require, including welfare fund requirements which differ by state.
Local knowledge is a real asset, not a formality
The second constraint is practical rather than legal. Local knowledge is real. The practice of a particular registry, the way a particular bench handles a category of matter, how long a certified copy actually takes, and whether an urgent mentioning is likely to be entertained are things that cannot be researched from another city. This is why local counsel are not merely a filing convenience, and it is why the coordinating role is about architecture rather than about doing the work remotely.
Briefing Local Counsel Properly
Most briefing failures are omissions rather than errors. Local counsel receive the matter and not the context, then make locally sensible decisions that are portfolio-wise wrong.
Send the portfolio context, not just the matter
Tell them what else is running for this client, what the client's overall position is, and which propositions the client is defending across matters. A local counsel who knows that an admission on a particular point would damage four other matters will not make it.
State the client's position on the recurring questions
Settlement appetite, tolerance for interim orders, willingness to give undertakings, position on costs, and the categories of concession that require prior approval. Write these down once for the portfolio and send them with every brief.
Define the reporting standard explicitly
What must be reported, in what format, and by when. Same day for hearing outcomes, immediately for any adverse or interim order, within a defined period for new listings. Vague expectations produce vague reporting.
Define the escalation triggers
The specific situations in which they must call you before acting: any settlement discussion, any concession on a listed proposition, any application for interim relief against the client, any costs order, any date fixed for evidence. An escalation list of six items is used. A general instruction to keep you informed is not.
Agree the document flow at the outset
Every pleading filed, every order received, and every notice served goes into the central record within an agreed period. Say where, say how, and make it a condition of the engagement rather than a request.
Confirm the fee arrangement in writing
Scope, structure, disbursement handling, invoicing cycle and who the invoice is addressed to. Fee ambiguity across ten local relationships becomes a serious administrative problem within a year.
Brief once for the portfolio, not repeatedly for each matter
Write a standing brief for the client: who they are, what the recurring litigation themes are, the positions they hold across matters, the reporting standard, the escalation triggers, and the contacts. Send it to every local counsel on engagement, and update it twice a year. Each new matter then needs only a short covering note. This single document does more for consistency across a scattered portfolio than any number of individual conversations, and it is the artefact that survives when a relationship changes.
The Reporting Standard
Standardisation is what makes consolidation possible. Ten counsel reporting in ten formats produce a portfolio nobody can summarise. The same ten reporting in one format produce a portfolio that summarises itself.
| Report | Trigger | Contents | Deadline |
|---|---|---|---|
| Hearing outcome | Every listing, including non-events. | What happened, what the court directed, the next date, what it is listed for, and who owes what step. | Same day. |
| Adverse or interim order | Any order against the client, any interim relief granted to the other side, any costs. | The order, its immediate effect, the compliance date if any, and the options including appeal or challenge with their timelines. | Immediately, by phone as well as in writing. |
| New matter or new listing | Any fresh proceeding involving the client, or a matter surfacing after a period of dormancy. | Parties, forum, subject matter, the relief sought against the client, and the first date. | Within a defined short period of becoming aware. |
| Monthly portfolio return | A fixed date each month. | Every matter with its stage, next date, outstanding steps and any change in risk assessment. | By the fifth of the following month. |
| Escalation | Any of the agreed trigger events. | The situation, the decision required, the timeline, and the recommendation. | Before acting, not after. |
The monthly portfolio return deserves emphasis because it catches what event driven reporting misses. Matters that have not been listed, matters where nothing has happened, and matters that have quietly been transferred or renumbered do not generate events, and therefore never appear in event based reporting. They appear in a monthly return because the return requires a line for every matter whether or not anything happened in it.
The Single Source of Truth
One record, holding every matter for the client across every jurisdiction, maintained centrally, accessible to the coordinating counsel and to the client's legal team, and updated by whoever has the information. Everything else in this piece is machinery for keeping that record accurate.
- Every matter, including the small ones. The cheque matters in small towns and the consumer complaints are exactly the ones that fall out of central records, and they are also the ones that produce surprising adverse orders because nobody was watching.
- A stable identifier for each. The CNR where available, because case numbers change on transfer and renumbering, and a portfolio tracked by case number will fragment within two years.
- Stage, next date and outstanding steps, kept current rather than accurate as at the last time someone asked.
- Local counsel named against each matter, with contact details, so that the question of who knows about this matter never requires research.
- Documents attached to the matter, not held in the city where they were created. Pleadings, orders and key correspondence at minimum.
- Risk assessment and exposure, reviewed periodically, so that the portfolio can be presented in the terms the client's board actually thinks in.
- A history that survives changes in counsel, which is the property the entire arrangement exists to protect.
Reported status and registry status are not the same thing
A central record fed only by what local counsel report is a record of what people remembered to tell you. It will drift, and it drifts most in exactly the matters that are least active, which are frequently the ones where something unexpected eventually happens. Reconcile the reported position against the court record periodically, matter by matter. Where the registry says a matter is listed next week and your record says the next date is in November, you have found a real problem while it is still cheap. Do this quarterly at minimum, and always before any report goes to the client's board.
The Coordination Routine
A scattered portfolio needs its own rhythm, distinct from the rhythm of the matters you personally conduct.
Daily: exceptions only
Adverse orders, escalations and anything requiring a decision today. Nothing else. A coordinating counsel who reads every hearing update daily will stop reading them within a month.
Weekly: the movement view
What was listed this week and what happened, what is listed next week, and which matters have not reported. That last column is the important one, because silence from a local counsel is the earliest signal of a coordination problem.
Monthly: the portfolio return
Consolidate the returns into a single client facing report: matters by stage, matters by risk, movement in the month, and decisions required. This is the artefact that justifies the coordinating role.
Quarterly: reconciliation and review
Reconcile against the registry, review the risk assessment on each matter, review local counsel performance against the reporting standard, and refresh the standing brief where positions have changed.
How CourtMesh Fits
Multi-city coordination is precisely the problem a centralised case management system exists to solve, because the alternative is a spreadsheet maintained by email, which fails in exactly the ways described above.
CourtMesh My Cases holds the full portfolio in one place, with documents, tasks and deadlines against each matter and team access so that local counsel, coordinating counsel and the client's own team can work from the same record rather than from five versions of it. Case tracking surfaces case status and next hearing dates from official sources across the Supreme Court, 25 High Courts, District Courts and Tribunals, which is the single most valuable capability in a scattered portfolio because it means your knowledge of a matter in a city you have never visited does not depend entirely on somebody remembering to report. Watchlist alerts reach you when something surfaces upstream, which turns the dormant matter problem from a quarterly discovery into a notification. And unified search across the same courts is there when a proposition being run in one city needs to be checked against how another High Court has decided it.
The limits are worth stating. The court record and the official cause list remain authoritative, registry data can lag, and no alert should ever be read as confirmation that nothing has happened. Local counsel remain indispensable, and the tooling does not reduce their role, it removes the part of your dependency on them that was never really about legal skill: whether you find out.
Architecture beats relationships in a scattered portfolio
Write a standing brief once for the whole portfolio. Define what must be reported, in what format, by when, and which six situations require a call before acting. Hold one record with every matter, a stable identifier, the current stage, the documents and the named counsel. Reconcile it against the registry quarterly. CourtMesh My Cases gives you that single record with team access, case tracking keeps status and next dates current from official sources across the Supreme Court, High Courts, District Courts and Tribunals, and watchlist alerts mean a matter in a city you have never visited stops depending on somebody remembering to write.
Explore CourtMesh
