VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Science? | NRF Research Translation Grant

Three students sit around open books and worksheets at a classroom table, reading, writing and discussing the work together.

eduKateSG · Why Science?

Move promising public research toward commercial interest by testing the uncertainties that matter—technical performance, users, safety, regulation, manufacturing and investability

A current guide to Singapore’s NRF Research Translation Grant: early-stage translation, GAP@RTG, VB@RTG, ecosystem initiatives, de-risking and responsible commercialisation.

Full chapter index · Science Learning Hub

NRF describes the Research Translation Grant as its primary broad-based scheme for early-stage research translation and a complement to RIE2030 sector initiatives.

The official page says RTG helps promising technologies from Singapore public research institutions progress toward private-sector interest and commercially viable assets.

RTG has two main modalities: Technology Translation Projects, including GAP@RTG and VB@RTG, and Innovation and Enterprise Ecosystem Development Initiatives.

Did you know? De-risking does not mean making a technology sound less risky. It means running the right tests so a team can replace important unknowns with evidence—and stop or change direction when the evidence says so.

The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements. This guide separates current published facts from practical learning advice. Programme details were checked on 27 October 2026; families and students should recheck the linked official pages before applying, paying or attending.

CHAPTER 1 OF 17 · Understand translation

1. RTG supports early-stage research translation

Back to contents

NRF positions RTG as broad-based support that helps promising public research move toward commercial interest. Translation begins after useful research evidence exists, then asks what additional proof is required for adoption or investment.

Research translation asks what additional evidence would make a promising technology credible to a company, investor or venture builder. The capability under inspection is translation framing. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Map the research result, target use and unresolved evidence gaps. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A grant application does not prove commercial viability.

Try this now

Map the research result, target use and unresolved evidence gaps. Label the result with the date and the capability “translation framing”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: A grant application does not prove commercial viability.

Contents · Next chapter

CHAPTER 2 OF 17 · Understand translation

2. RIE2030 creates the current policy context

Back to contents

The official page says RTG complements end-to-end RIE2030 initiatives for priority sectors while keeping a broad route across sectors. Teams should distinguish the current scheme purpose from older programme names and archived rules.

De-risking is a sequence of tests against technical, user, regulatory, manufacturing and commercial uncertainty. The capability under inspection is policy literacy. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Record the current policy edition and active portal call. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Do not reuse superseded RIE2025 terms as current requirements.

Field-note prompt

Record the current policy edition and active portal call. Label the result with the date and the capability “policy literacy”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Do not reuse superseded RIE2025 terms as current requirements.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 17 · Understand translation

3. Commercially viable assets need more than technical novelty

Back to contents

A technology may be scientifically interesting but difficult to manufacture, regulate, protect, integrate or sell. Define the asset, intended user, value proposition and evidence needed to move a real decision.

Commercial potential must never be used to skip scientific validation, safety or honest limitations. The capability under inspection is commercial reasoning. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Write an asset-user-decision statement with measurable uncertainties. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Novelty alone does not demonstrate demand or viability.

Learning move

Write an asset-user-decision statement with measurable uncertainties. Label the result with the date and the capability “commercial reasoning”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Novelty alone does not demonstrate demand or viability.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 17 · Understand translation

4. Public research performers are the starting base

Back to contents

RTG aims to translate technologies emerging from Singapore public research institutions. Confirm institutional ownership, inventor roles, background rights and technology-transfer processes before promising a pathway.

Ecosystem capacity matters because researchers need shared expertise and pathways as well as project funding. The capability under inspection is institutional governance. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Create an ownership and decision-rights map with the institution. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Only authorised offices can determine institutional IP positions.

Evidence practice

Create an ownership and decision-rights map with the institution. Label the result with the date and the capability “institutional governance”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Only authorised offices can determine institutional IP positions.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 17 · Compare modalities

5. Technology Translation Projects de-risk specific technologies

Back to contents

The TTP modality supports project-level work that advances early technologies. A plan should identify the largest technical and commercial uncertainties, then sequence experiments and market learning so each result changes a decision.

Research translation asks what additional evidence would make a promising technology credible to a company, investor or venture builder. The capability under inspection is de-risking design. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Build a risk register ranked by decision consequence. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Current RGP guidance defines eligible activities and costs.

Try this now

Build a risk register ranked by decision consequence. Label the result with the date and the capability “de-risking design”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Current RGP guidance defines eligible activities and costs.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 17 · Compare modalities

6. GAP@RTG is a bottom-up translation route

Back to contents

NRF describes GAP@RTG as supporting bottom-up proposals from public research performers across sectors to advance promising technologies to commercial interest. Fit depends on evidence and translation logic, not a fashionable sector label.

De-risking is a sequence of tests against technical, user, regulatory, manufacturing and commercial uncertainty. The capability under inspection is modality selection. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Show the starting evidence and the commercial decision each milestone enables. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: The active call controls detailed eligibility.

Field-note prompt

Show the starting evidence and the commercial decision each milestone enables. Label the result with the date and the capability “modality selection”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: The active call controls detailed eligibility.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 17 · Compare modalities

7. VB@RTG adds an eligible venture-builder partnership

Back to contents

VB@RTG supports jointly developed proposals between public research performers and eligible venture-builder partners. The partner can bring commercial guidance earlier, but scientific truth, role clarity and institutional governance remain essential.

Commercial potential must never be used to skip scientific validation, safety or honest limitations. The capability under inspection is partnership design. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Define each partner’s contribution, decisions, conflicts and handovers. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A partner relationship does not guarantee a spin-off or investment.

Learning move

Define each partner’s contribution, decisions, conflicts and handovers. Label the result with the date and the capability “partnership design”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: A partner relationship does not guarantee a spin-off or investment.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 17 · Compare modalities

8. IEDI strengthens ecosystem conditions

Back to contents

Innovation and Enterprise Ecosystem Development Initiatives support national-level capabilities and conditions for translation. NRF asks prospective applicants to discuss the proposed programme before developing a full proposal.

Ecosystem capacity matters because researchers need shared expertise and pathways as well as project funding. The capability under inspection is ecosystem design. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Frame the ecosystem bottleneck, beneficiaries and measurable capability change. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Use the official contact and current process before preparing a full proposal.

Evidence practice

Frame the ecosystem bottleneck, beneficiaries and measurable capability change. Label the result with the date and the capability “ecosystem design”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Use the official contact and current process before preparing a full proposal.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 17 · Test the technology

9. User discovery tests whether the problem is real

Back to contents

Talk to intended users, purchasers, operators and affected stakeholders without turning interviews into sales pitches. Separate observed workflow and decision criteria from polite interest.

Research translation asks what additional evidence would make a promising technology credible to a company, investor or venture builder. The capability under inspection is problem validation. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Maintain a user-evidence log with quotes, context and changed assumptions. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: User interviews do not prove willingness to pay or adopt.

Try this now

Maintain a user-evidence log with quotes, context and changed assumptions. Label the result with the date and the capability “problem validation”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: User interviews do not prove willingness to pay or adopt.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 17 · Test the technology

10. Technical milestones need decision thresholds

Back to contents

Define performance, reliability, reproducibility and boundary conditions for each stage. Use comparators that match the intended application. A prototype demonstration should say what it does and what it has not yet established.

De-risking is a sequence of tests against technical, user, regulatory, manufacturing and commercial uncertainty. The capability under inspection is technical validation. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Set pass, revise and stop thresholds before testing. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Do not move goalposts after seeing results.

Field-note prompt

Set pass, revise and stop thresholds before testing. Label the result with the date and the capability “technical validation”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Do not move goalposts after seeing results.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 17 · Test the technology

11. Safety and regulation belong in the plan early

Back to contents

Identify applicable standards, approvals, hazards and responsible-use questions before design choices harden. Early advice can reveal evidence needs that change experiments, materials or claims.

Commercial potential must never be used to skip scientific validation, safety or honest limitations. The capability under inspection is regulatory foresight. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Build a regulatory-and-safety evidence map with qualified guidance. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: This article is not regulatory, legal or medical advice.

Learning move

Build a regulatory-and-safety evidence map with qualified guidance. Label the result with the date and the capability “regulatory foresight”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: This article is not regulatory, legal or medical advice.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 17 · Test the technology

12. Manufacturing can change the science

Back to contents

Scale, yield, materials, quality control, supply chains and cost may alter performance. Translation experiments should test whether the core effect survives realistic production and operating conditions.

Ecosystem capacity matters because researchers need shared expertise and pathways as well as project funding. The capability under inspection is manufacturing readiness. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: List scale-up assumptions and design one stress test for each. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Laboratory success does not guarantee manufacturability.

Evidence practice

List scale-up assumptions and design one stress test for each. Label the result with the date and the capability “manufacturing readiness”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Laboratory success does not guarantee manufacturability.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 17 · Build the ecosystem

13. Intellectual property is one part of advantage

Back to contents

Patents, know-how, data, speed, standards and partnerships may contribute to defensibility. Record inventorship and prior art accurately, and involve institutional experts. IP strategy should follow the asset and route.

Research translation asks what additional evidence would make a promising technology credible to a company, investor or venture builder. The capability under inspection is IP literacy. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Create a defensibility map without making unsupported legal claims. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Qualified professionals determine legal rights.

Try this now

Create a defensibility map without making unsupported legal claims. Label the result with the date and the capability “IP literacy”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Qualified professionals determine legal rights.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 17 · Build the ecosystem

14. A venture case needs transparent economics

Back to contents

Estimate customers, price, costs, adoption time and capital needs as assumptions with sources and ranges. Update the model when technical or user evidence changes. A precise spreadsheet can still be wrong if assumptions are hidden.

De-risking is a sequence of tests against technical, user, regulatory, manufacturing and commercial uncertainty. The capability under inspection is commercial modelling. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Add source, uncertainty and sensitivity to every key model input. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Forecasts are scenarios, not guaranteed returns.

Field-note prompt

Add source, uncertainty and sensitivity to every key model input. Label the result with the date and the capability “commercial modelling”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Forecasts are scenarios, not guaranteed returns.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 17 · Build the ecosystem

15. Stop decisions can protect research value

Back to contents

If evidence shows weak need, unsafe performance or untenable economics, pausing can prevent waste and preserve knowledge for another use. Record why the decision was made and which assets remain valuable.

Commercial potential must never be used to skip scientific validation, safety or honest limitations. The capability under inspection is portfolio discipline. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Predefine kill criteria and an orderly close-out record. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Stopping a route is not the same as research failure.

Learning move

Predefine kill criteria and an orderly close-out record. Label the result with the date and the capability “portfolio discipline”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Stopping a route is not the same as research failure.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 17 · Build the ecosystem

16. Responsible claims protect trust

Back to contents

Describe readiness, validation population, test conditions and remaining risks in every pitch or public statement. Avoid presenting grants, patents or prototypes as proof of market success.

Ecosystem capacity matters because researchers need shared expertise and pathways as well as project funding. The capability under inspection is translation communication. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Use a claim-evidence-limit table in every deck. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Commercial urgency does not excuse exaggeration.

Evidence practice

Use a claim-evidence-limit table in every deck. Label the result with the date and the capability “translation communication”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Commercial urgency does not excuse exaggeration.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 17 · Build the ecosystem

17. Keep a complete translation receipt

Back to contents

Archive the current call, research evidence, IP guidance, user learning, partner roles, risk register, milestones, regulatory and manufacturing work, models, decisions and approved claims. The record should show how uncertainty changed.

Research translation asks what additional evidence would make a promising technology credible to a company, investor or venture builder. The capability under inspection is evidence governance. Keep the current official source, premise, evidence, decision, feedback and revision in one dated trail. That record helps collaborators distinguish a verified fact, a project assumption and a future possibility. The NRF page explains RTG structure; current RGP calls, institutional technology-transfer rules and award terms govern eligibility, partners, funding, dates and application requirements.

Put this into practice by turning the idea into a small, reviewable action: Build a translation evidence index with owners and versions. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Retention and disclosure follow institutional and award rules.

Try this now

Build a translation evidence index with owners and versions. Label the result with the date and the capability “evidence governance”.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Evidence checkpoint

Can another person trace the claim to a current source, observation or documented decision? Keep this boundary visible: Retention and disclosure follow institutional and award rules.

Contents · Previous chapter

RTG translation map

StageEvidence to keepBoundary to retain
Research assetPromising technology from public researchResearch evidence remains foundational
TTPGAP@RTG or joint VB@RTG routeCurrent call defines eligibility
De-riskingTechnical, user, regulatory, manufacturing and commercial testsPassing one test is not market success
EcosystemNational capabilities and conditions through IEDIProgramme discussion precedes full proposal

Science learning becomes useful when a student can show where a claim came from, why it applies and where it stops. Continue with the eduKate Science Learning Hub, compare choices in the Education Hub, and connect developing capabilities to education and career pathways. Families looking for science tuition or a science tutor can use the same evidence questions: what will the learner practise, what feedback will they receive, and how will progress be shown?

Move promising public research toward commercial interest by testing the uncertainties that matter—technical performance, users, safety, regulation, manufacturing and investability The happiest outcome is not a perfect label. It is a learner who can ask a sharper question, work safely, notice honestly, revise with feedback and stay curious about what comes next.

Primary sources and verification date

Source status checked 27 October 2026. Programme rules, dates, eligibility, access and participation routes can change; use the linked official owner for the current edition.

  • NRF Research Translation Grant — Official current scheme purpose, TTP and IEDI modalities, GAP@RTG and VB@RTG; updated 14 October 2026.
  • NRF Grants — Official current research and innovation grant directory; updated 31 August 2026.
  • Research Grants Portal — Official route to current grant calls, detailed requirements and grant management.

Continue the evidence journey