Ministry of Science International Collaboration Grants

This funding opportunity is intended for Israeli researchers who want to run real scientific research projects with international partners. The Ministry supports cooperation between Israeli teams and researchers in another country when the project is designed as a joint effort and managed through an approved collaboration framework.

The strongest way to understand this opportunity is to treat it as a track, not a single always-open solicitation. The program supports a specific type of grant, and each call can have different rules by year, by theme, and by partner country. That means the details that matter most to you are call-specific: partner eligibility, application windows, required documents, and scoring criteria.

Before you invest time, the practical first step is to confirm the active call text. The page currently listed in this record is an older English route (most.gov.il/English/Research/International_Cooperation/) that was flagged during a check as not reachable from that exact path. We are now directing readers to the ministry landing context where current call materials are published.

At-a-glance

What this opportunity is (and what it is not)

This is a grant opportunity for cross-border research collaborations, usually with a scientific and innovation focus. It is not a general travel grant, not a consultancy contract, and not necessarily a broad institution-building fund. It is meant for projects where research output is the central result and where the partnership itself is essential to success.

In plain terms, a strong fit is when you can answer all three questions convincingly:

• Is the research question easier, faster, or higher impact if done with partner country experts?
• Are there concrete reciprocal inputs from both sides (methods, data, equipment, skills, access, field sites, or complementary expertise)?
• Can the outputs be clearly delivered as joint science, not parallel solo work?

If you can only point to a letter saying “we collaborate”, but the core work is not truly joint, the grant is usually not a fit.

What it likely offers

The current listing and official framing indicate a grant mechanism supporting international research collaboration. In practice, this has been used for projects with these characteristics:

• Co-defined research goals across countries
• Joint execution plan with shared work packages
• Outcomes that benefit both sides or create broader international knowledge value
• Emphasis on applied or strategic scientific work where Israel can contribute distinct capabilities

This opportunity is often most useful for teams that are already in scientific dialogue and need funding to move from discussion to formal work: running experiments in parallel labs, validating models across sites, collecting cross-region data, or co-authoring deliverables.

You should not treat this as an immediate source for unrestricted exploratory funding. Most calls are selective, and selection generally assumes a realistic, already shaped research concept and a real partner commitment.

Who should apply and who should not

You may be a good fit if you are:

• A principal investigator at a university, institute, or recognized research organization in Israel
• Actively co-leading a project with an identifiable foreign PI
• Working in one of the priority scientific fields that the active call allows
• Ready to submit a proposal with measurable milestones and a credible budget

You are likely not a good fit if you are:

• Only looking for broad seed funding without a committed international partner
• Applying as a startup with no academic or research affiliation required by the current rules
• Seeking a general subsidy to attend conferences without a funded collaborative project plan
• Submitting very early-stage ideas without partner roles, tasks, and milestones defined

Quick fit test

Read this page as a checkpoint before you proceed:

1. Can your research question not be done well without the partner? If yes, good.
2. Do both teams have explicit roles that depend on each other? If yes, good.
3. Can you specify what success looks like at month 6, month 12, and month 24? If yes, good.
4. Have you identified at least one co-owner on each side who can sign off on scope and deliverables? If yes, good.
5. Can your PI and partner PI each explain the same science story without contradictions? If yes, you may be ready.

If you fail two or more checks, you will spend more time fixing strategy than writing text.

Eligibility: confirmed and unknown items

The dataset and public pages confirm three recurring expectations in broad terms:

• A joint team arrangement with an Israeli lead and international partner.
• At least one lead investigator arrangement across sides.
• An academic or research institution affiliation on the Israeli side in many calls.

Other elements are frequently present in call documents but must be verified in the specific call you are targeting:

• Country-level eligibility and eligible bilateral agreements.
• Which sub-fields are currently open.
• Whether industrial partners can co-own parts of the work.
• Whether multiple grants per team are allowed at the same time.

Do not assume general rules still apply. For each open round, read the exact call conditions and treat every bullet as binding.

How to decide if this is worth your time

Many applicants submit too early because they treat “international” as sufficient proof of value. The main question is whether this is your best effort for expected return.

Use this 4-factor score before committing:

• Strategic alignment (1-5): Does the call clearly match your problem area?
• Partner readiness (1-5): Do you already have a partner with time, signatures, and technical ownership?
• Preparation cost (1-5): How much work is missing to produce a submit-ready package?
• Selection probability (1-5): Can you evidence proof-of-concept, prior outputs, and institutional support?

A total below 12 suggests either delay or pivot to a pre-proposal with lower cost. A total above 16 usually means you can run a full proposal cycle with confidence.

If your score is high but your timeline is low, solve timeline first, not science writing. Most missed deadlines are execution issues, not scientific weakness.

Practical application process (what to prepare now)

Because active instructions and portals vary, use a process you can reuse across calls.

Step 1: Confirm the active call

Open the official ministry page and identify the currently published announcement. Confirm:

• Official title for the specific call round
• Eligibility matrix and partner restrictions
• Published deadline and time zone
• Submission portal URL and account creation requirements
• Required attachments and mandatory forms

Do not use outdated references in your draft text. If there is any mismatch between older internal notes and the active call, use the active call as the source of truth.

Step 2: Validate team and partnership structure

Set up the following before budgeting:

• Israeli lead PI and institutional host
• foreign lead PI and host institution
• explicit work package ownership table
• agreed authorship and IP plan

If the rules require both teams to sign before submission, draft a short partner commitment document early (one page is usually enough to align scope, responsibilities, and communication rhythm).

Step 3: Draft the technical plan around joint execution

A collaboration grant is weaker if it reads like one side is doing all key experiments. Write your work plan so interdependence is visible:

• who does what
• what data/resource moves across where
• what shared outputs each side controls
• what decisions are joint

The best narratives are concrete and testable, for example: Week 1–8 protocol harmonization, Week 9–16 pilot measurements, Week 17–24 cross-site validation.

Step 4: Build a realistic budget

Even before the full application form, build a full budget map.

Minimum components:

• Salaries or effort costs for both teams
• Consumables and field/lab costs
• Travel and mobility if collaboration requires it and if allowed in the call
• Project management and administrative overhead
• Data/storage, reporting, and dissemination costs
• Any compliance, translations, or legal review.

Put each cost against a specific milestone. A budget with disconnected figures is usually marked down.

Step 5: Pre-submission quality checks

Use an internal red-team read with three reviewers:

• one scientist for technical coherence
• one administrator for compliance and form completeness
• one external reader to catch jargon and missing clarity

Then perform a final compliance pass against the call checklist.

Required materials checklist

A typical submission pack for this type of grant usually contains:

• Project summary and objectives
• Detailed plan with milestones and indicators
• CVs or brief professional profiles for PIs
• Letters of commitment from partner institution(s)
• Budget and justification
• Partner organization details and role definitions
• Data privacy/compliance considerations where personal or sensitive data are involved
• Ethics approvals if required by research design

If the active call mentions additional mandatory attachments, include them exactly as required. If the call does not ask for an attachment, avoid adding unnecessary files that can create confusion.

Application timeline playbook

Below is a practical timeline if the deadline is fixed and you have 8 weeks to submit. If your timeline differs, scale proportionally.

For smaller teams, add an internal buffer of at least two full days for unexpected signature or portal issues.

How to prepare the proposal for non-specialist reviewers

Most reviewers are technical, but grant committees also include people who evaluate feasibility, governance, and policy fit.

Use this approach:

• Start every section with the real-world problem, then the method, then expected measurable outcome.
• Replace long explanatory blocks with simple logic: why this problem matters, why this partnership matters, why this budget is the smallest amount needed to deliver.
• Keep acronyms out of the first summary unless absolutely necessary.

A useful structure is:

1. Problem and opportunity
2. Why this partner pair is essential
3. What exactly will be done, step by step
4. What success looks like and how you will prove it
5. Why funds requested are sufficient

Financial strategy for selection committees

Grant officers generally expect financial discipline. A good budget communicates you understand delivery.

Use the following tests:

• If a cost increases but no output is attached, it is likely over-budgeted.
• If a budget item has no responsible owner, reviewers doubt execution control.
• If timeline and spending patterns do not align (e.g., all costs in month 1, all activities in month 9), it appears unmanaged.

A clear budget often has these qualities:

• staged spending over project life
• clear split between direct project costs and partner-related support
• explicit assumptions for exchange visits, testing infrastructure, and reporting obligations
• contingency buffer with rationale

Common mistakes and how to avoid them

Mistake 1: Submitting a generic international collaboration idea

Avoid a generic statement like “We collaborate with global teams on innovation.” Replace it with specific task-level joint work.

Mistake 2: Ignoring partner-country eligibility details

Many programs tie support to bilateral agreements. If partner country eligibility is ambiguous, your proposal can be rejected as out of scope.

Mistake 3: Treating the budget as optional

Some applicants build strong science text but leave budget logic thin. The committee cannot fund a concept without implementation realism.

Mistake 4: Waiting too late for partner commitments

If one signature is missing two days before submission, most teams lose points or get delayed by last-minute compliance correction.

Mistake 5: Confusing application portal with call portal

Some calls require external pre-steps, internal account access, and specific role permissions. Clarify portal flow at start.

Readiness checklist before pressing submit

• Are all partner roles named and consistent in every section?
• Is the proposal centered on joint activity, not two independent activities?
• Is the budget fully consistent with milestones?
• Are institutional affiliations clear for every PI?
• Are ethics, data and IP implications explained at project level?
• Are all required attachments complete and in the requested format?
• Is the submission performed before the hard deadline with enough buffer for technical glitches?

If one item fails, fix it first and re-run the checklist.

FAQ

Does this cover every international collaboration project?

Not necessarily. It covers calls or tracks that explicitly support international scientific collaboration under the Ministry framework. Every call may have different thematic and partner restrictions.

Is there one fixed deadline?

No universal fixed deadline can be assumed from memory. This record shows 2025-04-10, but users should always confirm the active announcement because dates vary by round.

What is the maximum funding amount?

This listing shows a funding range of ₪400,000 to ₪1,000,000. For the most reliable amount, check the exact active call document and budget section.

Who is allowed to apply?

Generally, Israeli academic or research institution-affiliated teams with eligible international collaboration partners. The detailed PI, institution, and track conditions can change by call.

Can smaller institutions apply?

Size is not always the deciding factor. Institutional readiness, partner quality, and execution plan matter more. Smaller teams can be strong if leadership, scope, and budget are realistic.

What if my project is already in progress?

Some calls allow continuation through new collaborative milestones; others require a defined proposal from your current stage. Use the specific call rules.

What to do after submission

Submission is not the finish line.

After submission:

• Save all versioned documents and evidence of what was submitted.
• Monitor official updates and addendum notices.
• Be ready to provide clarifications if requested.
• Keep financial records clean so post-award reporting is manageable.

If selected, start implementation planning immediately in week 1 after award rather than waiting for all partner invoices or approvals.

If not selected:

• Request reviewer comments if available.
• Convert comments into a revised roadmap.
• Decide if there is another active call cycle before your team energy dissipates.

Practical applicant roadmap for the next 30 days

Days 1-3: confirm active call, download all rules, map all must-have requirements.

Days 4-7: finalize partner PI agreement and confirm roles in writing.

Days 8-12: build concept note and budget skeleton.

Days 13-17: complete first full draft and send to reviewers.

Days 18-22: revise based on review, add missing formal documents.

Days 23-26: final quality pass, submission rehearsals.

Days 27-30: submit early, not at last minute, and archive proof of submission.

Even if your deadline has more than 30 days, this cadence helps avoid the panic phase where quality drops sharply.

Decision support: go / wait / pivot

Use this simple decision rule:

• Go if you have partner commitment, compliant scope, and budget coherence.
• Wait if the idea is strong but partnership documents are missing.
• Pivot if scope or country constraints mismatch the active call.

This saves time and avoids filing an avoidable poor submission.

Official links and channels to verify against

Because this is a government-linked program, use only official pages for final decisions.

• Ministry landing page: https://www.gov.il/en/departments/ministry_of_science_and_technology/govil-landing-page
• Ministry international relations context (where bilateral and cooperation goals are described): https://www.gov.il/en/departments/Units/most_intl_relations
• Research Authority summary page commonly used by applicants (with general track descriptions and submission path references): https://research.biu.ac.il/MOST

If these pages are not updated for your specific program window, use the ministry official calls channel from the same homepage and the direct call PDF/document link provided in that announcement.

Final recommendations

If you want this to become a winning application instead of a generic one, focus on three things:

1. Confirm every rule from the active call.
2. Prove joint execution, not only joint intention.
3. Tie every budget line to concrete outputs and timeline.

This opportunity can be competitive and administration-heavy, but teams that are specific, compliant, and partner-ready usually perform much better than teams with strong science but weak execution structure.