Forms.

Every school runs on forms it never had time to build.

• Fourteen field types

  Short and long text, number, email, phone, URL, dropdown, multi-select, multiple choice, date, time, a 1–5 rating and file upload — plus section titles to break a long form into parts.

• Build with a live preview

  Add a field, set its label and placeholder, mark it required, arrange the order — and watch the real form render beside you as you go, so what you ship is exactly what you saw.

• Validation that holds

  Required fields, a real email, a real URL, a number that is a number, a rating inside 1–5 — checked as the form is filled, so the data that lands is already clean.

• Who can see it, who can fill it

  Target a form to teachers, employees, admins, principals or heads of department — and choose whether each submission must link a student, or several at once.

• Report categories

  Group forms under colour-coded categories — counselling, discipline, daily logs, whatever your school keeps — so a sprawl of one-off forms reads as an ordered shelf.

• A submissions dashboard

  Every response in one panel — who submitted, when, against which student — with live counts of active forms and what came in today and this week, instead of a folder of files.

• Export templates

  Save the shape of an export once — the columns you want, the sort order, the filters, the grouping by class or section, even the filename — and reuse it every time you pull the data.

• An AI summary, optional

  Switch on a per-form summary and each submission gets a short read; across a day, the same engine rolls every response into one bilingual brief of wins, risks and what needs a decision.

• 01 / 04

  Scoped to a campus, exactly like everything else. Every form, category and submission carries its branch — so a multi-campus trust keeps each campus's forms its own, and a slug can't collide across the wall.

• 02 / 04

  Linked to the students you already have. A form can require a student — one or several — so the response isn't a stray row in a sheet but a record attached to the right child in the same system.

• 03 / 04

  On the same web, iOS and Android apps. A teacher fills the form on a phone between periods; an administrator reads the submissions panel from a desk. One login, one app, no separate forms tool.

• 04 / 04

  Within reach of Sol, the AI agent. Turn on a summary and each submission gets a read; across the day the same engine rolls every response into one bilingual brief — the assistant that already works across the school, working over your forms too.

Why it sits inside

A form is only as useful as where the answers land. Ours land next to the student.