Ask a bid team where deals come from and most will point at the announcements feed. That feed is real, but it is the last step of a process that started years earlier, in public, with a date attached. When a ministry awards a 36-month contract, it is also announcing, to anyone who does the arithmetic, roughly when it will need the next one. The teams that win re-tenders treat the contract end date, not the RFP date, as the start of pursuit.
This lesson is that arithmetic and what to do with it: how contract periods work, why the re-tender is on a schedule, what belongs in the months before the RFP, and what you are up against in the incumbent.
Contract periods and end dates
As covered in lesson 1, government work is awarded for a fixed term: 12, 24, 36, occasionally 60 months, with 36 common for services. The end date is simple arithmetic on the published record: award date plus contract period. A contract awarded in April 2024 for 36 months ends around March 2027, and everyone who read the award notice has known since 2024.
Two honest caveats. Extension options exist, and buyers sometimes bridge with short extensions when a re-tender runs late, so the end date is an approximation, not an appointment. And not every portal publishes the contract period, so not every award yields a computable date. Where it is published, though, the forecast is free, and it is the cheapest pipeline signal in government sales.
Why re-tenders run on a schedule
Three forces make the re-tender close to inevitable:
- The need does not expire with the contract. Cleaning, catering, maintenance, security, and connectivity do not stop because a term ended. Continuity of service is an obligation, not a preference.
- Procurement rules prefer competition. Across the six states, the rules lean against extending a contract indefinitely when the work can be re-tendered. Extensions buy months, not years.
- Budgets renew on cycles. A recurring service sits on a recurring budget line, and a funded need with an expiring contract becomes a tender by default.
The timing is also regular at the near end. To have a new contract signed before the old one lapses, the RFP typically lands roughly 3 to 6 months before expiry: enough time for the closing window, the two openings, and the award. Work backwards from the end date and you get an expected announcement window, months wide, but months in advance.
The positioning window
The positioning window is the 6 to 12 months before that expected RFP. It matters because everything that decides a re-tender takes longer than a closing window allows:
- Relationships. Meet the buyer's technical department while the requirements are still soft. Learn what the incumbent does well, what irritates the buyer, and how the evaluation will likely be weighted. After publication, contact narrows to formal clarifications.
- Prequalification. Vendor registration on the right portal, classification certificates at the right grade, a current CR, and a bond line agreed with your bank. Each takes weeks to months, and none of them compress into a closing window.
- Teaming. The local partner, the specialist subcontractors, the OEM authorization. The strongest partners in a category commit early and often exclusively, so late teaming means choosing from whoever is left.
- Evidence. References, case studies, and site familiarity, assembled while there is still time to create the missing ones.
When the RFP publishes, positioning is over. The requirements are frozen, the timeline is fixed, and the best partners are committed. Whatever you do after that point is bid production. Necessary, but it only converts the position you already built.
How incumbents defend
Every re-tender has a bidder with years of preparation: the incumbent. Its advantages are structural. It knows the real scope, including everything the documents undersell. It knows its own delivery costs to the dinar, riyal, or dirham, so it can price close to the line with confidence. Its staff are on site, its equipment is amortized, and its contacts sit inside the buyer entity. Its standard plays follow from those advantages: seek an extension before a re-tender, emphasize transition risk and switching cost, keep key subcontractors locked in, and price from knowledge while challengers price from guesses.
Challengers counter each play directly. Make the transition concrete and small: a written plan, absorbed staff, a parallel-running period. Use the category's published history, bidder counts and spreads from lesson 2, to price from data instead of fear. Team for the exact gaps the buyer has lived with, because after years of one supplier, the buyer knows precisely what it is missing. And start early enough that the buyer has a reason to want a competitive field: incumbents are hardest to displace when the alternative is unknown.
A worked example: backwards from March
Worked example: a catering contract expiring in March 2027
A 36-month catering contract at a public authority was awarded in April 2024 for 9,000,000. End date: around March 2027. Expected RFP window: roughly September to December 2026. A challenger positions backwards from that:
12 months out (early 2026): confirm the end date from the award record, register as a vendor with the authority, and open the first conversations with the department that owns the service.
9 months out: classifications and certificates current; the bond line agreed with the bank, sized for a bid bond and a 10 percent performance bond on a contract near 9,000,000.
6 months out: teaming signed with a logistics subcontractor the incumbent does not control; references assembled; a clear view formed of the two scope changes the buyer wants this time.
3 months out: a pricing corridor drawn from the category's published bid history; the bid team's calendar blocked for the expected window.
RFP lands in November 2026: the challenger is editing a bid it has effectively been writing for a year. A competitor that starts the same day faces vendor registration, certification, a bank, a partner search, and a pricing model, inside a five-week closing window. Most of that list is simply not possible in the time.
None of this requires software; it requires knowing the end dates early. At the scale of one buyer you can track them by hand from award notices. At the scale of a market, that is what Ishara's Recompete Radar automates: where portals publish an award date and a contract period, it computes the end date, names the incumbent, and filters by horizons from 6 to 24 months.
You now know when the deal will happen and who is defending it. The remaining question is what winning it should cost, which is where the category's published history becomes a pricing tool. That is the next lesson.