Document Work Story

Capture how the assignment came together, not just the final answer.

Mark helps instructors ask a better question than "Was AI involved?" It helps show whether students worked through the assignment in a way you can review.

Request a pilot demo See how it works

Process over panic

Recorded development instead of a black-box score

Code

Recorded change activity

Writing

Progress over time

Math

Steps and explanations

Mark does not detect AI use. It gives instructors recorded development they can review with the student and interpret in context.

How students use Mark

For assignments where process matters, Mark gives students a focused workspace that creates a record over time.

Students work in Mark

Students complete the assignment in a focused workspace for code, writing, math, or other process-heavy work.

Progress is saved over time

Mark autosaves as students work. External paste and drag-and-drop are blocked, while students can reuse material copied within the Mark editor.

Instructors review the record

Instructors can preview read-only saved versions or download the assignment's currently saved participant work from one consistent snapshot, which can be quicker than retrieving files individually from the LMS. This snapshot reflects current work in Mark; each student's assignment ZIP separately carries current documents, participant-usable copies, and a signed, frozen work story for LMS submission.

Inside the instructor view

See the workspace at a glance, then review one student's recorded development.

In this simulated CPU Scheduling Lab, the workspace report identifies which students have started and which have changed-content history. An instructor can then open a student's Work Story for the timing, files, and estimated changes behind the summary.

Simulated demonstration data

8 change markers

3 documents

5 approximate periods

3 UTC days

Excerpt from a simulated workspace Work Story report showing progress and change marker summaries — Excerpt from a simulated workspace report. View larger

Excerpt from a simulated participant Work Story showing an overview and timeline across three documents — Excerpt from a simulated participant Work Story. View larger

Context without a verdict. The largest editor addition represented 23% of Nina's estimated editor additions, while 66% occurred after each document's first change marker. Mark reports that distribution without claiming it proves authorship or misconduct.

How to read a Work Story

Useful evidence starts with understandable measurements.

Change markers Changed-content saves received by Mark, not keystrokes or complete revisions.

Approximate editing periods Groups of change markers separated by gaps longer than 30 minutes, not exact working sessions.

Save-supported editing time An upper-bound estimate from merged two-minute windows preceding editor change markers, not total active working time.

Estimated changes Comparisons between consecutive saved versions, not counts of manually typed characters.

The instructor defines the process expected for the assignment. Mark does not decide what a normal process looks like; it provides recorded development for comparison with the assignment's intended workflow.

Records instructors can actually use

The AI-era assignment problem looks different across disciplines, but the teaching need is the same: evidence of process.

Code assignments

Review change marker timing and change patterns alongside the submitted code.

Writing assignments

Review saved progress patterns alongside the submitted writing and any reflection the assignment requests.

Math work

Review submitted steps and explanations alongside change marker activity.

Shared visibility

Students can inspect the same underlying work story while instructors can review current progress across a workspace assignment.

Reviewable records

Freeze the document work story into the signed internal record inside the assignment package so the exported work story remains understandable and portable.

Support the process

Give instructors recorded development they can use to encourage steady work and reflection.

Built to avoid overclaiming

AI detection tools can create false confidence and difficult student conversations. Mark focuses on process evidence that instructors can interpret in context.

Not a magic verdict Supports instructor judgment instead of replacing it.

Works across assignment types Useful for code, writing, math, and other process-heavy work.

Designed for fairness Gives students access to their own work story and keeps ambiguous browser signals separate from server records.

FAQ

Do students need to install anything?

No. Students only need a browser and internet access.

How long does routine pilot setup take?

After instructors and students can sign in, routine setup can usually be completed in minutes. Creating a workspace, adding a document assignment, and joining a workspace each typically take less than a minute. Institutional sign-in or domain approval may require separate coordination with an identity or IT contact.

Can we pilot Mark without Microsoft sign-in?

Yes. Mark can provide local password accounts when Microsoft organizational sign-in is unavailable. Local accounts are protected by an authenticator-app verification code.

What do students use?

Students select an available assignment within a Mark workspace and work in its focused editor. Progress is saved over time, external paste and drag-and-drop are blocked, and students can inspect their own work story.

What does the instructor review?

Instructors can review current progress across a workspace assignment and preview read-only saved versions from the live Mark workspace. Live history provides context but does not identify which version was submitted to an LMS. A submitted assignment ZIP contains the current documents, participant-usable copies, and a signed internal record with a frozen work story covering save-supported editing time, approximate editing periods, per-document development, saved-change estimates, and chronological change markers. Browser-reported editor activity is labeled separately and is not treated as proof of authorship or misconduct. The goal is to understand how the assignment came together, not only whether the final answer looks correct.

Does Mark measure exact active working time?

No. Mark reports an upper-bound estimate of editing represented by changed-content saves. It merges overlapping two-minute autosave windows, excludes assignment-package and version-history restores as well as time between those windows, and labels the result as save-supported editing time rather than exact active work.

Is this AI detection?

No. Mark does not detect AI use. It creates process records that help instructors interpret student work in context.

Need a clearer record of student work?

Tell us what kind of assignments you use and what makes reviewing student work feel uncertain.

Request a pilot demo