Skip to content

Your school has most of the pieces. We build the rest.

Your systems each do their job, but the work between them still lands on your people. Ember builds what connects it, so the admin falls away and decisions come with their evidence.

An illustration of a school as a set of loops: teaching, compliance, student support, workforce, improvement and community. Students are at the centre, with the school’s people and systems around them. Joins that are lit glow amber, and gaps still carried by hand are dashed.
LanternAvailable now

Report comments in each teacher’s voice, checked against your school’s rules, signed off by leaders.

More about Lantern
  1. Lantern · now

    Lantern closes the gap between assessment and reports: comments drafted in each teacher’s voice, checked against your school’s rules, signed off by leaders.

  2. Already connected

    Lantern already joins teachers, leaders and your reporting rules in one flow, inside a school that runs on many more loops.

  3. Next

    Every school has more gaps like this one. Each new tool lights another, and each one stands on its own.

  4. Over time

    One loop at a time, the work between your systems stops landing on your people, and decisions come with their evidence.

Lantern: one comment, start to sign-off

A teacher’s notes become a comment in their voice.

Recorded in Lantern with an invented class. Typing and waiting are sped up.

The work between systems

Where the extra hours go.

Your staff carry information from one system to the next by hand. It rarely shows up in a budget, but it shows up in their evenings and weekends.

  • Report season weekends

    Marks are in one system, notes in another and reports in a third. Teachers bring them together after hours, and leaders read every comment before reports go home.

  • Evidence gathered after the fact

    The work was done all year. When a review or audit comes round, staff piece the evidence back together from old emails and shared folders.

  • The same details, typed three times

    A new enrolment is entered in one system, typed again into the next and copied into a spreadsheet. When a detail changes, someone has to update every copy.

Our approach

Fix the work underneath, one problem at a time.

Your systems are good at what they were bought for. The hard part is the work that happens between them, and that is where we start.

  1. 01

    Fix the process, not add a dashboard

    We change how the work gets done, so clean data comes out of it as a by-product. Another screen to check is not the goal. Less work for your staff is.

  2. 02

    People make every decision

    Ember drafts, checks and routes. The judgement calls stay with the people accountable for them, with the evidence in front of them.

  3. 03

    Privacy matched to the job

    Each tool collects only what its job needs, so you can review each one on its own terms instead of facing one large review.

  4. 04

    One problem at a time

    Each tool stands on its own and does one job well. Start with the problem that costs your staff the most, and add the next only when the first has earned it.

Lantern

Report season, with the checks already done.

Lantern helps teachers write school reports in their own voice, from their own notes. Every comment is checked against your school's rules before it reaches you.

  • Teachers stay the authors

    Lantern drafts from the teacher's notes. The teacher reviews, edits and approves every word, and nothing leaves without their say.

  • Your rules, applied every time

    Comments are checked against your school's rules and reporting requirements as they are written, not in a proofreading pass at the end.

  • Nothing invented about a student

    If a comment says something the teacher's notes don't support, Lantern flags it for the teacher to resolve rather than filling the gap.

  • Sign-off with the evidence beside it

    Leaders review comments with their checks attached, so sign-off is about judgement, not hunting for errors.

Lantern has its own site, with the detail on how it works and how it handles information.

Visit the Lantern site: TODO: Lantern site URL

Made here

Built in Australia, for Australian schools.

We design for the way schools here work, from the curriculum to the calendar.

  • The Australian Curriculum, and the state versions of it.
  • Reporting requirements from your state, your sector and your school.
  • Four terms a year, and the report seasons that come with them.

How we work with schools

Start with a conversation, not a contract.

We fit around the rhythm of your school year, and you decide each next step.

  1. Step 1

    Conversation

    We listen first. Tell us where the work between your systems lands on your people, and we'll be straight about whether we can help.

  2. Step 2

    Pilot

    A small group of your staff uses the tool on real work, so you see what changes before you commit.

    Pilot length: TODO: pilot length

  3. Step 3

    Rollout

    We bring the rest of your staff on board, set it up around the systems you already use, and support them through their first cycle.

  4. Step 4

    Partnership

    We keep improving the tool with you. When you're ready, we look at the next problem together.

Privacy, security and AI

Clear about what we do, and what we never do.

Your school is trusted with information about children and staff. Any tool you bring in has to earn that trust too.

What we do

  • Collect only the information each tool's job needs.
  • Keep a person in charge of every decision. The software drafts, checks and routes.
  • Keep a record of who did what, so questions can be answered later.
  • Share our privacy and security documentation for your school's review.

What we never do

  • Use student information to train third-party AI models.
  • Use student information for advertising, profiling or unrelated commercial purposes.
  • Let AI invent claims about a student.
  • Let software make a judgement call that belongs to a person.

Lantern's own site covers its privacy and security in detail: TODO: Lantern site URL

About Ember

A small Australian team building software for schools.

Ember Education builds software for the work that sits between the systems a school already has. We build on those systems rather than asking you to replace them.

We work to the rhythm of the Australian school year, from Term 1 planning to report season.

The team: TODO: whether and how to show the team

Book a conversation

Let's talk about one problem.

Tell us where the work between your systems lands on your staff. We'll listen, and tell you honestly whether we can help.