50/100

Moderate evidence

ProblemPublished recordEducationProblem Space

Understanding students’ GenAI usage, attitudes, and training needs for equitable and sustainable AI adoption in higher education

Truvace record
TRV-2026-3022raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
e4ba0f46816d…check it

Artificial Intelligence (AI) is expected to revolutionise Australian’s economy with the potential to generate up to $600 billion per annum to GDP by 2030 (Australian Government, Department of Industry, Science and Resources, 2024). To keep up with the accelerating growth of AI, the higher education sector needs to transition from traditional teaching models to an AI-integrated pedagogy. One of the key concerns in this transition is to ensure equitable and sustainable adoption of AI in higher education. This conc…

The problem

A semester-one 2026 survey of Humanities students at an Australian university found 98% use generative AI, with some of that use uncritical and potentially over-reliant and with varying access and competence.

What this doesn’t fix

The survey covered only Humanities students in Law, Accounting, Business and Education disciplines at one Australian university, so the results may not describe other student groups.

Sources

1 on file
  1. ASCILITE Publicationsdoi:10.65106/apubs.2026.3425
    Peer-reviewed2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3022, v1: “Understanding students’ GenAI usage, attitudes, and training needs for equitable and sustainable AI adoption in higher education.” Truvace, 2026-11-18. /record/TRV-2026-3022 (accessed on the day you copy it). sha256 e4ba0f46816dc695…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1e4ba0f46816d…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3022 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.