eduKateSG · Why Science?
Start with an important Singapore problem, assemble the disciplines the problem really needs, and protect scientific excellence while the team builds use-inspired basic research
A current guide to Singapore’s NRF Competitive Research Programme: multidisciplinary teams, use-inspired basic research, scientific merit, real-world relevance, collaboration and evidence governance.
The National Research Foundation says the Competitive Research Programme fosters multidisciplinary teams conducting cutting-edge research relevant to Singapore and society.
NRF describes CRP as funding use-inspired basic research selected through merit review based on scientific excellence.
The official page states that a proposed theme must be motivated by an important need or problem to be solved and directs applicants to the Research Grants Portal for current details.
Did you know? “Use-inspired basic research” can pursue deep understanding and practical relevance at the same time. The need helps select the question; rigorous science determines whether the explanation is trustworthy.
The public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details. 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 index
Chapters 1–9: official scope, use-inspired basic research, Singapore relevance, merit review and portal guidance
- 1. CRP joins an important need to basic research
- 2. Singapore relevance should be specific
- 3. Use-inspired basic research protects curiosity and purpose
- 4. Scientific excellence is the merit-review foundation
- 5. Multidisciplinary should change the work
- 6. Choose a common vocabulary early
- 7. Work packages need dependencies and handovers
- 8. Methods should answer the shared question
- 9. Data governance must cross institutional boundaries
Chapters 10–17: problem framing, disciplines, interfaces, methods, data, milestones, communication and public value
- 10. Milestones should be evidence gates
- 11. Budgets should reveal the programme logic
- 12. Team culture must surface contradictions
- 13. Negative results can protect public value
- 14. Translation remains a later evidence journey
- 15. Communication should serve several audiences
- 16. Capability is part of the programme legacy
- 17. Keep a complete CRP governance receipt
CHAPTER 1 OF 17 · Read the programme
1. CRP joins an important need to basic research
NRF describes the programme as use-inspired basic research motivated by an important need or problem. The team must convert that need into researchable gaps, mechanisms and tests without assuming that the desired solution is already correct.
Use-inspired basic research begins with a real need but still asks fundamental questions whose answers are uncertain. The capability under inspection is problem translation. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Write separate need, knowledge-gap and research-question statements. 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: Societal importance does not guarantee a particular scientific answer.
Try this now
Write separate need, knowledge-gap and research-question statements. Label the result with the date and the capability “problem translation”.
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: Societal importance does not guarantee a particular scientific answer.
Relevance can arise from local constraints, systems, populations, climate, infrastructure, economy or public need. Explain why the Singapore context changes the research question or value, while avoiding claims that only Singapore can benefit.
A multidisciplinary team adds value only when disciplines change the question, method or interpretation together. The capability under inspection is context 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Trace the local context to one research decision in each work package. 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: Relevance claims require evidence and current context.
Field-note prompt
Trace the local context to one research decision in each work package. Label the result with the date and the capability “context 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: Relevance claims require evidence and current context.
CHAPTER 3 OF 17 · Read the programme
3. Use-inspired basic research protects curiosity and purpose
Basic questions can be selected because solving them may unlock a practical capability. Keep the causal chain explicit: need, unknown mechanism, proposed study, possible capability and remaining translation steps.
Scientific excellence and Singapore relevance should be joined by a causal argument rather than placed in separate slogans. The capability under inspection is causal 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Draw an evidence chain from fundamental unknown to possible use. 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 plausible use is not a delivered outcome.
Learning move
Draw an evidence chain from fundamental unknown to possible use. Label the result with the date and the capability “causal 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: A plausible use is not a delivered outcome.
CHAPTER 4 OF 17 · Read the programme
4. Scientific excellence is the merit-review foundation
The official page says projects are selected through merit review based on scientific excellence. A strong proposal explains prior evidence, method validity, novelty, feasibility, alternatives and the limits of interpretation.
Large collaborative research needs visible decisions, interfaces and ownership. The capability under inspection is scientific quality. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Audit each major claim for source, test and disconfirming evidence. 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: Selection remains competitive and call-specific.
Evidence practice
Audit each major claim for source, test and disconfirming evidence. Label the result with the date and the capability “scientific quality”.
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: Selection remains competitive and call-specific.
A team is multidisciplinary when different forms of expertise affect shared questions and decisions. Define where one discipline supplies a model, measurement, dataset or interpretation needed by another, rather than placing parallel tasks beside each other.
Use-inspired basic research begins with a real need but still asks fundamental questions whose answers are uncertain. The capability under inspection is team integration. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Create an interface map showing inputs, outputs and decision owners. 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: Many disciplines do not automatically create integration.
Try this now
Create an interface map showing inputs, outputs and decision owners. Label the result with the date and the capability “team integration”.
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: Many disciplines do not automatically create integration.
The same term can mean different things across fields. Build a glossary for key variables, units, populations, evidence standards and uncertainty. Record disagreements instead of smoothing them away.
A multidisciplinary team adds value only when disciplines change the question, method or interpretation together. The capability under inspection is concept alignment. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Run a cross-discipline concept-mapping session before finalising methods. 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: Definitions must remain appropriate to each field.
Field-note prompt
Run a cross-discipline concept-mapping session before finalising methods. Label the result with the date and the capability “concept alignment”.
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: Definitions must remain appropriate to each field.
Large programmes fail when timing and data assumptions are invisible. Show which package depends on which sample, model, instrument or decision and what happens if it is late or invalid.
Scientific excellence and Singapore relevance should be joined by a causal argument rather than placed in separate slogans. The capability under inspection is programme architecture. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Draw a dependency graph with acceptance criteria for every handover. 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: Formal changes may need funder approval.
Learning move
Draw a dependency graph with acceptance criteria for every handover. Label the result with the date and the capability “programme architecture”.
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: Formal changes may need funder approval.
Each discipline may prefer its own methods, but the portfolio should converge on the programme’s core uncertainty. Explain why each method is needed, how outputs combine and what contradictory results would mean.
Large collaborative research needs visible decisions, interfaces and ownership. The capability under inspection is method integration. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Build a method-to-question matrix with integration points. 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: Method novelty does not substitute for validity.
Evidence practice
Build a method-to-question matrix with integration points. Label the result with the date and the capability “method integration”.
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: Method novelty does not substitute for validity.
CHAPTER 9 OF 17 · Build the team
9. Data governance must cross institutional boundaries
Define provenance, access, formats, identifiers, privacy, security, intellectual property and retention before data begin moving. A shared repository is useful only when meaning and permissions travel with the files.
Use-inspired basic research begins with a real need but still asks fundamental questions whose answers are uncertain. The capability under inspection is data stewardship. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Create a data-flow map with owners and access rules. 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: Ethics and institutional policies govern data use.
Try this now
Create a data-flow map with owners and access rules. Label the result with the date and the capability “data stewardship”.
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: Ethics and institutional policies govern data use.
A milestone is useful when it triggers a decision. Predefine evidence for continuing, revising or stopping a work package and how downstream teams will adapt. This makes uncertainty manageable without pretending the path is fixed.
A multidisciplinary team adds value only when disciplines change the question, method or interpretation together. The capability under inspection is adaptive 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Attach decision criteria and contingency actions to every major milestone. 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: Reporting requirements come from the active award.
Field-note prompt
Attach decision criteria and contingency actions to every major milestone. Label the result with the date and the capability “adaptive 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: Reporting requirements come from the active award.
Personnel, equipment, consumables, facilities and collaboration costs should connect to work packages and capability. Explain timing, alternatives and shared-resource use. Budget realism supports scientific feasibility.
Scientific excellence and Singapore relevance should be joined by a causal argument rather than placed in separate slogans. The capability under inspection is resource 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Link each major cost to a method, milestone and owner. 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 approved costs and current terms govern spending.
Learning move
Link each major cost to a method, milestone and owner. Label the result with the date and the capability “resource 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: Only approved costs and current terms govern spending.
Disciplines can disagree about data quality, causation or useful scale. Leaders should create routines where disagreement is documented and tested. Junior members need safe ways to raise errors and risks.
Large collaborative research needs visible decisions, interfaces and ownership. The capability under inspection is collaborative culture. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Add a structured dissent and resolution section to programme meetings. 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: Host conduct and escalation policies apply.
Evidence practice
Add a structured dissent and resolution section to programme meetings. Label the result with the date and the capability “collaborative culture”.
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: Host conduct and escalation policies apply.
When a mechanism fails or a solution performs poorly, the evidence can prevent waste and redirect the field. Preserve null and negative findings, test method limitations and communicate boundaries.
Use-inspired basic research begins with a real need but still asks fundamental questions whose answers are uncertain. The capability under inspection is learning from failure. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Write a decision memo whenever a premise is rejected. 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: Never hide evidence to preserve a preferred narrative.
Try this now
Write a decision memo whenever a premise is rejected. Label the result with the date and the capability “learning from failure”.
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: Never hide evidence to preserve a preferred narrative.
CHAPTER 14 OF 17 · Govern the evidence
14. Translation remains a later evidence journey
CRP supports use-inspired basic research, not an automatic product. If results suggest application, identify further validation, regulation, engineering, user or manufacturing evidence. Keep readiness levels honest.
A multidisciplinary team adds value only when disciplines change the question, method or interpretation together. The capability under inspection is translation 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Create a post-research evidence ladder without promising completion. 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: Potential application is not commercial readiness.
Field-note prompt
Create a post-research evidence ladder without promising completion. Label the result with the date and the capability “translation 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: Potential application is not commercial readiness.
CHAPTER 15 OF 17 · Govern the evidence
15. Communication should serve several audiences
Specialists need method and uncertainty; decision-makers need options and evidence; the public needs clarity without hype. Prepare connected explanations that preserve the same factual boundary.
Scientific excellence and Singapore relevance should be joined by a causal argument rather than placed in separate slogans. The capability under inspection is science 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Build a claim-evidence-limit table for programme communication. 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: Public interest does not justify premature disclosure.
Learning move
Build a claim-evidence-limit table for programme communication. Label the result with the date and the capability “science 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: Public interest does not justify premature disclosure.
CHAPTER 16 OF 17 · Govern the evidence
16. Capability is part of the programme legacy
A CRP can leave methods, datasets, instruments, trained researchers and collaborations even when the original route changes. Define how useful assets will be maintained and accessed responsibly.
Large collaborative research needs visible decisions, interfaces and ownership. The capability under inspection is capability building. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Track scientific outputs and lasting capabilities separately. 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: Future support and adoption are not guaranteed.
Evidence practice
Track scientific outputs and lasting capabilities separately. Label the result with the date and the capability “capability building”.
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: Future support and adoption are not guaranteed.
Archive the call, need statement, proposal, reviews, award terms, team roles, interfaces, approvals, budgets, data provenance, milestones, decisions, outputs and limitations. The index should show how a multidisciplinary programme learned.
Use-inspired basic research begins with a real need but still asks fundamental questions whose answers are uncertain. 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 public NRF page explains the CRP purpose; the current Research Grants Portal call, host policies and award terms govern eligibility, funding, dates and submission details.
Put this into practice by turning the idea into a small, reviewable action: Build one programme register with owners, dates and evidence links. 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 follows funder and host policies.
Try this now
Build one programme register with owners, dates and evidence links. 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 follows funder and host policies.
CRP research architecture
| Stage | Evidence to keep | Boundary to retain |
|---|---|---|
| Need | Important problem relevant to Singapore and society | Need does not predetermine the result |
| Science | Use-inspired basic research with scientific excellence | Merit review governs selection |
| Team | Disciplines connected through shared questions and interfaces | A list of experts is not integration |
| Delivery | Evidence, milestones, data and responsible communication | Current call and award terms govern |
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?
Start with an important Singapore problem, assemble the disciplines the problem really needs, and protect scientific excellence while the team builds use-inspired basic research 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 Competitive Research Programme — Official scheme purpose, multidisciplinary structure, use-inspired basic research and merit-review basis.
- NRF Grants — Official directory of current Singapore research funding schemes; updated 31 August 2026.
- Research Grants Portal — Official NRF route to current and upcoming grant calls and grant-management guidance.
