From the Student Success edition of November 2, 2026
Penn pilots the Rumi writing-process platform with 17 instructors to make student AI use visible in take-home writing; faculty split on value and surveillance
University of Pennsylvania (Center for Excellence in Teaching, Learning, and Innovation); reported by The Daily Pennsylvanian · Higher education teaching, writing and academic integrity · United States (Philadelphia, Pennsylvania)
- Publisher
- The Daily Pennsylvanian
- Original publication
- The Daily Pennsylvanian, 1 November 2026
- Source retrieved
- 2026-11-03
What happened
The Daily Pennsylvanian reports (1 November 2026) that 17 Penn instructors teaching nearly 20 classes across the four undergraduate schools piloted Rumi this semester, a Google Docs-like writing workspace that lets instructors set guardrails on student AI use and see writing and revision history. Penn describes it as not an AI detection service; instructors can enable models such as ChatGPT, Gemini and Claude. CETLI's director calls it a cross-school, short-term experiment aimed at learning. A Wharton professor was unsure it would improve writing but expected it to make students think twice; a political scientist said it feels 'a little big-brothery' but gives confidence; a Middle Eastern Languages professor rejected such tools as easy to fool and associated with surveillance.
Why it matters
Shows institutions shifting from AI detectors to process-visibility tools for take-home writing, and the trust and surveillance trade-offs that student-success and teaching centres must manage.
Evidence and measured results
Interviews and statements from the teaching-centre director and four instructors; pilot scale stated; no outcome measures yet.
Limitations and uncertainty
Single-institution, one-semester pilot; no learning or integrity outcome data; vendor capabilities described only briefly.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-03; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Take-home writing is hard to trust under generative AI, and detectors are unreliable.
- Stakeholders
- Teaching and learning centre
- Writing programme leads
- Academic integrity office
- Faculty pilot participants
- Student government
- Discovery questions
- Which courses depend most on take-home writing?
- What evidence would you accept in an AI misconduct case?
- How will students be consulted in a pilot?
- Value hypothesis
- Interpretation: process visibility may preserve take-home assignments with less reliance on detectors, if students accept it.
- Potential engagement
- Design and evaluation support for a one-term writing-process tool pilot.
- Unsupported claims
- The tool improves student writing
- The tool prevents AI misuse
- Students broadly support process tracking
Pre-sales engineering
Role takeaway
- Fit
- Writing-process workspace integrated with the LMS; not a detector.
- Architecture and integration
- LMS single sign-on and gradebook links; optional instructor-enabled model integrations; storage of revision histories.
- Prerequisites
- Data-protection impact assessment
- Retention policy for revision data
- LMS integration
- Constraints
- Students may draft outside the tool
- Workarounds reported by faculty
- Third-party model terms vary
- Security
- Revision histories are sensitive student records; restrict access and define permitted use in conduct cases.
- Proof of value
- Instructor time spent reviewing histories
- Student-reported trust and burden
- Referral outcomes compared with detector-based cases
Delivery
Role takeaway
- Work
- Run and evaluate a cross-school writing-process pilot with clear data-use rules.
- Dependencies
- Faculty volunteers
- Vendor contract for pilot term
- Student feedback channel
- Ownership
- Teaching and learning centre.
- Skills and adoption
- Instructors need guidance on reading revision histories and discussing AI use with students.
- Governance checkpoints
- Data-use rules approved before launch
- Student consultation
- End-of-term scale-up decision
- Acceptance criteria
- Proposed: student and instructor survey at term end
- Proposed: documented rule on process data in conduct cases
- Proposed: instructor review time measured
- Risks
- Perceived surveillance
- Tool easily gamed
- Extra instructor workload
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?
Process-capture tools sit alongside the LMS and hold full revision histories, with optional integration of third-party models chosen by instructors.
Governance
Who approves, reviews and stays accountable for outcomes?
Pilots need stated evaluation criteria, student input and rules on how revision data may be used in misconduct cases.
Security and privacy
What data, permissions and controls need testing?
Revision histories and keystroke-level process data are sensitive student records; one instructor raised surveillance concerns.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed; process-tracking tools may affect students who draft offline or use assistive technology.
Procurement
What should contracts, pricing and exit terms secure?
Penn uses a short-term pilot route before school or university-wide adoption, which limits lock-in.
Operating model
Which teams own the service once it runs?
The teaching centre owns the pilot and feedback loop; instructors opt in course by course.
Publication history
- 2026-11-02Student Success · Issue 564 resources
Stable resource ID: daily-pennsylvanian-penn-rumi-writing-process-pilot-17-instructors-20261101