See how the paper came together.
WriteSight is an add-in for Microsoft Word that records how a document was written, then gives faculty a clear view of the writing process. It is built for a conversation about the work, not a verdict about the student.
WriteSight is rolling out through university pilots. Add your email and we will reach out about bringing it to your course or program.
Live on Microsoft AppSource, granted per pilot. No cookies, no tracking, no list-sharing.
The faculty report: the writing process behind a paper, framed to start a conversation.
AI changed the question.
Faculty increasingly need to understand not only what a student submitted, but how the work came together.
AI detectors estimate that from the finished text alone. WriteSight takes a different approach: it shows the writing process itself, and leaves the interpretation with the educator.
How WriteSight works
Three quiet steps, from the first draft to the faculty report.
The student writes
Once the student is signed in, WriteSight records quietly inside Word while they draft. There is no separate app to open and no session to start by hand.
The process is recorded
How the document was built is captured as a tamper-evident record kept inside the document itself. It attests to the process, not to a copy of the writing.
Faculty read the report
The instructor opens a clear summary of the writing process, framed for a conversation. There is no score to accept or dispute.
What the report shows
The shape of the work
Writing sessions, active time, and the span from first draft to final, so a paper written over two weeks looks different from one produced in a single sitting.
Patterns worth a question
Steady revision, or moments like a large pasted passage, surfaced plainly as things worth asking about, never as proof of anything.
No integrity score
WriteSight never produces a percentage, a risk level, or an accusation. It gives you information to interpret, not a verdict to enforce.
Built for a conversation
The report is designed to open a discussion with a student about their process, where real learning about writing, revision, authorship, and academic integrity can happen.
Built for responsible institutional use.
Writing-process information helps faculty ask better questions: what changed between drafts, how a student approached revision, what explains a sudden shift in a document. The report supplies context; the educator supplies judgment. For a program, that is a steadier alternative to high-stakes decisions made from a single automated score.
No guilt scores
A consistent, process-informed approach across courses, with no automated risk numbers or accusations.
Minimal collection
WriteSight records the process, not the student's writing, and keeps that record with the document.
People stay central
Faculty interpretation and the conversation with the student remain the point. The tool informs; it never decides.
It records the process, not the paper.
WriteSight captures how a document was written, the rhythm of typing, pausing, pasting, and revising, as a tamper-evident record. That record is stored with the document rather than in a central repository, and it never includes a copy of the student's writing. WriteSight uses separate sign-in and licensing services to confirm access; those do not hold the prose or the process record. Faculty see the process behind the work, never a surveillance feed of the student.
Questions
Is WriteSight an AI detector?
No. WriteSight does not guess whether AI was used and never produces a score or an accusation. AI detectors estimate from the finished text alone; WriteSight takes a different approach and shows how the document was written, leaving the interpretation to the educator.
What does "tamper-evident" mean?
It means the record is designed so that changes to the recorded history can be detected rather than silently rewritten. That is what lets a reader trust that the process they are seeing is the process that actually happened.
What exactly does WriteSight record, and what does it not?
It records the shape of the writing process: session timing, typing and pausing, pasted passages, and revision over time. It does not record a copy of the text you write. The report is built from how the document came together, not from its contents.
Does WriteSight send any writing-process data to ScholarVera?
The writing-process record stays with the document and is not sent to ScholarVera. WriteSight uses account and licensing services to sign a user in and confirm access, and those do not contain the writing or the process record.
What does the faculty report contain?
A summary of the writing process: the number of sessions, active writing time, the span from first draft to final, a view of activity over time, and neutral observations such as a large pasted passage. It is framed to prompt a conversation, not to deliver a judgment.
What if a student writes offline, or in another application?
WriteSight records the work done in Word with the add-in signed in. Writing done in another application, or with the add-in turned off, is not captured, so the report reflects the drafting that happened in Word. That is a limit worth naming plainly rather than implying the record is exhaustive.
Can WriteSight be used in an academic-integrity process?
WriteSight provides process information that can inform a faculty member's questions and a conversation with a student. It is not designed to be standalone proof of misconduct and should not be treated as a verdict. The judgment stays with the educator and the institution.
Can students see their own record?
The current focus is the faculty view used in our pilots. A student-facing view, where a writer can share the process behind their work, is on the roadmap.
How do we get WriteSight?
WriteSight is live on Microsoft AppSource and is rolling out through university pilots, granted per participating course or program. Add your email above and we will reach out about a pilot that fits your setting.
Bring the process into the conversation.
WriteSight is in pilot studies with universities. Tell us about your course or program and we will be in touch.
Live on Microsoft AppSource, granted per pilot. No cookies, no tracking, no list-sharing.