DEC 2026 Survey: 88% of Students Use AI, Only 29% Trust Instructors

The Digital Education Council’s AI in Higher Education Global Survey 2026 finds that 88 percent of students worldwide use artificial intelligence in their studies, yet only 29 percent believe their instructors are equipped to guide them. The practical response should be immediate: universities should replace blanket AI rules with course-level, purpose-based permissions; define permitted, prohibited, and disclosure-required uses; redesign assessments to test both independent and AI-assisted competence; and establish a documented escalation path from campus IT and support desks to academic policy owners.
The survey, reported by News Ghana, draws on 45,398 responses from 118 institutions across 35 countries. Its most important finding is not adoption alone, but the disconnect between use, educational value, and confidence in institutional guidance. Nearly nine in ten students use AI, but only 5 percent of users say it has transformed how they learn.
Universities therefore face a governance and course-design problem, not merely a software rollout. Students are already experimenting with AI through browsers, personal and managed accounts, extensions, mobile applications, learning platforms, and productivity environments. Institutions now need to explain where that assistance supports learning, where it defeats the purpose of an assignment, what information must remain outside AI systems, and who answers questions when technical access and academic permission diverge.

A diverse team studies AI governance, security, and compliance through a layered digital workflow.Students Have Adopted AI Faster Than Universities Can Explain It​

At 88 percent, global student use of AI is no longer an emerging behavior. It is part of the ordinary infrastructure of studying, sitting alongside browsers, word processors, search engines, and learning-management systems. Any university still designing its strategy around whether students might begin using AI is addressing a question that student behavior has largely settled.
Yet adoption is not uniform. DEC reports that 92 percent of students in Latin America use AI in their studies, compared with 85 percent in Europe, the Middle East and Africa, and 65 percent in the United States and Canada. Those disclosed figures indicate different regional starting points, but they do not provide a complete comparison across every metric or every region.
RegionStudent AI adoptionIntegrity concernFaculty or student outlook
Latin America92%Not reported in the provided survey factsHighest specified student-adoption figure
EMEA85%48% fear classmates misuse AIOther outlook measures not reported in the provided survey facts
US and Canada65%73% fear classmates misuse AI55% support restrictions; 43% support an outright ban; faculty intent to use AI in teaching was 67%
APACNot reported in the provided survey factsNot reported in the provided survey facts57% of faculty are excited about AI; half of students expect fewer opportunities
This partial regional picture is still enough to show why one universal rule will be difficult to apply credibly. Institutions are working with different levels of student use, concern about unfair advantage, faculty enthusiasm, and employment anxiety. Those differences affect which problems need attention first.
Digital Education Council chief executive Alessandro Di Lullo argued that a blanket policy would not serve every student or faculty member well. The operational alternative is not the absence of rules. It is a shared institutional framework translated into course-level instructions that reflect the purpose of particular learning activities.
Adoption itself does not show whether students can verify an answer, detect fabricated material, protect sensitive information, attribute assistance, or recognize when AI use prevents an assignment from measuring the intended skill. Those capabilities require explicit teaching and practice.
The immediate task for universities is therefore to convert an already common student behavior into visible, assessable, and appropriately governed work.

The 29 Percent Trust Figure Is the Survey’s Real Emergency​

Only 29 percent of students worldwide believe their instructors are equipped to guide them on AI. In the United States and Canada, that figure falls to 17 percent. The result challenges the university’s role as the institution responsible for teaching students how knowledge should be produced, tested, documented, and defended.
Students do not need instructors to compete with AI systems at generating text. They need instructors to explain when an output may be useful, when it may be misleading, what evidence is missing, which uses are legitimate in a discipline, and how students remain accountable for work completed with machine assistance. Those are academic judgments rather than basic software-support questions.
DEC’s trust figures do not establish why students hold these views. One possible explanation is inconsistency in what students encounter: an instructor may prohibit AI without explaining the instructional purpose, allow it without defining boundaries, or require disclosure without showing what an adequate disclosure looks like. The survey does not prove that these practices caused the trust result, but each can make policy harder for students to interpret.
When formal guidance is limited or inconsistent, students may rely more heavily on peers, social media, vendor interfaces, and trial and error. That can create an informal layer of learning outside the curriculum, although DEC’s data does not establish its scale or effects.
The institutional risk is clearest at the point of enforcement. A student may have to navigate different rules across several courses, distinguish brainstorming from substitution, preserve evidence of authorship, and decide whether an embedded feature counts as AI assistance. The university still determines whether the resulting work complies with academic standards.
A credible policy must therefore provide a workable model of practice:
  • What assistance is permitted without disclosure?
  • What assistance is permitted only with disclosure?
  • What must remain the student’s independent work?
  • What information must never be submitted to an AI service?
  • What records of prompts, outputs, sources, or revisions must be retained?
  • Who resolves uncertainty before an assignment is submitted?
Clear answers reduce the need for students, faculty, and support staff to improvise policy.

North America Is Combining Low Trust With Strong Support for Restriction​

The United States and Canada stand out in the disclosed figures for strong student support for restrictions. DEC found that 55 percent of students there support some form of institutional restriction on AI, including 43 percent who want an outright ban.
The same region reports lower student adoption than the global figure and greater concern that classmates are exploiting AI. Seventy-three percent fear that peers misuse AI to get ahead, compared with 60 percent worldwide and 48 percent in EMEA.
These figures are consistent with a perceived fairness problem, but the survey does not establish that fairness concerns caused support for restrictions. Students may support limits for several reasons, including academic integrity, learning quality, privacy, uncertainty about acceptable use, or concern that rules are not enforced consistently.
Faculty intent to use AI in teaching in the United States and Canada fell from 76 percent in 2025 to 67 percent in the 2026 survey, a decline of 9 percentage points. The provided survey facts do not establish how that figure ranks against every other region, nor do they demonstrate what caused the decline.
It would also be inappropriate to present the regional figures as proof of a self-reinforcing cycle. They show attitudes and reported behavior at the same time: low student confidence, concern about peer misuse, support for restrictions, and declining faculty intent. Universities should investigate whether those issues interact on their own campuses rather than assume that DEC has demonstrated a causal chain.
The practical implication is that North American institutions need rules capable of supporting both fairness and instruction. Students who want a level playing field need more than a general ban. They need comparable expectations across course sections, assessment designs that make competence visible, and a reliable process for resolving ambiguous cases.

The Technology Is Present, but the Course Design Is Missing​

Only 15 percent of students say AI appears in many of their courses. Another 43 percent see it in only a few. Those figures help explain how overall use can reach 88 percent while only 5 percent of users describe AI as transforming how they learn.
The gap suggests that much student use may occur outside formally designed course activities, although the survey figures alone do not identify exactly how students are using the tools. AI may assist with interpreting instructions, summarizing material, generating examples, organizing drafts, translating text, or working through difficult concepts without being explicitly addressed in the course.
The operational question for each assignment is not simply whether AI is present. It is what the assignment is intended to prove.
A course may require students to compare generated claims with primary evidence, document revisions, identify weaknesses in machine output, defend decisions orally, or demonstrate an underlying skill independently before using AI assistance. In other cases, the educational purpose may require unaided work from beginning to end.
That distinction should appear in the assignment instructions rather than remain an unwritten expectation.

Compact course-policy template​

AI use in this course
  • Allowed without disclosure: Brainstorming initial ideas and checking grammar, unless an assignment states otherwise.
  • Allowed with disclosure: Creating or revising an outline. Identify the tool or type of assistance used and explain how the output affected your work.
  • Prohibited unless specifically assigned: Producing the final analysis, argument, interpretation, code, or other work that the assessment is designed to evaluate.
  • Never enter: Student records, unpublished research, confidential institutional information, assessment materials, answer keys, or other protected data.
  • Retain when required: Prompt and output notes, relevant drafts, source checks, and a short record of revisions made after using AI.
  • When uncertain: Ask the instructor or designated academic owner before submitting the assignment. Technical availability does not constitute academic permission.
Departments can adapt this template to disciplinary needs, but each version should preserve the same categories: permitted use, disclosure-required use, prohibited use, protected information, recordkeeping, and an owner for questions.

Timeline​

2024 — DEC’s first global student survey placed overall AI adoption closer to 86 percent, indicating that student use was already widespread.
2025 — Faculty intent to use AI in teaching in the United States and Canada stood at 76 percent.
2026 — The DEC AI in Higher Education Global Survey reports 88 percent global student adoption. North American faculty intent is reported at 67 percent, while only 29 percent of students worldwide and 17 percent in the United States and Canada believe instructors are equipped to guide them.
The timeline indicates modest growth in adoption from an already high base alongside unresolved questions about guidance and educational value. Institutions should now measure progress through course clarity, assessment validity, student competence, data protection, and confidence in academic guidance—not merely the number of users or accounts.

Faculty Training Has Not Yet Produced Broad Student Confidence​

Sixty-four percent of faculty worldwide report completing AI literacy training. That is an important institutional input, but it sits beside the much lower share of students who believe instructors are equipped to guide them.
DEC’s figures do not explain the difference. Training may vary in length, depth, disciplinary relevance, and connection to classroom practice. Faculty may also possess knowledge that is not visible to students because it has not been translated into assignment instructions, demonstrations, feedback, or consistent course policies.
Completion is therefore an incomplete measure. An institution can count workshop attendance, module completion, or distribution of a guidance document. Students encounter the result when they ask whether a particular use is allowed, challenge an incorrect output, disclose assistance, or receive different answers in different courses.
Faculty development should connect technical literacy to academic responsibilities:
  • Designing assessments that distinguish independent from assisted performance.
  • Establishing discipline-specific standards for verification and attribution.
  • Handling student, research, and institutional data appropriately.
  • Preserving accessibility and equitable participation.
  • Explaining disclosure and recordkeeping expectations.
  • Responding consistently to suspected misconduct.
  • Directing technical, privacy, and policy questions to the correct institutional owner.
Central governance can establish common definitions and minimum safeguards. Academic departments must determine how those safeguards apply to programming, design, medicine, law, history, language study, laboratory work, and other fields. A single feature-based policy cannot adequately express every discipline’s learning objectives.

Assessment Is Where Institutional Readiness Becomes Testable​

Fewer than three in ten students believe their assessments reflect the skills needed in an AI-shaped workplace. That finding goes directly to the value students expect from a degree.
Assessment states what competence means in operational terms. If students do not see a relationship between assessed work and future practice, universities need to examine both the design of the assessment and how its relevance is communicated.
The response should not be to insert AI into every task. Workplace readiness includes knowing when to use assistance, when to work independently, how to inspect a result, and when automation introduces unacceptable risk. Different professions and disciplines will set those boundaries differently.
A defensible assessment strategy tests both forms of competence:
  1. Independent competence: Can the student explain foundational concepts, perform essential operations, and exercise judgment without AI assistance?
  2. AI-assisted competence: Can the student use an allowed tool effectively, verify its output, protect sensitive information, document assistance, and accept responsibility for the final result?
  3. Transfer and defense: Can the student explain decisions, respond to questions, and apply the underlying knowledge in a new context?
Process evidence can help. Draft histories, source notes, oral defenses, supervised work, iterative feedback, practical demonstrations, and reflective explanations can show how a conclusion was reached. None is a universal solution, and each has workload, accessibility, and scalability implications. A combination selected for the course is more useful than attempting to infer authorship solely from the surface characteristics of a finished submission.
As a matter of analysis, assessments built primarily around generic take-home products may become harder to interpret when students have access to increasingly capable assistance. Universities should respond by making reasoning, verification, and independent competence more visible—not by assuming that any one detection or enforcement method can restore certainty.

Regional Anxiety Requires Different Operational Responses​

DEC’s regional findings show why common governance principles need local and course-level implementation. In the United States and Canada, 73 percent of students fear classmates are misusing AI to get ahead. In APAC, half of students expect AI to shrink opportunities in their field, compared with 41 percent worldwide.
Those concerns call for different responses. A student worried about unfair advantage needs consistent rules, credible assessment, and confidence that standards apply across comparable courses. A student worried about employment needs curriculum mapping, career guidance, and a clear explanation of which human and AI-assisted capabilities the program intends to develop.
In APAC, 57 percent of faculty say they are excited about AI and believe it can make learning more effective. That reported enthusiasm coexists with elevated student concern about future opportunities. The survey does not establish why faculty and student outlooks differ, but institutions should address both rather than assume enthusiasm about teaching resolves anxiety about employment.
EMEA offers another contrast. Student adoption stands at 85 percent, while 48 percent fear peers are misusing AI to gain an advantage. The corresponding integrity-concern figure is higher in North America. The partial data shows that high reported adoption can coexist with different levels of concern, but it does not provide a comprehensive explanation for the regional difference.
Latin America records the highest specified adoption figure at 92 percent. Institutions operating in such an environment should assume AI is already part of many students’ study practices and focus policy on learning purpose, access equity, verification, disclosure, and responsible handling of information.
The regional findings support a layered approach: common institutional safeguards, department-level interpretation, course-level permissions, and assignment-level instructions.

Purpose-Based Permission Provides More Clarity Than a General Rule​

A blanket ban is easy to state and may be appropriate for particular tasks. It is not sufficiently precise as the sole policy for an entire institution.
Some learning activities require unaided practice. Some assessments must establish that an individual can perform a task independently. Some AI services may be inappropriate because users could expose confidential, personal, proprietary, licensed, assessment-related, or research-sensitive information.
Other uses may support the educational purpose without replacing it. Brainstorming, grammar review, accessibility assistance, translation, outlining, explanation, or code review may be acceptable in one context and prohibited in another. The relevant question is whether the assistance preserves what the task is designed to assess.
The stronger model is purpose-based permission. Each course or assessment should state:
  • Why the task exists.
  • What competence it measures.
  • Which forms of assistance preserve that purpose.
  • Which forms of assistance would substitute for the student’s required work.
  • What disclosure and evidence must accompany allowed use.
  • What data cannot be submitted.
  • Who can authorize an exception or resolve uncertainty.
“AI use” is too broad to function as a complete policy category. It can describe correcting grammar, generating an outline, translating text, explaining a concept, writing code, producing a draft, fabricating a source, or completing an entire assignment. Rules become more credible when they distinguish among those activities.
Precision is not permissiveness. Institutions can be stricter about uses that undermine learning while giving clearer instructions for uses that support it.

Campus IT Must Treat AI as a Governance Boundary​

For WindowsForum readers and campus technology teams, the survey’s trust problem has a direct operational payoff. AI access may occur through managed Windows devices, institution-provided or personal accounts, browsers, extensions, learning platforms, mobile devices, and features embedded in productivity software, including Microsoft 365 environments.
The key distinction is between technical availability, institutional approval, and academic permission.
A feature may be accessible on a managed device without being approved for protected data. A service may be institutionally licensed without being permitted for a specific assignment. A tool may satisfy a technical requirement while raising unresolved academic, privacy, records, accessibility, procurement, or research-governance questions.
Campus IT should not be expected to decide whether AI-generated material is acceptable in a dissertation, laboratory report, examination, or programming assignment. Those decisions belong to academic owners. IT should control accounts, configuration, service inventory, access, security boundaries, and technical support while maintaining a reliable path to the offices that own academic and data policy.

Managed accounts and licensing​

Institution-managed accounts can provide clearer support and governance than personal accounts, but access must not be presented as universal permission. Universities should define:
  • Who qualifies for an account or license.
  • Which services and embedded features are institutionally approved.
  • Whether personal accounts may be used for university work.
  • What happens to prompts, outputs, and account data when a user leaves.
  • Which retention and deletion rules apply.
  • Whether different populations receive different features or service levels.
  • Where users can find current terms and support boundaries.

Browser and extension exposure​

AI may enter the environment through browser extensions or integrated features rather than a separately installed application. Device inventory and application controls should therefore account for extensions, add-ins, plug-ins, and embedded interfaces.
The objective is not merely to list products. Administrators need to understand where users can send text, files, screenshots, web content, or selected data outside the immediate application context. Where visibility is incomplete, policy should acknowledge the limitation rather than imply comprehensive technical control.

Data classification​

Users need specific prohibited-data categories, not a generic warning to “avoid sensitive information.” The institution should connect AI guidance to its existing data-classification model and provide recognizable campus examples.
At minimum, policy should address student records, unpublished research, assessment materials, answer keys, confidential personnel information, restricted institutional communications, credentials, regulated data, licensed content, and information covered by contractual obligations.
An approved institution-managed alternative should be identified where legitimate work requires AI assistance. Telling users not to use external services is less practical when no supported route exists for an approved use case.

Support-desk boundaries​

Service-desk staff will receive questions that cross technical and academic boundaries. They may be able to answer whether a feature is enabled, which account is active, whether an extension is installed, or where retention rules are published. They should not improvise answers about authorship, disclosure, misconduct, or assignment permission.
A documented escalation workflow should distinguish among:
  • Account and licensing issues.
  • Windows, browser, extension, or application configuration.
  • Security and privacy review.
  • Data-classification questions.
  • Records and retention questions.
  • Accessibility concerns.
  • Procurement and contract questions.
  • Research-governance questions.
  • Course and assignment permissions.
  • Academic-integrity disputes.

Action checklist for admins​

  • Inventory approved AI services and embedded features. Map institution-managed AI access across Windows endpoints, browsers, extensions, Microsoft 365 and other productivity environments, learning platforms, mobile access, and centrally licensed services.
  • Record ownership for every service. Identify the technical owner, contract owner, security reviewer, privacy owner, records owner, accessibility contact, and academic-policy contact where applicable.
  • Publish prohibited-data categories. Use the institution’s existing classification framework and give concrete examples such as student records, unpublished research, assessment materials, answer keys, credentials, personnel information, and contract-restricted content.
  • Identify approved institution-managed alternatives. For legitimate academic or administrative use cases, tell users which supported service or workflow is available instead of leaving them to choose an external tool.
  • Define account and licensing rules. State who receives access, whether personal accounts are permitted for institutional work, how identity is managed, what happens when affiliation ends, and where users can report missing or inconsistent access.
  • Define retention and deletion expectations. Explain what users should retain for academic disclosure, what the institution retains for operational purposes, and which office answers records questions.
  • Separate access from permission. State plainly that an enabled or institutionally licensed feature is not automatically authorized for every course, assessment, dataset, or research activity.
  • Route assignment questions to academic owners. Direct questions about allowed use, authorship, disclosure, and assessment requirements to the instructor, department, program, or designated academic-policy office.
  • Create a service-desk decision tree. Give frontline staff approved response language, ownership contacts, escalation criteria, ticket categories, and expected handoff procedures.
  • Document urgent escalation paths. Define how staff should respond when a user reports possible exposure of protected data, unpublished research, assessment content, credentials, or other restricted information.
  • Coordinate policy changes with technical changes. Before enabling a new feature or changing a license, confirm that privacy, security, records, accessibility, support, communications, and academic owners have reviewed the user impact.
  • Review browser and extension controls. Determine what can be inventoried or managed on institutional devices and clearly communicate where controls do not extend to personal devices or accounts.
  • Provide reusable course-policy language. Make the compact template available through syllabus tools, learning platforms, faculty-development materials, and support knowledge bases.
  • Test the escalation workflow. Use sample questions to verify that a student or faculty member receives a consistent answer without being repeatedly transferred between IT and academic offices.
  • Measure outcomes, not only deployment. Track clarity of guidance, response consistency, policy exceptions, reported data exposures, faculty readiness, student confidence, and assessment redesign—not just license counts or feature activation.

The Next Measure of Progress Is Institutional Clarity​

The Digital Education Council’s figures describe a university sector in which student AI use is common but structured educational value remains limited. The central problem is no longer access. It is whether institutions can make expectations understandable and competence visible.
The strongest response is a connected operating model:
  1. Central governance defines data, identity, security, privacy, records, accessibility, and procurement boundaries.
  2. Academic leadership defines common expectations for integrity, disclosure, and independent competence.
  3. Departments translate those expectations into disciplinary practice.
  4. Courses state purpose-based permissions.
  5. Assignments explain allowed assistance, prohibited substitution, disclosure, and required process evidence.
  6. IT manages approved services, accounts, Windows and browser exposure, and technical support.
  7. Service desks escalate academic questions rather than answering them by improvisation.
  8. Assessment measures both unaided knowledge and responsible AI-assisted performance where appropriate.
This approach does not require every instructor to embrace every AI use. It requires every student to receive a clear answer about the work being assessed.
DEC’s 88 percent adoption figure shows that the tools are already part of student practice. Its 29 percent instructor-confidence figure shows that access has not produced confidence in guidance. The 5 percent transformation figure shows that widespread use has not automatically translated into perceived educational change.
Universities should treat those results as a mandate for specificity. The next phase will be decided in syllabus language, assignment instructions, assessment design, managed-account rules, browser and extension controls, data-classification guidance, and support-desk escalation procedures.
The institutions that respond best will not be those that merely enable the most features or publish the strictest general statement. They will be those that can tell a student, instructor, researcher, or administrator—clearly and before a problem occurs—what is allowed, what is prohibited, what must be disclosed, what information must remain protected, and who has authority to decide.

References​

  1. Primary source: NewsGhana
    Published: 2026-07-12T11:37:07.971290
  2. Related coverage: gna.org.gh
  3. Related coverage: news.gallup.com
  4. Related coverage: justoglobal.com
  5. Related coverage: uew.edu.gh
  6. Related coverage: lemonde.fr
 

Back
Top