From the Research Universities edition of September 26, 2026
Georgia Tech interim AI Academic & Research policy: approved tools, protected-data limits, human oversight, disclosure
Georgia Institute of Technology (Office of the Provost / EVPR) · Higher education research administration · United States (Atlanta, GA)
- Publisher
- Georgia Tech Policy Library
- Original publication
- June 2026 (effective); review December 2026
- Source retrieved
- 2026-09-27
What happened
Georgia Tech’s interim policy governing AI in Academic and Research Contexts (effective June 2026) requires community members to use Institutionally Approved or Local-POC Limited Use AI tools for academic/research work; prohibits submitting Protected Data or PII into tools outside approved scope; mandates human oversight/verification of AI outputs before reliance; and requires appropriate disclosure of AI use in scholarly communications. An AI Governance Officer and Committee coordinate tool approval and points of contact. Why now: as campuses expand AI/HPC capacity and research agents show low claim-reproduction rates, research-admin control layers become operationally binding—not optional guidance.
Why it matters
Research administration adopting AI agents and shared AI tools needs enforceable approval, data-handling, oversight, and disclosure controls that transfer to other R1 governance designs.
Evidence and measured results
Georgia Tech Policy Library page opened via HTTPS; effective date June 2026, tool-approval, protected-data, human oversight, and disclosure provisions taken from the opened policy text.
Limitations and uncertainty
Interim policy without published compliance metrics; effective June 2026 (older than last edition) included for newly relevant control-layer why-now; does not evaluate scientific agent performance.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-26; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Research units adopt AI tools and agents faster than institutional approval, data, and disclosure controls can keep up.
- Stakeholders
- Provost / EVPR
- Research integrity / ORIA
- CIO / OIT governance
- College AI points of contact
- PIs and lab managers
- Discovery questions
- Is there an institute AI registry and Limited Use path?
- How is Protected Data defined and enforced in AI tools?
- Who verifies AI outputs before scholarly use?
- What disclosure standard applies to grants and manuscripts?
- Value hypothesis
- An interim academic/research AI policy with approved tools, data limits, human oversight, and disclosure can reduce uncontrolled AI use while enabling sanctioned tools.
- Potential engagement
- Gap assessment of campus AI tool inventory against an approved-registry and protected-data control model.
- Unsupported claims
- Measured reduction in research misconduct
- Complete prevention of shadow AI
- Scientific quality improvement from policy alone
- Identical fit to every state system
Pre-sales engineering
Role takeaway
- Fit
- Policy-backed allowlist of AI tools with local Limited Use exceptions and data-class enforcement for research systems.
- Architecture and integration
- Connect IdP, data classification labels, AI registries, and research platforms so unapproved tools cannot receive Protected Data.
- Prerequisites
- Data classification scheme
- AI Governance Officer/Committee
- Local AI POCs
- Tool approval standard
- Training modules
- Constraints
- Interim policy
- No published compliance KPIs
- Companion admin policy dependency
- Student personal-tool carve-outs
- Security
- Block Protected Data/PII into non-approved scopes; monitor prompt-injection and audit trails per companion IT policy.
- Proof of value
- Share of research AI use on approved tools
- Documented Limited Use reviews
- Training completion
- Disclosure appearing in sample scholarly outputs
Delivery
Role takeaway
- Work
- Publish registries, appoint POCs, roll training, embed disclosure guidance in grant/manuscript workflows.
- Dependencies
- OIT registry platform
- ORIA / research integrity
- College deans for POCs
- CTL for instructional guidance
- Ownership
- AI Governance Program coordinates; Provost/EVPR own academic/research decisions; units own local POCs.
- Skills and adoption
- Train PIs and students on verification, disclosure, and approved-tool selection; train POCs on Limited Use triage.
- Governance checkpoints
- Annual policy review
- Tool approval audits
- Misconduct process linkage
- Acceptance criteria
- Approved and Limited Use registries published
- Protected-data guidance live
- POC network designated
- Risks
- Shadow SaaS AI tools
- Uneven college enforcement
- Disclosure without verification
- Policy lag vs agent capabilities
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?
Institute and local AI registries; Local AI Points of Contact; separation of academic/research vs administrative AI policies; training requirements via AI Governance Program.
Governance
Who approves, reviews and stays accountable for outcomes?
Central AI Governance Committee plus unit POCs; annual review; enforcement via existing academic and research misconduct channels; funder/publisher policies still apply.
Security and privacy
What data, permissions and controls need testing?
Hard stop on Protected Data/PII in unapproved tools; prompt-injection awareness; monitoring/audit trails referenced to companion administrative AI policy.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Policy lists accessibility among guiding principles and requires education offerings; Local POCs are the workforce layer that makes registries usable.
Procurement
What should contracts, pricing and exit terms secure?
Prefer Institutionally Approved AI tools; route new research tools through approval standard before contract—especially those touching Protected Data.
Operating model
Which teams own the service once it runs?
Central governance with distributed college POCs is the operating model for research AI enablement under control.
Publication history
- 2026-09-26Research Universities · Issue 204 resources
Stable resource ID: gatech-ai-academic-research-policy-202606