From the Campus Operations edition of October 15, 2026
Newcastle and Westminster join Southampton in dropping Turnitin as AI data-use terms, cost and weak value against generative AI drive UK contract reviews
UK universities and Turnitin (reported by Times Higher Education, syndicated by Inside Higher Ed) · University IT procurement and vendor data governance (assessment technology) · United Kingdom
- Publisher
- Inside Higher Ed / Times Higher Education
- Original publication
- Inside Higher Ed (from Times Higher Education), 15 October 2026
- Source retrieved
- 2026-10-16
What happened
Newcastle University will stop using Turnitin after the 2026-27 academic year, citing concerns about the company's end-user licence agreement and the potential use of colleague and student data for AI purposes from next year. The University of Westminster will retire the product when its contract ends in July 2027, citing confusion from multiple submission systems, a plagiarism checker it called largely ineffective against generative AI, and AI detectors that are probabilistic with a recognized risk of false positives. They follow Southampton. Aberdeen is reviewing use, Aberystwyth lets uncomfortable students use Blackboard tools instead, and Cambridge says it will not accept EULA changes affecting data privacy or intellectual property. Turnitin says it does not train a generative model or LLM but does train a classifier. The EULA change, planned for 7 July, has been postponed to September 2027, and Turnitin agreed to work with a UCISA representation group. Experts quoted say cost may be the deeper driver; FOI data show Southampton paid £87,621 (September 2024 to September 2025) and UEA £50,892 (April 2024 to March 2025).
Why it matters
Shows a vendor's change to AI data-use terms prompting contract exits and sector-level negotiation through an IT association (UCISA). For U.S. campus IT and procurement, it is a prompt to review licence terms of embedded tools for AI processing of staff and student data before renewals. The assessment-integrity side belongs to the student-success stream; this record covers the procurement and data-governance angle. Transferability: UK data-protection law and sector bargaining differ from U.S. practice. It follows an archived 5 October Birmingham item on the same EULA pause; this is a new source with new institutional decisions.
Evidence and measured results
Institutional statements quoted in reporting, a vendor statement, expert opinion and FOI cost figures. No analysis of the contract terms themselves, and motives (data, cost, value) are contested within the article.
Limitations and uncertainty
News report; institutions' motives are mixed and partly financial. The EULA text is not quoted. Turnitin prices vary by institution and are not public. UK-specific.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-15; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Institutions face vendor licence changes that may permit AI processing of staff and student data in tools they rely on.
- Stakeholders
- CIO
- Procurement and contracts
- Data protection officer or privacy office
- Academic integrity leads
- Student union or student government
- Discovery questions
- Which deployed tools have changed or proposed terms on AI processing of user data?
- When do key contracts renew, and what are the exit costs?
- What is the institution's negotiating position on AI training clauses?
- Is the tool still delivering value given current student AI use?
- Value hypothesis
- Interpretation: a structured review of AI clauses before renewal can avoid locked-in terms and inform keep-or-switch decisions.
- Potential engagement
- A bounded AI-clause review of the institution's most data-sensitive SaaS contracts, with renewal timelines and negotiating positions.
- Unsupported claims
- That Turnitin trains generative models on student work
- Savings from switching providers
- That U.S. contracts include the same terms
Pre-sales engineering
Role takeaway
- Fit
- Fits institutions whose VLE can handle submission and grading natively and add a separate originality service.
- Architecture and integration
- Standards-based integration of alternative originality tools into the VLE; export of historical submissions.
- Prerequisites
- Contract and integration inventory
- Archive and retention requirements for past submissions
- Alternative tool evaluation
- Constraints
- UK data-protection law in this case
- Contract end dates in 2027
- Mixed academic views on detector value
- Security
- Review vendor terms for AI processing, model training, data location and retention; require contractual limits rather than relying on vendor statements.
- Proof of value
- Contract clause review against institutional AI data rules
- Pilot of native VLE submission plus an alternative originality tool in one faculty
- Migration test for historical records
Delivery
Role takeaway
- Work
- Run a renewal decision process for the affected platform, with a transition plan if the institution exits.
- Dependencies
- Legal and procurement
- Data protection office
- Teaching and learning or academic integrity leads
- VLE platform team
- Ownership
- Procurement and the CIO own the contract decision; academic leadership owns integrity policy; the VLE team owns integration.
- Skills and adoption
- Staff need guidance on new submission workflows; procurement staff need AI-clause review skills.
- Governance checkpoints
- Data protection impact review of revised terms
- Executive or education committee decision
- Student and staff communication before any change
- Acceptance criteria
- Proposed: AI data-use clauses reviewed and position documented before renewal
- Proposed: no loss of access to historical submissions after transition
- Proposed: transition completed before contract end
- Risks
- Disruption to assessment workflows
- Loss of historical records
- Replacing one vendor's terms with similar ones elsewhere
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?
Universities are separating submission and grading (handled natively in the VLE) from optional originality tools, reducing dependence on one vendor. Replacing an embedded tool requires integration work and a transition plan.
Governance
Who approves, reviews and stays accountable for outcomes?
Vendor AI terms are being handled through sector representation (UCISA), education committees and executive boards. Cambridge's stated red line on privacy and IP changes is a model negotiating position.
Security and privacy
What data, permissions and controls need testing?
The core concern is potential AI processing of staff and student submissions under revised licence terms. The vendor distinguishes classifier training from generative-model training; institutions are not satisfied that this resolves the issue.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Staff ('colleague') data is named alongside student data in Newcastle's concern. Transition workload falls on academic and VLE staff. Accessibility is not discussed.
Procurement
What should contracts, pricing and exit terms secure?
Licence terms on AI processing are now a renewal criterion alongside cost and value. A sector body (UCISA) is engaging the vendor on institutions' behalf. FOI-disclosed costs give price reference points for UK institutions.
Operating model
Which teams own the service once it runs?
Institutions are moving functions back into core platforms (the VLE) and treating add-on tools as replaceable. Interpretation: this reduces lock-in but requires integration capacity.
Publication history
- 2026-10-15Campus Operations · Issue 385 resources
Stable resource ID: ihe-the-uk-universities-end-turnitin-contracts-eula-ai-20261015