DEV Community

Dome
Dome

Posted on Fully Autonomous

How to spot a GeM tender amendment that changes your bid

An extension to a GeM tender may give a reseller three more days to respond. An amendment posted at the same time could also triple the warranty or require a new authorization letter. I’d send those two changes to different people. The deadline goes to the calendar. The warranty goes to the person who priced the bid.

This JavaScript example compares two snapshots of a bid. It uses fictional records and treats the official tender and corrigendum as the source you check before submitting.

Record what could change your quote

Archive the original document and each amendment against the same official bid ID. Assign your own increasing revision numbers as you capture them. Keep the source document beside each snapshot so you can explain why you flagged a change.

Record times with the offset shown on your source. In this example the times are in India Standard Time, so the strings end in +05:30. Capture authorization as true, false, or null when you couldn’t tell from the document. A reviewer needs that third state.

const trackedFields = ['deliveryDays', 'warrantyMonths', 'oemAuthorization'];

function classifyRevision(before, after) {
  if (before.bidId !== after.bidId || after.revision <= before.revision) {
    return { action: 'ignore', changed: [] };
  }

  const deadlines = [before.closeAt, after.closeAt].map(value => Date.parse(value));
  const changed = trackedFields.filter(field => before[field] !== after[field]);
  const incomplete = deadlines.some(deadline => !Number.isFinite(deadline)) ||
    trackedFields.some(field => before[field] == null || after[field] == null);

  if (incomplete || changed.length > 0) return { action: 'review', changed };
  return { action: deadlines[0] === deadlines[1] ? 'unchanged' : 'update_calendar', changed: [] };
}

const before = {
  bidId: 'EXAMPLE-BID', revision: 1,
  closeAt: '2026-12-02T15:00:00+05:30',
  deliveryDays: 30, warrantyMonths: 12, oemAuthorization: false
};
const extension = { ...before, revision: 2, closeAt: '2026-12-05T15:00:00+05:30' };

console.log(classifyRevision(before, extension));
// { action: 'update_calendar', changed: [] }
console.log(classifyRevision(before, { ...extension, warrantyMonths: 36 }));
// { action: 'review', changed: ['warrantyMonths'] }
console.log(classifyRevision(before, { ...extension, oemAuthorization: null }));
// { action: 'review', changed: ['oemAuthorization'] }
Enter fullscreen mode Exit fullscreen mode

Put a person on each review

Check the latest official bid and amendments on GeM BidPlus. Give a warranty change to pricing, a different delivery window to operations, and a new authorization requirement to the OEM contact. In a team of one, put the next step and the person you need to hear back from in the same row.

The sample knows about three fields. Add quantity, consignee locations, samples and other requirements that change your own cost or eligibility. If an alert says unchanged, it means those configured fields matched. Give the latest official documents a read before you submit.

Use DOME’s GeM tender explorer to build a shortlist of bids to monitor.

AI disclosure: This article was drafted with AI for DOME. The sample bid records are fictional and the classifier was checked against five cases.

Top comments (0)