International Science Council Global Science Fund

Captured cycle: This page is retained for historical guidance. Confirm whether the program has reopened before planning an application.

International Science Council Global Science Fund

Overview

The Global Science Fund is an ISC-supported funding mechanism connected to the Council’s broader mission of using science as a global public good. The opportunity page you will find through ISC has moved from an older route (/actionplan/global-science-fund/) to https://council.science/our-work/global-science-fund/, so the record is currently a bit messy. If your first instinct is to stop at the old URL, do not. Use the new canonical page and then verify the active status of any call.

In plain language, this is for organizations that want to use a targeted grant to build collaboration across borders, disciplines, and institutions to work on scientific work with real-world outcomes. It is not a single-researcher scholarship program. It is about project teams, evidence-based planning, and practical implementation. The previous listing indicates a maximum award of up to $100,000 and a closing date of 2025-05-30. Treat that date as historical unless you can confirm that a new round is open, because some ISC pages are program-level and do not always show a live call directly.

The practical implication for readers is simple: this is a chance to move a collaborative science idea from concept toward action, but only if you can demonstrate that your consortium can operate responsibly, transparently, and globally. If your team is still one person and one lab, this likely is not the right fit. If you already have three to ten partners on an active shared strategy, it could be.

At-a-glance

What this opportunity is for

The fund sits at the intersection of grant support and convening power. In many global initiatives, funding is only one piece; what matters equally is whether there is a clear ecosystem of partners, delivery capacity, and follow-through. This is especially true for ISC, because the underlying framing is collaborative rather than competitive-competitive in a narrow way.

For many teams, the confusion comes from over-reading the title. “Global Science Fund” sounds broad, but this is usually not funding for random science ideas. ISC’s positioning around a global public good means proposals tend to be judged on shared benefit and implementation relevance. In most cases, a strong proposal explains:

• Which global challenge it addresses.
• Who will carry out each part of the work.
• How knowledge will be shared, not just produced.
• How the project scales or can be replicated after the grant period.

The opportunity is therefore best understood as a structured invitation to coordinate work, not simply to win a small grant and do one-off reporting. The program framing is strongest for mission-like efforts: climate adaptation, data systems, ecosystem and water resilience, equity and inclusion in science practice, science-policy interfaces, and transdisciplinary models where social and technical knowledge need to be co-produced.

What it offers (and what it likely does not)

What it likely offers:

• Seed or small-scale grant support to initiate or strengthen multi-actor international research or action.
• Visibility and confidence for teams that can demonstrate a serious governance model.
• A chance to align with ISC priorities and broader global efforts in sustainability science.
• A pathway to build credibility with other funders by proving your team can deliver across borders.

What it likely does not offer by itself:

• A blank cheque for unrelated local pilots.
• A single-researcher personal award or early-career fellowship format.
• A substitute for your own institutional budget and financial controls.
• A chance to be approved with low-detail plans.

The value of this opportunity is amplified when your ask is practical and measurable. ISC is interested in outcomes, but also in how you organise knowledge, engagement, and governance to get there. The strongest applications feel like project plans with a public good lens, not grant narratives built around funding as the center of the story.

Is this worth your time? A practical decision framework

Use this framework before you invest 5, 10, or 20 hours in drafting.

1) Relevance score (40%)

Ask: Does your project directly address a global challenge where collaboration changes what is possible?

• High fit: climate impact, social resilience, sustainability transitions, cross-border systems, policy-linked implementation, or knowledge brokerage.
• Medium fit: technical science questions with some partnerships and policy relevance but limited global impact design.
• Low fit: single-institution pilot with no external partners and no external beneficiaries.

If you score low here, the effort is often not worth it.

2) Collaboration readiness (30%)

Ask: Can you show that partners are real, not aspirational?

• You should name who leads what, with clear roles, not just affiliations.
• You should provide a mechanism for decisions, conflict resolution, and timelines.
• You should already have letters of interest or evidence of commitment.

If at least one partner has a defined scope and signed letter of intent, this is often a good sign.

3) Execution realism (20%)

Ask: Can your consortium produce tangible outputs in the grant window?

• Do you have data access, ethics approvals, permissions, and baseline logic?
• Is there a realistic budget and cash flow?
• Can you deliver at least one visible output before the grant closes?

If your current readiness is mostly conceptual with no timeline anchors, this could become a low-yield effort.

4) Institutional stewardship (10%)

Ask: Can your lead organization legally and administratively run cross-border funds?

• Is there a finance owner?
• Is there reporting capacity?
• Have you handled donor terms before?

A good grant partner is not only about science quality; it is about operational trust.

If your total score is under about 70 out of 100, pause and build capacity before applying.

Who should apply

The opportunity is built for organizations and coalitions with proven collaborative capacity. Good candidates include:

• Research consortia led by universities, science academies, international NGOs, and mission-oriented networks.
• Regional or cross-regional alliances that can combine local knowledge and technical expertise.
• Teams with social and natural science integration capacity.
• Groups that can show how the project contributes to outcomes beyond publication.

Not ideal:

• Single actor projects with minimal partnership structure.
• Teams where most core components depend on one person.
• Proposals without any implementation pathway or who treat the grant as a subsidy without accountability.

Suggested applicant profile checklist

Eligibility and readiness checklist

The record lists three baseline criteria. Treat these as a starting gate:

1. ISC member organizations and partners.
2. Collaborative international project.
3. Focus on global challenges.

These three are broad but not optional.

1) ISC member organizations and partners

If you are not an ISC member or a direct partner, do not assume ineligibility without confirming. You may still qualify indirectly through alliance channels or partnered structures. But your application should explain why your entity is accepted as a credible implementing partner in the ISC ecosystem. Evidence you can provide:

• Existing formal collaboration histories.
• Governance or partnership documents.
• Previous joint activities with ISC-linked institutions.

If your team does not have those, your first step is to secure a partner with institutional standing.

2) Collaborative international project

This is likely the strongest differentiator. Your proposal must make collaboration operational, not rhetorical.

A collaboration is operational when:

• Decision rights are explicit.
• Data or workstream handover is clear.
• Roles are role-based (lead, co-lead, technical, community engagement, communications, monitoring).
• You have a partner comms cadence (e.g., monthly checkpoints, shared tracker, version control for drafts).

3) Focus on global challenges

Global challenge means your project contributes to a problem that is broader than one institution or city. It may still be local in operations, but your learning should be transferable. Good framing examples:

• Water stress and climate vulnerability pathways.
• Governance and inclusion in access to science, data, or capacity.
• Policy-relevant science in agriculture, sustainability, and risk adaptation.
• Ecosystem-scale interventions where knowledge needs social co-creation.

How to apply (practical, concrete workflow)

Because the page currently maps to a broader program page, treat this as a two-layer process: verify the active call first, then apply fast with a polished package.

Step 1: Confirm current status before drafting

• Open the canonical URL in the browser.
• Confirm whether an active call for applications is live.
• Confirm deadline, budget, and required language.
• Confirm whether the call asks for project concept notes, full proposals, or letters first.

If status is unclear:

• Contact ISC program staff through official channels listed on their site.
• Ask one direct question: “Is this call currently open, and if so, what is the latest application portal and full template?”

Step 2: Build a one-page concept

Start with a one-page concept to test fit internally:

• Problem statement (what issue, where, and for whom).
• Who is involved (all named organizations and roles).
• What success looks like after 6 to 12 months.
• Why collaboration is essential.

If this is not coherent in one page, your full proposal likely will not be coherent either.

Step 3: Set a realistic timeline

Use a reverse timeline from deadline:

• 4 to 6 weeks before: finalize partner commitments and data access assumptions.
• 3 weeks before: draft budget and procurement assumptions.
• 2 weeks before: draft narrative, impact logic, and risk register.
• 1 week before: collect peer review comments and final signatures.

Even if this looks compressed, this is a good minimum.

Step 4: Build required materials

Use concise bundles and make each one answerable by an external reviewer in one pass:

• Executive summary (max 1,000 words).
• Partner letters and role matrix.
• Budget with justification.
• Monitoring, evaluation, and learning plan.
• Data/privacy and ethics or governance note where relevant.
• Implementation schedule and risk mitigation plan.

Step 5: Pre-submit peer review

Run a red-team review inside your consortium:

• A scientist asks: is the methodology sound?
• A program lead asks: is timeline realistic?
• A finance lead asks: is budget auditable?
• A partner asks: is ownership clear?

If you cannot answer all four, pause.

Timeline and deadline strategy

The existing record lists a deadline of 2025-05-30. Because many ISC pages are program-level and can be restructured, use this as a benchmark only if the page confirms it is the current open round.

If this specific deadline is truly historical:

• Do not submit to a closed cycle.
• Use your materials as a foundation for the next call.
• Set a 2-week internal review cycle every quarter so you can submit immediately when a new round opens.

If a live call exists with a different deadline:

• Rebuild your schedule backward from that date.
• Prioritize essentials first (narrative, partner map, budget, evidence).
• Use internal hard cuts for each milestone.

When working across countries, align your calendar with shared working hours. Add a one-day buffer before all internal deadlines for time zone lag.

Required materials: what to prepare

Narrative section

Your narrative should answer these directly:

• What is the problem and why is it urgent now?
• Why is collaboration essential and not optional?
• What concrete outputs will the project produce?
• How does this help people beyond one country or one institution?
• What is the path from outputs to impact?

Budget section

A clean budget is not just numbers. It proves governance maturity.

Include:

• Staff costs tied to specific deliverables.
• Partner coordination costs.
• Data or platform costs for shared workflows.
• Community/field engagement costs where relevant.
• Monitoring and reporting costs.
• Contingency line and explanation.

Avoid vague lump sums. Every cost should map to an activity.

Evidence section

Give your proposal evidence, not adjectives:

• Prior joint outputs.
• Previous letters from beneficiaries or institutions.
• Previous budget or reporting track records.
• Any prior publications, policy uptake, toolkits, or implementation frameworks.

Risk and compliance section

Include at least five explicit risks and mitigations:

• Partner delays.
• Data permission delays.
• Regulatory differences across countries.
• Cost overrun.
• Staff turnover.

For each risk, name who is accountable and what trigger activates the contingency.

Common mistakes to avoid

1. Submitting a technically strong idea with a weak governance model.
2. Treating collaboration as a list of names without role clarity.
3. Submitting vague budget lines with no direct activity mapping.
4. Ignoring reporting and dissemination obligations.
5. Underestimating coordination cost in international work.
6. Framing impact as publication-only.
7. Skipping partner confirmation and calling it “in progress.”
8. Copying generic language from previous applications without adapting to this specific opportunity.

Review your draft with this test: can a reviewer tell what this project will do in 6 months, 12 months, and 3 years? If one part is vague, strengthen it.

Common red flags that reduce approval chances

• No measurable outcomes.
• Overly broad scope with no phasing.
• Underdescribed decision governance.
• No local co-ownership or beneficiary-facing logic.
• Hidden assumptions that only one partner has the true delivery role.
• Weak language around ethics, consent, data sharing, or benefit-sharing.

Selection mindset and readiness tips

ISC-style opportunities often reward three habits:

• Clarity: your proposal should be easy to scan.
• Discipline: every section should align to a clear result.
• Accountability: you show who does what, by when, and with what evidence.

Before you submit, test each paragraph:

• Does this sentence help an external reviewer decide if the project is real?
• Does it add measurable detail?
• Does it show partnership depth?

If you need fewer than half the words and less detail to make your case, your application is probably clearer than average.

How to decide whether it is worth proceeding

Use the following decision prompts:

• Can we show at least one strong letter from an international partner?
• Do we have internal ownership for finance and reporting?
• Is our timeline plausible with current capacities?
• Can we describe success in terms of concrete outputs and beneficiaries?
• Are we prepared to be transparent about limitations?

If you answer yes to at least four prompts, proceed to a full draft. If you answer yes to two or fewer, pause and scale back or redesign with a more realistic scope.

If your project is rejected

Rejection is common in global funding. Do not treat this as a failure of science quality alone.

Take these steps:

1. Keep all reviewer notes and internal notes.
2. Capture exactly where clarity broke (scope, partner confidence, budget, risk).
3. Rework your proposal into the smallest coherent pilot version.
4. Build a stronger pre-existing collaboration layer and reapply when a new call opens.
5. Use the existing grant narrative to update your organization’s evidence systems.

Good programs often reward teams that keep showing up with better evidence and stronger governance, not first-round perfection.

FAQ

What should I do first?

Open the official page on the ISC site and confirm whether a live call exists. If details are not visible, ask the ISC contact listed for partnerships or opportunities. Do not rely on the old URL.

Is this an open, always-on fund?

Based on current page behavior, it is not clearly always-on from the visible record. Treat it as a program-linked opportunity that can have changing call windows.

Is the listed deadline of 2025-05-30 still usable?

Use it only if the official page explicitly confirms a live call with that deadline. In many cases, the date in records may reflect a previous round.

Who can lead the application?

A lead institution with finance and reporting capacity, supported by named partners, is best. Avoid solo institutional leadership unless project complexity is very low.

Can smaller organizations apply?

Yes, if they are part of a credible partnership structure. The strength is often in consortia, not size.

Do I need to be an ISC member?

The published criteria mentions ISC member organizations and partners. Treat membership/partnership as a threshold and verify current requirements from the call materials.

What if our consortium has uneven resources?

That is common. Be explicit about this in your internal planning. Good proposals do not require identical capacity across partners; they require clear division of labour.

How much evidence is enough?

Enough to prove you can start now. A strong short evidence set includes existing partnership documents, prior milestones, and a realistic budget that can be externally audited.

Official links and resources

• Official Global Science Fund page: https://council.science/our-work/global-science-fund/
• ISC Science Missions for Sustainability context: https://council.science/mission-science/
• ISC partnership pathway for funders and coalitions: https://council.science/science-missions-partners/
• About ISC and program context: https://council.science/about-us/
• ISC priorities and program portfolio: https://council.science/what-we-do-overview/
• ISC contact and support context shown on program pages (use embedded contact links on the official site)

Next steps you can take in the next 7 days

1. Confirm live status and collect official call documents.
2. Assign roles: science lead, finance lead, and partner lead.
3. Draft and circulate a one-page concept note.
4. Build a risk register and timeline that reflects international coordination.
5. Prepare a partner confirmation packet (letters, roles, commitments).
6. Make a hard go/no-go decision based on readiness criteria.

If you have to submit to a current call quickly, do not perfect everything. Perfect the minimum viable proposal first:

• A clear problem statement.
• A clear partnership map.
• A clear budget.
• A clear output timeline.
• One clear risk section.

Then submit, and improve after submission for future cycles. This opportunity rewards clarity, collaboration quality, and execution discipline.