Every event your district runs, on one platform.

Rostra takes a professional learning day, a county conference, a vendor expo or a community meeting from the first registration form through badge printing, attendance records and the journal entry your finance office posts. Your administrators configure all of it. No vendor ticket required.

Registration types
5 types
Card and ACH gateway
CyberSource
Finance system path
eFinancePlus
Deployment
Browser only

Pick a registration type

Form, fee and approval path update live

Individual registration

form/ind-01

Fields on this form

    Approval path

      Charge handled as

      Every field, rule and approval step above is built in the form designer by your own staff. The five types can run on one event or on five separate branded pages.

      A twenty seat breakout and a four hundred seat conference run on the same system

      • Five colleagues gathered around a table working through printed materials at a breakout session.
        Breakout workshops Room capacity, seat holds and a waitlist that promotes itself.
      • An audience seated in a darkened auditorium watching a presenter on stage.
        Multi day conferences Concurrent tracks, speaker logistics and certificates at the close.
      • Attendees standing and talking in small groups during a break beside rows of chairs.
        Community and vendor events Exhibitor booths, sponsor tiers and walk-in registration at the door.

      Everything an event needs, in one place

      Most teams run events on a registration tool, a spreadsheet, a payment portal and a printer, and spend the week afterwards reconciling all four. Rostra keeps one attendee record from the form they filled in to the certificate they download.

      Showing all features.

        Registration and event pages

        One platform, a separate front door for every event

        A summer leadership institute and a Saturday family engagement fair should not look like the same website. Each event gets its own page with its own logo, colours, header image, copy and policy text, published on your domain and owned by the team running that event.

        • Independently managed pages

          Delegate a page to a school, department or committee. Permissions keep each team inside its own event.

        • Conditional forms

          Show a purchase order field only when the payer is a district, or an accessibility question only when a session is selected.

        • Approval routing

          Route by cost, registration type, school or funding source. Approvers act from email or from the queue.

        • Attendee records that persist

          One profile per person across every event, carrying history, credits earned and communication preferences.

        Six district staff seated around a conference table in discussion during a leadership session.

        Summer Leadership Institute

        events.district.org/sli

        Sessions

        20

        Tracks

        4

        Three colleagues looking at a laptop together in a bright meeting room.

        New Teacher Onboarding

        events.district.org/onboarding

        Cohorts

        6

        Contact hours

        18

        County Vendor Expo

        events.district.org/expo

        Exhibitor booths

        64

        Sponsor tiers

        4

        Registration forms

        3

        Scheduling, sessions and tracks

        Concurrent sessions, without the spreadsheet

        Build the agenda by track, set room capacity, and let attendees hold a seat when they register. Capacity, waitlists and conflicts are checked as the schedule is built, not the week before.

        Filter the grid to see how tracks are separated

        Time
        Leadership
        Instruction
        Operations
        Technology
        A speaker with a microphone addressing seated panellists during a breakout session.
        Panels, workshops and breakouts all live on the same schedule, with their own capacity and their own speakers.

        Speakers

        Speakers hold their own profile, upload a headshot and bio, confirm session times and post handouts. Their schedule updates when yours does.

        Exhibitors

        Booth selection, staff badge allocation, insurance documents and electrical requests all sit on the exhibitor record.

        Live sessions

        Polls, moderated questions and shared notes run inside the session so facilitators keep one screen open, not four.

        Check-in, badges, attendance and certificates

        The morning of the event, at the door

        Scan a code from a phone, search by last name, or register a walk-in on the spot. The badge prints, the attendance record opens, and the room count moves. Try it.

        A printed registration desk sign taped to a dark panel at the entrance to an event.

        Door 2, main atrium

        Summer Leadership Institute, day 1

        Checked in

        184

        Badges printed

        184

        Currently on site

        171

        Arrival log

          A bundle of blank conference badges on blue lanyards held ready for arriving attendees.

          Badge, printed on arrival

          Attendee badge showing the event name, attendee name, organisation, a scannable code and the sessions the attendee is registered for. Summer Leadership Institute Marisol Vega Northside Middle School Individual registration Registered sessions 9:00 Opening, Auditorium 10:30 Budget clinic, Rm 210 13:30 Data walk, Rm 118 SLI-2026-0148 Scan at each session door

          Certificates issue themselves

          Session scans roll up into a contact hour total. When an attendee meets the rule you set, the certificate generates with their name, hours and the event details, then goes out by email and lands in their profile for later download.

          Payments, invoicing and finance integration

          Money moves from the registration form to your ledger

          Registrations create a receivable the moment they are submitted. Card and ACH payments clear through CyberSource. Purchase orders become invoices. Everything reconciles to a single batch your finance office can post to PowerSchool eFinancePlus.

          How a payment travels from registration to your finance system A registration creates a charge. Card and ACH payments are authorised and settled through CyberSource, while purchase order registrations produce an invoice with dunning reminders. Both routes meet in the Rostra ledger, which produces a reconciled daily batch. That batch is exported to PowerSchool eFinancePlus or another finance system through a secure API or scheduled file transfer. Registration charge created CyberSource Card and ACH, tokenised auth / capture / refund Invoice Purchase order and terms issue / remind / credit Rostra ledger Fund, account and project codes applied per event daily reconciled batch PowerSchool eFinancePlus Secure API or scheduled file transfer, mapped to your chart receipts / AR / journal entries

          Invoicing

          Issue, adjust, credit and void invoices against a registration. Reminders go out on the schedule you set.

          Financial reports

          Build reports across payments, refunds, receivables and registrations, then save and share them with your team.

          Open integration

          REST API with scoped keys, webhooks on payment events, and scheduled exports over SFTP where a file is preferred.

          Card data handling

          Payment pages are hosted by the gateway so card numbers stay out of Rostra. Designed to support a PCI DSS SAQ A scope.

          Dashboards, reports and exports

          Answers before the meeting, not after it

          The same data serves three different readers. The coordinator watching today's numbers, the cabinet reviewing the season, and the business office closing the books.

          Operational view

          Illustrative figures from a sample event

          Registrations received by week

            CSV Excel PDF Scheduled email API

            Any view on this page exports in these formats, with the filters you applied still in place.

            Built for the phone in the hallway

            Attendees register, view their agenda and show their code from a browser on any device. Staff check people in, look up a record and read dashboards from the same phone.

            Your data stays yours

            Full extracts of registration, attendance and financial records are available on demand or on a schedule, in open formats, without a service request.

            Standard and custom reports

            Start from a packaged report, change the columns, filters and grouping, then save it as your own and set it to run each Monday.

            Two attendees taking notes and using a tablet during a session.

            Communication and engagement

            Keeping people informed, then finding out how it went

            Announcements, reminders and changes reach attendees on the channel they chose. Surveys go out before and after, and the results attach to the event record where the next planning committee will actually find them.

            Notifications

            Send by event, session, track or registration type. Trigger on a schedule, on approval, on payment or on a room change.

            Surveys

            Build pre-event and post-event forms, send them to the right segment, and read the results by session and by presenter.

            Networking

            Opt-in attendee directory, direct messages and interest matching, with an administrator switch for events where it is not appropriate.

            In-session interaction

            Live polls, moderated question queues and shared notes, with the responses saved to the session for the report afterwards.

            Self-service configuration

            Changes your team makes on a Tuesday

            The measure of a platform is what happens when a deadline moves or a new fee category appears. In Rostra those are settings, edited by an administrator, taking effect immediately. Vendor involvement is for the things that genuinely need it, such as a new integration endpoint.

            • Forms, fields, validation rules and conditional logic
            • Approval routing, roles and permission sets
            • Fee schedules, discount codes and refund rules
            • Page branding, badge layouts and certificate templates
            • Email content, notification triggers and sending windows
            • Account codes, report definitions and export schedules

            Settings, registration rules

            Saved 2 minutes ago

            Close registration

            Applies to all types except walk-in

            14 Jun, 17:00

            Purchase orders accepted

            Group, sponsor and exhibitor types

            Waitlist full sessions

            Promotes automatically when a seat opens

            Attendee networking directory

            Off for events with students present

            Certificate rule

            Minimum contact hours to qualify

            4.0 hrs

            Nightly finance export

            Batch delivered to eFinancePlus

            23:30 CT

            Security and accessibility

            Built for the data schools hold

            • SOC 2 aligned controls

              Access management, change control, logging and supplier review are operated against the SOC 2 Trust Services Criteria. We share our current report on request.

            • Card scope kept narrow

              Card entry is hosted by the gateway. Rostra stores gateway tokens rather than card numbers, which is designed to support a PCI DSS SAQ A scope for your district.

            • Student and staff data

              Where student information is present, our terms address FERPA obligations along with data ownership, retention and deletion if you leave.

            • WCAG 2.1 AA target

              Public registration pages, attendee views and administrative screens are built and tested against WCAG 2.1 level AA, because a registration form that excludes people is not a registration form. A current VPAT is available.

            Implementation

            From kickoff to your first live event

            1. 01

              Discovery and account structure

              Event inventory, registration types in use today, fee categories, chart of accounts and the approval chains each department follows.

            2. 02

              Configuration and branding

              Forms, workflows, page templates, badge and certificate layouts, built alongside your administrators so they can maintain them afterwards.

            3. 03

              Gateway and finance connection

              Gateway setup and test transactions, then the finance export mapped to your fund and account structure and checked with the business office.

            4. 04

              Pilot event

              A real event runs end to end, including door check-in and badge printing, with our team present on the day.

            5. 05

              Handover and training

              Administrator and coordinator training, documentation for your intranet, and a named support contact.

            Questions people ask before they switch

            Does the platform work with CyberSource specifically?

            Yes. CyberSource is a supported gateway for card and ACH, using hosted payment pages and tokenised references so card data does not enter Rostra. Your existing merchant account and account codes are used, and refunds and voids are initiated from the registration record. Other gateways can be connected where a department already has one in place.

            How does the eFinancePlus integration actually work?

            Rostra produces a reconciled daily batch of receipts, receivables and journal entries, coded to the fund, account and project structure you supply during implementation. Delivery is by secure API where available, or by scheduled encrypted file transfer in the layout your finance team specifies. The mapping is validated against a test period before the first live posting.

            Can several teams run their own events at the same time?

            That is the normal case. Each event has its own page, forms, fee schedule, workflows and team. Permissions scope a coordinator to their own events while district administrators retain a consolidated view across all of them, including combined financial and attendance reporting.

            What do we need on site to check people in and print badges?

            A browser on a laptop, tablet or phone. Camera scanning works without extra hardware, and handheld scanners are supported where you already own them. Badges print to standard label and card printers, and a queued mode keeps the line moving if the venue network is unreliable.

            How much of this can we change ourselves?

            Everything listed in the configuration section is administrator editable, including forms, workflows, fees, branding, badge and certificate templates, notifications, roles and report definitions. We expect to be involved when you add a new external integration or need a change to the finance export layout.

            Let’s Talk About Your Product

            Get expert guidance on scope, architecture, timelines, and delivery approach so you can move forward with confidence.

            What happens next?