From the Student Success edition of October 4, 2026
University of Victoria Studiosity trial: 49 of ~350 students used Writing Feedback; not recommended for general rollout
University of Victoria, Division of Learning and Teaching Innovation · Higher education academic support / AI-enabled formative writing feedback · Canada (University of Victoria, British Columbia)
- Publisher
- University of Victoria Learning and Teaching Innovation
- Original publication
- Final report PDF dated January 2026 (Fall 2025 pilot)
- Source retrieved
- 2026-10-05
What happened
In a Fall 2025 volunteer pilot across three courses (Commerce, Health Information Science, Education; about 350 students), 49 students used Studiosity's Writing Feedback and 24 used Study Assist at least once. Use clustered around assignment release and due dates and declined over the term. UVic concluded the tool was a poor pedagogical fit for general rollout but may suit writing-intensive courses with required draft–feedback–revision cycles, such as English as an Additional Language courses, when explicitly prescribed rather than optional.
Why it matters
Why now: the 30 Sep 2026 Georgia State/NISS post reports strong outcomes for the same platform. UVic's institution-run report is the counterweight: under optional, non-exclusive positioning, uptake was about 14% and episodic. Together they show that adoption design, not the tool, drives exposure.
Evidence and measured results
Vendor-supplied application analytics (3 Sep–11 Dec 2025), instructor survey, two short student surveys; not a controlled study; no learning-outcome analysis. Baseline: enrolled population of ~350.
Limitations and uncertainty
Small, self-selected instructor sample; three courses; descriptive only; Canadian context with in-house writing supports; students could use ChatGPT and other tools in two courses, diluting uptake.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Campuses buying AI writing feedback assume students will use it; optional deployments can see little sustained use.
- Stakeholders
- Teaching and learning center
- Writing and academic skills services
- Faculty in writing-intensive courses
- Procurement
- Discovery questions
- Which courses require multiple drafts of the same text?
- Will faculty prescribe the tool at a defined assignment stage?
- What competing GenAI tools are students permitted to use?
- Value hypothesis
- Targeted, prescribed use in drafting-based courses is more likely to generate sustained engagement than campus-wide optional access.
- Potential engagement
- Targeted pilot in one writing-intensive sequence (for example EAL) with prescribed draft stages and institution-owned usage metrics.
- Unsupported claims
- Campus-wide adoption
- Learning gains (not measured)
- Integrity benefits
Pre-sales engineering
Role takeaway
- Fit
- Formative writing feedback in courses with required iterative drafting.
- Architecture and integration
- LMS embed plus institution-owned export of per-stage usage linked to assignment submissions.
- Prerequisites
- Contractual access to granular usage data
- Assignment-stage tagging in the LMS
- Constraints
- Vendor analytics lack quality and outcome measures
- Concurrent use of other GenAI tools
- Security
- Limit draft retention and secure institutional rights to usage data.
- Proof of value
- Per-stage uptake among enrolled students
- Draft-to-draft change on a blind sample
- Comparison with prior-year grade distributions
Delivery
Role takeaway
- Work
- Redesign target assignments with a prescribed feedback stage, update syllabi, and monitor uptake termly.
- Dependencies
- Faculty assignment redesign
- Syllabus statements on tool scope
- Ownership
- Teaching and learning center with course instructors.
- Skills and adoption
- Students are taught when AI feedback helps and when to seek disciplinary or human feedback.
- Governance checkpoints
- Placement decision before purchase
- Mid-term uptake review
- Retarget-or-stop decision at term end
- Acceptance criteria
- Defined minimum share of enrolled students using the prescribed stage
- Sustained use beyond the first assignment
- Instructor-reported fit per course
- Risks
- Low uptake wasting license spend
- Deadline-only tactical use
- Displacement of human writing support
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?
Brightspace embed alone did not drive use; analytics captured counts and timing but not engagement quality or outcomes, so institutions need their own outcome linkage.
Governance
Who approves, reviews and stays accountable for outcomes?
Decide placement (prescribed stage in an assignment vs optional resource) before procurement; UVic recommends against positioning the tool as universal.
Security and privacy
What data, permissions and controls need testing?
Usage data came from the vendor; institutions should secure rights to granular usage data and limit draft retention.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Possible targeted value for EAL learners; low general uptake means equity benefits are not automatic.
Procurement
What should contracts, pricing and exit terms secure?
Price and scope pilots by targeted course, not campus-wide seats; require usage and outcome data access in contract.
Operating model
Which teams own the service once it runs?
Use targeted deployment in writing-intensive sequences with explicit draft stages and keep human writing support alongside it.
Publication history
- 2026-10-04Student Success · Issue 284 resources
Stable resource ID: uvic-studiosity-trial-final-report-20260130