Picture the desk your paper lands on. Somebody is holding a stack of files and has no power to invent a single fact. They cannot assume your address, guess which of three people with your name you are, or decide that you probably meant the thing you did not write down. Every question your application leaves open is a reason to put it aside — not out of unhelpfulness, but because a file that cannot be decided today has to wait for something, and things that wait get buried. So the job is not persuasion. It is removal: taking away, one by one, every reason somebody would have to defer your matter rather than dispose of it. Three habits do almost all of that work. Address the decision, not the feeling — most applications describe a situation at length and never actually state what they want somebody to order, which leaves the reader to guess at the request before they can grant it. Ask for one thing, because different asks travel to different desks and a file cannot be closed until the slowest of them comes back. And give them the number they search on — a file, application, account or acknowledgement reference is the single most valuable line on the page, and it is the line people most often leave out. None of this is about elegant writing. The best applications are plain, short and slightly dull, and they get decided while better-written ones are still waiting for somebody to work out what was being asked.
Everything useful in this subject comes from picturing the reader accurately, and almost nobody does.
They are not hostile. They are not lazy. They have a stack of files, a limited window in which each one can be dealt with, and no authority whatsoever to supply a fact you did not give them. They cannot assume which of three addresses is current, cannot decide that you probably meant the adjacent thing, cannot fill a blank.
Which means an incomplete application is not merely weaker. It is undecidable, and the only thing that can be done with an undecidable file is to set it aside pending something.
And a file set aside is very hard to bring back. Nobody rejected it. Nobody is against it. It simply stopped being the thing on top of the pile, and the pile kept arriving.
So the question to ask of every sentence you write is not “is this true” or “is this moving”. It is: does this help somebody decide today? Sentences that fail that test are costing you, not helping you.
The distinction that decides how the whole document should be written, and the two get blended constantly, usually because the situation contains both.
An application asks an office to do something it has the power to do. Issue, correct, transfer, permit, restore, release. It is forward-looking and it is addressed to whoever holds that power.
A complaint objects to something that has already happened. It is backward-looking, it usually goes to a different function, and it is measured by different standards.
A document attempting both reads as a grievance with a request attached, and it tends to be treated as a grievance — which means it goes to whoever handles grievances, and the thing you actually wanted does not get done.
So decide first. Where you need something done, write an application and keep the history to what explains the request. Where the real subject is that somebody did something wrong, that is a complaint, and our complaint guide deals with writing one that produces a specific answer rather than a sympathetic one.
And where you genuinely need both, write two documents. They will travel to the right places and neither will hold up the other.
Everything else on this page is detail on these. An application missing any one of them is incomplete in a way the reader will notice before you do.
Who you are — in the form their records use. Your name as it appears on their file, not as you would ordinarily write it, and every reference number you hold.
What happened — in dates, briefly, limited to what makes the request understandable.
What you are asking for — one sentence, unmistakable.
What is attached — a numbered list, matching the bundle.
How to reach you — an address that is current, a number that is answered, and an email that is read.
Five parts, one page, attachments behind. The order can vary and the request should appear early rather than late; what cannot vary is that all five are present and each is findable in a glance.
The most useful drafting trick on this page and it takes about a minute.
Somebody eventually has to write a decision. Imagine the sentence you would like to see in it — the correction sought is allowed, the document may be issued, the request is granted — and then write your request as the mirror of it.
This does two things. It forces you to discover whether you actually know what you are asking for, which is startlingly often not the case at the beginning. And it hands the reader language they can use, which removes a small piece of work from their day.
Put that sentence somewhere unmissable. Many people set it apart on its own line, and that is not a presentation flourish — it is so that somebody scanning the page finds the request without reading the page.
Then read your draft and ask whether a stranger could state your request after ten seconds with the document. If not, the sentence is not doing its job.
Resisted by almost everybody, for an entirely understandable reason: if you are going to the trouble of writing, it feels wasteful not to raise everything at once.
Here is why it costs you. Different requests are frequently dealt with by different people, on different criteria, at different speeds. A file cannot be closed while any part of it is open, so the straightforward request waits for the complicated one. And if one part of the bundle is refused, the refusal tends to attach itself to the whole.
Separate applications move independently. The easy one is granted next week. The difficult one takes its own time without holding anything hostage.
Where two requests are genuinely inseparable — the second only makes sense if the first is granted — keep them together and say plainly why they are one matter.
And where you are filing several on the same day, number them in your own note and track them separately, because you will otherwise lose which acknowledgement belongs to which.
Small, dull, and it does more work than any sentence you will write.
Offices find things by reference. A file number, an application number, an account or registration number, a receipt number, the number printed on an acknowledgement they gave you last year. Give them every one you have, near the top, labelled.
Without it, somebody has to search for you by name, in a system that may hold several similar names, and that search is work — which means it can be postponed.
Where you do not have a reference, say so explicitly and give the next best identifiers: the date of the earlier transaction, the office it was done at, and any other detail that narrows it. That is far better than leaving the reader to wonder whether you simply did not mention it.
And when you receive a reference of any kind, write it into your own note the same day. The commonest cause of a slow second application is a first acknowledgement nobody can find.
The single change that improves most drafts more than anything else.
Compare two versions of the same fact. Despite repeated requests over a long period, nothing was done. Against: Applied on the fourth of March. Reminded on the second of April and the ninth of May. No reply received.
The second is shorter, it is checkable, it can be copied straight into a file note, and it is much harder to argue with. The first asks the reader to take your word for a characterisation.
So write the history as a short sequence of dated events. Each line: what happened, when, and where the proof of it is. Nothing else.
This also protects you from the thing that quietly damages applications: a single overstatement. A reader who finds one exaggeration begins checking everything, and an otherwise good application becomes a suspicious one.
Which leads to the rule underneath all of this: do not write anything you cannot show. If a document does not exist, do not describe it as though it does. If a conversation happened, say it was a conversation.
Most of the skill in this work is subtraction, and most of the resistance to it is entirely human.
The things that do not belong: how long you have been dealing with this and how tiring it has been; what somebody said to you in a tone you did not like; what you think of the office generally; comparisons to other people’s cases; and anything you would not want read aloud.
They do not belong because they do not help the decision, and because everything on the page competes for the same short attention. A page carrying four useful facts and six irrelevant ones is read as a page of ten things, and the useful four are diluted.
The exception worth stating: where delay or hardship is itself the reason the request should be granted, that belongs — as facts, dated, not as feeling.
The practical method is to write the long version first, for yourself, and then cut it to the sentences a stranger needs. Almost nobody can write the short version straight away and there is no reason to try.
And leave out any threat of what you will do next. In a first application it changes nothing except the temperature, and a matter treated as defensive is treated more slowly.
Worth a section because people swing between two registers and both cost them.
The first is elaborate courtesy — long formal openings, ornate phrasing, a great deal of deference. It is harmless and it wastes the top third of a page that gets skimmed.
The second is anger, which is frequently deserved and always counter-productive on paper. It gives the reader something to react to instead of something to decide, and it makes it easy for a file to be handled by somebody more junior than it should be.
What works is neither: plain, specific and unbothered. A sentence that states a fact and stops. The impression you want to leave is of somebody organised who will still be here next month, which is a far more persuasive quality than either politeness or heat.
And write as though the person reading it is not the person you are annoyed with, because they usually are not.
An application sent to the wrong desk is not refused. It is forwarded, slowly, or it sits.
So spend five minutes establishing who decides this kind of thing at this office. Ask at the counter, ask on the telephone, look at whatever the office publishes. The question is simple: which officer deals with this, and is there a particular way such applications should reach them?
Address it to that post rather than to a person’s name where you can, because people move and posts do not. Where you have a name, use both.
If you genuinely cannot find out, address it to the head of the office and say in the first line what it concerns. That is a reasonable default and it gets routed internally.
And if you are told at the counter that it should go somewhere else, ask them to tell you exactly where, and write that down. That sentence is worth more than the trip.
The mechanical half of an application, and it shapes the impression the whole file makes.
List them in the application, numbered, in the order you mention them. Arrange the bundle in that same order. Where there are more than a handful, put an index sheet on top.
Copies, never originals. Carry the originals to be produced if sight is wanted, and take them home with you. Our certified true copy guide covers which kind of certification a particular office is likely to accept and what the endorsement has to carry.
Copy both sides of every page, including the blank ones, and check that every attachment is legible as a stranger would read it rather than as somebody who already knows what it says.
Attach what supports the request and not everything you own. A thick bundle is not more convincing; it is slower to read, and it invites the reader to look for the relevant page rather than be shown it.
And refer to each attachment at the point in the text where it matters — as at annexure three — so that the reader never has to search for what you meant.
Not because templates are bad. Because of what people do with them.
A template is a shape, and the shape is genuinely useful — it reminds you of the five parts and stops you forgetting the reference line. That is a real contribution.
What it cannot do is know your facts. So what arrives at the office is somebody else’s situation with your name inserted: phrases that do not describe what happened, references to documents you do not have, and a request that is approximately but not exactly what you want.
The reader notices immediately, because the specific parts and the borrowed parts do not sound alike. And an application that does not match its own attachments is an application that comes back.
So use one for structure if it helps, then throw away every sentence you did not write, and check the final draft against your own bundle line by line.
The cheapest quality check in this entire subject, and it takes ten minutes of somebody else’s time.
Hand your draft to a person with no knowledge of the matter — a relative, a colleague, anybody literate and unconnected — and ask them three questions after they have read it once.
What is this person asking for? If they hesitate, or answer with a paragraph, your request sentence has not done its job and nothing else on the page will rescue it.
Who are they? If the identifying details are not obvious in a glance, the reader at the desk will have the same trouble with a much shorter attention span.
Is anything here confusing? The places a stranger stumbles are precisely the places an office will raise a query, and a query costs a fortnight where a rewrite costs a minute.
You will resist this, because the draft feels obvious to the person who wrote it. That feeling is exactly the problem the test exists to catch — you are the one reader who already knows what you meant.
Write in whatever the office ordinarily works in, unless its own rules say something different.
That is not a concession — it is practical. A plain application in the language of the desk is read and acted on. An elegant one in a language somebody has to carry to a colleague acquires a delay that has nothing to do with its merits.
Where you file in two languages, make sure they say exactly the same thing, and be especially careful with the request sentence and with dates, which are where translations drift. Say which version you signed.
And keep technical or legal-sounding phrasing out of it unless you know precisely what it means. A borrowed phrase used slightly wrongly is worse than the plain sentence it replaced, because it changes what you appear to be asking for.
Where the application or its annexures are to be signed electronically, settle that before the file is assembled rather than after. Our e-sign assistance guide explains why the receiving office should be asked first, and why a document cannot be adjusted once signatures exist.
Four routes, and the difference between them is almost entirely about evidence.
At the counter — hand in two copies and ask for one back, stamped with the date. That stamped copy is the best proof there is and it costs nothing.
By post — use a mode that produces a record of delivery, and keep it with the application. Note the date it was sent as well as the date it arrived.
On a portal — save the reference number and the confirmation, and take a dated capture of the screen showing both. Systems change and references get regenerated.
By email — keep the sent item and any delivery or read confirmation, and send to the address the office publishes rather than to somebody’s personal one.
Where the office prefers a particular route, use it, and where you use another as well, say so in the document so that nobody deals with it twice.
The most important paragraph on this page, and the one that is most often skipped for the most ordinary reason — the queue was long and somebody said it was fine.
An application that cannot be shown to have been filed was not filed. Not as a matter of principle; as a matter of what happens next. Six months later, with no acknowledgement, there is nothing to follow up on and no way to establish when the clock started.
So do not leave without something: a stamped copy, a receipt, a reference number written down in front of you, a delivery record. Whatever the route produces, take it.
If the counter will not stamp a copy, ask what it does issue, and if the answer is nothing, file by a route that generates its own record instead. That choice is yours and it is worth making.
Then photograph or scan the acknowledgement the same day. The small piece of paper that proves an application exists is exactly the kind of thing that goes missing.
Not a description of any particular office, because they differ. A general shape, though, and knowing it changes how you write and how you chase.
Broadly, a paper that comes in gets received and entered somewhere, routed to whoever deals with that subject, examined for completeness, put up with a note to whoever decides, and then decided and communicated.
Two of those five are where things stop, and neither is the decision. A file can sit at routing, because it is not obvious whose subject it is. And it can stop at examination, because something is missing and nobody has told you yet.
Which explains two things this page keeps insisting on. Say in the first line what the application concerns, so routing is instant. And attach everything, listed, so examination has nothing to send it back for.
It also tells you what to ask when you follow up, and the question is not “what is the status”. It is: where is the file now, and is anything awaited from me? That produces an answer somebody can actually give, and the second half of it occasionally produces the whole explanation.
The difference between people whose matters move and people whose matters do not is rarely the first application. It is this.
Decide the interval on the day you file — a fortnight, a month, whatever suits — and put it in a calendar. Then follow up on that date whether or not you feel like it, and not before.
Each follow-up is short: the reference, the date of the original, one sentence saying what was requested, one sentence asking for the current position, and a copy of the original attached. Three or four lines.
What this avoids is the common pattern of silence for three months followed by a long letter written in frustration, which reads as a new grievance rather than as a continuation and frequently starts the reading over.
And keep every follow-up, sent and received, in one place with the original. By the fourth one you will not remember the sequence, and the sequence is what makes the next step possible.
Extremely common, rarely deliberate, and the response to it is a specific technique rather than more effort.
You receive something that acknowledges your application, restates it, mentions that the matter is under consideration, and answers nothing. The instinct is to write again at length. That produces another reply of the same kind.
What works is narrowing. Quote their reply, in one line. Name the question it did not answer, in one line. Ask that question again on its own, and stop.
A letter containing exactly one question is very hard to answer without answering it. A letter containing six is easy to reply to in general terms, and general terms is what you will get.
If the same thing happens twice, ask when a decision can be expected and note the answer. A date given in writing, even a vague one, changes the shape of every conversation after it.
A refusal is information. A refusal without a reason is not, and the two need different handling.
Where a reason is given, read it as narrowly as you can. Most refusals turn on one specific thing — a document, a criterion, a form of proof — and where that is so, the answer is often a fresh application that cures it rather than an argument about the old one.
Where no reason is given, ask for one, in writing, as a short separate application. A reason is worth having even if the decision stands, because without it you are guessing, and people who guess file the same application twice.
Where the reason given does not match the facts, say so once, specifically, attaching the document that shows it — and then let it rest with whoever has to consider it rather than sending a second version of the same letter.
And where the matter is genuinely a dispute rather than an administrative gap, that is a different route with a different document. Our legal notice service prepares correspondence for that stage, and our consumer complaint drafting service the version for goods and services.
There is one situation where even a well-drafted application is the wrong first move, and that is an ongoing financial fraud — there the telephone beats the letter by a distance. Our online financial fraud guide sets out that order, and what the written work should contain once the emergency steps are done.
Handled with care, because urgency is claimed constantly and is occasionally real.
The way to convey it is not with language. It is with facts and a date. Something is happening on a particular day; the request has to be decided before it; here is the document that shows the date.
That gives the reader something they can act on and, more importantly, something they can write down when they explain why this file was taken out of order. Nobody can do that with a sentence saying the matter is very urgent.
Say it once, near the top, and do not repeat it. Urgency stated three times reads as pressure rather than as a fact.
And where the deadline is unavoidable and close, ask at the office whether there is a route for such cases rather than assuming there is not. Frequently there is, and it has its own small procedure.
A common example is a welfare registration or claim prepared for a worker who would rather not fill forms at a counter — our labour card guide sets out how to do that properly, including reading the completed form back before anybody signs.
Common, and the place where otherwise complete applications fail on a technicality.
Where you are filing for another adult, you generally need something in writing from them saying you may. Our authority letter service prepares the ordinary version, and our consent letter service the version that records somebody agreeing to something rather than authorising you to act.
For anything substantial, or where money or property is involved, the authority needs to be more formal than a note — ask the office what it accepts before assuming.
Where the person cannot attend or cannot sign, do not improvise and above all do not sign in their name. Ask the office how it deals with that situation; established ways exist and they differ.
And say in the application, plainly, who is applying and in what capacity. An application that reads as though it comes from one person and is signed by another creates a question that stops the file.
One setting where this style of writing pays for itself immediately is the end of a job, where almost everything is obtained by asking the right desk for a specific thing in writing. Our termination and full-final documentation guide uses exactly this approach to get a computation, a clearance list and a set of letters moving.
Some applications need a supporting document that does more than assert.
Where the office wants your account of something on oath — that a document was lost, that two names are one person, that you hold nothing else of a kind — that is an affidavit and not part of the application itself. Our notary affidavit service prepares one, and our declaration and undertaking services the lighter forms.
Two things to get right. Such a document should say only what you know, in your own words, and never more than the office actually asked for. And the application should refer to it by number like any other attachment.
What you should not do is put sworn-sounding language into the body of an application. It does not make the application stronger and it can commit you to something you did not intend to say.
Where you are unsure which is wanted, ask the office in those terms: do you need this as a statement in the application, or as a sworn document? They will tell you, and the answer saves an afternoon.
A good example of an application that lives or dies on one precise sentence is a correction to a record — our voter ID correction guide shows what that sentence has to say and what evidence has to sit behind it.
A useful fork, because a good many applications are really questions.
If you do not yet know what happened to your file, what the reason for a decision was, or what the office holds, then the thing to obtain first is information — and an application asking for a decision, filed before you know the position, is frequently the wrong document.
Where the body is one that has a formal route for supplying information, that route exists precisely for this, and our RTI application service prepares such a request where it fits.
Where it is not, ask the plain question in a short letter of its own, quoting the reference, rather than folding it into a longer application.
The sequence that works: find out the position, then ask for the thing. The sequence that wastes months: ask for the thing, be refused for a reason you could have discovered, and apply again.
Frustrating, common, and there is a specific way out of it that does not involve losing your temper with either.
The pattern: one office says the matter is dealt with elsewhere, and the other says the same thing back. Nobody is refusing anything, so there is nothing to challenge, and the matter can sit between them indefinitely.
The move is to convert the verbal into the written. File your application at one of them, plainly, and ask — in the application itself — that if this office is not the appropriate authority, it be transferred to whichever is, and that you be informed to whom it has gone.
That single sentence changes the situation. An office can tell you at a counter that it is not their subject. Recording that in response to a written application, and saying whose subject it is, is a different act, and it usually produces either a transfer or the actual answer.
Keep the acknowledgement, note the date, and follow up on the same rhythm as any other application. If a transfer happens, ask for the new reference and start quoting it.
And write down, each time, who told you what and when. Where a matter is genuinely stuck between two desks, that short list of dated statements is the most useful thing you can hand to anybody senior enough to unstick it.
Five minutes at each step, against reconstructing everything later from memory.
One folder per matter, holding: the application as filed, the attachments as filed, the acknowledgement, every follow-up, every reply, and a single sheet listing what happened on what date.
That one sheet is the valuable part. It is what lets you write the next letter in two minutes, it is what you would hand to anybody helping you, and it is what makes an escalation possible without a week of preparation.
Scan everything the same week. Paper relating to an ongoing matter travels between bags and desks and it is exactly the paper that goes missing.
And where somebody else may have to continue this — you are travelling, unwell, or the matter concerns a family member — tell one person where the folder is. Our document verification service is a different exercise, but the same instinct applies: a file another person can pick up is worth more than a perfect file only you can read.
Worth stating plainly, because expectations here cause the sharpest disappointment.
It cannot create a power the office does not have. The best-written application in the world asking for something outside the office’s authority is refused, correctly.
It cannot supply a document that does not exist. Where the requirement is evidence you do not hold, the work is obtaining it, not phrasing around its absence.
It cannot make an unfavourable fact go away. It can put that fact in its proper context, which is a real and useful thing, and which is not the same as hiding it.
It cannot guarantee an outcome, and anybody promising one on the strength of drafting is selling something else.
What it can do is make sure that a request which should be granted is capable of being granted today, by a person with limited time and no discretion to guess. That is a narrower claim and it is worth a great deal.
None of them are refusals. That is the point — most applications do not fail, they stall.
The request was never actually stated, so the reader had to work out what was wanted.
No reference number, so finding the file was work and the work was postponed.
Three asks in one letter, so the simple one waited for the complicated one.
No acknowledgement taken, so there is nothing to follow up on and no date the clock started from.
Attachments that do not match the list, so the file was returned for completion and the loop began again.
Silence for months, then a long angry letter, which was read as a new grievance rather than as a continuation.
We begin with a question that takes longer to answer than people expect: what decision are you actually asking for, and who has the power to make it? A good share of the work is finished once that is settled, and it is frequently not the request the conversation started with.
Then we read what you already hold — the earlier correspondence, the acknowledgements, the documents — because the references buried in those papers are usually the most valuable things in the whole file and almost nobody quotes them.
Then we write: one ask in one sentence, the history as dated facts with nothing in it we cannot show, the identifiers the office searches on, and an attachment list that matches the bundle you will actually carry.
We also tell you the unglamorous parts — which route to file by, what to insist on walking out with, and what date to put in your calendar for the first follow-up. Those three decide more outcomes than the drafting does.
And where the right document is not an application at all — because what you need first is information, or because the real subject is a complaint — we say so before writing the wrong thing well.
We will not write what cannot be shown. Not a date that is convenient, not a document described as existing when it does not, not a fact softened into something it was not. An application containing one untrue line puts every other line in doubt.
We promise no outcome. Drafting makes a request decidable. It does not make it grantable, and anybody suggesting otherwise on the strength of wording is not being straight with you.
We do not prepare documents for proceedings. Those have their own form and their own rules and they belong to whoever is conducting your matter.
We do not draft threats. A first application is not the place, and a document written to intimidate an office generally slows the matter it was meant to speed up.
We do not file in your name without authority, and where somebody is acting for another person we want that in writing before anything goes in.
Drafting begins at ₹1,500, the usual span is 1 – 3 days, you are told the whole figure before we start, and nothing is payable in advance. A follow-up letter later, or a narrow reply to a non-answer, is a much smaller job and is priced as one.
Most of the time goes on the papers rather than the writing. Reading earlier correspondence to find the reference nobody quoted, and working out which office actually decides this, takes longer than composing the page and matters more.
Where the position is not yet known, we will usually suggest finding that out first rather than drafting around a gap. That occasionally means less work for us in the short run and it is still the right order.
And the plain note this page owes, because the whole subject is within anybody’s reach: state the request in one sentence. Ask for one thing. Quote the reference. Attach copies, never originals. Do not leave without an acknowledgement. Follow up on a date you chose in advance. Those six habits are free, they are most of what a drafted application buys, and if this page gives you nothing else it has been worth more than the figure at the top of it.
Most applications are not refused; they stall, because the person reading them cannot act without asking a question. We work out what decision is actually being sought and who has the power to make it, read the papers you already hold for the reference numbers nobody quotes, and write one ask in one sentence with the history as dated facts and an attachment list that matches your bundle. Then we tell you the unglamorous parts that decide the outcome: which route to file by, what to walk out holding, and the date to follow up.
Two doors, both free. Clients search a factual directory of enrolled advocates. Advocates apply to be listed on it — no fee, no commission, nothing paid in either direction.
Search Bar Council enrolled advocates by what your matter is about, by court, or by city. Searching and sending a request are both free.
Enrolled advocates anywhere in India can apply to be listed. Your entry is published only after we verify your enrolment number with your State Bar Council.
This directory carries no ratings, no reviews, no rankings and no fees — only the factual particulars the Bar Council of India permits, published at each advocate's own request. Browse the network · Terms for Advocates