You might notice two labels on government procurement portals if you have dealt with tenders before. One is "corrigendum". The other is "amendment". In many cases, the procuring office uses them as if they mean the same thing. In other cases, the terms point to different items inside the same tender. At times, a single change notice gets one label even though the actual content looks like it matches the other label better.
You might notice two labels on government procurement portals if you have dealt with tenders before. One is "corrigendum". The other is "amendment". In many cases, the procuring office uses them as if they mean the same thing. In other cases, the terms point to different items inside the same tender. At times, a single change notice gets one label even though the actual content looks like it matches the other label better.
This mix of terms shows up often on Indian government procurement sites. Even so, the day-to-day impact of a change to the tender set does not depend on the exact label. What matters for your bid is whether you can spot the updates, understand why they were made, judge how big the changes are, and follow what you are required to do next..
This blog lays out how corrigenda and amendments differ in principle. It also clarifies the significance of that difference, even when practice fails to maintain clear distinctions. Most importantly, it focuses on the questions that you should answer regardless of which label you see: what was changed, how major it is, and what actions it calls for from you.
The Distinction in Principle
In a strict sense, and in line with how these terms show up in formal purchasing papers, corrigendum and amendment do the work in different ways.
A corrigendum comes from a Latin idea tied to correction. It is used when the first tender has an error. That error might be a typo. It might be a wrong date. It might be a wrong figure or a miscounted quantity. It might also be an incorrect link to a standard or a technical requirement that was stated by mistake. The key point is that the tender’s goal was right, but the text carrying that goal was not.
So the corrigendum fixes the flawed part. It brings the document back to what was intended from the start. An amendment, in the strictest meaning, does something else. It changes the original tender, even though the wording in the first version was not wrong. The buying body now wants the content to be different. It may be responding to a new view, revised needs, or a shift in how the work should be handled. In short, an amendment adds a new intent. It is not meant to repair a mistaken expression from the earlier tender.
The difference matters in a practical way. One type of notice, a corrigendum, points to a flaw in the first paper. It says the original text was wrong. It also implies that people who relied on that text when they submitted offers were led astray. Another type of notice, an amendment, reads like a change in the rules. It can mean the task or condition has been updated. In that case, the submitters have to adjust their bids to match the new requirement.
In real life, the line is not so clean. Sometimes a buyer sees that a spec was not clear, not truly wrong. Even so, the buyer may still post a corrigendum. In effect, that “fix” can add new demands, because it just clears up earlier unclear wording. There are also cases where the buyer shifts its position. If the buyer changes a requirement in a way that is more like a structural revision, it might still label the update as a corrigendum.
Then there is how some portals handle it. Many procurement sites use “corrigendum” as a catch-all. They apply the same label to any update after the tender is posted, even when the update is not really the same kind of thing.
Why the Label Matters Less Than the Content
Procurement people on the buy side and on the supply side learn early how to read. They do not stop at the title or the label. They check what is inside the change note and judge it on its own. What you do next depends on what the document says, not on how it is named.
Start with one question. What has actually been changed? Then pick out the exact parts of the tender that now differ from before. Is it a date that moved? Is it a quantity? Is it a technical specification? Is it an eligibility rule? Is it a BOQ line item? Is it a commercial term? Is it a required document list? Once you know the type of change, you can see what parts of a bid that is submitted or still in progress must be revisited.
Next, ask how big the change really is. A typo fixed in a project title does not change the deal. But a new or corrected technical spec for a key performance measure can shift the whole outcome. This matter level guides how fast you need to act and how much work is required.
Does this change affect bids that were already sent? That is the key point for bidders who submitted before the update went out. When the due date is over and a new extension is added, some earlier bids might need updates. If there is no extension and the change is small, the earlier bids might stay as they are. Still, you have to look closely at what the change says and what the portal allows for bid edits.
Do bidders have to do anything? Not always. Some updates are only for information. Others ask bidders to confirm they agree to the new terms. In some cases, bidders must submit the bid again. The notice about the change should spell out what bidders must do. If it is not clear, the best move is to ask through the official question process.
.
Categories of Change and Their Typical Impact
Rather than focusing on the corrigendum-versus-amendment distinction, a more practically useful categorisation of tender changes is by their content and impact on bid preparation.
Administrative changes affect dates, addresses, contact details, portal access information, and procedural instructions. A change to the pre-bid meeting date, the query submission deadline, the bid submission time, or the bid opening date falls in this category. These changes are immediately operationally significant because they affect your bid calendar, but they typically do not require any substantive revision to the bid's technical or financial content. They do require immediate updates to your internal tracking and calendar systems.
Specification changes affect the technical requirements that the goods, works, or services must meet. A revised performance parameter, an updated material standard reference, a changed dimensional requirement, or a new testing protocol falls in this category. These changes may require revision of your technical proposal, re-evaluation of whether your proposed solution remains compliant, and potentially revision of your BOQ pricing if the specification change affects the cost of delivery. The materiality of a specification change ranges from negligible, a corrected cross-reference to a standard whose requirements are identical to the one previously referenced, to transformative, a changed performance requirement that your proposed solution cannot meet.
BOQ changes affect the measurement and pricing structure of the financial bid. New items added, existing items removed, quantities revised, units of measurement changed, or item descriptions clarified are all BOQ changes with direct financial impact. These changes require careful comparison of the original and revised BOQ to identify every line that has changed, reassessment of rates for affected items, and in some cases a fundamental revision of the cost model if the BOQ change is extensive.
Eligibility changes affect the qualification criteria for participation. A revised turnover threshold, a changed experience requirement, a new certification requirement, or a modified bid capacity formula are eligibility changes that may admit new potential bidders, exclude previously eligible ones, or require bidders to reassess and re-document their eligibility position. These changes are among the most consequential because they determine who can participate in the competition at all.
Commercial and contractual changes affect the payment terms, liquidated damages provisions, performance security requirements, completion period, retention arrangements, or other conditions of contract. These changes affect the risk profile and financial model of the contract and require reassessment of bid pricing, risk provisions, and cash flow planning.
Scope changes affect what the contractor is required to deliver. Additional work items, removed work items, or redefined project boundaries are scope changes that require comprehensive reassessment of the bid from the technical approach through the programme to the pricing. A significant scope change in a tender that has already been studied and priced in detail effectively requires the bidding exercise to be partially or substantially restarted.
How to Process a Change Document Systematically
Many bidders slip up as soon as a change note shows up. They read it one time, focus on the headline, and then stop. They do not do a full review. As a result, they miss side effects. They also overlook links inside the document that point to other places, which must be updated too. The bid team then works from a partial view of what still needs to be done.
You can use the same workflow for any tender change note. It works whether the paper says "corrigendum," "amendment," or "something else."
First, read the whole document. Do not rely on the short recap or the opening pages. Key points can show up much later. If you skim and only catch the main headline, you can miss a smaller change and end up sending a bid that does not meet the requirement on that smaller point.
Next, list what has actually changed. Write down each item that was modified in the tender. For each item, note the old wording and the updated wording. Keep this list as your main working sheet while you update the bid.
Then, judge how important each change is on its own. One change can matter a lot, while another in the same note might be minor. If you rank them separately, you can spend time on what matters most while still handling the smaller items.
Check each updated part against where you are in bid prep right now. Which step is that section in? Is it done already? Did you send it in? If it needs edits, how much work is left?
Revise your compliance list and your bid schedule so they match the updates. If the due date moved, adjust every earlier internal date that depends on it. If you added a new document to provide, put it on the compliance list and name who will write it.
Tell the full bid team about the changes, especially anyone who is working on the sections that got touched. If a technical detail is only shared with the bid manager and not with the writer who is drafting that section, the new version will not show up in the bid.
Write down what you found and what you did. Keep a short internal note that states what changed, whether it matters, and what you plan to do next. This gives you a paper trail if someone later asks if the change was handled.
When Multiple Changes Are Issued in the Same Tender
Tenders with long bid periods can get more than one change notice. In some cases, a second change notice comes in before bids are due. Handling this kind of sequence is not the same as reading each notice alone.
If a first change notice has already been issued, then the next one needs a clear check. You have to confirm what version of the tender the new notice is changing. If the second notice edits a part that the first notice already edited, that part now has three versions. The newest version is the one set by the second notice. If the second notice edits a different part, then it does not clash with the first. It just adds another item to the overall list of changes.
A practical way to avoid mix-ups is to keep a change log for each tender that is still open. The log should note each issued change notice. It should also show the issue date, the sections that were touched, and which version is in force for each affected section. With this, people do not lose track when they process notices one at a time. The log also shows the full chain of changes. That helps when preparing the bid. It also helps later if there is a dispute about what the bid was based on.
It also matters that several changes can add up. When you review them together, the overall effect may be bigger than what any single notice suggests. For example, a shift in the technical specification, plus a change to the completion period, plus a change to the LD rate can form one combined risk picture. That risk has to be checked as one set, not as three small separate items.
The Timing Problem: Changes After Submission
A specific category of change that requires particular attention is the change issued after the submission deadline, which creates the situation analysed in the earlier blog on scope changes after submission. The principles from that analysis apply here too, and this section focuses on the specific dimensions that are most relevant in the corrigendum and amendment context.
A change issued after submission with no deadline extension typically implies that the procuring entity considers the change minor enough that already-submitted bids remain valid and evaluable without modification. In these cases, the evaluation committee is expected to apply the amended provision when evaluating all bids, effectively treating all submitted bids as if they addressed the amended requirement even though they were prepared against the original.
This assumption creates risk for the bidder in two directions. If your bid is non-compliant with the amended provision, you may be disqualified even though you complied with the original provision as published. If your bid is compliant with the amended provision by coincidence but other bidders are not, you gain a competitive advantage from the change that was not your doing.
A change issued after submission with a deadline extension explicitly invites bidders to revise and resubmit. Whether using this opportunity is mandatory or optional depends on whether the change is material enough to affect compliance if not addressed. Where re-submission is optional and your original bid is compliant with the amended provision, re-submission may not be necessary. Where your original bid is non-compliant with the amended provision, re-submission is essential to avoid disqualification.
A change issued after submission that materially changes the scope, specifications, or commercial conditions without extending the deadline, thereby preventing bidders from revising their submissions to address the material change, is procedurally questionable and potentially challengeable as unfair to bidders who submitted in good faith against the original specification. The pre-bid query mechanism for raising concerns about such situations has passed by this stage, and the formal complaint mechanism through the procuring entity or the CVC is the appropriate channel.
Building a Process That Catches Every Change
Bidders often overlook the effect of a change note because they fail to notice it. Sometimes they do not check it at all. When a team is rushing to finish the technical part and set prices for the BOQ, it is easy to skim over the procurement portal. A new change note can sit there for a day or two, and the team may not see it. This risk gets worse in a live tender with a short deadline. If a change note was posted the day before and you notice it late, you can end up with serious issues. Even a small delay can turn into a major problem fast.
You should treat portal checks as a daily task for every tender that is open. Do not wait for a quiet moment. Keep the habit in place from the day bids are published until the submission day. Many e-procurement sites show a pop-up notice when new files are added. Some also send email alerts to bidder accounts. Make sure those alerts are turned on the right way. Confirm they go to the correct person on the team. Also confirm that the person who gets the alerts is expected to read new notes right away and share them with others.
A missed change note that leads to a noncompliant bid or wrong pricing is not just bad luck. It is a breakdown in the process. A good monitoring setup should flag every update across all open tenders, no matter where you are in the bid window when the change is posted.
Final Thought
A change document might be named a corrigendum, an amendment, an addendum, or a clarification. The name itself does not decide how it affects your bid. What matters is the text and the actions it asks from you. For every change document, you can ask the same simple thing. What is different now compared with what was true before this document came out? And what do I have to do because of that difference?
Not every change has the same weight. Some items are only for your records. Other items mean you must update one part of your technical proposal. Some changes push you to reprice large parts of the BOQ. A few changes force you to rethink your position in a real way, which can change your go or no-go call. Bid teams learn to sort these cases out fast and correctly. They do it with a set method, not with a last-minute reaction.
At the time you submit, your tender must match the tender that exists at that time. That means you must include every issued change up to your submission deadline. If your bid is based on an older version, it means you missed something or you did not handle it fully. In government purchasing, that mismatch is where problems show up. It is also where authorities reject bids.
