If you are choosing software for a scientific program, this is the case in one place: what Rostrum spans, what it refuses to bundle, and the operational details that decide whether conference week is calm or frantic.
One record, end to end
Conferences don't break in the software — they break between it. A society's program passes through six stages between the call opening and the doors opening, and when each stage lives in a different tool, the gaps get bridged with spreadsheets, re-keyed data and email. That bridging is where content goes missing and deadlines slip.
Rostrum spans the whole path with a single record. A submission arrives through the call, is assigned to reviewers, scored, accepted, converted into a presentation, placed in a session, and shown on the sign outside the room — the same record the whole way. Nothing is retyped at a hand-off. Move a talk on the schedule and the room sign, the attendee app, and the speaker's own upload deadline all follow it. The span is the product: a society that begins its cycle here never hands the program off to anyone.
Twelve modules, switched on per event
Rostrum is a small catalog of products, enabled per event (Chapter 01, Chapter 05). A spring workshop that needs a schedule and file collection turns on nothing extra; a 2,000-abstract annual congress with an open call, poster hall, signage and a delegate app turns on five or six. Both run on the same platform, and the workshop never pays for machinery it will not open. Products can be switched on mid-flight — signage can be added the week of the show.
The program layer — and nothing else
Rostrum does not sell audiovisual production, onsite staffing, or registration. That is not a posture; it is a description of what the product is — and it means Rostrum can never become the reason you keep a supplier you would otherwise replace. Your AV partner is your business. Your registration system is your business. If either changes next year, the program doesn't move and the price doesn't move.
The price is published on the website, and so is this manual — you can evaluate the platform, its settings and its defaults without booking a demo. And your data is never held hostage: the program leaves in a spreadsheet the same way it can arrive in one.
Deadlines live in the venue's timezone
Every schedule time and every deadline in Rostrum is evaluated in the event venue's timezone — a midnight deadline in Vienna is midnight in Vienna, wherever the speaker or the server happens to be. Reminders go out on the intervals you choose, deduplicated to one email per person per day, and the sweep runs automatically every hour whether or not anyone is watching (Chapter 18). Chasing the eleven people who haven't uploaded stops being somebody's late-night job.
Most participants never see a password
Late speaker content has one cause above all others: a login nobody remembers. So for the people around the program, Rostrum doesn't ask for one. Speakers upload through a personal link; reviewers and attendees sign in with a short code sent to their email (Chapter 03). The program committee stops chasing passwords, and the people who touch a conference once a year have nothing to learn.
An assistant that proposes — never acts alone
Athena, the built-in assistant, answers questions grounded in this documentation and drafts the genuinely tedious work — a complete program from a plain-language description, session groupings from a pile of unplaced talks, event setup pre-filled from your website (Chapter 24). Everything is a proposal you review before anything is created; it reads titles and abstracts, never author identities; and when it is off, the platform simply works as it always did.