Writing provenance and evidence infrastructure

Verify authorship with evidence.

Not a detector’s guess: a consented, sealed record of how work was written, so universities can verify authorship and administer AI-use policies, and anyone can check it.

✓ Evidence, not a detector score✓ Tamper-evident, checkable by anyone✓ Limits stated, people decide
History_essay_draft.docx Recording

The railway did more to reshape the nineteenth-century town than any act of parliament.

By 1851, more than half of the population lived in towns, a figure I compare with the parish records in the section that follows

Bibliography to follow…

Typed Pasted Automated Untracked◆ SEAL READY
Process
not output
Evidence
not a guess
Both sides
protected
Consent
not surveillance

Choose yours.

Schools and universities

Authmarks for Education

Writing provenance and evidence infrastructure for universities: verify authorship, administer AI-use policies and manage academic integrity risk with consented process evidence, and give students a fair way to show how they worked.

Teams and professionals

Authmarks for Business

Verifiable authorship and compliance records an auditor can check, priced per seat. The writer sees and owns their full record and shares it with clients and regulators.

The institution

Verifiable process evidence for integrity reviews and appeals, with its limits stated and less reliance on detector scores.

The student

A way to show their own work. Recording is off until they allow it for a document.

The business

Verifiable authorship, and records the writer can see, share and an auditor can check.

The verification

A tamper-evident seal anyone can check, with a named person who attested.

A detector’s guess puts both sides at risk.

Detectors read finished text and guess a probability it was machine-written. When the guess is wrong, an honest student carries the accusation, and the institution has to defend a probability in a hearing or an appeal. Rewriting a finished draft changes what the detector reads, so the guess does not get better under scrutiny. An integrity decision needs a record of how the work was written.

The authorship verification category includes output detectors that score finished text and writing-replay tools that record an edit log. Authmarks is a third approach: record the process as it happens, with consent, have a named person attest, and seal a record anyone can check.

Guessing after the fact

A score you have to defend

Statistical detectors are probabilistic: they produce a score, not a record anyone can check. A wrong score can lead to a false accusation, and detectors get less useful as writing tools get better.

The Authmarks approach

A record made as the work is written

Record the writing process while the work is created, then seal it into a tamper-evident record anyone can check, with a named person attesting before sealing. A reviewer reads what happened; the decision stays with people and the institution’s own policy.

One record that protects both sides.

An integrity matter has two parties, and both are exposed when the evidence is a guess. Authmarks gives the institution verifiable evidence, with its limits stated, for a review or an appeal, and gives the student a fair way to show how the work was written. The record states what was observed. People decide, under the institution’s own policy.

For the institution

Evidence a reviewer can verify

Due process rests on evidence both sides can examine. A sealed record of the writing process is that evidence, and it does not depend on a detector’s guess.

  • Process evidence for integrity reviews and appeals, instead of a detector score
  • A labelled history of each submission: typed, pasted, dictated, automated, or unknown
  • Text the record did not see is marked unknown, never filled in
  • A custody trail and the author's signed declaration sealed into every record
  • Retention set to match your records policy
  • LMS integration through LTI 1.3
  • Legal hold, and a chain-of-custody case file with a SHA-256 manifest
  • Institution-owned records that stay when a teacher leaves
  • Integrity-office case workflow: second reviewer, appeal and case record

Authmarks for Education →

For the student

A way to show your own work

A student who wrote their own work should not have to prove a negative. With a record, an honest writer can show a reviewer how the work was written.

  • Recording is off until the student allows it for a document, and can be paused
  • The student sees their recording status and signs an AI-use declaration before the record is sealed
  • Honest work has its own process evidence for a reviewer to weigh
  • A detector score no longer has to be answered with memory and drafts alone
  • Labels are observations for a person to read, never a finding of misconduct
  • The detailed evidence is for their teachers, so it cannot be used to game the record
  • A free account: the extension, the desktop app and the editor

If you have been accused →

Where did this paragraph really come from?

A pasted paragraph rarely starts where it lands. It may have been copied from an article into a notes file on Monday and pasted into an essay on another computer on Thursday. Source lineage shows that path, one step at a time, back to the earliest place the copy was witnessed.

Source lineage
Follows copied text back to its original source, across apps, devices and days, and shows each step, marking which steps Authmarks verified itself and which a device reported.
Character-level lifecycle
Every character in the sealed text carries a labelled source (typed, pasted, dictated, inserted by a tool, or unknown), followed while recording was on from the moment it arrived, through every edit and move, to the seal.
Source lineage3 witnessed steps · earliest first
  1. Journal article on a library databaseReported by the device
    Browser, laptop · Copied · Monday 09:14
  2. Research notesReported by the device
    Word desktop app, laptop · Pasted 09:15, copied again · Wednesday 16:40
  3. Changed between these steps while recording did not see it: 38 characters, shown as a gap
  4. History essay, the assignmentVerified by Authmarks
    Google Docs, library computer · Pasted · Thursday 19:02

Illustration only, not real data.

The limits, stated

  • A step that a device reported and Authmarks could not check itself is labelled as reported, never presented as verified.
  • When text was changed between two steps and recording did not see the change, the timeline shows a gap. Those characters are not credited to the source, and not to the writer either.
  • A source that was never witnessed is never named. Pasted text with no witnessed copy is shown as pasted, source unknown.
  • Copy sources are recorded only when the organisation turns them on and the writer agrees. Copied text stays on the device unless it matches what is pasted or typed into a recorded document.
  • Lineage is an observation for a reviewer to weigh. It never decides anything by itself.

Patent-pending methods: the methods behind source lineage and the character-level lifecycle are covered by provisional patent applications, so we describe what they show, not how they work.

Four steps. One record a reviewer can verify.

From the writing to a record an instructor, an integrity panel or a client can check, without leaving the document you already write in.

1

Capture with consent

Recording starts only after explicit, document-level approval — on every surface. Off by default, revocable anytime.

2

Classify & verify

The record shows how the writing arrived while recording was on — typed, pasted, suggested, or untracked. It never reduces the document to a single score.

3

Review & attest

Authors or designated reviewers confirm accountability before high-trust outputs. A named person stays in the loop.

4

Seal & verify

A sealed record anyone can check. The fuller writing record stays with people the owner authorises.

One seal. Every place you write.

Authmarks witnesses writing wherever it happens. Every surface feeds the same sealed record — one record, one attestation, one public check.

Browser extension

Google Docs & Word, in the browser

One extension witnesses writing in both editors — the tools people already use, with nothing moved and nothing re-formatted.

Native add-ins

Inside Word and Google Docs

A native add-in for Word and an add-on for Google Docs will bring the record into the editor itself — no browser extension required. Coming soon.

Authmarks Write

Our own editor — desktop and web

A native desktop app and a web writing room with its own document drive, live collaboration, and the capture record built in from the first keystroke.

Phone app

Writing on your phone

A phone app for writing is coming soon.

Liveness signals

Physical input, not injected text

Typing-rhythm analysis and voice-matched dictation generate signals about whether physical input, not script injection, produced the text — signals for a reviewer, not a verdict.

Public verify

Anyone can check the seal

No account needed. Anyone can check a sealed record at authmarks.com/verify. The cryptographic check verifies our signature is intact — it does not depend on your account or ours.

Ask one character ten questions.

A sealed record should be able to answer these, in plain language.

01
Which part of the text?
The record follows the writing, not a single score for the whole draft.
02
Who typed it, per person?
Named authorship, with co-authors attributed where they signed in.
03
When was it written?
The record keeps time with the writing.
04
How did it arrive?
Written in the session, brought in, suggested, or not witnessed. The label is for a reviewer — never a verdict.
05
Was a person writing?
The record is about human effort. It is not a claim that every possible way of producing text will be identified.
06
What about text that was removed?
The record does not pretend unseen or removed work was never there.
07
What about text that replaced other text?
Replacing a passage is part of the record, not a fresh blank page.
08
Confidence and evidence?
Untracked regions are marked untracked — never silently attributed to a human.
09
Was consent on?
Explicit, per-document, revocable — the consent state is recorded with the session.
10
Sealed, and checkable?
Once sealed, a third party can check that the record still matches what was sealed.

The methods behind the record are patent-pending, which is why this page describes what the record answers — not how it is produced.

Written. Reviewed. Sealed.

A person writes — in Docs, in Word, or in the Authmarks editor. A named person stands behind the record. Then it is sealed, so a third party can check that it still matches.

While writing
The work is witnessed

Recording is on only because the writer allowed it for that document.

Before seal
A named person attests

The author, or a reviewer they choose, accepts responsibility for the record.

Sealed
The record can be checked

After sealing, someone can check that the record still matches what was sealed.

Illustration only.

Detectors are being switched off. The need is not.

Institutions are switching detectors off after false positives and contested hearings — but they still have to show who did the work.

~6,000 misconduct cases

Australian Catholic University reported around 6,000 academic misconduct cases in 2024, with roughly 90% AI-related; cases relying on detector-only evidence were dismissed.

ABC News · 9 Oct 2025

WSU cancelled AI detector

Washington State University cancelled its AI detector in February 2026; about one-third of related hearings concluded “not responsible.”

WSU provost memo

94% of UK students

Ninety-four percent of UK students report using AI in assessed work.

HEPI 2026

Curtin disabled detector

Curtin University disabled its AI detector from 1 January 2026.

Curtin University

Institutions still have to show who did the work, fairly. A record of the writing process is evidence both sides can examine in a review or an appeal. Authmarks connects to Canvas and other LMS platforms via LTI 1.3, and students can start with a free account today. See how institutions get started →

Provable authorship, records an auditor can check.

For organizations and the professionals inside them, anywhere a document’s authorship has to survive scrutiny. The writer sees their own full record, a named person stays accountable, and a sealed record can be shared with a client or a regulator who checks it themselves. Authmarks for business →

Enterprise & regulated industries

Compliance & accountability

A record of human review for regulated content, of the kind auditors and Article 50 transparency duties ask about, captured as the work is done.

Media & publishing

Editorial transparency

Show how content was produced and reviewed before publication — the human-oversight record regulators increasingly expect.

Consulting & agencies

Verified deliverables

Hand clients work with a verifiable record of how it was produced — a differentiator when anyone can generate a polished draft.

Provisional patent protection.

The methods behind the capture, the record, and the seal are patent-pending.

Status

Patent-pending methods

The capture, source lineage, fusion and sealing methods are covered by provisional patent applications.

Access

Start free

A free plan is available — sign in with Google and start sealing your own work. Institutions and teams write to sales@authmarks.com.

In the browser

Google Docs & Word

One extension witnesses both editors. A named person attests.

Beyond the browser

The desktop app

Our free desktop app witnesses typing and copy-paste on the computer, keeping key text only in programs where a document can be. Native add-ins are coming soon.

Every character, accounted for.

Authmarks classifies tracked writing by category and keeps untracked text explicit — so reviewers can assess process integrity without reducing the work to a simplistic “AI / not AI” verdict.

Human-typed

Written by a person during the session.

Pasted

Brought in from outside the session.

Robotic / automated

Not written by a person at the keyboard. A label for review, not a verdict.

Programmatic

Inserted by software rather than typed.

Suggested / autocomplete

Accepted from a suggestion while writing.

Dictated (voice-checked)

Spoken into the document; the recording is checked, against the writer’s own voice once they have set it up.

AI tool

Grammarly or Gemini, when the change is witnessed as coming from the tool.

Co-author

Written by another person recording the same document.

Unknown / untracked

No recorded provenance — never silently attributed to a human.

The verification underneath the record.

A record only helps if nobody has to take it on trust. Underneath every Authmarks record is a seal built on open standards, so an integrity panel, a client or a regulator can check it for themselves.

Integrity

Tamper-evident

The writing events are hash-chained as they arrive and the finished record is sealed with a C2PA signature. A change after sealing shows up as a failed check.

Authenticity

Who and when

Each seal names the author who signed the declaration, chains later reviews to it, and carries an RFC 3161 time-stamp of when it was signed.

Chain of custody

Where the evidence came from

The seal records which connections submitted the evidence, over what period, and any mismatch between the signed-in account and what a device reported.

A valid seal shows the record has not changed since it was sealed. It does not decide what happened; that is for the people reviewing it. Read about the evidentiary standards →

A named person takes responsibility — before anything is sealed.

This is the core of what makes an Authmarks record trustworthy. Before a session can be sealed, a person reviews the work and accepts responsibility for it — either the author reviewing their own work, or someone they invite to review it. Authmarks records who that person is and that they attested, and the seal stays locked until they do. It’s how the record carries clear editorial responsibility, in line with EU AI Act-aligned principles of keeping a natural person in control wherever AI contributes.

Step 1

Finish the draft, open review

When the writing is complete, open Human review from the session before sealing. The seal is gated behind this step.

Step 2

Self-review, or invite a reviewer

Two paths, one principle. Review your own work and stand behind it, or send an invite so a second named person reviews it and takes responsibility. Either way, accountability has a name attached.

Step 3

Confirm responsibility & add a note

The reviewer confirms they’ve reviewed the work and accept responsibility — accounting for any AI or automation involved — and can leave a note for context.

Step 4

Seal unlocks

Only once review is complete does the seal unlock — so the final, verifiable record always carries a human who stands behind it.

A record you can check, not just take on trust.

To record how work was written, Authmarks has to process the writing it records. The point is not to hide it from us; it is to make the result something a reviewer can check, while collecting little and leaving the writer in control of recording.

Tamper-evident by design

Each sealed record can be checked by a third party. A change after sealing is visible as a failed check. The fuller writing record stays with people the owner authorises.

Consent-first & minimal

Recording is explicit and per-document. Nothing is recorded until you allow it for that document. You can turn recording off.

Retention that matches the record

Unsealed session telemetry is short-lived by default. Sealed provenance may be retained for verifiability, legal, contractual, or anti-fraud reasons. In-region hosting and organisation-held keys are available as enterprise options.

Built for accountability, in the tools people already use.

Institutions are moving away from detector scores and toward evidence they can explain in a review or an appeal. For business, since 2 August 2026, AI-generated text published to inform the public must be disclosed, unless a person reviewed it and holds editorial responsibility. Authmarks’ named attestation is a record of that review. For generative systems already on the market before that date, Article 50(2) machine-readable marking has a grace period to 2 December 2026.

Article 50, live
Transparency duties apply from 2 August 2026; named human review is the exception Authmarks records.
Start free
A free plan is available — sign in with Google. Institutions add the workflow layer on top.
Docs · Word · beyond
Browser extension for Docs and Word and the desktop app available now. Native add-ins are coming soon.

Embed the record where work already happens.

The sealed record lives with the document. From there, a partner can surface it in an e-signature workflow or a learning system.

Built to partner requirements

LMS platforms such as Canvas connect today via LTI 1.3. REST API integrations are scoped with partners. The capture surfaces already span Google Docs, Word, the desktop app, and our own editor; deeper integrations follow the engagement.

  • Keep the sealed record with the document
  • Hand off to e-signature or LMS review flows
  • REST API shaped to your security and retention model

Start with a free account.

Teachers start free with one class. Businesses get a 14-day trial of Pro or Team with no card. Institutions: one agreement covers every course.