OpsCore // Eventz

Registration, attendance, certificates.
One record.

Run conferences, workshops and professional development end to end. Your own staff configure it. No vendor ticket required.

Delegates in lanyards being checked in at a conference desk.

Education Leadership Conference 2026

Delegate 0184

Registeredyour form, your rules, district PO
14 April
Checked inscanned at the door
9 June, 08:41
Sessions attendedscanned at each one
4 of 5
Certificateissued on the maths, verifiable by anyone
6.5 hours

Demonstration record. Invented conference and delegate.

The whole thing, in half a minute.

Every screen in this film is the running product, recorded against real records.

Everything an event programme needs.

The full lifecycle, from the first draft of an event through to the financial report and the participant's certificate.

Registration you configure yourself

Build the form, add conditional rules, and take individual, group, sponsor, exhibitor and vendor registrations with approvals and waitlists.

Registrations, every event
The OpsCore Eventz registrations console listing attendees with confirmation numbers, event, type, balance and status, and filters for awaiting review and waitlisted.
Educators seated at round tables in a professional development workshop while a presenter speaks.

Events of any type or size

Conferences, workshops, professional development, meetings and expos. In person, virtual or hybrid, with many events running at once.

Check-in, badges and attendance

QR check-in on any phone or tablet, badge design and printing, and attendance recorded session by session.

Reporting without a developer

A standard report library plus a builder: pick a dataset, choose fields, filter, group, save and export.

Reports
The OpsCore Eventz reports area, listing the standard report library alongside saved reports.

Finance built for accountability

Invoices, payments, refunds, discounts and reconciliation, with every financial export permission-gated and written to the audit log.

Integration-ready

A scoped REST API and outbound webhooks, with secure file exchange as the alternative when a district cannot open a connection.

Communications that run themselves

Announcements, templates and automation, with a delivery log that records what was actually sent rather than what was scheduled.

The payoff

It ends with someone's name on a document.

Eligibility comes from attendance, required sessions, credit hours or a completed survey. When the rules are met the certificate issues itself, numbered and on your letterhead. Anyone can confirm that number on a public page, so nobody has to phone your office to check a candidate.

Issued automatically when your rules are satisfied
Numbered, and verifiable by anyone without an account
Rendered on the organization’s own letterhead and accent
A certificate of completion issued by OpsCore Eventz, naming the recipient, the event, the credit hours, the signing director, the issue date and the certificate number with a line telling the reader where to verify it.

Nothing is re-keyed between one step and the next.

  1. 1

    Publish

    The event goes live on your own branded page with its registration form attached.

  2. 2

    Register

    Someone registers. Conditional rules ask only the questions that apply to them.

  3. 3

    Invoice

    A district is invoiced, or a card is taken. Refunds and discounts stay on the same record.

  4. 4

    Check in

    A phone at the door scans them in, then scans them into each session they attend.

  5. 5

    Certify

    Credit hours total up. The certificate issues itself when the rules are met.

  6. 6

    Report

    Attendance, money and outcomes come out as a report you built yourself.

Three ways in. One system.

An administrator, a staff member at the door and an attendee each see a different surface onto the same records.

Administrator
The OpsCore Eventz events console listing every event with its status.

The console

Events and sessions, speakers, sponsors and vendors, forms, communications, badges, certificates, finance, reports, roles and the audit trail.

Staff at the door
The OpsCore Eventz staff check-in screen with a scanner and session rows.

Check-in

A phone or tablet, a roster and a scanner. Check people into the event, then into each session, with no access to anything else.

Anyone, no account
The public OpsCore Eventz page where anyone can enter a certificate number to verify it.

Verification

A public page that takes a certificate number and answers. Attendees get their own portal for agendas, payments, surveys and certificates.

A programme administrator working at a laptop in a quiet office at dusk.

Built for public money

It has to survive being reviewed.

Public-sector programmes get audited, and the answer to “who changed this and when” cannot be a shrug. Every privileged action is checked on the server, not in the interface, and recorded with the actor, the record and what changed.

12 roles, 71 permissions
Start from the roles that ship, or build your own. Access is granted by permission, not by job title.
Organizations cannot see each other
Enforced server-side on every request. A record from another organization returns not-found, never a permission error.
A real audit history
Actor, entity, before and after. Financial exports are permission-gated and written to the log as they happen.
An API with scopes
Keys are hashed, scoped and rate limited. A money figure only comes back to a key that holds finance access.
Book a walkthrough

Straight answers.

Who is this actually for?

Organizations that run events for other people rather than for themselves. Education service centers, districts, county departments of education, state agencies and the associations around them. The unit of work is a programme of many events per year with credit hours attached, not a single annual conference.

Can our own staff change things, or do we file a ticket?

Your staff change things. Forms, workflows, branding, email templates, certificate rules, reports, permissions and financial mappings are all administrator-controlled from inside the console. An ordinary change never needs the vendor.

Is each organization really separated?

Yes, and it is enforced on the server on every request, not in the interface. A record belonging to another organization does not return a permission error, it returns a not-found, so the system never confirms that the record exists at all.

How do certificates get verified?

Every certificate carries a number, and there is a public verification page that takes it. Anyone checking a candidate can confirm the certificate without an account and without you being asked to look it up.

What does the API let us do?

Read events, sessions, registrations, attendees, invoices and payments, and write registrations, attendees and attendance. Keys carry scopes, so a finance figure is only returned to a key that holds finance access. Writes go through the same rules the interface uses, including the conditional logic on your forms.

What is not built yet?

Bulk import of records from a spreadsheet, the admin screens for group registration, and a background worker to run report schedules on their own. The product says so where it matters rather than presenting an empty screen as a working feature.

See it with your own programme in it.

We will walk one of your real events through registration, check-in and a certificate.

Book a walkthrough