How to spot a likely rebid before the new tender is published

Forecast boundary

A contract end date creates a question, not a tender

The planned end of an existing contract is evidence that the current arrangement has a boundary. It does not reveal what the buyer will do at that boundary. The buyer may exercise an option, make a permitted modification, award through an existing framework, run a new competition, bring the work in-house, reduce the scope or let the requirement end. More than one outcome may remain credible until the buyer publishes or acts.

Use the end date to open a renewal hypothesis record. Name the contract, preserve the source and list the possible outcomes without ranking them from habit. A prior competition, a continuing operational need and a fixed end can support closer monitoring. They still do not prove a rebid. The phrase “likely rebid” belongs only beside the reasons, counter-evidence and next trigger. The phrase “tender open” requires the official notice that starts the relevant procedure.

Contract clock

Reconstruct the term from source fields and clauses

Begin with the contract-details or result record, then inspect the governing contract or tender documents when they are publicly available. Capture conclusion date, service start, base duration, base end, optional periods, notice needed to exercise them, renewal count and maximum possible end. TED eForms has separate fields for options, option descriptions, renewal descriptions and the maximum number of renewals. Keeping them separate prevents the common error of adding every optional year to the current term.

Mark the provenance of each date. “Stated” means the source gives the date. “Calculated” means it was derived from a stated start and duration, with the formula retained. “Current by modification” means a later official record changed it. “Assumed” is not an acceptable production state; replace it with unknown and a named gap. If service start depends on mobilization or an order, a contract conclusion date may not yield the delivery end. Read the actual definition before calculating.

Contract lineage

Check changes and closure before predicting replacement

A contract can move after award. In TED eForms, a contract modification notice refers to a settled contract and later modifications build from the latest relevant notice. The current UK guidance likewise describes contract change notices for modifications that meet its publication rules. A change may affect term, value, scope or supplier position. Link it through the official contract identifier and read the changed field. Do not infer an extension merely because value increased, or infer a rebid because scope decreased.

Closure evidence matters too. TED’s voluntary completion form can report a contract after it finishes or terminates. Under the current UK regime, “contract termination” for notice purposes covers all ways a public contract comes to an end, and a contract termination notice is generally required subject to stated exceptions. A completion or termination record can close the incumbent phase, but it still does not prove the replacement route. Record actual end, reason where published, final value basis and any linked follow-on notice as separate facts.

• Link every change to the same official contract identifier.
• Preserve the field changed, date, legal basis and source version.
• Recalculate the clock only when the term evidence changes.
• Treat completion as closure evidence, not replacement evidence.
• Keep publication exceptions visible when a record may be absent.

Vehicle boundary

Do not use a framework expiry as the call-off expiry

A framework establishes terms for later awards. Its end controls when new call-offs can be made under the governing rules; it is not automatically the end of every contract already awarded through it. A call-off has its own identifier, supplier, scope, value and term. Forecast the delivery contract from those fields. Keep the framework as a related purchasing vehicle with its own renewal or replacement hypothesis.

This distinction can create two legitimate watches. One asks whether the buyer or central purchasing body will replace the framework, which may matter to suppliers seeking future access. The other asks what happens when an individual call-off ends, which may lead to another call-off, a competition elsewhere or no replacement. Never multiply the framework maximum value across listed suppliers or treat all framework members as incumbents on a specific call-off.

Buyer intent

Search forward from the buyer and backward from the contract

Use two searches. The backward search starts from a new planning or tender record and asks whether it cites the incumbent procurement, contract, framework or project. The forward search starts from the incumbent and looks across the buyer’s official pipeline, planned procurement, prior information, market engagement, tender and transparency publications. Search stable identifiers first, then distinctive scope phrases, locations, classification codes, contract manager or business unit, and incumbent supplier. Record why a candidate matches and why it might be unrelated.

Current UK pipeline guidance illustrates the boundary. Covered authorities publish qualifying planned procurements under specific spending and contract-value rules, may add voluntary entries, and can change their plans. The guidance expressly says that an authority is not legally bound to proceed with a procurement in its pipeline notice. Absence is also incomplete evidence because the duty does not cover every buyer or contract. A linked planned notice strengthens the hypothesis. A tender notice confirms that a procedure has started. Neither should inherit the incumbent scope without a comparison.

• Match official identifiers before fuzzy titles.
• Compare scope, geography, term, classifications and buyer unit.
• Preserve a possible match separately from a confirmed successor.
• Check whether the new requirement was split, combined or narrowed.
• Promote the record to live only from the governing open notice.

Confidence

Grade the claim, not the attractiveness of the account

Use a small verbal scale. “Confirmed” means an official source states the event, such as an exercised extension or live replacement procedure. “Supported” means several direct signals align, for example a dated pipeline entry that cites the contract and a near maximum end. “Plausible” means the timing and continuing need fit but buyer intent is not published. “Weak” means the connection rests mainly on age, title or historical cadence. “Contradicted” means a current source supports a different outcome. Confidence describes the forecast evidence, not the likelihood of winning.

Always include disconfirming evidence. An unused option, recent modification, active framework route, performance remediation, changed policy, lower spending or announced service closure can weaken a replacement hypothesis. Do not convert the labels into hidden numerical scores. Two agents given the same record should be able to explain the same grade from cited facts, even if a human reviewer chooses a different commercial priority.

Triggers

Replace the guessed publication date with observable triggers

A record needs a next check that another operator can execute. Good triggers include a stated option-decision deadline, the buyer’s next pipeline update, a planned notice date, the end of market engagement, a contract-change publication, the start of a procurement window or the current maximum end. Where the source supplies no event, choose a review date based on the remaining term and the team’s preparation lead time, label it as an internal watch date, and never display it as the buyer’s timetable.

The permitted work changes with the state. Before buyer intent appears, update capability mapping, incumbent facts and source queries. After an official planning notice, prepare proportionately and follow its stated action. When a tender notice opens the procedure, create a separate live opportunity and retrieve the controlling documents. If an extension is confirmed, move the successor watch to the new boundary. If the buyer closes or absorbs the requirement, record the contradiction and stop repetitive alerts.