A tender notice occupies a few column inches and gets written the way advertisements get written — quickly, late, by whoever is free. Then it behaves like nothing of the sort. It is the first document of whatever contract follows. People read it, believe it, spend money preparing because of it, and months later point at it in a room where somebody is asking how a decision was reached. And here is the part that decides how it should be drafted: you are writing for two readers at once. The first is the person you hope will bid, and writing for them alone produces something short and appealing. The second is the person who will later say the process was not open — a disappointed bidder, a member of your own committee, an auditor, somebody who simply wants to know. That second reader never appears while you are writing and governs every sentence, because the notice is what they will be reading. Two consequences run through everything below. A requirement you did not state is very hard to apply afterwards, and one you did state has to be applied to everybody, including the party you would have preferred. And the dates are the spine of the thing: the single commonest objection to any process is not that the wrong party won, it is that there was not enough time for anybody else to try. None of this makes the notice longer. It makes it deliberate, which is a different quality entirely and takes about an hour more than the version written in a hurry.
Worth separating properly, because the two things sit on the same page of the same newspaper and look identical from a distance.
An advertisement persuades. Nobody arranges their affairs around it, nobody is entitled to rely on it, and if it overstates something the consequence is disappointment rather than dispute.
A tender notice is relied on by design. That is its entire function. It exists so that people who do not know you will act on it — prepare, spend, arrange, decline other work — on the strength of what it says.
Which changes what “good” means. A good advertisement is memorable. A good tender notice is one that nobody has to interpret, because interpretation is where two people read the same sentence differently and one of them later feels cheated.
So the qualities to aim for are unglamorous: complete, unambiguous, consistent with the detailed documents, and dated in a way that leaves room. None of those are writing skills. They are checking habits.
The most useful idea on this page, and the one that settles most drafting arguments before they start.
While you write, one reader is vividly present: the contractor or supplier you hope will respond. Writing for them alone produces a notice that is short, inviting and incomplete, because everything awkward feels like it will discourage people.
The second reader is invisible at the moment of writing and is the one who matters. Somebody who will ask, later, whether this was genuinely open. A bidder who lost. A member of your own committee who was not in the room. An auditor. Somebody in your organisation who has inherited the file.
That reader will have the notice in front of them and very little else. Which means the notice has to carry, on its own face, the answer to their question.
A practical drafting test that takes ten seconds and prevents most problems: read each sentence as if a disappointed bidder were reading it aloud. Sentences that sound different in that voice are the sentences to rewrite.
Not a figure of speech. In substance, the notice begins the chain that ends in an agreement.
Look at what follows it. Somebody responds because of what it said. The detailed documents elaborate what it said. The comparison of responses is done on the basis it set out. The award is defended by reference to it. And the contract is with the party selected through it.
Which is why an inconsistency between the notice and the detailed documents is not a small untidiness. It is two versions of the terms, both published, both relied on by somebody.
So the checking step that gets skipped and should not: after drafting the notice, read it against the detailed documents line for line, looking specifically for anything stated differently rather than for anything stated wrongly.
Where the eventual contract is already drafted, read the notice against that too. Our vendor agreement and service agreement services prepare the document at the far end of this process, and it is a great deal easier when the notice and the agreement were written by people who had seen each other’s work.
The rule with the sharpest edges, and it cuts both ways.
A requirement not stated is very hard to apply. Rejecting a response for failing something the notice never mentioned is the clearest possible illustration of a process that changed after people had committed to it.
A requirement that was stated has to be applied to everybody. Including a party you know, trust and would prefer. A condition waived for one respondent and enforced against another is not a condition at all; it is a preference with paperwork.
Together these produce a discipline that is uncomfortable at the drafting stage and comfortable everywhere afterwards: every condition has to be decided before publication. There is no later.
The practical consequence people resist is that this makes drafting slower. It does. It also converts an hour of argument now into the absence of a much longer argument in four months, which is an exchange most organisations would take if it were offered in those terms.
And the awkward one worth saying aloud in the room: if a condition exists only because a particular party satisfies it, that will be apparent to every reader who is not that party.
Not a checklist of legal requirements, because those are set by your own rules and they differ — a government body, a company, a society and a trust are not working from the same book, and a list copied from the internet is how a process gets challenged.
What every notice needs in substance, though, is the same six things, and if any of them is missing a reader has to guess.
Who is inviting — named properly, with an address and a means of contact that will be attended.
What is being invited — described so that the right people recognise it and the wrong people do not waste a week.
Who may respond — the eligibility, stated plainly.
What they must do — where the full terms are, what has to be submitted, in what form, where.
By when — every relevant date, unambiguous, with times where times matter.
What happens next — when and where responses will be opened, in whatever terms your process uses.
Ask your own rules what must be added to that. Then draft to your rules rather than to the six, which are the floor and not the standard.
The most common drafting failure and the easiest one to see from outside.
It happens innocently. Somebody has a brochure, or a quotation already in hand, and the specification gets written from it because it is the document on the desk. What results is a description that exactly one party satisfies, complete with the phrasing from their own literature.
Every reader who is not that party can see this immediately. It is the single most-cited ground of complaint in this area, and it is frequently raised against processes where nothing improper was actually intended.
The cure is a habit rather than a rule: describe the outcome and the constraints, not the object. What must it do, at what scale, in what conditions, meeting what standards, within what boundaries. Let the responses tell you what satisfies that.
Where a genuine reason exists to require one specific thing, say what the reason is in the notice. A stated reason can be discussed. An unstated one looks like something it may not be.
Each condition narrows the field, and narrowing the field is exactly what somebody will later examine.
So put every one of them through a single test, out loud, with somebody else in the room. What risk does this protect against, and is it the least restrictive way of protecting against it?
Most conditions survive that easily, because most of them are about capacity, experience or standing and the connection to the work is obvious. The ones that do not survive it are the ones worth arguing about now rather than later.
Two patterns to look at hard. Conditions that are proxies — a requirement that stands in for something you actually care about and excludes people who could meet the real thing. And conditions carried forward from a previous notice because it was easier to copy the document than to think about it.
Be equally careful about how each condition will be evidenced. A condition nobody can prove is a condition you will have to waive, and a waived condition is the beginning of a complaint.
And say where documents supporting eligibility must be submitted and in what form, because a respondent who is eligible but files the proof wrongly creates a decision nobody wants to make.
More processes are criticised on timing than on any other ground, and timing is entirely within your control at the drafting stage.
A notice usually carries a sequence rather than a single deadline: when it is published, when the detailed documents become available, when questions may be asked, when answers will be given, the last date and time for responses, and when responses will be opened.
Every one of those should be a date a reader can act on, and where an hour matters the hour should be printed. “Within a week” is not a date. “By the end of the month” has produced arguments in more organisations than anybody would believe.
Two mechanical points that cause real disputes. Say which time zone or clock governs if there is any chance of doubt, and say what happens if the last date falls on a day the office is closed, because somebody will arrive to find a locked door and they will be right to complain.
And write the dates in a form nobody can misread. A date rendered in figures alone is read differently by different people, and it costs nothing to write the month in words.
The question this page is asked most and the one where a printed number would do the most damage, so here is the test rather than a figure.
Could somebody who first learns of this on the day it is published realistically prepare and submit a response by the last date? Not somebody who already knew it was coming. Somebody starting from the notice.
That is the question that will be asked later, so it may as well be the question asked now. And it takes into account things a deadline set from a diary does not: collecting documents, obtaining certificates from elsewhere, arranging any deposit, and getting a physical submission to a physical place.
Where your own rules set a minimum period, treat it as a floor and not a target. A process at the legal minimum is a process whose timing is the first thing anybody looks at.
And where the requirement is unusual, or the responses will take real work to prepare, allow more than you think. Nobody has ever complained that a tender was open too long.
Almost every notice is a short document pointing at a longer one, which is sensible, and the pointing has to be exact.
Say where the detailed documents can be obtained, from when, until when, and on what terms — whether they are downloaded, collected, or issued on request, and whether anything is payable for them.
The failure that recurs: documents said to be available from a date and not actually available until three days later, which quietly eats the response period and is noticed by everybody who tried.
So check availability on the morning of the stated date yourself, the way an outsider would — open the page, or walk to the counter — rather than assuming the arrangement worked.
And keep a record of who obtained documents and when. That list is useful during the process and it is essential afterwards, particularly when a corrigendum has to reach people.
Frequently dropped to save time, and dropping it costs more time than it saves.
A period in which prospective respondents may ask questions, and in which the answers are given to everybody, does three useful things at once. It surfaces ambiguities in your own documents while they can still be fixed. It prevents a respondent proceeding on a misunderstanding that only emerges when their response is rejected. And it demonstrates, on the record, that the same information was available to all.
The rule that makes it work is one line: answers go to everybody, not only to the person who asked. A clarification given privately is an advantage given privately, whatever was intended.
Where an answer changes anything material, it is not an answer any more — it is a corrigendum, and it belongs in the next section.
And publish the questions and answers together as a set, so that a reader arriving late sees the whole conversation rather than one half of it.
A short section, and short on purpose.
Most notices refer to a deposit accompanying the response, and many refer to a charge for the detailed documents. Whether yours does, in what amount, and how it is handled are decided by your own rules and by your organisation, and this page will not suggest figures or arrangements.
What the notice owes the reader is clarity about existence and location: that such a requirement applies, and where its terms are set out in full.
Three things worth checking regardless of the amounts. That the notice and the detailed documents say the same thing about them. That the mode of payment named is one that actually works on the dates concerned. And that what happens to a deposit afterwards — returned, adjusted, retained — is stated somewhere a respondent can find it before they part with money.
The complaints in this area are almost never about the amount. They are about money that went somewhere and took months to come back, with nobody able to point at the sentence that said it would.
Usual, useful, and occasionally treated as decoration.
A stated time and place for opening does something no other sentence in the notice does: it lets the process demonstrate itself. Anybody who cares can be present, and the fact that they could have been is worth something even when nobody comes.
Which means the sentence has to be kept. An opening moved without notice, or held earlier than announced, undoes the whole benefit and creates a grievance out of nothing.
So state a time you can keep, say who may attend, and if the time has to move, announce the move the same way the notice was announced rather than by telephoning the people you happen to know.
And record what happened at the opening — who attended, what was received, what was opened. That record costs one sheet of paper and answers the majority of questions that ever arise about a process.
Present in almost every notice and widely misunderstood in both directions.
What it does: it preserves room. It makes clear that publishing an invitation is not a promise to accept anything, which is a fair thing to say and a reasonable thing for a reader to know in advance.
What it does not do: it does not license a decision on grounds the notice never mentioned, and it will not rescue a process that applied an unstated criterion or applied a stated one unevenly. It is a reservation, not a shield.
Which is worth knowing because organisations sometimes relax after including it, on the understanding that the sentence covers everything. It covers the decision not to proceed. It does not cover the decision to proceed differently from what was announced.
So include it, and then draft the rest as though it were not there. That is the posture that produces a process nobody has to defend.
Small, dull, and the cause of a particular kind of argument that is very hard to resolve.
Where a notice appears in more than one language, two texts now exist, and somewhere in them two words will not mean quite the same thing. A respondent who read one of them is not being unreasonable for having relied on it.
So decide, before publication, which version governs if they differ, and say so in both. It is a single line and it removes an entire category of dispute.
Then have both versions checked by somebody who reads the language properly, rather than trusting that a translation of a technical requirement came out meaning the same thing. Specifications translate badly and dates translate worse.
Our newspaper advertisement guide covers the mechanics of publishing in more than one title and language — editions, proof, and what to do about a misprint — and that is deliberately not repeated here.
The test is not where you published. It is whether a person capable of doing this work could reasonably have missed it.
Answer that honestly and the placement decisions make themselves. Where do people in this trade actually look? Is the work local, regional or open to anybody? Is there a place such opportunities are conventionally posted, and would its absence there be noticed?
Then add whatever your own rules require, which may be more and is never less. The two questions are different and both have to be satisfied.
The pattern that satisfies neither, and is surprisingly common, is publication that is technically correct and practically invisible — the right kind of place, chosen so that nobody who might compete would ever be looking at it.
Our newspaper advertisement booking service handles the placing, and our public notice drafting and publication service the wider family of notices that are published for reasons other than inviting offers.
Increasingly the norm and worth a moment’s thought rather than an assumption.
Two questions decide it. Do your own rules permit it, and is that genuinely where people in this trade look? Those are different questions and both have to be yes.
Where both are yes, online publication has a real advantage: the record is precise. There is a timestamp, a page, and a version, and that is better evidence than most alternatives.
It also has a specific weakness, which is that a page can be edited without a trace. So keep your own dated capture of the page as published, and capture it again after every corrigendum. A page that quietly changed is the worst kind of record because it looks like a good one.
Many organisations do both — the full documents online, a shorter notice where people who were not already watching will see it. That combination is usually the honest answer to the question at the head of this section.
The ordinary pattern, and it works provided the short version is doing its job rather than merely being short.
A short notice must be complete about the essentials, accurate about where the full terms are, and consistent with them. Those are three separate tests and the third is the one that fails.
A short notice that contradicts the detailed documents is not a summary. It is a second set of terms, published in the place that more people read, and somebody will rely on the wrong one entirely reasonably.
So the last step before placing a short notice is always the same: put it beside the detailed documents and check every fact in it — every date, every figure, every condition — against them.
And make sure the short notice says, in terms, that the detailed documents govern. That line is not a substitute for consistency, but it tells a reader what to do when they find a difference.
The single most mishandled step in this whole subject, and the mishandling is almost always well-intentioned.
Something needs to change. A date, a quantity, a condition, an error. Somebody sends a message to the people who have already collected documents, because those are the people they know about.
Which leaves everybody who was going to respond later working from terms that no longer apply. A change known to some and not to others is precisely what a challenge is made of, and the fact that nobody intended an advantage does not help afterwards.
The rule is one sentence. Publish the corrigendum the same way you published the notice. Same place, same kind of visibility, plus direct intimation to anybody who has already come forward.
Say clearly what has changed and what has not, and number the corrigenda if there is more than one, so that a reader arriving late can tell whether they have the whole picture. And keep every version in the file, including the one that was wrong.
Ordinary, usually sensible, and occasionally the thing that saves a process.
After a substantial corrigendum, extending is the safer choice almost every time. People have been preparing against different terms, and the fair question is whether the remaining period is enough for the new ones.
An extension is itself a corrigendum and goes out the same way. Say the new date plainly, say whether anything else has moved with it, and say whether responses already submitted stand or may be replaced.
That last point is forgotten constantly and matters to anybody who submitted early. Somebody who filed against the old terms deserves to know whether their response is still in play.
And an extension granted quietly to one party is not an extension. It is the thing every rule in this area exists to prevent.
It happens — a requirement changes, funding moves, somebody realises the specification is wrong — and how it is handled matters more than the fact of it.
Announce it in the same place the notice appeared. People who spent money preparing are entitled to be told rather than to discover it, and the organisation that tells them properly is in a much better position if anybody asks later.
Record why. Not for anybody outside — for the file, and for whoever has to explain this in a year. A cancellation with no recorded reason is the kind of gap that invites a theory.
Deal with deposits and document charges promptly and say what is happening to them. Money left sitting after a cancelled process generates more ill will than the cancellation itself.
And if the requirement comes back later in a different form, say so openly when it does. A re-issued notice that quietly resembles the cancelled one, with the conditions adjusted, is the pattern people notice.
Collected badly by almost everybody, and it takes five minutes to collect properly.
Keep the complete page as published, showing the title of the publication, the date, and the notice in its position on the page. A cutting of the notice alone proves nothing about where or when it appeared, which is the only thing anybody will want to know.
Keep the booking record alongside it, and the same for every corrigendum. Where the notice is significant, an endorsed copy is worth having — our certified true copy guide explains what such an endorsement actually states and what it must carry.
For an online publication, keep a dated capture showing the address and the content together, taken on the day.
Then scan the lot and store it as one set. The question about a tender never arrives while the file is on somebody’s desk; it arrives when the file is in storage and the people concerned have left.
A small discipline that converts a pile of paper into an answer.
One folder, physical or otherwise, holding: the approval or decision to invite, the notice as drafted, the notice as published with proof, the detailed documents, the questions and answers, every corrigendum with its proof, the record of who obtained documents, the record of the opening, and the dates as they actually happened.
Put an index sheet at the front listing what is in it. Whoever needs this next will not be you, and they will be looking for one item rather than reading the whole thing.
Keep it longer than the process. Questions about how something was awarded tend to arise when the work itself goes wrong, which can be years later and has nothing to do with the notice at all.
And store it somewhere that survives a change of staff. A perfect file on one person’s laptop is not a file.
And whatever the invitation produces eventually becomes a contract, which is a separate document with its own logic — our vendor agreement guide sets out what that contract has to do that a purchase order cannot.
A fair question — if the rules binding a public body do not bind you, why do any of this?
Because the discipline is not primarily about outside scrutiny. It is about being able to explain a decision inside your own organisation. A purchase that cannot be explained is a problem with your board, your partners or your auditors long before it is anybody else’s.
There is also a practical benefit that has nothing to do with propriety: a clear invitation produces comparable responses. Vague invitations produce responses that cannot be compared with one another, and then somebody picks on instinct and calls it a decision.
So use as much of this page as fits your size. Even a one-paragraph invitation benefits from saying what is wanted, who may respond, by when, and how the responses will be handled.
And where the invitation leads to an agreement, have the agreement ready in outline before the invitation goes out — our agreement drafting service prepares it, and knowing what the contract will say changes what the notice should ask for.
The smallest version of this subject and, in day-to-day terms, the most common.
A building needs work. A trust needs a supplier. An association is spending money that belongs to its members, and somebody has to choose.
Here the value of a written invitation is almost entirely social. A documented process is the difference between a decision people accept and a decision people argue about for two years, and in a residents’ body that argument has a way of outliving the work.
So keep it simple and keep it visible: what is wanted, who may respond, by when, where responses go, and when they will be opened and in front of whom. Put it where the members can see it and not only where the rules require it.
Our society and trust public notice service handles notices for such bodies, and our company statutory notice publication service the notices a company has to publish for reasons of its own constitution.
The other half of the audience, and a short section that saves people a great deal of wasted effort.
Read it in this order, which is not the order it is printed in. The dates first. Can you actually do this in the time available, including obtaining anything you do not already hold?
Eligibility second. Do you qualify, today, with documents you can produce? Not “could we arrange it” — today.
Where the full terms are, third. Get them before forming any view, because the notice is a summary and the summary is not what you will be judged against.
Only then read about the work itself. Most of the afternoons wasted in this area are spent reading about work by people who were never going to be eligible or never had the time.
And before you submit anything, check whether a corrigendum has been issued. People forget, and a response prepared against superseded terms is usually just rejected.
Worth saying plainly, because expectations here cause real bitterness.
A notice does not promise that anything will be awarded. It does not promise that the lowest figure wins, unless it says so. And it does not promise that your costs of responding will be met by anybody — they will not.
What you are entitled to expect is narrower and more useful: that the conditions applied are the ones published, that they are applied to everyone, and that the process announced is the process followed.
So keep your own file too. The notice as you saw it, the date you saw it, the documents you obtained, the corrigenda, and what you submitted and when. That file costs nothing and it is the whole of your position if you ever need one.
And if something looks wrong, raise it in writing, promptly, before the last date rather than after the result. A question asked in time is a question. The same question after a decision reads as a complaint about losing.
Where the point has to be put to the organisation in writing rather than argued, the ordinary craft of doing that applies — our application drafting guide covers writing one ask, in dates, to somebody who can act on it.
Handled briefly, because by the time it happens the work that decides the outcome has already been done or not done.
Your answer is the file. Either it shows a notice that stated the conditions, published where people could see it, changed only by corrigenda published the same way, with dates that left a real window and a record of what happened — or it does not.
What is useful at that moment is to answer specifically rather than defensively. Take the complaint point by point and respond to each with a document. Sympathetic generalities make an ordinary query look like something worse.
Where the matter turns legal, whoever you engage for it is engaged and paid by you directly, and we stay on the documentation side. Our legal notice service prepares correspondence where that step is needed.
And afterwards, whatever the outcome, note what the complaint exposed. Most of them point at one sentence that was ambiguous, and that sentence is in your template for the next notice too.
Said in the middle rather than at the end, because it shapes what the rest of this is worth.
What to require is your decision. We can test a condition against the question set out above and tell you what a reader will make of it. We cannot tell you what risk your organisation should be protecting against.
Whom to award is your decision, and not one we take part in. A firm that drafts your notice and also advises on who should win is a firm with a problem, and so are you.
What your rules require is a question for your rules. We will ask you what they say and draft to them. We will not tell you what they say, because the organisations reading this page are governed by different books and confident generalities are how processes get challenged.
What we are useful for is narrower and real: turning decisions you have taken into a notice that says them completely, consistently and in the order a reader needs them.
None of them dramatic, all of them ordinary, every one avoidable at the drafting stage.
A specification written from one supplier’s brochure, visible as such to everybody else.
A response window nobody starting from scratch could meet.
A short notice that disagrees with the detailed documents, so that two sets of terms are in circulation.
A change told to some and not to others, which is the shape of every challenge in this area.
A condition applied unevenly, usually waived once for a good reason and never recorded.
No proof of publication, discovered three years later when somebody asks where and when it appeared.
We start from what you have already decided to invite, and we ask the questions that a notice cannot be written without: who is inviting, what exactly is wanted, who may respond, what your own rules require to appear, and every date in the sequence.
Then we draft. Complete, in the order a reader needs it, with the awkward parts stated rather than left for later, and with each eligibility condition put back to you against one question — what risk does this protect against, and is this the least restrictive way of protecting against it.
Then we check the notice against your detailed documents, fact by fact, because a short notice that disagrees with them is two sets of terms rather than one. That check finds something on most jobs.
Then we place it where you have decided it should appear, and hand you the proof of publication in the form that is actually useful — the whole page as published, with the booking record and the dates.
And when something has to change, we prepare the corrigendum and place it the same way, which is the step that most often goes wrong when nobody is responsible for it.
We do not decide what to require. Conditions belong to the organisation that carries the risk, and we would be the wrong people to set them.
We take no part in evaluation or award. Not an opinion, not a comparison, not a recommendation. A firm that drafts the notice and then helps pick the winner has compromised the notice.
We do not interpret your governing rules for you. We ask what they say and draft to the answer. Telling an organisation what its own procurement rules require, from the outside, is exactly the confident guess that gets a process challenged.
We promise no publication date. Space and schedules belong to the publisher, and a date offered in advance would be somebody else’s to keep.
We do not draft around a preferred party. If a specification is written so that only one party can satisfy it, we will say so before it is published rather than after somebody else does.
Drafting and placing begins at ₹2,500, the usual span is 2 – 5 days, you are told the whole figure before we start, and nothing is payable in advance. A corrigendum later, if one is needed, is a smaller piece of work and we price it as one rather than as a fresh job.
The publication charge is separate and belongs to whoever publishes. We tell you what it is rather than folding it into ours, because those are two different things and you should be able to see both.
What lengthens the work is almost never the drafting. It is a decision that has not actually been taken yet — a condition nobody has settled, a date that depends on somebody’s approval, a specification still being argued about internally. We would rather wait for those than publish around them.
And the plain note this page owes: the most valuable parts of it cost nothing at all. Test every condition against one question. Leave a window somebody could actually meet. Read the short notice against the detailed documents. Publish every change the same way you published the notice. Keep the whole page, not a cutting. Do those five things and most of what goes wrong in this area simply does not.
A tender notice is the first document of whatever contract follows, and it is examined far more carefully than it is written. We take the decisions you have already made and turn them into a notice that is complete, unambiguous and consistent with your detailed documents; we put every eligibility condition back to you against one test; we check the short notice against the long one fact by fact; we place it where you have decided it should appear; and we hand you proof of publication in the form that is actually useful. What to require and whom to award stay entirely yours.
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