See how
writing happens.
EduWrite surfaces the full arc of a student's composition — drafting, revising, returning — so instructors can ground their judgment in what actually happened. No flags. No scores. No algorithmic suspicion. Just the process, made visible.
A look at the platform.
A short walkthrough of the platform — how process data gets recorded while students compose, and how it shows up for instructors during review.
Assessment has lost sight of the process.
When instructors only see a final PDF, the intellectual work that produced it becomes invisible. Research, drafting, revision, the slow return to a paragraph the next morning — none of it is part of the record.
Detection tools answered that gap with algorithmic suspicion: a score, a flag, a confidence interval. The result has been unreliable at best and harmful at worst — false positives, eroded trust, and a pedagogy increasingly organized around policing rather than teaching. EduWrite takes a different path. We surface the process and leave interpretation where it belongs — with the instructor.
Disputes without evidence
Integrity conversations get stuck in "prove it" loops. Neither faculty nor students have the record of how the writing actually came together.
Brittle detection
Algorithmic markers cannot reliably distinguish legitimate assistance from dishonesty. They produce suspicion as a default state, not as a considered judgment.
Invisible labor
Hours of real work — outlines abandoned, sentences reworked, sources wrestled with — leave no trace in a final document. Students who engage honestly have nothing to show for it.
How EduWrite works.
A lightweight integration that fits inside existing course workflows. No new platform to administer, no student surveillance, no instructor overhead.
01. Students write
Composition happens where it already does — in a familiar editor connected to the course. No new login, no lockdown environment.
02. Process is recorded
Composition events — bursts, revisions, pauses, returns — are captured server-side as a temporal record of the draft.
03. Instructors review
The process appears alongside the final draft as a visual playback and plain-language summary. Instructors interpret. EduWrite does not.
The writing metrics view.
Every draft generates a plain-language report of how it came together — drafting style, active time, revision behavior, paste events, pacing, and more. The data is surfaced without interpretation. What it means for a given assignment is the instructor's call, not ours.
Principles we don't flex on.
EduWrite is built on a small number of commitments that shape every product decision. When surfacing and interpreting come into conflict, we choose surfacing every time.
-
Present, don't prescribe
We surface data about the writing process. We do not label, score, or flag students. Interpretation stays with the instructor.
-
Record the text, not the person
No cameras, microphones, keystroke biometrics, or desktop monitoring. The record is of the composition, not the composer.
-
Disparate impact is a design concern
EduWrite does not flag students, score them for risk, or alert instructors about individual drafts. Features that direct scrutiny toward specific students carry disparate impact risks, regardless of how accurate the underlying signal is.
-
Process data belongs to the process
Writing records are used to support assessment in the course that generated them, not to train models or build cross-institutional profiles.
Foundations
EduWrite is grounded in decades of composition research on process-based writing and equitable assessment. The materials below explain the approach in more depth.
Why surfacing the writing process addresses what detection tools cannot — and why the distinction matters pedagogically.
ResearchA review of the compositional research that informs EduWrite's approach to surfacing writing activity.
PolicyOur commitments on retention, access, and the boundary between course-level data and everything else.
For InstitutionsWhat a pilot looks like at the department level — scope, timeline, support, and what we ask of partners.
Pilot EduWrite with your department.
We're working with a small number of composition programs to refine the platform in real courses. If your institution is thinking seriously about how to move past detection, we'd like to hear from you.