Universities

The timetable makes the meeting. The register makes itself.

A seminar is created where your timetable already lives, the right people are already invited, and who attended goes back into the system that asked for it — without anybody taking a register or reconciling two lists a week later.

Attendance is a compliance job, not a curiosity

Somebody has to prove it — to a funder, to a regulator, to a visa office. A headcount will not do it, and a spreadsheet somebody typed up is a claim rather than a record.

Every meeting produces spans: who was there and for how long, down to the minute they arrived and the minute they left. Your institution decides what late means and what proportion counts as attending, and the sum behind each verdict is printed beside it — so the person who disagrees with one can be shown exactly what produced it.

A seminar is not a video call

It has a shared board, a document on every screen, tests with six kinds of question, a code and science workspace that runs in the browser, and a library of written material you can put up in one press.

All of it is shared properly: somebody arriving twenty minutes late gets the whole board rather than the part they were present for.

Your people are not in your time zone

Institutions recruiting and teaching across several continents spend more time working out when something can run than running it. Every meeting carries its own zone, and a meeting that has to move stays the same meeting with the same link.

The parts that matter most to you

Out of about a hundred. Each one has a page saying what it does and what it will not do.

  • It plugs into the system you already run

    From your timetable, your learning platform, or your own software — with the right people already invited, and what happened sent back.

  • Present, late or absent — by your rule

    Your organisation decides what late means and what counts as attending. The arithmetic behind every verdict is printed next to it.

  • It goes back where it came from

    Automatically, as well as exporting — so nobody reconciles two lists a week later.

  • The Lab

    One document the whole meeting edits, with Python and JavaScript running inside the browser rather than on our machines.

  • The lesson library

    Twenty-two written packs across coding, mathematics, physics and chemistry — plus whatever your organisation writes for itself.

  • Tests

    Multiple choice, select-all, true or false, matching, ordering and written answers — marked, with auto-hand-in when the time runs out.

  • Recordings that include what was on the stage

    The presented document, the whiteboard, the shared workspace and the idea wall are drawn into the file — not just the cameras and the shared screen.

  • Rosters that stay in step

    People arrive from the system your organisation already runs, and stay in sync, so nobody maintains a second list.

Everything it does

What you can ignore

The broadcast studio, the cricket module and the door cameras are all real and almost certainly not what you are here for. Nothing is switched on until somebody asks for it.

Not quite you?

Tell us how your organisation actually runs

We will answer with what this would look like for you — which parts you would use, which you would never touch, and what it would take to connect it to what you already have.

info@seeuall.com