Start with the current court rule
Use this guide as a practical checklist, then verify the current court-specific rule, practice direction, registry instruction or official form before filing or relying on the process.
Purpose of a vakalatnama
The document evidences authority for an advocate to act in the proceeding within the applicable legal and professional framework. It should be linked to the correct party and matter.
Identity and signatures
Check the party name against the memo of parties and other filing documents. Required signatures, advocate details and stamps or endorsements should be verified under the relevant court's current practice.
Vakalatnama versus power of attorney
A vakalatnama relates to advocate representation; a power of attorney can authorize specified acts more broadly. They are not interchangeable documents.
Common filing checks
Registry scrutiny may look for missing signatures, inconsistent party details, required stamps or the absence of authorization. Delhi High Court's objection material expressly includes power-of-attorney/vakalatnama-related checks.
Change of counsel
Where counsel changes, follow the applicable professional and court procedure. Do not assume a new vakalatnama alone resolves every issue involving discharge, consent or prior representation.
Use court-specific rules, not memory
Court filing practice changes through rules, practice directions, circulars, registry instructions and technology updates. A lawyer who learned a format in one court or one year should not assume the same requirement remains current elsewhere. Check the issuing court's present rules and notices before filing, especially for paper size, service requirements, document formatting, court-fee treatment, e-filing interaction and registry objections. Delhi High Court's current e-filing page and notifications illustrate how operational requirements can be updated by later directions.
Build a pre-filing verification record
Before submission, record the court, case category, filing type, applicable rule or practice direction, required service, document set and any court-specific form or fee. Keep that short checklist with the file. It becomes useful when the registry raises an objection because the team can distinguish whether the problem came from the document, the filing metadata, service, format or a later court instruction.
Separate formal compliance from legal sufficiency
A filing can be technically compliant yet legally weak, and a legally strong pleading can still be rejected for procedural defects. Registry scrutiny typically addresses filing requirements rather than the merits. Young lawyers should therefore run two reviews: one for substantive legal content and another for filing mechanics, signatures, attestations, annexures, pagination, indexing and prescribed forms.
Keep version control
Physical and electronic workflows both create version risk. Maintain one final filing set and clearly separate earlier drafts. The index, page numbers, annexure references and signatures should correspond to the version actually submitted. Where the filing is later re-filed after objections, preserve the earlier acknowledgment or diary reference and mark the corrected version so the file history remains clear.
Do not rely on outdated fee or timing tables
Older court handbooks can explain the structure of a process, but exact fees, counter timings and operational arrangements may have changed. Use older official material only for stable background unless the current court website confirms the detail. For any amount, office timing or submission method that affects today's action, verify the current official source or registry information.
Final quality-control pass
Before the document or request leaves your hands, check it as though you were the registry reader who has no knowledge of the drafting history. Confirm the case identity, party names, document title, date, signatures, annexure references, page ranges and court-specific requirements. Then check it again as the hearing lawyer: can every important reference be found quickly, and is the latest operative order easy to locate? This two-perspective review catches both filing defects and practical usability problems.
What this guide does not replace
This guide explains recurring filing and court-practice concepts. It does not override the current rules, practice directions, registry decisions or judicial orders of the relevant court. Where the requirement affects limitation, maintainability, evidence, professional responsibility or another material legal issue, obtain qualified case-specific advice and use the current official source.
Working-file discipline
A well-managed filing file should show what was prepared, what was actually submitted, what the registry returned, what was corrected and what the court ultimately registered or acted upon. Keep the filing acknowledgment, objection sheet or portal status, corrected document set and later case number together. This is especially important when several team members work on the matter, because the version on a local computer may not be the version that reached the court. After every material filing event, update the chronology and note the official reference number so the team can reconstruct the procedural history without relying on memory.
Handover and team-check discipline
Court-practice errors often arise when one person drafts, another person files and a third person appears. Use a short handover note that states the exact filing version, filing or diary reference, unresolved objections, latest order, next procedural task and any document still awaited. The note should distinguish facts confirmed from the official record from assumptions or pending checks. If a corrected document replaces an earlier version, make that replacement explicit and remove obsolete copies from the active hearing bundle. Where the filing process produces a new case number, CNR, copy-application number or inspection reference, add it immediately to the working file. This simple discipline improves reliability because the lawyer attending court can reproduce the procedural history without reconstructing it from messages, draft folders or memory. It also makes post-hearing updates easier, because the team can reconcile the new order or direction against the exact filing set that the court had before it.
Practical verification table
| Check | Practical rule |
|---|---|
| Court | Confirm court-specific rule or direction |
| Document set | Use final controlled version |
| Signatures/attestation | Check before submission |
| Index/pages | Cross-check final sequence |
| After filing | Track objections, re-filing and registration |
