Your reporting standard,
on every comment.

01 · Compliance & consistency

Your rules, enforced on every comment. Not hoped for.

Reporting consistency usually depends on teachers remembering a policy under deadline. Lantern makes it structural. Your rules, prohibited and preferred phrasing, required structure, character limits, are checked on every draft and tuned per faculty and year group, so a Year 3 effort comment and a Year 10 subject report are each held to the standard that actually applies to them.

• No diagnostic or medical languagewhole school
• Required structure: strength → growth → next stepYears 7–10
• 200–320 charactersYear 3 effort comments
• Subject-specific verbs from the faculty glossaryScience department
• Forward-looking final sentenceEnglish department

Rolling out in stages? Schools can run Lantern as a compliance checker alone: comments written anywhere are uploaded and returned with per-comment findings and suggested fixes. No drafting, just the safety net under your existing process.

02 · The end of proofreading

Read for content. Sign off. Move on.

Most of a reviewer’s time during reporting is spent on the mechanics: spelling, grammar, capitalisation, the wrong student’s name, a comment forty characters over the limit. Lantern handles those before a comment ever reaches a reviewer, so leadership time goes to the judgement that actually needs a human: is this fair, is it accurate, does it reflect the child?

Conventions, handled

Grammar, spelling and house-style conventions are corrected and flagged on the draft, not left for a reviewer to catch at 11pm.

Limits, respected

Character and structure rules are met before sign-off, so no comment bounces back over a formatting technicality.

Judgement, surfaced

Anything that needs a professional eye is flagged for review rather than buried, so your attention lands on the comments where your judgement actually changes something, not the ones that are already fine.

03 · Sign-off workflow

A clear path from teacher to leadership, and a record of it.

Reporting is a chain of approvals, but it usually runs on shared documents, email threads and trust. Lantern makes the chain explicit, so everyone can see where each comment is, and the whole round is captured in an audit trail you can stand behind.

Teacher drafts and approves

Comments are written in the teacher's own voice and only leave their desk once they have read and approved each one. The teacher is always the author of record.

Coordinator review

Faculty heads and year-level coordinators see their cohort in one queue, every comment already passing the rules, and approve, return, or annotate without retyping a word.

Executive sign-off

A final approval gate for leadership, with a live view of what is drafted, returned, approved and outstanding across the whole reporting round.

Locked and recorded

Once signed off, comments lock. Every view, edit and approval is written to an immutable audit trail: who changed what, and when.

04 · Cohort insight

See the whole cohort, not one comment at a time.

Quietly, every round, Lantern is building the richest dataset your school has ever had about its own reporting: thousands of comments passing through one consistent process, aggregated and de-identified. That turns into leadership insight no external editor or stack of finished PDFs could ever give you. The shape of a round as it happens, progress against deadline, themes and language patterns by faculty and year group, and where a faculty is drifting from the agreed standard. It is always a view of the cohort, never a profile of a child.

Insight is a differentiator, not an afterthought. See what cohort-level reporting looks like and what it surfaces for leaders mid-round.

05 · The economics

Cheaper than external editors, and far smarter.

Many schools quietly pay for outside proofreaders, or burn executive and coordinator hours on the same work, every reporting round. Lantern absorbs the mechanical pass for a predictable per-school fee, and unlike an editor, it enforces your specific rules, matches each teacher’s voice, keeps everything onshore, and leaves you with analytics and an audit trail an editor never could.

External editing today

[PLACEHOLDER: typical external proofreading spend per reporting round], recurring every semester, with no rules enforcement, no voice matching and no record of what changed.

Lantern

[PLACEHOLDER: Lantern per-school annual price]: drafting, rules enforcement, sign-off, analytics and onshore hosting in one predictable fee.

Time returned

[PLACEHOLDER: average leadership and teaching hours returned per round], based on schools running Lantern across a full reporting cycle.

The honest comparison

Why not just let staff use ChatGPT?

Some schools have wired up their own GPT, and plenty of teachers are quietly using a chatbot already. A general model can produce a paragraph. What it can’t do is enforce your standard, hold a character limit, keep each teacher’s voice, or leave you with a record you can defend, the things that make reporting safe at the scale of a whole school.

No rules, no consistency

A chatbot doesn’t know your policy, so consistency depends on every teacher prompting well under deadline. Lantern enforces your rules on every comment, the same standard from the first to the four-hundredth.

No record you can defend

A chat history isn’t an audit trail. Lantern records who drafted, edited and approved every comment, aligned to the Australian Privacy Principles.

The bigger risk is quieter. The moment a teacher pastes a student’s name and details into a free or consumer AI tool, identifiable student information has left the country, and many such tools reserve the right to train on it. Under the Australian Privacy Principles that obligation sits with the school. Lantern keeps every draft and note onshore in AWS Sydney and never uses your data to train models. See the security & data sovereignty story.