First PrinciplesWorks

Critical Developments · Planned application 02

SitRep

Seat the class you actually teach.

Intelligent seating plans.

Explore the product planAll planned apps

Planned feature set

A seating plan should remember the room, the class and the reason.

SitRep is planned as a fast, teacher-controlled seating-plan tool. It combines a clear room map with explainable planning constraints, helping staff arrange pupils deliberately without pretending that an algorithm understands the class better than the person teaching it.

01

Room and roster builder

Create reusable room layouts, load a class list and produce a workable plan without drawing the furniture again every term.

02

Explainable constraints

Record practical requirements such as access, visibility, separation or support, then show why a suggested arrangement was made.

03

Teacher override

Move any pupil at any point. Suggestions assist professional judgement; they never lock the teacher into a generated answer.

04

Useful classroom views

Switch between planning, teaching, print and cover views so the same plan remains useful beyond the setup screen.

Why it earns a place

Different by design.

A product should do more than put a polished skin over the same institutional friction.

01

Intelligent, not mysterious

Every suggestion should be traceable to a visible rule or teacher-entered constraint rather than an opaque pupil score.

02

The room is part of the plan

Doors, fixed desks, access routes and teaching positions matter; SitRep starts with the actual space.

03

Made for change

Plans can be adjusted quickly as staff learn more about the class, rather than treated as a document completed once.

Expected impact

Where the time comes back.

The intended impact is quicker plan creation, more useful handover to cover staff and fewer classroom decisions being trapped in one teacher’s memory.

  • Faster plan updates
  • Better-informed cover
  • Clearer classroom routines

Build a new plan

Current friction
Redraw the room, copy pupil names and manually check each known constraint.
Planned change
Reuse the room, load the roster and resolve visible constraints in one planning view.

Respond to change

Current friction
Move names around a static document and risk losing the reasoning behind earlier choices.
Planned change
Adjust the live arrangement while keeping relevant constraints and teacher notes in view.

Prepare cover

Current friction
Export or explain a plan separately, often without the information that makes it useful.
Planned change
Provide a clean cover view with only the information the covering colleague is authorised to see.

No invented stopwatch claims. Numeric time savings will be published only after pilot schools have established a baseline and measured the same task using the product.

Security · UK GDPR

School data deserves more than a padlock icon.

These are requirements for the planned service, not a claim that an unfinished product is certified or that software makes a school automatically compliant.

Collect less

Define the minimum fields needed for each job, validate imports and avoid copying wider MIS records into the product without a clear purpose.

Control access

Use role-based permissions, least-privilege defaults and auditable administrative actions for data that should not be visible to every member of staff.

Protect and delete

Treat encryption in transit and at rest, tested backups, retention controls and reliable deletion as baseline technical requirements.

Make procurement evidence available

Prepare a clear data map, processing agreement, subprocessor list, retention schedule, technical-measures summary and practical DPIA support before contracting.

School-facing boundary: the school will still need an appropriate lawful basis, privacy information, access policy, retention decisions and—where the risk requires it—a DPIA. The supplier’s job is to make those decisions informed, documented and technically enforceable.

Back to planned apps