One month. One or two classrooms. Free.

Then you decide, with what the teachers said and what the data showed.

For teachers

Every morning, one page: who is stuck, and on what.

LOOP prints a math practice sheet for each child, reads the scanned pages back overnight, and has one page waiting for the teacher before school: the misconception behind the wrong answers, and exactly which children have it.

No student logins. No app for children. Nothing to install.

Sample, invented dataTuesday morning
1

Did yesterday come back

24 of 25 sheets are ready. One page needs another scan.

2

Where the class is

Add within 10078%
Subtract within 10064%
3

What to reteach, and to whom

Borrowed from the wrong column

C1-003, C1-011, C1-016

4

What needs your eyes

Item 5 for C1-008. Is this a 7 or a 1?

71
5

Tomorrow, already prepared

Six focused problems are queued for each child from what today showed.

The problem

A stack of graded worksheets can't tell you what three children have in common.

Grading twenty-five sheets gets you scores. Knowing six children made the same mistake as last Thursday takes a second pass nobody has time for.

LOOP does that second pass. It puts the shared mistake and the children who made it on one morning page.

How it works

Paper in, paper out. The computer stays out of the classroom.

01

Print

One sheet per child, built from what that child missed.

02

Write

Pencil on paper. The same skill, with different problems.

03

Scan

The stack goes through the copier. The teacher uploads the scan on her page.

04

Read overnight

Every answer box is read. Errors are grouped by the misconception behind them.

05

Adjust

Tomorrow's sheets are queued from what today showed.

When it isn't sure

We show you every box we couldn't read.

Handwriting is hard, and any system that claims otherwise is rounding. A blank or an unsure read never quietly becomes a number in LOOP.

An unsure box goes on the morning page as a question with the child's handwriting next to it. The teacher chooses the answer and moves on.

And when it can't say why, it doesn't.

LOOP shows the wrong answer without inventing an explanation.

What lands each morning

Five things, in the order you need them.

Did yesterday come back

See whether the full stack was read and what needs another scan.

Where the class is

See the skills that are solid, shaky, or stuck.

What to reteach, and to whom

See the mistake pattern in plain language and the children who share it.

What needs your eyes

Answer only the boxes the reader could not settle.

Tomorrow, already prepared

Each child's next practice is queued from what today showed.

Nothing else

No feed to clear. No student accounts to manage.

Where it fits

LOOP does not replace what you already run. It feeds it.

Your benchmark screener

Three times a year, it shows a score, a tier, and a level of risk.

Your intervention programs

They help teachers teach the students who need more.

LOOP

Daily practice for every student. Per student, per skill, with the mistake named.

Utah classrooms

Built for the classroom HB 273 describes.

K through 3

Classroom screen time is prohibited except for computer science standards and standards assessments.

Grades 4 through 6

Technology is balanced with teacher-led, print-based and analog methods.

Where LOOP lands

Students work on paper. The teacher uses the printer, copier, and one page before school.

Read the HB 273 page

What a pilot month looks like.

0

Week 0

We meet the teachers and tune the sheets to what the class is learning.

1–2

Weeks 1 and 2

One skill. Daily paper practice and one uploaded scan.

3–4

Weeks 3 and 4

We widen to the next skills with the teachers.

✓

End of month

We bring you the teacher feedback and the data. Then you decide.

What we bring.

  • Setup and a teacher walkthrough.
  • Sheets tuned to the skill the class is on.
  • The morning page.

What we ask.

  • Print and use the sheets as the day's practice.
  • Scan and upload once a day.
  • Answer the boxes the reader was unsure of.
  • Give us honest feedback.

After the month.

You decide whether to keep going.

If LOOP is not a fit, the school keeps everything the pilot produced. Deletion on request is a command with a count, not a promise.

Student data, in plain language.

A class code per child

One class code per child, plus the child's worksheets and the skill records made from them. A first name is optional, and a numbered class keeps none. No last names, birthdays, logins or photos of faces.

Short, stated retention

The uploaded scans are usually deleted 3 days after the scan (7 if they could not be read). LOOP keeps a picture of each whole page and of each answer for checking, on one clock per page: usually 3 days after the scan; while an answer on that page still needs checking, until a day after it is checked, if that is later; and never past 7 days. Records are kept one school year. All of these are provisional and confirmed before signing. The automatic deletion is switched on before any real student's work is uploaded.

Only answer boxes leave

Pictures of answer boxes go to a commercial AI API, one box at a time. No name, code, or date is attached. The provider's current default retention is 30 days.

The inventory is ready

The full element-by-element inventory for NDPA Exhibit B is ready to send.

Read the full Student data page

Request a pilot.

Tell us what you would want to try. This goes straight to a person.

Goes to a person, not a CRM. We don't add you to anything.

One month. One or two classrooms. Free.

Request a pilot