AI literacy must be built for each discipline, not taught the same way to everyone
How an engineering student thinks about AI differs fundamentally from how a nursing student or graphic designer approaches the same tools. This gap matters because a single institutional AI training programme cannot prepare students for the specific demands of their field.
An engineering student views AI as "augmentation, not replacement"-a tool for repetitive work while they retain responsibility for core logic and final validation. A graphic design student draws a different line entirely: AI can serve as tutor or supporter, never as author. A nursing student's view is shaped by professional accountability that the discipline carries by design. These distinctions are grounded in how each field actually works.
What discipline-specific AI literacy looks like
In STEM subjects, AI literacy connects directly to the scientific method. Reproducibility, audit trails, and the conditions under which results can be trusted are not abstract values-they are working practices. A biology or chemistry student needs to understand where a model's output comes from and when it might fail. In research, hallucination corrupts the entire research process. AI literacy in STEM means learning to interrogate a tool the way a scientist interrogates data.
Humanities disciplines face a different problem. The authorial voice, the interpretive act, reading sources for argument rather than information: these are what the disciplines teach, not assessment conventions. When AI summarises a primary source, it produces a statistically probable description, not a reading. A history student who uses AI as a substitute for interpretation bypasses the very act the subject exists to teach. AI literacy in the humanities works best as provocation: what does this tool produce, what has it left out, and why does that matter to your argument?
Professional fields-medicine, law, social work, nursing, teacher education-present a third challenge. These disciplines operate under regulatory standards that pre-exist AI and are not optional. A law student who submits a brief citing cases that do not exist could harm a client. A nursing student who relies on AI output without applying clinical judgement could harm a patient. The stakes are concrete. AI literacy for professional programmes must centre on accountability: who is responsible for this output, under what regulatory framework, and how do you demonstrate appropriate judgement?
How institutions can build effective guidance
The variation between fields is wide enough that a single framework cannot address all three. What works is guidance built at module level, specific to the discipline, assessment type, and stage of work.
The most effective approaches share one feature: they ask students to account for their AI use rather than simply declare it. In engineering programmes, students walk through code logic in a short oral, explaining which design decisions were theirs and where AI contributed. In philosophy seminars, students compare an AI-generated argument with their own position and articulate precisely where and why they diverge. In clinical education, oral defence formats require students to justify a clinical decision regardless of what tool assisted their initial workup.
A postgraduate design course requires students to submit 100 to 200 pages of research with reflective analysis on every page. This format makes AI shortcuts visible because the assessment traces the student's thinking throughout the project, not just at submission.
These approaches share a second feature: the presence of a visible accountability moment changes how students use AI throughout the module. Students who know they will need to explain their work in person use AI to test and deepen understanding. Students who face no such moment have no equivalent incentive.
Five practical steps for institutions
- Design AI guidance at module level, not institution level. The variation across creative arts, STEM, healthcare, and humanities is too wide for any uniform approach to work. Module teams are best placed to define what AI use looks like in their specific learning outcomes, assessment types, and disciplinary norms.
- Assess explanation of AI use, not declaration. A brief oral component, process reflection, or structured conversation about submitted work creates a far stronger incentive for genuine engagement than any checkbox.
- Align AI guidance with disciplinary purpose. The question is not "how much AI is acceptable?" but "what does AI do to the specific kinds of knowledge and judgement this programme develops?" Starting from that question produces guidance students can actually use.
- Coordinate expectations across teaching teams. A 10-minute conversation at the start of the academic year, producing a shared position on AI use across a programme, resolves the most commonly reported source of student confusion.
- Address unequal access to AI tools. Where AI use is expected or encouraged, the quality differential between paid and free tools becomes a socio-economic issue. Students who cannot afford paid tools work with worse outputs and spend more time correcting errors. Institutional licensing is a practical way to close that gap.
Students as partners in curriculum design
Students can describe with precision when AI supports genuine learning and when it replaces it. That clarity is currently invisible and largely unused. Bringing it into curriculum design through structured seminar discussions, peer case analysis, or disciplinary ethics workshops produces better guidance than any top-down framework. It treats students as partners in working out what learning means in their field rather than subjects to be governed.
The discipline problem with AI literacy does not require a complicated solution. It means treating each field on its own terms and building guidance that starts from what the subject is actually for.
For educators developing AI guidance in your institution, explore resources on AI for Education and consider the AI Learning Path for Teachers to support your implementation.
Your membership also unlocks:
