Participation is a system, not a livestream: what London’s People’s Question Time makes visible

Participation is not created by opening a microphone. It is created by the rules, channels and follow-up that determine who can enter a conversation and what happens once they do.

London’s People’s Question Time, held in Islington on 21 October 2026, is a useful current example. City Hall described a free two-hour event with an in-person audience, a livestream and a route for registered online participants to submit questions. It also published specific accessibility support and clear limits on capacity and question selection.

The lesson for community organisations and local businesses is not to copy a civic meeting. It is to treat participation as a service journey rather than a promotional promise.

Access is a stack, not a single feature

The event page lists British Sign Language interpretation, live speech-to-text reporting, an induction loop and wheelchair access. It says a transcript can be requested after the event. The livestream could be watched without registration, while registration was required to submit a question online.

Those details matter because “hybrid” only describes the channels. It does not tell someone whether they can understand the discussion, contribute to it or revisit it afterwards.

For a small organisation, the equivalent stack may be simpler: step-free venue information, captions, a named contact for adjustments, plain-language instructions, remote participation and a written summary. The important point is to design the whole route before announcing that an event is open to everyone.

City Hall’s Public London Charter makes a related distinction between a space being present and a space being genuinely public. Its principles include welcome, openness, community focus, free access, privacy, transparency and good stewardship. The guidance also says community-led and cultural activities should reflect London’s diversity, and that rules should be developed transparently with communities.

That is useful beyond planning policy. A community event can be free and still contain hidden costs: travel, time, childcare, confidence, registration friction or uncertainty about what will happen in the room.

Publish the selection rule before asking for contributions

People’s Question Time did not imply that every question would be heard. The page explains that in-person contributors would be selected from the audience, online participants could vote on questions, moderation would apply, and selection was not guaranteed. It also asked participants to keep to one concise, relevant question.

These constraints are not automatically exclusionary. Time and capacity are real. The design question is whether the constraints are visible early enough for people to make an informed choice.

A local forum, creative workshop or business roundtable should therefore publish four things before collecting contributions:

1. who can participate;
2. how contributions will be selected;
3. what moderation removes;
4. what happens to useful contributions that do not fit the live session.

The fourth point is often missing. City Hall’s page provides a route to contact the Mayor when a question is not chosen. In a smaller event, that might be a published Q&A, a short response document, a second session or an explicit list of decisions the organiser will take forward.

Without that route, “have your say” can become a collection exercise rather than a relationship.

Measure opportunity, contribution and consequence separately

Attendance is easy to count. Meaningful participation is harder.

A practical event dashboard should separate at least three stages:

• Opportunity: registrations, accessibility requests fulfilled, livestream access and no-show or drop-off patterns.
• Contribution: questions submitted, people speaking, workshop inputs or ideas captured.
• Consequence: responses published, decisions changed, commitments assigned and follow-up completed.

This prevents a large audience from being mistaken for broad participation. It also stops a small but useful working session from looking unsuccessful simply because it did not generate a large reach number.

The event page reviewed for this article describes the intended participation architecture; it does not establish who attended, whose questions were selected or whether the process influenced later decisions. Those outcomes require post-event evidence.

The counterpoint: more channels can create more friction

Adding a livestream, chat, registration platform, accessibility support and follow-up route creates operational work. Every channel needs ownership, moderation and testing. A small team can make participation worse by promising five routes and managing none of them well.

The answer is not maximal complexity. It is a smaller number of dependable routes, chosen around the people the event is meant to involve.

Before the next announcement, draw a one-page participation map. Start with the audience, then record the entry route, access support, contribution method, selection rule, response owner and follow-up date. Test it with someone who did not write the event copy.

That map is the real creative brief. The poster and social posts can invite people in, but only the participation system determines whether they can take part with confidence.