From the Student Success edition of September 30, 2026
LMS traces from weeks 1–8 predict AI-assisted exam-cheating risk at 73.1% accuracy—for guidance, not discipline
Hacettepe University (Gökhan Akçapınar) · Higher education computing education / academic integrity analytics · Türkiye (public university; first-year Computer Education and Instructional Technology undergraduates)
- Publisher
- arXiv
- Original publication
- Submitted to arXiv 29 September 2026 (cs.CY); to be presented at ICETC 2026
- Source retrieved
- 2026-10-01
What happened
Among 52 first-year undergraduates in an Introduction to Programming course, 23 (44.2%) were labeled high-risk for AI-assisted cheating based on suspicious final-exam log behaviors (copy, focus-loss, right-click) in a proctored face-to-face exam. Using five features from 27 early-semester LMS/video candidates, Logistic Regression under LOOCV with fold-specific preprocessing achieved Accuracy 73.1% (Balanced Accuracy 0.718, AUC 0.760). Most stable predictors—course-module views, assignment submissions, and video-access days—were lower in the high-risk group. Authors frame predictions for timely academic guidance, not misconduct findings; labels are behavioral proxies, not verified AI use.
Why it matters
Offers HE student-success teams an early-warning pattern complementary to post-hoc homework detectors: thin early engagement may foreshadow integrity-risk behaviors, but only as outreach triggers with human judgment. Reinforces that analytics must stay outside automatic discipline pipelines.
Evidence and measured results
LOOCV classification on n=52 with exam-log-derived risk labels and early LMS/video features; feature selection via Mann-Whitney U per fold. Small single-course sample; proxy labels; preprint/conference paper.
Limitations and uncertainty
n=52; single course/country; high-risk label from exam-log proxies not confirmed AI use; 73.1% accuracy leaves substantial error; LOOCV optimism risk; preprint.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-01; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Integrity risk surfaces too late; campuses want early signals without automatic misconduct pipelines.
- Stakeholders
- student success
- academic integrity office
- CS/education faculty
- advising
- registrar/LMS owners
- Discovery questions
- Who receives early risk alerts?
- What outreach happens before any allegation?
- How will we revalidate on local LMS data?
- Value hypothesis
- Early LMS engagement alerts can trigger timely academic guidance when human-reviewed and policy-gated away from discipline.
- Potential engagement
- One-course shadow-mode early-warning pilot with advisor outreach scripts and accuracy audit.
- Unsupported claims
- Verified individual AI cheating from LMS score
- 73.1% portable accuracy
- Replacement for assessment redesign
Pre-sales engineering
Role takeaway
- Fit
- LMS-integrated early-alert services for programming or online-assessed HE courses.
- Architecture and integration
- LMS/video feature job → score service → advisor queue UI → no write path to conduct; audit log of views/actions.
- Prerequisites
- LMS API access
- advisor staffing
- local labeled validation set or proxy protocol
- Constraints
- proxy labels
- small-N source
- jurisdictional transfer
- Security
- Education-record minimization; role-based reviewer access; retention limits on proctoring artifacts.
- Proof of value
- Outreach completion rate
- False-positive review notes
- No misconduct cases opened from score alone
Delivery
Role takeaway
- Work
- Define guidance scripts, train advisors, run week-8 scoring, document non-punitive contacts, revalidate features.
- Dependencies
- LMS data steward
- course faculty
- advising capacity
- Ownership
- Course instructor with student-success advising; integrity office only on independent evidence.
- Skills and adoption
- Advisors deliver AI-use guidance and support without accusatory framing.
- Governance checkpoints
- Policy sign-off guidance-only
- threshold review
- end-term disparity audit
- Acceptance criteria
- Published guidance-only rule
- Human contact before any allegation
- Local performance memo
- Risks
- Stigma of low engagement
- Threshold gaming
- Cross-context model failure
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?
If building early alerts, score LMS engagement features in week 8, route to advisor/instructor outreach queues, and hard-separate from conduct systems. Calibrate thresholds for high recall outreach vs high precision escalation.
Governance
Who approves, reviews and stays accountable for outcomes?
Policy must state that LMS risk scores are guidance signals only; prohibit sole use for misconduct findings; require human review, student-facing AI-use guidance, and appeals. Local revalidation required before transfer from Türkiye programming context.
Security and privacy
What data, permissions and controls need testing?
LMS and exam-behavior traces are sensitive education records. Minimize feature sets, restrict reviewer access, avoid storing raw keystroke/focus logs longer than needed, and prevent vendor secondary use.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Low early LMS engagement may reflect work hours, disability, or access barriers—not cheating intent. Outreach must offer support resources and avoid deficit labeling; advisor workload is a real staffing cost.
Procurement
What should contracts, pricing and exit terms secure?
Prefer early-alert products with human-outreach workflows, explainable features, and contractual bans on automatic disciplinary actions. Require local revalidation clauses.
Operating model
Which teams own the service once it runs?
Operate early AI-integrity risk scores as student-success outreach, parallel to—but gated from—conduct processes; pair with assessment redesign and clear AI-use guidance.
Publication history
- 2026-09-30Student Success · Issue 243 resources
Stable resource ID: akcapinar-lms-early-ai-cheating-risk-20260929