Quick poll, we're deep in October now and time is the scarce resource. Reply with A, B or C for what's swallowing your hours this week: A) Writing, the text itself B) Budget, the numbers and justification C) Partners, the consortium and coordination I want the raw picture, so vote before you read the rest. Here's why each one is a trap, and the trap is different in each case: A) Writing feels productive because you can always improve a sentence. That's exactly the danger, prose has a point of diminishing returns and you pass it early. Endless rewriting is often avoidance of a harder, unfinished section (usually impact or the work plan). If writing is eating your week, ask whether you're polishing to avoid deciding something. B) Budget feels like admin, so it gets pushed late, and then it fights back. A budget that doesn't visibly match the work plan reads as a credibility problem, effort with no matching activity, or a cost with no matching task. The trap is treating it as arithmetic to finish at the end, when it's actually part of your implementation argument. Draft it alongside the work packages, not after. C) Partners is the one time-sink you don't fully control, and that's the trap, it expands to fill whatever you give it. Waiting on a partner's section, a letter, a figure. The fix is to set a hard internal cutoff and build the proposal so a late or thin contribution doesn't sink the whole thing. Chasing consortium consensus on wording is a bottomless well. Cast your vote in a reply, A, B or C, and one line on why. I'll come back with a targeted suggestion for whichever is winning, and it's useful to see where the group's time is actually going this week.

A short one you can act on today, because it catches more lost points than any writing tip I know. Most proposals that score below threshold aren't badly written. They just quietly fail to answer something the call explicitly asked for. The evaluator has a scoresheet built from the call's criteria, and if a criterion has nothing to score against, that's not a low mark, it's a gap. The walkthrough, 20 minutes, do it before you polish anything: 1. Open the call's evaluation criteria and the topic text side by side with your draft. For Horizon that's usually Excellence, Impact and Implementation, but read the actual sub-points, they vary by call and cluster. 2. For each sub-criterion and each "the proposal should describe / address / demonstrate" line, find the exact place in your draft that answers it. Not the general vicinity, the sentence. 3. Where you can't point to a sentence, you've found a gap. Mark it. That's a place a reviewer's scoresheet has a blank. 4. Watch especially for the easy-to-miss requirements that still carry marks or are eligibility gates: data management, open science, gender dimension, ethics, and any cross-cutting priorities the topic names. A missing DMP or gender-dimension paragraph isn't a style issue. 5. Only after every criterion maps to real text should you go back to improving prose. The mindset shift: you're not writing an essay about your project, you're filling in an answer for every box the evaluator has to score. A brilliant section that answers a question nobody asked earns nothing. Always confirm the exact criteria and any topic-specific requirements in the call conditions on the Funding & Tenders Portal, don't rely on last year's structure. Check yours now: run the map for your current draft and reply with the one criterion you found least covered. Naming it is half the fix, and someone else here is almost certainly staring at the same gap.

We're in the thick of the autumn deadlines now, so let's talk about the least glamorous skill in proposal writing: triage. When time is short, the instinct is to polish what already looks good. That's backwards. Evaluators score against the criteria in the call, so your remaining hours should go to the parts that carry marks and are still weak, not the parts that already read well. Here's the order I protect when the clock is against me: 1. Objectives that are actually measurable. If a reviewer can't tell whether you succeeded, everything downstream wobbles. Fix vague objectives first. 2. The impact pathway. Not the vision, the pathway: who benefits, through what route, and what has to be true for it to work. This is where proposals quietly lose points. 3. Methodology credibility. Enough detail that the approach is convincing, and honest about assumptions and risks. And what I cut, or stop touching, when time runs out: - Re-wording sentences that are already clear. Clarity has a ceiling; you hit it faster than you think. - Extra references beyond what's needed to show you know the field. - Design flourishes on figures. A clean, legible figure scores the same as a beautiful one. - Chasing a perfect summary at the expense of the sections that hold the marks. Get the summary solid, then move on. The uncomfortable truth: a proposal that's strong on objectives, impact and method but a little rough on prose beats a beautifully written one that's vague on what it will actually deliver. One caveat, always check the call conditions on the Funding & Tenders Portal, weightings and page limits differ by call and can change how you triage. Your turn, two quick things in a reply: what's your next deadline, and what's the single biggest blocker between you and submitting? I'll read every one and point you somewhere useful.

I have put the call-monitoring part of my own workflow online, free and open to anyone: funding.s-n-m.eu It sweeps eight public sources once a day and lists what is open. As of this morning: 1,370 open calls and 283 forthcoming, across 70 funding bodies — the EU Portal, Grants.gov, UKRI, SNSF, ICGEB, IDRC, Novo Nordisk Foundation and CZI. Two things it does that a portal search does not: - It reads the scope text for exclusion clauses, so a call that mentions your field ten times but excludes it does not sit at the top of your list. - You can type your institution's name and get calls ranked against what your institution actually publishes on, using public bibliographic data. No account, no tracking cookies, nothing to install. If it saves you the Monday-morning portal crawl, it has done its job.

September is where the calendar stops being theoretical. Of the public research calls I follow, 344 close within the next thirty days. Whatever you are applying for this autumn, you have almost certainly already met it. Which makes this the moment for the least glamorous habit in grant work: reading the call to the end before you commit any real time to it. Here is why, with a live example you can check yourself. HORIZON-CL6-2026-01-CIRCBIO-07 — "Advancing the European bio-based innovation enabled by biotechnology and biomanufacturing concepts". The word biotechnology is in the title, and six more times in the scope text. If you run a health biotechnology group, read the title and skim the summary, this call looks like it was written for you. Further down the same document: "The applications in health biotechnology, as well as the biofuel/bioenergy area are excluded, to avoid overlaps with Horizon Europe Clusters 1 and 5." It closes on 17 September. A team that read the top of the page and started drafting has ten days left and no eligible proposal. There is nothing unusual about that call. The sentence that rules you out is almost never in the title or the summary. It sits in the scope, in the specific conditions, or in the general annexes — because that is where the boundary between one cluster and another gets drawn. The habit, which costs about two minutes: 1. Open the topic on the Funding & Tenders Portal and read the scope and the specific conditions to the end. Not the summary. 2. Search the page for "exclud", "not eligible", "out of scope", and the name of your own field. 3. Only then decide whether it is worth a fortnight. The Portal is the source of truth for any specific topic. Dates, conditions and exclusions change between versions, so check them there rather than trusting a summary anywhere else — including mine. Second thing, and I said I wanted to make this a habit here: win of the week. Drop one small win from your grant work in the comments. Read a Work Programme properly. Got an answer out of a partner who had gone quiet. Said no to a call that did not fit — saying no early is a win, it is a fortnight you did not lose.