eduKateSG · Why Science?
Learn how an H3 research attachment turns a strong interest into a disciplined investigation—with questions, methods, mentorship, uncertainty and a defensible record
A fact-checked guide to A*STAR’s H3 Research Attachment Programme, its official scope and school coordination, plus practical habits for independent science research and honest pathway reflection.
A*STAR says the H3 programme was introduced by the Ministry of Education in 2006 to promote multidisciplinary and independent learning.
The official page identifies strong interest and aptitude in biomedical science, physical science or engineering and says junior-college participants conduct an investigative study in science or engineering.
A*STAR states that attachments are coordinated through schools with the A*STAR Graduate Academy and involve mentorship by selected teachers and researchers.
Did you know? “Independent learning” in research does not mean working alone. It means taking responsibility for a question and record while using supervision, critique and safety systems well.
The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence. 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, school coordination, question design and responsible planning
- 1. Read the H3 programme as independent, mentored inquiry
- 2. School coordination comes before personal planning
- 3. A research interest needs a tractable question
- 4. A literature trail explains why the question matters
- 5. Methods are arguments made operational
- 6. Safety and ethics shape the project from the start
- 7. A laboratory notebook protects the reasoning chain
- 8. Mentorship works through prepared decisions
- 9. Data quality begins before analysis
Chapters 10–17: methods, mentorship, uncertainty, communication and tertiary-level readiness
- 10. Controls and comparisons carry meaning
- 11. Uncertainty belongs in the result
- 12. Analysis should be reproducible
- 13. Scientific writing connects claim, evidence and limit
- 14. A presentation is a test of understanding
- 15. A failed plan can still produce strong learning
- 16. Tertiary readiness is a capability, not a promise
- 17. Close with a research receipt another person can audit
CHAPTER 1 OF 17 · Understand the programme
1. Read the H3 programme as independent, mentored inquiry
A*STAR describes the programme as multidisciplinary and independent learning for students with strong interest and aptitude in biomedical science, physical science or engineering. Junior-college students conduct an investigative science or engineering study under selected teacher and researcher mentorship. Each phrase matters: the work is student-owned, cross-disciplinary possibilities are real, and supervision remains essential.
In an independent investigation, read the h3 programme as independent, mentored inquiry is part of the argument for trusting the result. The practical capability here is programme interpretation. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Underline every noun and verb in the official description, then rewrite it without adding promises. 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 official programme and school determine current eligibility, subjects and selection.
Try this now
Underline every noun and verb in the official description, then rewrite it without adding promises. Label the result with the date and the capability “programme interpretation”.
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 official programme and school determine current eligibility, subjects and selection.
CHAPTER 2 OF 17 · Understand the programme
2. School coordination comes before personal planning
The official application procedure says attachments to A*STAR are coordinated through schools with the A*STAR Graduate Academy. Students should ask their school about current offerings, internal criteria, timelines and academic expectations. Published partner arrangements can change, so a historical list or another college’s process is not a safe substitute.
School coordination comes before personal planning connects a scientific idea to a decision that another researcher should be able to inspect. The practical capability here is administrative literacy. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Ask the school coordinator for the current programme brief and decision calendar. 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 assume a direct application route or copy another school’s procedure.
Field-note prompt
Ask the school coordinator for the current programme brief and decision calendar. Label the result with the date and the capability “administrative 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 assume a direct application route or copy another school’s procedure.
CHAPTER 3 OF 17 · Understand the programme
3. A research interest needs a tractable question
“Cancer”, “energy” or “robots” names a field, not an investigation. A tractable question connects a defined system, measurable outcome, plausible method and realistic time. Early narrowing is productive: it gives the literature search a purpose and makes safety, equipment and analysis conversations concrete.
The research record becomes stronger when a research interest needs a tractable question is explicit rather than left to memory. The practical capability here is question formulation. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Draft the question in one sentence, then mark population or system, exposure or input, outcome and comparison. 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: Feasibility and safety can require a major change of question.
Learning move
Draft the question in one sentence, then mark population or system, exposure or input, outcome and comparison. Label the result with the date and the capability “question formulation”.
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: Feasibility and safety can require a major change of question.
CHAPTER 4 OF 17 · Understand the programme
4. A literature trail explains why the question matters
Reading is not a pile of summaries. Start with reliable reviews or authoritative background, find the key primary studies and trace definitions and methods to their source. Record search terms, dates and inclusion choices. The literature trail should show what is known, where findings disagree and why the proposed study adds a useful test.
For H3 learning, a literature trail explains why the question matters shows how ownership and mentorship can work together. The practical capability here is research synthesis. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Create an annotated source table with claim, method, relevance and limitation. 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: Citations must support the nearby statement; do not cite a paper you have not read.
Evidence practice
Create an annotated source table with claim, method, relevance and limitation. Label the result with the date and the capability “research synthesis”.
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: Citations must support the nearby statement; do not cite a paper you have not read.
A method turns a scientific idea into steps that can generate interpretable evidence. Define materials, sampling, controls, measurements, timing and analysis before collecting data. Ask how each choice answers the question and which bias it might introduce. A polished protocol without this logic is only a recipe.
In an independent investigation, methods are arguments made operational is part of the argument for trusting the result. The practical capability here is method design. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: For every procedural step, write the reason it exists and the error it is meant to control. 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 only approved procedures, facilities and supervision.
Try this now
For every procedural step, write the reason it exists and the error it is meant to control. Label the result with the date and the capability “method 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 only approved procedures, facilities and supervision.
CHAPTER 6 OF 17 · Design the inquiry
6. Safety and ethics shape the project from the start
Responsible research does not add safety and ethics after the exciting design is complete. Hazards, human or animal involvement, sensitive data, consent, waste and access permissions can change what is feasible. Follow the host institution’s approvals and the mentor’s instructions; a student’s enthusiasm never overrides them.
Safety and ethics shape the project from the start connects a scientific idea to a decision that another researcher should be able to inspect. The practical capability here is responsible research. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Add a risk, permission and data-protection column to the plan before work begins. 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 improvise around an approval, access rule or safety control.
Field-note prompt
Add a risk, permission and data-protection column to the plan before work begins. Label the result with the date and the capability “responsible research”.
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 improvise around an approval, access rule or safety control.
CHAPTER 7 OF 17 · Design the inquiry
7. A laboratory notebook protects the reasoning chain
Record dates, versions, settings, sample identifiers, deviations and observations close to the work. Distinguish what happened from what you think it means. When a procedure changes, preserve the earlier version and explain why. A trustworthy notebook lets the team reconstruct decisions, including mistakes.
The research record becomes stronger when a laboratory notebook protects the reasoning chain is explicit rather than left to memory. The practical capability here is research documentation. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Design a page template with objective, setup, action, observation, deviation and next decision. 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 rewrite the past to make the project look smoother.
Learning move
Design a page template with objective, setup, action, observation, deviation and next decision. Label the result with the date and the capability “research documentation”.
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 rewrite the past to make the project look smoother.
Selected teachers and researchers provide expertise and supervision, but students learn more when they arrive with evidence and choices. A useful update states the question, what changed, the current interpretation, one uncertainty and the decision needed. This makes feedback actionable and protects genuine independent learning.
For H3 learning, mentorship works through prepared decisions shows how ownership and mentorship can work together. The practical capability here is collaborative reasoning. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Send a brief agenda before the next meeting and record the decision afterward. 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: Mentor guidance does not transfer authorship of work the student did not do.
Evidence practice
Send a brief agenda before the next meeting and record the decision afterward. Label the result with the date and the capability “collaborative 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: Mentor guidance does not transfer authorship of work the student did not do.
File names, units, calibration, missing-value rules and metadata determine whether later analysis is trustworthy. Decide these conventions before a dataset grows. Keep raw data read-only, document transformations and link each figure to the code or steps that produced it.
In an independent investigation, data quality begins before analysis is part of the argument for trusting the result. The practical capability here is data stewardship. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Build a data dictionary and test it on a small pilot 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: Never delete or alter raw observations simply because they are inconvenient.
Try this now
Build a data dictionary and test it on a small pilot record. 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: Never delete or alter raw observations simply because they are inconvenient.
A result becomes interpretable through comparison. Controls help distinguish the effect of interest from background change, measurement drift or procedural artefact. The right control depends on the system, so explain its logic rather than inserting one mechanically.
Controls and comparisons carry meaning connects a scientific idea to a decision that another researcher should be able to inspect. The practical capability here is causal reasoning. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Draw a diagram showing each group or condition and the inference its comparison 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: A control reduces specific uncertainty; it does not prove every alternative wrong.
Field-note prompt
Draw a diagram showing each group or condition and the inference its comparison enables. 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 control reduces specific uncertainty; it does not prove every alternative wrong.
Variation, measurement limits, sample size and analytic choices affect how much a result can support. Report uncertainty clearly and resist turning a suggestive pattern into a definitive claim. Unexpected results can improve the project when they lead to a better check or narrower conclusion.
The research record becomes stronger when uncertainty belongs in the result is explicit rather than left to memory. The practical capability here is calibrated interpretation. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Write the strongest claim supported, then a second sentence stating the most important uncertainty. 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: Statistical significance alone does not establish importance, mechanism or generality.
Learning move
Write the strongest claim supported, then a second sentence stating the most important uncertainty. Label the result with the date and the capability “calibrated interpretation”.
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: Statistical significance alone does not establish importance, mechanism or generality.
Whether the work uses a spreadsheet, code or manual calculation, preserve inputs, formulas, versions and exclusions. Give files stable names and keep an analysis log. Another informed person should be able to follow the path from raw observations to the displayed result without guessing.
For H3 learning, analysis should be reproducible shows how ownership and mentorship can work together. The practical capability here is reproducibility. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Reproduce one figure from a clean copy of the raw data and note every dependency. 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 hide hand edits or undocumented exclusions.
Evidence practice
Reproduce one figure from a clean copy of the raw data and note every dependency. Label the result with the date and the capability “reproducibility”.
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 hide hand edits or undocumented exclusions.
CHAPTER 13 OF 17 · Explain what changed
13. Scientific writing connects claim, evidence and limit
A strong report explains the question, places it in context, describes enough method to evaluate the evidence, presents results without decoration and discusses what follows. Put citations next to the claims they support. State limitations where readers need them, not only in a ceremonial final paragraph.
In an independent investigation, scientific writing connects claim, evidence and limit is part of the argument for trusting the result. The practical capability here is technical communication. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Audit each paragraph: identify its claim, evidence, source and boundary. 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: Clear writing cannot rescue unsupported or overextended claims.
Try this now
Audit each paragraph: identify its claim, evidence, source and boundary. Label the result with the date and the capability “technical 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: Clear writing cannot rescue unsupported or overextended claims.
CHAPTER 14 OF 17 · Explain what changed
14. A presentation is a test of understanding
Explaining the project to an unfamiliar audience reveals gaps. Lead with the problem and question, show only the method needed to interpret the result, label figures fully and say what changed in your thinking. Prepare for “How do you know?” and “What else could explain this?” rather than memorising a performance.
A presentation is a test of understanding connects a scientific idea to a decision that another researcher should be able to inspect. The practical capability here is oral defence. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Give a three-minute explanation to a peer and record the questions that remain unclear. 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 disclose confidential data or unpublished details without permission.
Field-note prompt
Give a three-minute explanation to a peer and record the questions that remain unclear. Label the result with the date and the capability “oral defence”.
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 disclose confidential data or unpublished details without permission.
CHAPTER 15 OF 17 · Explain what changed
15. A failed plan can still produce strong learning
Equipment may fail, samples may behave unexpectedly or the original question may prove too broad. Research maturity shows in the response: document the problem, distinguish error from evidence, consult the mentor and revise transparently. A smaller defensible study is better than an impressive story built on missing records.
The research record becomes stronger when a failed plan can still produce strong learning is explicit rather than left to memory. The practical capability here is adaptive problem-solving. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Write a decision memo for one setback: evidence, options, chosen revision and 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: Never fabricate, backfill or conceal data to protect the original plan.
Learning move
Write a decision memo for one setback: evidence, options, chosen revision and consequence. Label the result with the date and the capability “adaptive problem-solving”.
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 fabricate, backfill or conceal data to protect the original plan.
CHAPTER 16 OF 17 · Explain what changed
16. Tertiary readiness is a capability, not a promise
A*STAR says the programme lays a foundation for future research at tertiary level. That is a learning aim, not a guaranteed university place or career. The useful evidence lies in sustained reading, method choices, data care, response to critique and honest communication—capabilities that can inform many study routes.
For H3 learning, tertiary readiness is a capability, not a promise shows how ownership and mentorship can work together. The practical capability here is pathway literacy. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Map three project tasks to capabilities and then to questions for course exploration. 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: Participation does not guarantee admission, scholarship or employment.
Evidence practice
Map three project tasks to capabilities and then to questions for course exploration. Label the result with the date and the capability “pathway 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: Participation does not guarantee admission, scholarship or employment.
CHAPTER 17 OF 17 · Explain what changed
17. Close with a research receipt another person can audit
Collect the official programme brief, question versions, source trail, approvals, protocol, notebook index, data dictionary, analysis record, figures, feedback, revisions, final claims and reflection. The receipt should show what the student did, how decisions changed and what remains uncertain.
In an independent investigation, close with a research receipt another person can audit is part of the argument for trusting the result. The practical capability here is research provenance. Keep a dated trace of the starting idea, the action taken, the evidence noticed, the feedback received and the next decision. This makes progress visible without pretending that one activity proves permanent mastery. The central learning move is from answering a supplied question to defending why a question, method and interpretation deserve confidence.
Put this into practice by turning the idea into a small, reviewable action: Create a one-page provenance map linking every major claim to its evidence file. 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: Retain data only as permitted and follow the host institution’s record rules.
Try this now
Create a one-page provenance map linking every major claim to its evidence file. Label the result with the date and the capability “research provenance”.
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: Retain data only as permitted and follow the host institution’s record rules.
H3 investigation control panel
| Stage | Evidence to keep | Boundary to retain |
|---|---|---|
| Question | Scope, variables, rationale and feasibility | A clear question can still change with evidence |
| Method | Procedure, controls, calibration and safety | Follow institutional approvals and mentor direction |
| Evidence | Raw data, exclusions, analysis and uncertainty | Do not remove inconvenient results silently |
| Claim | What the results support and what remains open | A research attachment is not an admission guarantee |
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?
Learn how an H3 research attachment turns a strong interest into a disciplined investigation—with questions, methods, mentorship, uncertainty and a defensible record 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.
- A*STAR H3 Research Attachment Programme — Official history, fields, benefits, mentorship and school-coordinated application route.
- A*STAR Student Awards — Official directory describing the investigative-study purpose and Singaporean eligibility.
- MOE notes on subjects offered for pre-university course — Official MOE document listing partner H3 science research programmes; students must rely on their school for current offerings and selection.
