Adapt good research without outrunning the award
Research plans can change because evidence, technology and real operations change. A grant variation approval helps a team adapt honestly by showing what was requested, what was decided and which conditions now govern the project.
Why this English matters now
A research grant variation approval records an authorised change to a funded project; it is not the same as the request or a team's revised plan.
Researchers searching grant variation, project scope change, budget reallocation or research extension need to separate scientific justification from formal authority.
Current NRF and Singapore grant sources checked on 27 October 2026 say scope changes may be proposed for scientific or operational reasons and are generally considered favourably when they remain aligned with grant objectives.
Clear English allows useful adaptation while keeping funding, ethics and implementation in the correct order.
Checked against the official sources on 27 October 2026. The article explains how to read a document and make a safer next decision; it does not replace the issuing institution.
The reading method
Build a variation register with award, current scope, proposed change, category, reason, evidence, objective alignment, budget effect, milestone effect, compliance impact, request date, decision, conditions, effective date, system updates and reporting consequences.
- Read from funder, PI, research team, finance office and ethics or regulatory body perspectives.
- Keep proposed, submitted, pending, partially approved, approved, implemented and reported separate.
- Use an old-state-request-decision-new-state chain.
Read with every responsible person in view
- For investigators, explain change through evidence and objective alignment.
- For project and finance teams, implement only the approved version and date.
- For students and families, understand that responsible research can adapt without pretending the original plan was useless.
Different people can read the same sentence for different jobs. The student needs the next action; the administrator needs a routable record; the family needs a realistic timeline; the eventual recipient needs evidence that fits its stated purpose. Good English keeps those needs aligned without inventing authority.
Official factual floor
These first-party sources support the factual claims and should be reopened for any live transaction:
- NRF Grant Management and Investigator-led Projects
- NRF Research Grants Portal
- NUS Centre for Family and Population Research Grant Calls
- NUS Centre for Medical Education Genesis Grant Terms
Did you know?
NRF reported in October 2026 that scope-change requests are generally considered favourably when aligned with grant objectives. Generally favourable is evidence about approach, not a promise about one application.
Full chapter index
- 1. Authenticate the variation approval
- 2. Name the exact change
- 3. Separate proposal from approval
- 4. Connect change to grant objectives
- 5. Explain why the change is needed
- 6. Read budget and scope together
- 7. Coordinate ethics and regulatory amendments
- 8. Protect work while the request is pending
- 9. Read conditions and partial approvals
- 10. Update all downstream records
- 11. Communicate the change honestly
- 12. Keep the variation evidence chain
What this part of the document is doing
Open the funder's or host institution's formal record and match award, project, principal investigator, requested change, decision, conditions and effective date. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A supervisor's supportive reply is filed as the funder's approval. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. match award
- 2. match request
- 3. match decision
- 4. save the formal record
Put into one sentence, the sequence is to match award, match request, match decision, and save the formal record. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Authentication supports responsible funding. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Scope, aims, methods, budget, personnel, institution, start date and end date can follow different variation routes. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A budget transfer is described as a harmless administrative update although it changes research activity. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. classify change
- 2. identify affected documents
- 3. find required route
- 4. avoid bundled requests
Put into one sentence, the sequence is to classify change, identify affected documents, find required route, and avoid bundled requests. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Classification supports project management. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
NRF says grant recipients may propose scope changes; a proposal remains pending until the authorised decision is recorded. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: The revised work begins because the change is scientifically sensible. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. record proposed state
- 2. continue authorised work
- 3. wait for decision
- 4. record effective date
Put into one sentence, the sequence is to record proposed state, continue authorised work, wait for decision, and record effective date. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: State vocabulary supports governance. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
NRF reports that scope-change requests are generally considered favourably when aligned with grant objectives. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: The team quotes generally favourably as a guarantee. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. restate objectives
- 2. explain alignment
- 3. identify trade-offs
- 4. avoid certainty
Put into one sentence, the sequence is to restate objectives, explain alignment, identify trade-offs, and avoid certainty. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Evidence writing supports research. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Scientific developments, operational reasons, feasibility findings or new risks should be linked to evidence rather than convenience alone. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: The request says circumstances changed without naming data, constraints or consequences. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. state trigger
- 2. show evidence
- 3. compare options
- 4. justify the chosen route
Put into one sentence, the sequence is to state trigger, show evidence, compare options, and justify the chosen route. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Argument writing supports professional decisions. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
A budget movement can alter deliverables, staffing, procurement and milestones even when the total award stays unchanged. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: Money moves from fieldwork to software while the approved participant plan remains untouched. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. compare old budget
- 2. compare new activity
- 3. update milestones
- 4. seek all required approvals
Put into one sentence, the sequence is to compare old budget, compare new activity, update milestones, and seek all required approvals. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Quantitative English supports finance. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
A grant variation cannot retrospectively approve a changed protocol, consent form, site or regulated activity. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: Funder approval is treated as permission to implement a participant-facing change. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. check ethics impact
- 2. check regulatory impact
- 3. submit required amendments
- 4. align effective dates
Put into one sentence, the sequence is to check ethics impact, check regulatory impact, submit required amendments, and align effective dates. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Systems reading supports participant safety. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Teams should distinguish work allowed under the current award from activities that depend on the proposed variation. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: Every project task stops even though most approved work can continue. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. map current authority
- 2. isolate changed work
- 3. protect deadlines
- 4. document interim plan
Put into one sentence, the sequence is to map current authority, isolate changed work, protect deadlines, and document interim plan. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Scenario planning supports continuity. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
A decision may approve one element, reject another, impose a cap or require revised deliverables. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: The word approved in the subject line is taken to cover every requested change. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. read operative paragraphs
- 2. map each request item
- 3. copy conditions
- 4. update only approved elements
Put into one sentence, the sequence is to read operative paragraphs, map each request item, copy conditions, and update only approved elements. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Close reading supports accurate administration. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Budgets, accounts, procurement, staffing, milestones, ethics records and reporting templates should reflect the same approved version. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: The funder approves an extension but the finance system still blocks the new end date. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. list affected systems
- 2. assign updates
- 3. verify propagation
- 4. resolve mismatches
Put into one sentence, the sequence is to list affected systems, assign updates, verify propagation, and resolve mismatches. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Systems thinking supports organisations. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Collaborators and trainees need a concise explanation of what changed, what did not and when the new state applies. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: The project is announced as redesigned even though only a reporting deadline changed. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. name approved change
- 2. name unchanged work
- 3. state effective date
- 4. share necessary actions
Put into one sentence, the sequence is to name approved change, name unchanged work, state effective date, and share necessary actions. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Professional English supports teams. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Archive original award, request, evidence, reviews, decision, conditions, compliance amendments, system updates and later reports separately. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: Only the revised budget remains, making the reason and authority impossible to reconstruct. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. archive old state
- 2. archive request
- 3. archive decision
- 4. archive implementation
Put into one sentence, the sequence is to archive old state, archive request, archive decision, and archive implementation. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Records management supports research careers. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
Evidence examples: what the wording can and cannot prove
Label and operative sentence
Use a heading to locate the research grant variation approval, then read the whole sentence that controls the decision.
Check: Navigation words help; complete clauses decide.
Current source and saved evidence
Keep a dated copy, but reopen the official source before a live deadline.
Check: An authentic record can still be out of date.
Requirement and recommendation
Preserve must, should, may, encouraged and recommended.
Check: Modal verbs change responsibility.
Interim and final state
Record an interim state without expanding it into a promise.
Check: Evidence is reliable only within its stated scope.
Practice studio
Change classifier
Name the exact dimension that moves.
- scope
- budget
- people
- time
Alignment case
Connect evidence and trade-offs to grant objectives.
- reason
- evidence
- objective
- consequence
Implementation map
Propagate the approved change safely.
- system
- owner
- effective date
- verification
Advice for students, families and advisers
For investigators
- Do not implement a proposed change as if it were approved.
- State scientific and operational reasons with evidence.
For project and finance teams
- Update budgets, milestones and systems only from the operative decision.
- Keep old and new versions for audit and learning.
For students and families
- A variation can be a sign of thoughtful learning rather than failure.
- Avoid announcing new outcomes before the project actually tests them.
Frequently asked questions
Is a request the same as approval?
No.
Are scope changes always rejected?
No. NRF says they may be proposed and are generally considered favourably when aligned with objectives.
Does generally favourable guarantee approval?
No.
Can budget move without scope impact?
Sometimes, but check the terms and activity consequences.
Does funder approval replace IRB amendment?
No.
Can unchanged work continue while a request is pending?
Map what remains authorised and follow current terms.
What is partial approval?
A decision that accepts only some requested elements or adds conditions.
When does the new scope apply?
Use the decision's effective date and implementation records.
What should be saved?
Original award, request, evidence, decision, conditions and system updates.
Why English?
Because proposed, pending, approved and implemented are different states.
Useful next reading
- Research Grant Award Letter — how the original award defines the starting authority
- IRB Continuing Review Outcome — how ongoing ethics status remains separate from funding decisions
Closing thought
The best variation record shows that research can learn and change without losing its promise to funders, participants, collaborators or the public: say exactly what moved, why and under whose authority.