From the Student Success edition of October 8, 2026
Coventry Early Student Support AI flags attendance and Aula activity for staff outreach after evaluation on more than 9,000 student records
Coventry University (Professor James Brusey, Research Centre for Computational Science and Mathematical Modelling; Andrew Turner, Vice-Provost and Deputy Vice-Chancellor Education) · Higher education student success / early alert, retention and advising support · United Kingdom (Coventry University)
- Publisher
- Coventry University News
- Original publication
- Coventry University news dated Wednesday 7 October 2026
- Source retrieved
- 2026-10-09
What happened
Coventry University's Early Student Support project uses AI to analyse attendance records and activity on Aula, the university's learning platform, so staff can spot potential issues sooner. Led by Professor James Brusey and delivered through the AI Adoption Lab, the work has been evaluated using more than 9,000 student records across the first two teaching blocks of 2025-26, with additional historical datasets under review. Students are not contacted by AI; when the system identifies someone who may need support, a staff member reaches out to discuss circumstances and help. Vice-Provost Andrew Turner said the technology is not there to replace people or make decisions about students, and that staff remain responsible for understanding circumstances and determining support. Brusey described the project as early-stage with encouraging initial results but did not publish precision, recall, fairness or retention-effect figures in the article.
Why it matters
Dated 7 October 2026 and not in the archive at check_sources, it is a concrete HE retention architecture: LMS and attendance signals, human-only outreach, and an explicit non-decision role for AI. Useful contrast to tutoring tools that act directly on students.
Evidence and measured results
University news with named leaders; stated evaluation on more than 9,000 student records in teaching blocks 1–2 of 2025-26; process description of staff-only contact. No published performance metrics or outcome deltas in the article.
Limitations and uncertainty
Institutional news, not an independent evaluation; 'encouraging' results without effect sizes; early stage; UK setting may limit transfer of data-protection and advising models.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-09; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Advising teams cannot scan attendance and LMS activity at scale, so at-risk students are contacted late or unevenly.
- Stakeholders
- Vice-provost or associate provost for student success
- Retention / advising leadership
- Success coaches
- Institutional research
- Data protection officer
- Discovery questions
- Who is allowed to contact a flagged student, and how soon?
- What data sources feed the model, and have students been notified?
- Which outcomes will count as success besides model accuracy?
- Value hypothesis
- Advisory early-alert scoring may focus limited adviser time earlier; Coventry has not yet published outcome effects.
- Potential engagement
- An early-alert design review: data inventory, human-in-the-loop workflow and evaluation plan on a pilot college.
- Unsupported claims
- That the Coventry tool improves retention
- That AI contact is unnecessary in all contexts
- That 9,000 records prove accuracy
Pre-sales engineering
Role takeaway
- Fit
- Universities with attendance and LMS activity data and staff ready to own outreach.
- Architecture and integration
- Batch or near-real-time scoring of attendance and LMS features into a staff-only work queue; no student-facing chatbot path from the risk model.
- Prerequisites
- Attendance and LMS data agreements
- Staff identity and case-management hooks
- Audit log of flags and actions
- Constraints
- Early-stage evaluation
- UK legal context differs from U.S. FERPA practice
- Risk of biased flags without fairness checks
- Security
- Restrict flag visibility to assigned staff, minimize retained features, and document lawful basis / FERPA school-official rationale.
- Proof of value
- Outreach completed within the target window
- False-positive burden acceptable to advisers
- Fairness audit across student groups before scale
Delivery
Role takeaway
- Work
- Stand up a staff-only early-alert queue, train advisers, and run a time-boxed pilot with progression measures.
- Dependencies
- Adviser capacity
- IR evaluation design
- Data protection approval
- Ownership
- Student success / advising owns outreach decisions; data science owns the model; DPO owns privacy controls.
- Skills and adoption
- Adviser training on interpreting flags without treating them as ground truth.
- Governance checkpoints
- Privacy review
- Fairness check on pilot flags
- Go/no-go after teaching block
- Acceptance criteria
- Zero automated student contacts from the model
- Documented owner and response SLA for each flag
- Pilot report includes outreach completion and next-term progression
- Risks
- Alert fatigue
- Stigmatizing contact
- Scaling before fairness and outcome evidence
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?
AI analyses attendance plus Aula engagement features to surface candidates for human follow-up; no automated student messaging or decisioning described.
Governance
Who approves, reviews and stays accountable for outcomes?
Keep early-alert AI in an advisory role with named staff ownership of outreach and support decisions; publish how students are selected and how to contest flags.
Security and privacy
What data, permissions and controls need testing?
Combining attendance and LMS activity is sensitive; the article does not detail retention, access controls or student notice, which campuses must specify before scale.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Staff capacity to hold supportive conversations is the scarce resource the tool is meant to focus, not replace.
Procurement
What should contracts, pricing and exit terms secure?
Buy or build early-alert features only with contractual human-in-the-loop requirements and auditability of flags.
Operating model
Which teams own the service once it runs?
Define who receives flags, expected outreach time, and how success coaches or advisers close the loop.
Publication history
- 2026-10-08Student Success · Issue 324 resources
Stable resource ID: coventry-early-student-support-ai-attendance-aula-20261007