Thirteen classroom systems, one place

What each one costs you, and what takes its place

1. Birthday chartClass dashboard

   Redrawn every September, and a child who joins in January is added in biro — if they are added at all.

   Upcoming birthdays appear on the class dashboard each morning, alongside the timetable and class jobs, for every child on the register.

   See the feature Try it in the demo

2. Jobs boardClass jobs

   Moving the pegs is one more Monday job, and the same few children somehow end up with the jobs they like.

   Line leader, lunch helpers and the rest rotate automatically each week and show on the dashboard.

   See the feature Try it in the demo

3. Homework tick list by the doorHomework check-in

   It records who handed homework in, then goes nowhere. The marks are typed up again somewhere else later.

   Students tick in each morning, and it links straight to your gradebook.

   See the feature Try it in the demo

4. Reading logHomework goals

   Signed at home, checked by nobody, and lost by half term.

   Daily targets like "read every night", tracked night by night instead of in a booklet that comes back once a term.

   See the feature Try it in the demo Read: The reading log nobody checks

5. Points chart or marble jarClass points

   By November the stickers are peeling, the totals are disputed and the chart needs redrawing.

   Award points from the board. Each child sees their own balance and level, and nothing needs recounting.

   See the feature Try it in the demo Read: Why class points charts fall apart by November

6. Prize boxReward store

   Prizes cost money, run out, and have no connection to the points that were meant to earn them.

   Students spend their points on rewards you set, so the points and the prizes are finally one system.

   See the feature Try it in the demo

7. Star of the Week certificateAchievements

   Written up on Friday, forgotten by Monday, and nobody can remember who had it three weeks ago.

   Set awards up once. Class points are added automatically and recent winners stay on the dashboard.

   See the feature Try it in the demo Read: Star of the Week and the Monday morning problem

8. Laminated seating planSeating plans

   One layout cannot serve maths groups, guided reading tables and science partners at the same time.

   A saved table plan for each subject or class, switched in one tap.

   See the feature Try it in the demo Read: Seating plans that survive a real timetable

9. Objectives rewritten on the whiteboardClassroom Screen and lesson widgets

   Rewritten every morning in primary, and every period in secondary.

   The objective, materials, bell ringer and a visual timer are set up once and put on the board from a browser tab.

   See the feature Try it in the demo Read: The whiteboard objective you rewrite every morning

10. Lolly sticks in a potFair name picker

    It feels fair, but a random draw still lets the same names come up again and again while others wait weeks.

    Picks a name at random on the Classroom Screen and spreads turns across the whole class.

    See the feature Try it in the demo Read: Pulling sticks isn't fair

11. Paper exit slipsExit tickets

    A pile of slips goes home in your bag and rarely makes it into a mark book.

    Students answer on the board, the answers mark themselves, and the scores go straight into the gradebook.

    See the feature Try it in the demo Read: Where do exit tickets actually go?

12. Marks spreadsheetWeighted gradebook

    Formulas break, tabs multiply, and reconciling them eats the week before reports.

    Homework, exams and exit tickets are weighted once, in one place, and every student's categories are on one screen.

    See the feature Read: A weighted gradebook without the spreadsheet headache

13. Incident notebookBehaviour log

    Notes end up split between a notebook, emails and memory, and are hard to pull together when a parent meeting comes round.

    Positives, concerns and parent contact sit on one record for each child, for the whole term.

    See the feature Read: What belongs in a behaviour log