Every cut-off, in order.

A pronounced one. September alone carries 685 of the 1730 cut-offs on this site, 40% of the year in one month, followed by October (270) and November (200). The quietest month is August, with 22. The reason is administrative rather than seasonal: European work programmes open in the spring and close before the evaluation rounds that precede the next budget year, and the US federal cycle pushes its own deadlines towards the end of the fiscal year. If you plan capacity, plan it around that curve, not around a steady trickle.

The median call is open for 133 days between opening and its cut-off, half of them give less. A quarter give 78 days or fewer, and a quarter give more than 190. That is the whole reason the fit check asks how fast you could submit: a 60-day window is comfortable for a single applicant and close to impossible for a consortium you have not assembled yet. Measured across 1296 calls that publish both dates.

616 calls close within 30 days. Those are the ones worth reading first, not because they are better, but because everything else can wait a week and they cannot. The list is sorted by cut-off precisely so this question answers itself.

Usually not. Most programmes run annually, so a topic that closed in September typically reopens in the next work programme with a similar scope and a new identifier. 34 calls on the site publish more than one cut-off, meaning a second chance inside the same call. The ones that genuinely happen once are pilots and preparatory actions, and those say so in their conditions.

Because a month only lists calls whose NEXT cut-off falls in it. A call with several cut-offs sits under the nearest one, so it appears once rather than in every month it is open. Months far ahead look thin for a duller reason: those work programmes are not published yet. 670 calls are announced with no date at all and appear in no month, they sit in the full list, sorted last.

The corpus is re-synced every night and the site is rebuilt with it. Cut-offs and countdowns are recomputed at build time, so a call that closed since the last sync leaves the site rather than sitting here with a stale date.

Because a call whose last cut-off has passed is not open, whatever its status field says. On the last build 1129 calls our sources still list as open had already closed, so they are not here.

Yes. The fit check reads every call against your organisation on the gates that decide admissibility (structure, co-financing, maturity, and whether the cut-off is still reachable) and shows the sentence behind each verdict. Calls that block you are shown with the condition that blocks them, because sometimes it is one you can change.