Know whether your programmes build anything.

A programme with 36 sessions and a full room every week can still be reaching a different set of people every time. Without a record of who was actually present, nobody can tell the difference between a community and a queue.

Blocks fixed in venues and rooms. Cards in the hands of the staff and ambassadors who work your programming, and with the guests and members who attend it. A host can also check people in from the list. Every method writes the same verified presence record, under consent captured at the moment of capture. No mandatory app download for guests to attend or check in.

The default institutional view is aggregate: unique participants, total presences, first-time versus returning composition, frequency, first-to-second and second-to-third progression, and comparison by programme and location. Small cohorts are suppressed rather than shown. Circuit does not hand you member names, emails, phone numbers or a bulk export of the people who attended.

Institutions support communities they do not control: the ambassador-led run club, the sponsored format, the independent promoter, the resident-led club. Circuit measures whether those communities have depth without absorbing them into your customer database. The organiser keeps the participant relationship. You get the evidence about the programme.

A member carries one Circuit identity between communities, and that does not make their history portable to everyone who supports one. Circuit can understand patterns across independent communities without handing any institution the member graph. If a member chooses to connect their Circuit to an account of yours, that connection is theirs to make and theirs to revoke: explicit, purpose-specific, separate from attendance consent, and never a silent match against a CRM or CDP record.