event67
Open menu

The app for a public meeting or consultation

A public meeting is judged on whether people felt heard, and that judgment is made in the twenty minutes when the floor is open. An ordered, visible question list changes how that twenty minutes goes.

1,000
an 85-attendee hearingOne dot ≈ 8 attendees

A planning figure for a local consultation on a live issue. Most of these sit close to or under the free tier.

What makes a hearing feel fair

A public meeting app carries the agenda and papers for a hearing, consultation or council session, collects questions from attendees before and during it, ranks them by how many people want them asked, and keeps the questions and their vote counts. event67 provides that. It does not run votes, broadcast the meeting, or satisfy any specific open-meetings statute, and those boundaries decide whether it fits your process.

A question list the public can see being built

The perception of fairness at a public meeting comes from visibility. When attendees can see the ranked question list and watch their own question rise, a chair taking the top item is doing something observable rather than something contested. Moderation actions are not logged.

Papers attached to the item they belong to

Consultation documents are famously hard to find at the moment they matter. Entering the agenda as timed items with the relevant document attached to each means an attendee reads the paper where it is being discussed.

Notice that arrives, and can be shown to have arrived

Invites are branded and delivery is tracked per recipient, so an authority can see which notices were delivered. Whether that satisfies a statutory notice requirement is a legal question for your own advisers; we make the record available rather than certify it.

An account of what was raised

The reports archive keeps every question, its vote count, every poll result and every moderation decision for the meeting. For a consultation that has to demonstrate it listened, this is a materially better artefact than a summary written afterwards.

From notice period to published answers

  1. Notice period

    Publish the agenda and papers

    Create the event on the notice date and enter the agenda as timed items with documents. Import the notified list as CSV and send branded invites, with delivery tracked per recipient.

    Uses the agenda and branded invites with delivery tracking.

  2. Before the meeting

    Open questions early

    Advance questions with voting produce better questions and give officers time to prepare a real answer. It also surfaces the issue nobody on the panel expected, which is better found a week early than at the microphone.

    Uses questions and voting.

  3. Arrival

    Attendance without a sign-in sheet

    QR check-in with a live count. Treat it as an operational figure. If your process requires a certified attendance record, that has to come from your own procedure, not from an arrivals widget.

    Uses check-in.

  4. The floor

    The ranked list, taken in order

    The chair works down the ranked list. Moderation can hold a question, and the hold is logged. Attendees see the queue, which is the mechanism that makes an ordering feel legitimate rather than arbitrary.

    Uses moderated Q&A.

  5. After

    Answer what you did not reach

    The unanswered questions are already ranked and written down. Publishing answers to them is the single most visible thing an authority can do to demonstrate that a consultation was not theatre.

    Uses announcements.

Preparing a public meeting

Five steps. The first one is a legal review, and skipping it is not an option in this sector.

  1. Check your open-meetings obligations first

    Streaming, records retention and accessibility requirements decide whether event67 can be part of your process at all. Establish that before configuring anything.

  2. Create the event on the notice date

    So the app itself can carry the agenda and papers through the notice period.

  3. Enter the agenda with documents attached

    Item by item, timed, with a named officer for each.

  4. Open questions during the notice period

    With voting. This is where a consultation gets its best material.

  5. Set moderation to moderated and brief the moderator

    Not admin-only. Note that moderation is not logged, so the ranked list itself, which attendees can see, is what answers a complaint about the ordering.

What an 85-attendee hearing costs

Eighty-five attendees activate. Fifty are free and thirty-five are billable once for that meeting. Most local consultations sit at or below this size.

activated attendees
85activated attendees
billable, after the first 50 are free
35billable, after the first 50 are free
for the whole event, at $5.00 each
$175for the whole event, at $5.00 each

A hearing with fifty or fewer activated attendees costs nothing at all.

The boundaries that decide whether this fits

Public-sector processes are governed by rules that software does not change. These are the ones that most often disqualify an event app, and they apply to event67.

  • No streaming or broadcast. Many open-meetings requirements now expect a public livestream; event67 does not provide one.
  • No voting, balloting or recorded decisions. Live polls are opinion instruments only.
  • No anonymous questions. Every question carries the asker's identity.
  • No accessibility conformance certification. We run WCAG AA contrast checking in the theme editor, which warns and confirms rather than blocking, and that is a starting point rather than a VPAT.
  • No public-records retention scheme, no FOIA workflow and no compliance certification of any kind.
  • No ticketing or payments.

Last updated

What it costs

Free up to 50
activated attendees, on one live event
$5
per activated attendee beyond 50
$4,750
the most one event can ever cost, whatever happens past 1,000

Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.

See the full pricing

Questions people actually ask

Does event67 satisfy open-meetings law?

That is not a claim we can make, and any vendor who makes it about your jurisdiction should be treated carefully. event67 provides an agenda, question collection with voting, a moderation queue and an archive. Whether that meets your statutory obligations is a determination for your own legal team, and in most jurisdictions the streaming requirement alone means event67 is part of a process rather than the whole of it.

Can the meeting be broadcast through the app?

No. There is no video streaming of any kind. If you are required to broadcast, run the stream on your existing platform and use event67 for the agenda, the questions and the record.

Is there a VPAT or an accessibility conformance report?

No. What exists is a WCAG AA contrast check in the theme editor that warns and confirms before a save, and it never blocks one. For a procurement that requires formal conformance documentation, that is not sufficient and we would rather say so now.

Can residents submit questions anonymously?

No. Questions are attributed. For a hearing on a sensitive local matter this can suppress participation, and it is worth weighing against the improvement in question quality that attribution produces.

Who can see the questions?

Attendees in the meeting see the ranked list, and organizers see everything in the console. The event itself is not indexed by search engines and is visible only to people you invite, so publishing a public record of the questions is a deliberate act you take, not a default.

Let the room decide which question is first

Questions collected during the notice period, ranked by attendees, and every moderation decision logged.