From the Research Universities edition of November 10, 2026
The use of generative artificial intelligence in the development and review of research funding applications (updated Tri-Agency guidance)
CIHR, NSERC, SSHRC and the Canada Foundation for Innovation (Government of Canada) · Research funding (federal research funding agencies) · Canada
- Publisher
- Science.gc.ca
- Original publication
- Page modified 30 October 2026
- Source retrieved
- 2026-11-11
What happened
Canada's three federal research councils and the Canada Foundation for Innovation say they have updated their guidance on generative AI in developing and reviewing research funding applications. A key update is that institutionally procured and deployed generative AI tools are not permitted for reviewers carrying out reviewer responsibilities. The agencies also reformatted their FAQ into applicant and reviewer sections to show where generative AI use is and is not permitted, and say the update underscores research integrity, transparency and confidentiality. The update notice on the opened page is short and does not itself list the detailed rules; the notice is dated 30 Oct 2026. Included now because it is a recent change by national funders that narrows what universities can offer reviewers, and it complements the archived AMRC and Springer funder-policy items by covering a government-funded agency stance.
Why it matters
Relevant to Canadian and other universities whose faculty serve as reviewers and whose research offices license enterprise AI tools: the update says that a campus-procured tool does not make AI use acceptable for review work.
Evidence and measured results
Government agency update notice and guidance page; no empirical evaluation, sample or measured outcomes. Only the update notice page was opened; the detailed guidance and FAQ pages were not read in this run.
Limitations and uncertainty
Short update notice only; details come from the full guidance and FAQ pages, which were not opened; applies to Tri-Agency and CFI processes, not other funders; page states a modification date rather than a publication date; no evidence on effects or compliance.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Campus AI tool programs may give faculty a false impression that institutionally approved tools are acceptable for reviewing confidential funding applications.
- Stakeholders
- Vice president for research
- Research administration and sponsored programs
- Faculty affairs
- CIO or AI governance lead
- Discovery questions
- Which faculty review for these agencies?
- Which AI tools do reviewers have access to?
- How does our tool catalog describe review uses?
- Who tracks funder policy changes?
- Value hypothesis
- Clear reviewer guidance and tool-catalog wording may reduce confidentiality breaches; the notice does not measure incidents or benefits.
- Potential engagement
- A short policy and tooling review comparing campus AI offerings and communications with the full agency FAQ.
- Unsupported claims
- Compliance with any specific rule beyond the notice
- Applicability to non-Canadian funders
- Evidence of breach rates
- Cost or efficiency effects
Pre-sales engineering
Role takeaway
- Fit
- Relevant as a policy constraint on enterprise AI offerings used by academic reviewers.
- Architecture and integration
- Add reviewer-context notices to AI portals and document which tools are approved for applicant tasks versus none for agency review work.
- Prerequisites
- Inventory of AI tools available to faculty
- Full text of agency guidance and FAQ
- Data-flow documentation
- Constraints
- Notice lacks detailed rules
- Agency-specific scope
- Enforcement mechanisms unstated
- Security
- The notice stresses confidentiality; enterprise hosting is not an exception for reviewers.
- Proof of value
- Map tools reviewers can reach
- Confirm portal notices match the FAQ
- Spot-check that review-related prompts are not encouraged by templates
Delivery
Role takeaway
- Work
- Read the full guidance, update reviewer and applicant communications, revise tool-catalog language and brief affected faculty.
- Dependencies
- Agency guidance text
- Research administration time
- Communications channel to faculty
- Ownership
- Research administration owns reviewer guidance; IT and AI governance own tool-catalog language.
- Skills and adoption
- Faculty reviewers need short instruction on what is prohibited and where applicant uses differ.
- Governance checkpoints
- Policy wording check against the full FAQ
- Annual review of agency updates
- Incident route for confidentiality concerns
- Acceptance criteria
- Proposed: reviewer notice issued
- Proposed: tool catalog states review-use limits
- Proposed: named owner tracks agency changes
- Risks
- Misreading a short update notice
- Conflicting funder rules
- Faculty unaware of the change
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Institutional AI tool catalogs should flag review-related contexts as out of scope for approved tools used by agency reviewers, and avoid presenting enterprise tools as a safe route for reviewing confidential applications.
Governance
Who approves, reviews and stays accountable for outcomes?
Research offices should align reviewer instructions with the updated agency rules, separate applicant uses from reviewer uses, and check the detailed FAQ for the specific permitted and prohibited cases before issuing local policy.
Security and privacy
What data, permissions and controls need testing?
The stated emphasis is confidentiality of applications; the notice indicates that institutionally deployed tools are not an exception for reviewers, so enterprise tenancy alone should not be treated as sufficient.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Faculty reviewers may lose institutional tools for language help in review work; the notice does not state whether other limited uses are allowed, so check the FAQ.
Procurement
What should contracts, pricing and exit terms secure?
When procuring or promoting enterprise AI, state use cases clearly and avoid marketing it for reviewing confidential funding applications covered by these agencies.
Operating model
Which teams own the service once it runs?
Places responsibility for reviewer conduct with the agencies and reviewers, and for tool-catalog clarity and communication with the research office.
Publication history
- 2026-11-10Research Universities · Issue 633 resources
Stable resource ID: canada-tri-agency-updated-ai-guidance-research-funding-reviewers-institutional-tools-prohibited-20261030