Austria FFG BRIDGE Program

Austria FFG BRIDGE Program

BRIDGE is the FFG funding instrument for projects that are genuinely between science and industry. It is not a grant for purely exploratory lab work with no pathway to use, and it is not a normal company-only development grant.

If you want this program to work, understand this in plain terms:

• The project must be research-led, but with realistic potential for exploitation.
• Science and companies must work together as a consortium.
• The research contribution must be the dominant part (at least 80% of project focus/cost share), and companies co-finance or contribute in-kind.

You can use BRIDGE for different technologies and fields, because the program is topic- and technology-open. What matters is the quality of the science-industry integration and whether reviewers can see a real move from knowledge to use.

At-a-glance

What BRIDGE is, in practical terms

BRIDGE sits in the space between two outcomes that often do not meet naturally:

• A university/Institute has a research idea with potential.
• A company needs that idea to become something useful in a commercial context.

The program is designed for this handoff moment. The official call states that funded projects are:

• research-led (grundlagennahe),
• collaborative between science and industry,
• and aimed at eventual application, not pure publication output.

That is why BRIDGE is most useful for teams asking, “Can this research finding move into an industrial setting?” rather than “Can we produce a market-ready product next year?”

The program also explicitly states that clinical studies are not its focus. A narrow exception exists for clinical pilot validation of a substance, therapeutic approach, or medical device up to 30% of total costs, provided clinical work is not the dominant project focus.

Who should apply

BRIDGE is usually a good fit when a team can show all of these points:

1. Scientific lead and practical demand are both present You have a clear research output (method, model, material, mechanism, or platform) and a company that can absorb and use it.
2. The collaboration is real, not paper Company partners are not passive beneficiaries; they have concrete tasks and contributions.
3. The project is at an “industry-adjacent research” stage
4. The work is likely to finish in a controlled 36-month window
5. The team can show realistic follow-up You do not need to present full commercialization, but you should show where results can go next.

BRIDGE is also specifically built to help teams including doctoral candidates and postdocs become part of transfer projects, which can support continuity in a way pure project contracts often do not.

Who should avoid BRIDGE

If your idea sits mostly in one of these buckets, start with a different instrument first:

• Company-only late-stage development with minimal research novelty.
• Contracting a research unit to solve a predefined industrial task with no co-owned scientific objective.
• A project where company tasks dominate the budget and scientific share drops below the program logic.
• A project that cannot show why BRIDGE, and not another FFG program or private source, is the right bridge stage.

What BRIDGE is good for

From the current official call and initiative page, these are the strongest use cases:

• Turning a scientific concept into industrial process understanding.
• Starting a new collaboration between a university group and a company team.
• Creating early transfer prototypes or validation routes without pretending the output is full commercialization.
• Building a reusable collaboration model for future large-scale development funding.

The program is open to all sectors and themes. The same language applies whether the topic is materials science, digital systems, life science, manufacturing, or another domain, as long as the research transfer logic is convincing.

Eligibility and consortium requirements

Use this as your first pass before writing a full proposal:

Mandatory structure

• Minimum two project participants.
• At least one partner from science and one from industry.
• Demonstrable cooperation, not commissioned work.
• Minimum 80% research-side project focus/cost weight.
• Clear project duration planning and budget coherence.

Eligible participant types

FFG states that universities, universities of applied sciences, and scientific institutions are eligible on the science side. On the industry side, companies of various sizes participate, with grant intensity linked to largest company size.

COMET centres (K-centres) are generally eligible, but the submitted project must be a new topic and clearly separated from existing COMET scope.

New collaborations are valued

The program text notes that newly formed collaborations can be positively weighted. In practical terms, this rewards:

• new or newly deepened joint project design,
• mutual project ownership,
• explicit co-execution planning,
• and shared delivery obligations.

Funding logic, grants, and budget discipline

Grant cap and rates

For BRIDGE 2026/1:

• Max grant per project: EUR 360,000.
• Grant support is tied to the industrial research category and scales by company size:
  • Small enterprise (KU): up to 80%
  • Medium enterprise (MU): up to 70%
  • Large enterprise (GU): up to 60%

The official call materials also provide indicative cost examples to illustrate how these percentages influence total eligible project cost.

Research-side focus is strict

The program insists that the research side remains the heavy share. At a minimum, around 80% of project efforts and costs should be on science partners.

This is not only an accounting rule. Reviewers interpret it as proof that the project is research-originated and that industrial work is oriented toward transfer, not vice versa.

Key costs often eligible

The call lists eligible cost types such as:

• personnel,
• materials and consumables,
• use of facilities/equipment,
• travel related to project tasks.

Do not treat this as a complete list for your specific consortium; the final guide and FFG cost rules clarify eligible cost definitions.

Timeline and decision process

For BRIDGE 2026/1, the official page gives:

• Opening: 11 March 2026
• Closing: 11 June 2026 at 12:00
• Decision session: 6 October 2026

This timeline matters because the quality of the consortium and budget logic is decided early, and weakly prepared applications often fail long before scoring. Internal cleanup usually takes longer than writing:

• partner alignment and governance,
• role ownership (who does which task, who signs what),
• budget split and evidence,
• in-kind contribution definitions,
• partner financial readiness.

Application process from a non-rejecting perspective

The key to passing first review is preparation clarity. A good plan:

1. Read the BRIDGE 2026/1 call page and all linked documents.
2. Confirm your project is within the call’s subject logic and date window.
3. Define the consortium with at least one science and one company participant.
4. Set project outputs and decision-ready exploitation route in one page.
5. Build partner cost structures and co-financing commitments before narrative writing.
6. Draft the core project narrative around:
   • scientific basis,
   • transfer mechanism,
   • expected use or validation output,
   • expected company benefit,
   • risks and mitigations.
7. Register partners in eCall and collect all required declarations.
8. Align deadlines internally and submit with buffer.

Required material set (from official program page and linked guide)

The official BRIDGE page explicitly points to:

• BRIDGE application materials (Ausschreibung PDF / Leitfaden),
• FFG costs guide,
• FFG funding directive (Offensive),
• and official call-specific submission documents.

Treat these as mandatory references. If you are submitting a resubmission, the guide distinguishes specific pathways and additional materials.

Language

The public call page includes an English program description. The official BRIDGE 2026/1 application page is in German. The Leitfaden text indicates German as the base language and notes that English is possible. If you are non-native or building an international consortium, confirm document language expectations up front in your internal process.

Selection criteria in everyday language

FFG uses technical and economic review layers. In simple terms:

• scientific quality and novelty,
• implementation feasibility,
• transfer potential and exploitation logic,
• consortium suitability,
• and compliance with formal requirements.

These are reviewed by external and internal expert pathways, then consolidated in the BRIDGE board review before recommendation.

So do not write only “great science.” Write:

• what you are solving,
• why this specific company context matters,
• how the research result changes current practice,
• and what happens if implementation risk appears.

What the proposal should prove (not just state)

1) Your problem is real

Not “interesting science,” but a concrete scientific/industrial pain point.

2) Collaboration is operational

Show clear work packages and deliverables where each partner produces outputs.

3) Exploitation is realistic

You do not need full commercialization plans, but you need the route and first target outcomes.

4) Additionality is credible

Your proposed project should add value beyond existing funded efforts. Do not recycle the same scope as prior work without clear novelty.

5) Financial logic matches the rulebook

If the project economics and required grant rate do not align at planning stage, scoring and form checks both degrade.

Practical “worth your time” framework

Use this framework before you invest in full drafting:

Rate each item 0–5.

• Is there genuine research novelty and transfer relevance?
• Is there active company commitment (time, staff, data, facilities)?
• Can you defend the 80% research focus?
• Is the exploitation pathway plausible for your own resources?
• Are financial statements/partner declarations ready or realistically gatherable?
• Can you explain governance and roles clearly?

If your score is below 18/30, fix gaps before drafting. Strong teams can still save time by delaying submission and completing missing evidence instead of trying to improvise after drafting.

What to prepare before writing

You will save time by completing these before sentence-level drafting:

• a short internal project fit note signed by all partners,
• one-page consortium map (roles, work packages, decision process),
• draft cost split for each partner,
• draft exploitation paragraph: “what gets transferred and to whom,”
• partner readiness file with documents and responsible contacts,
• versioned source links (call page, Leitfaden, cost guide).

This lets your writing team focus on clarity and competitiveness, while your admin team handles compliance.

Common mistakes to avoid

1. Treating BRIDGE like a commercialization-only instrument.
2. Using a company-dominated project structure with weak science-side share.
3. Understating co-financing/in-kind commitments.
4. Waiting for the final 48 hours and failing portal checks in time.
5. Ignoring additionality and claiming incremental work without novelty.
6. Submitting governance with no operational partner ownership.
7. Assuming “we heard one of these programs before” is enough for form compliance.
8. Missing the practical difference between “research participation” and “contract execution.”
9. Failing to explicitly connect scientific quality to industrial transfer.

Application planning tips that usually make or break proposals

Start with the one-page concept

Write one page with five fixed points:

• problem,
• scientific approach,
• transfer plan,
• partner roles,
• expected outputs.

If this page is weak, the full proposal usually follows suit.

Use a simple governance plan

Write down:

• who leads scientific quality,
• who leads exploitation planning,
• who manages finances,
• how disputes are escalated.

Even a three-line governance model helps reviewers trust implementation.

Build risk notes with owners

A simple risk register section is usually valuable:

• technical risk + mitigation owner,
• industrial integration risk + owner,
• schedule risk + owner,
• compliance risk + owner.

Do not promise zero risk. Show risk control discipline.

FAQ (officially grounded)

Is BRIDGE only for science-heavy projects, or can it include applied pilot work?

Both, with priority for foundational, research-oriented collaborations that are already moving toward use.

Can I apply with one company and one university only?

Yes, minimum requirement is at least one research and one company participant, as long as the consortium is coherent.

Can clinical-related projects apply?

Clinical studies are not the core focus. The call allows a narrow pilot exception up to 30% of total costs when not the main research focus.

Are new collaborations acceptable?

Yes. Newly created partnerships are explicitly noted positively.

What if my university project already exists in a COMET framework?

COMET participants can be eligible, but the BRIDGE project must be a distinct new topic and separated from existing framework scope.

Who decides final approval?

Review and assessment combine external and internal expert steps, followed by a BRIDGE board recommendation with FFG participation.

Is English accepted?

The program page has an English version and the official call page is German. The BRIDGE 2026/1 guidance notes that English is possible. Confirm your exact submission language requirements before finalizing narrative.

Where can I see nearby BRIDGE call history?

The official pages include 2026/1 details and links to prior calls.

What to do next

If you want to move from interest to submission:

1. Save the BRIDGE 2026/1 page and the call Leitfaden.
2. Run your consortium through the readiness score and identify any missing commitments.
3. Confirm budget shares and cost categories before drafting.
4. Prepare a realistic timeline with submission milestones:
   • partner readiness,
   • cost sign-off,
   • draft proposal,
   • legal/administrative check,
   • portal readiness.
5. Submit with enough time to fix portal issues.

If key elements are missing at this stage, pause writing and close those gaps first. BRIDGE rewards quality and realism, not speed.

Official links

• Program page: https://www.ffg.at/en/programme/bridge
• BRIDGE 2026/1 call page: https://www.ffg.at/ausschreibung/bridge-2026-1
• BRIDGE 2026/1 Leitfaden (official PDF): https://fdoc.ffg.at/s/vdb/public/node/content/OzCHsVz7TGe_psGn1yzwLw/1.0?a=true
• FFG costs guide: https://www.ffg.at/recht-finanzen/kostenleitfaden
• FFG legal basis for the FFG Offensive 2024–2026: https://www.ffg.at/recht-finanzen/rechtsgrundlagen
• BRIDGE board and session list: https://www.ffg.at/bridgebeirat

What BRIDGE actually is in practical terms

BRIDGE is best described as a bridge mechanism between two worlds:

• the world of research and scientific exploration (universities, universities of applied sciences, research institutes, and related partner types), and
• the world of production and market orientation (companies that can take results toward exploitation).

The program design avoids narrow vertical sector themes. It is intentionally open to all disciplines and technologies as long as the project is research-driven and transfer-oriented.

The practical point this matters for: BRIDGE is not a fit when your project idea is already a fully validated commercial product. It is better for ideas and experimental-stage knowledge that still need industrial collaboration to become usable. That is why the program is grouped under industrial research logic in the EU funding context.

What BRIDGE is good for and when it is not

Use BRIDGE if your consortium can show all of these

1. Scientific depth + commercial clarity. You should be able to explain a real knowledge-to-market pathway rather than simply a publication-only project.
2. Real company participation. The company side should be actively involved in the project work, not just named as a passive beneficiary.
3. Novel collaboration advantage. BRIDGE values projects where the consortium is newly formed or creates new collaboration dynamics.
4. Nationally anchored impact. The program is national in scope and intended to strengthen Austrian research-industry links.

Avoid BRIDGE if your project is mainly

• A pure service contract for one firm.
• A routine testing activity with no meaningful research transfer.
• A purely clinical study program where clinical phases are the main content.

FFG’s call text explicitly says clinical studies are not the main focus, with a narrow allowance for pilot validation of substances, therapy concepts, or medical devices up to 30% of total costs, and only if clinical focus is not dominant.

Who can apply and how to decide if your team fits

A BRIDGE application is usually strongest when one of these combinations exists:

• A university lab has a result that needs industrial context and commercialization.
• An applied research institute has TRL-ready work but needs company-driven integration.
• A company has a technical problem and needs deep scientific know-how to de-risk an innovation route.
• A doctoral or postdoctoral team can move with clear supervision between science and industrial needs.

The minimum is simple: the call requires at least two participants and explicitly at least one from science and one from economy.

The official call page defines this as:

• research projects as consortia from science and industrial partners,
• with realistic commercialization potential,
• and company-side participation in implementation or financing.

That means your fit is usually good if both sides can describe concrete, shared outputs.

A good fit candidate can answer:

• What scientific result do we turn into a practical technology?
• What does the company commit to in time, personnel, and resources?
• What part of the result is novel versus incremental?
• Can the project be run in 12–36 months?

A bad fit usually appears when:

• One side has unclear commitment.
• Commercialization is only aspirational with no defined exploitation path.
• The consortium has too many weak links, no clear project lead, and unclear governance.

The funding logic and financial expectations (what FFG checks)

Grant amount and intensity

For BRIDGE 2026/1, FFG states max grant is EUR 360,000 per project. The grant intensity depends on the largest participating company:

• Small enterprise (KU): up to 80%
• Medium enterprise (MU): up to 70%
• Large enterprise (GU): up to 60%

The call guide example states the practical result of this logic:

• with KU, total project costs around EUR 450,000 can reach full 80% support,
• with MU, around EUR 514,000 can reach 70%,
• with GU, around EUR 600,000 can reach 60%.

FFG links these amounts to the industrial research budget framework. That means budget discipline is not optional. You need to design costs so the requested grant and eligible cost base are coherent.

Why the 80/20 split is central

The official conditions stress that the core of project efforts should be on the research side. In plain language:

• At least about 80% project share (in work and budget logic) should be at the research partner side.
• Company side finances the remaining part, including possible in-kind contributions.

If your consortium is structured the other way around, you are likely to fail early on scoring or formal compliance.

What is typically eligible

From the published BRIDGE instrument pages and current call information:

• personnel costs,
• material and third-party costs,
• use of facilities/equipment,
• travel and related project-cost categories.

Project duration is capped at 36 months.

What BRIDGE covers in plain English

In practical terms, BRIDGE funds collaborations where a research-led idea is shaped into applied innovation within a manageable time window. Think of it as a “transfer program” with scientific rigor.

FFG documents describe the goals as:

1. transferring foundational knowledge toward economic use,
2. deepening and starting cooperation between science and industry,
3. supporting high-quality research capacity in industry-linked environments,
4. strengthening human-resource movement from academia to industrial innovation contexts.

When writing your concept note, make your proposal explicitly mirror these goals. A strong project narrative states:

• what scientific question is being answered,
• where and how industrial constraints shape the experiment and iteration,
• what new knowledge moves into a company environment,
• who can use and further develop results.

Eligibility details you must not skip

Consortium and partner rules

1. At least two participants, with one from science and one from industry.
2. Project should be truly cooperative, not commission-based.
3. New or newly deepened collaboration between science and industry has explicit advantage.
4. Existing COMET centers can be eligible if the project topic is new and clearly separated from existing center scope.

The call text also says BRIDGE can involve new researcher profiles, including doctoral students and postdocs. For many teams this is key because it proves career and capacity development, not just output delivery.

Eligibility and scope checks you should perform immediately

Before spending writing time, answer these with evidence:

• Is there a real company participant with documented role in work execution?
• Do the partners collectively cover the technical work and exploitation chain?
• Do the planned costs keep the research share at the required level?
• Are annual financials ready for each economic participant (or a valid replacement package if newly formed)?
• Is the project likely to be complete and review-ready within max 36 months?

If any answer is “not yet,” you can still fix it, but do it before opening eCall.

Current call timeline and decision reality

For BRIDGE 2026/1 the official timeline is:

• submission period: 11 March 2026 to 11 June 2026 (12:00)
• decision session: 6 October 2026

This is important strategically. Many teams prepare a technically strong idea but underestimate how much early coordination takes:

• partner legal alignment,
• project planning,
• internal financial data collection,
• CV and declaration readiness,
• consortium role definition.

If you start too late, you lose internal quality time, then rush the application, then lose points in clarity and consistency.

Application process: a practical checklist

BRIDGE applications happen through eCall. The process is easiest if you treat it as a sequence.

1. Open the official BRIDGE call page and download the current documents list.
2. Read the BRIDGE Leitfaden and costs guide.
3. Confirm your consortium list and governance model.
4. Define who leads and who is responsible for exploitation tasks.
5. Prepare the project description in plain language for first review pass.
6. Build the cost table, then cross-check with grant intensity and co-financing.
7. Register all partner entities in eCall and collect legal/financial data.
8. Verify upload requirements against the call’s documents.
9. Run an internal review with a checklist against form criteria.
10. Submit before deadline with buffer for portal glitches.

What to prepare (documented at source)

FFG’s call guide and eCall-based submission flow indicate these as required submission components:

• Project description in eCall (full substantive proposal).
• Resubmission side letter (if this is a resubmission path).
• Cost plan per partner and project budget structure.
• Annual data for all economic participants including financial statements as required.
• Additional supporting projects where relevant for continuity or additionality.

If the company is a startup or newly founded entity, financial documentation requirements can differ, often requiring a business plan replacement for missing statements. Plan this early.

The call guide also requires additionality clarity: your proposed project needs to be distinguishable from already funded work. FFG explicitly warns against double claiming costs or presenting an iteration that is not clearly separated from previous projects.

How to write the proposal to reduce rejection risk

Start with the one-page story first

Even though formal forms are longer, reviewers do first-pass based on narrative coherence. A useful working structure:

• Problem: what real industrial or scientific gap you target.
• Method: how research and company work are linked.
• Outputs: what outputs become transfer-ready.
• Economics: how and where this enables value.
• Execution: who does what, by when.

Build the proposal from evaluation logic, not template convenience

The BRIDGE review process includes external expert assessment plus internal review and board recommendation. Keep that in mind:

• scientific quality and novelty are judged as real content,
• implementation and transfer feasibility are judged separately,
• the final recommendation requires both to be strong.

Your text should explicitly connect scientific novelty to exploitation realism. A common weak proposal has either too much science without implementation, or too much commercialization without scientific credibility.

Make risk management explicit but realistic

The best BRIDGE teams do not claim zero risk. They show they understand risk and have controls:

• technical risks (materials, process reproducibility, integration issues),
• timeline risks (prototype iteration delays, access bottlenecks),
• governance risks (partner dependency, communication failures),
• compliance risks (IP, publication timing, confidentiality).

Do not overcomplicate with jargon. Use one-page risk tables with owner and mitigation.

Is BRIDGE worth your time? A readiness scorecard

Before you start writing, score 0–5 on each criterion:

• Research novelty with clear technical novelty (0–5)
• Company co-investment readiness (0–5)
• Data needed for eCall and cost plans already available (0–5)
• Clear exploitation pathway to market/industrial use (0–5)
• Internal governance clarity (0–5)

If your total is below 18, do not submit as-is. You can still use BRIDGE, but you should first close governance or scope gaps.

High score indicates you can move confidently toward drafting and can spend writing cycles on competitiveness, not compliance rescue.

Common mistakes that waste months

1. Submitting a project that is mostly applied company R&D and not research-led.
2. Underestimating required 80% research-side share.
3. Missing the company commitment to co-finance or in-kind support.
4. Weak project management plan after month 6 and no defined responsibilities.
5. Treating budget as a clerical add-on instead of a strategic validation tool.
6. Ignoring decision calendar and leaving validation to last-day submission.
7. No separation from previous projects; costs overlap or unclear novelty.
8. Inconsistent partner roles with no signed coordination model.
9. Assuming English-only language is always accepted; confirm language requirements for your specific documents.

The above are preventable with early internal checks against the published BRIDGE criteria and checklist.

Practical FAQ

Does BRIDGE fund exploratory science with a commercialization path, or only near-market projects?

It is designed for research-led, foundational projects with recognizable exploitation potential. It is not meant to replace late-stage commercialization programs.

Is BRIDGE only for specific technologies?

No. The published call states thematic openness.

How often are calls published?

FFG indicates typically one to two submission windows per year. Check the initiative page for the next open round because dates change per year.

Can new partnerships apply?

Yes, and newly formed cooperation is explicitly noted as positively weighted.

What if we already have a COMET or other framework relationship?

Possible, but for existing K-center/COMET environments the project must be clearly a new topic and distinct from current center scope.

Who decides the final result?

External expert review is done first, then project assessment by FFG experts, and then a BRIDGE board recommendation with FFG participation.

Are clinical-related projects possible?

They are not the core focus. Pilot clinical studies can be included only under narrow conditions and only when not the main research focus.

What to do next (after reading this)

1. Open the BRIDGE program page and current call page, then confirm whether BRIDGE 2026/1 is still open.
2. Download and read the BRIDGE 2026-1 Leitfaden, FFG costs guide, and legal basis page.
3. Confirm your consortium structure against the eligibility rules.
4. Estimate budget with grant intensity logic before proposal drafting.
5. Do a pre-submission dry run using the section order above.
6. If you are missing key docs or partner signatures, pause writing and close those gaps first.

Official links

• Program page (official): https://www.ffg.at/en/programme/bridge
• Current call page used in this rewrite: https://www.ffg.at/ausschreibung/bridge-2026-1
• BRIDGE Leitfaden 2026-1 (official PDF): https://fdoc.ffg.at/s/vdb/public/node/content/OzCHsVz7TGe_psGn1yzwLw/1.0?a=true
• FFG cost guide: https://www.ffg.at/recht-finanzen/kostenleitfaden
• FFG legal basis page for OFFENSIV 2024–2026: https://www.ffg.at/recht-finanzen/rechtsgrundlagen
• BRIDGE board and historical schedules: https://www.ffg.at/bridgebeirat