What is writing-process evidence?

Writing-process evidence is a record of how a document developed inside a captured environment, such as edits, revisions, timing and checkpoints. Its value depends on what was captured, whether the record can be verified and how carefully its limits are applied.

Is process evidence the same as an AI detector?

No. Process evidence records activity while work develops. An AI detector analyses finished text and estimates whether it resembles generated text. Neither should become an automatic misconduct decision, and each has a different evidence boundary.

Does Loam make academic-integrity decisions?

No. Loam gives teachers a readable and verifiable record of captured writing activity. The teacher or school applies the assessment rules, hears the student's explanation, considers other evidence and makes the decision.

Loam field guides

How can schools assess writing in the AI era?

Schools can strengthen take-home writing by combining clear rules, assessment design, a reviewable writing-process record and human judgement. These resources explain what process evidence can show, where its limits begin and how it differs from AI detection. They are written for teachers and school leaders making practical, privacy-conscious assessment decisions.

Primary question: How can teachers and schools review student writing fairly when generative AI is available?
Search intent: Find practical, source-led guidance on writing-process evidence and assessment review.

Editorial responsibility: Difinity Pty Ltd, operator of Loam

Published 29 July 2026

Last verified 29 July 2026

Which answer do you need first?

What can schools use instead of an AI detector?Build a fairer workflow around clear rules, staged work, student explanation and reviewable process evidence.What should Australian schools consider?Connect national and NSW guidance with Sydney data residency, privacy boundaries and teacher-led review.What is proof-of-process assessment?Start with the category, Loam's evidence model and the boundary between a record and a verdict.What can a writing-process record prove?Test the strongest and weakest claims before using process evidence in a school decision.How is process evidence different from an AI detector?Compare what each approach observes, what each misses and why neither should become an automatic verdict.What can Google Docs version history show?Understand the practical value and limits of a familiar document history before choosing a dedicated process tool.How does Loam capture the process?Follow the student writing flow, teacher replay and human review from start to finish.Can I inspect a sample record?Use the local verifier with a synthetic demonstration and read the evidence chain.

Who are these resources written for?

Teachers can use them to frame a conversation about a submission. Heads of department can use them to define a consistent review process. School leaders, privacy teams and IT reviewers can use them to test product claims, governance boundaries and the questions that belong in a pilot.

Teachers

Understand what a record shows before drawing a conclusion.

Faculty leaders

Build a repeatable, documented and appealable review process.

School leaders

Separate assessment design, evidence and product procurement.

Privacy and IT

Inspect the capture boundary, verification model and data terms.

Claim boundary

What do these resources promise, and what do they refuse to claim?

Can show

Which facts a writing-process record can support inside its capture boundary.
How official guidance distinguishes a signal from sufficient evidence.
What Loam records, verifies and exposes for human review.
Which practical questions a school should ask before adopting a process tool.

Cannot prove

That Loam eliminates cheating, contract work, retyping or second-device use.
That a writing record establishes authorship, identity or ownership of ideas.
That an AI detector or any single process signal proves misconduct.
That an Australian authority, regulator or education department endorses Loam.

Every guide keeps product facts, external guidance and editorial interpretation separate. Where a source applies to higher education rather than schools, that scope is stated beside the claim.

How are sources and updates handled?

Each answer-led guide names an accountable publisher, shows its publication and last-verified dates, and links material claims to primary sources. Product claims point to Loam's current technical, privacy or product pages. Policy claims point to the relevant public authority rather than to a secondary summary.

The Australian Framework for Generative AI in Schools is the national starting point for responsible and ethical AI use in school education. TEQSA's take-home assessment guidance is useful evidence guidance from higher education; it is labelled as such and is not presented as a school rule.

Can I inspect Loam instead of taking the claims on trust?

Yes. Start with the local evidence verifier. It includes a synthetic demonstration PDF, keeps the file in the browser and explains what a valid supported record can and cannot establish. Then compare that technical boundary with the Privacy Policy and the product walkthrough.

Source ledger

Which primary sources support this page?

01
Australian Department of Education — Framework for Generative AI in Schools
National framework for responsible and ethical generative-AI use across Australian school education. Last modified 17 June 2025.
02
TEQSA — Detecting AI-generated text and securing take-home assessment
Australian higher-education guidance on version history, process-writing tools and why AI scores require additional evidence. Updated 8 May 2026. TEQSA does not endorse Loam.
03
Loam — How the writing and review flow works
Product-specific primary source for what Loam captures, what a teacher reviews and where the evidence boundary stops. Last checked 29 July 2026.
04
Loam — Verify a Loam document locally
Product-specific primary source for Loam's verifier, synthetic demonstration, evidence chain and explicit proof limitations. Last checked 29 July 2026.

What practical review can you do next?

Review Loam for a schoolMove from the evidence model to governance, rollout and procurement questions.Take the technical routeInspect verification, privacy boundaries, retained data and the synthetic proof file.Plan for accommodationsSee how teachers can adapt a writing task without treating one workflow as universal.Bring a review questionAsk Loam about a specific teaching, privacy, security or procurement requirement.