The club,
in one place.

Every QRID member gets a feed the moment they sign in: their own club's notices, musical evenings, and committee announcements, alongside anything from the other clubs they hold reciprocal or dual membership at. Nothing is public by default. Visibility follows the club, not the internet.

A member directory replaces the printed handbook: search by name, profession, or shared interest, and follow the people worth staying in touch with. Every member gets a profile, a public handle for the ones they choose to share, and a showcase for the ones who want to put their work in front of the club.

A club's membership categories become classes in QRID: full, associate, life, junior, corporate, whatever the club's bylaws define. Each class carries its own dues plan, its own privileges, and its own path in. An application records a sponsor and a seconder the way the committee's minute book always has, and standing (good standing, in arrears, suspended) is a fact the system tracks, not a spreadsheet someone updates by hand.

Dues post to the house account automatically on the class's billing schedule. A member's standing and their house account balance are the same record the front desk, the treasurer, and the member's own app all read.

What's On carries the club's whole programme, weekly rituals and one-off evenings alike, with cross-club discovery for members who want to see what partner clubs are hosting. A member RSVPs from the app; the ticket is a QR code that scans at the door, no printed list, no plus-one confusion.

Capacity, waitlists, and member-versus-guest pricing are set per event. Attendance feeds straight back into the club's records, so a well-attended series is a fact the committee can see, not an impression.

AGMs and EGMs run as scheduled ballots inside the app: motions, candidates, and a voting window the constitution defines. Members vote once, proxies are recorded and checked against eligibility, and the tally is produced from the same record the vote was cast into, not re-keyed afterward.

Committee terms, officer elections, and standing sub-committees live in the same governance module, so a club's constitution becomes a configuration, not a set of rules only the secretary remembers.

A member travelling to a reciprocal club carries a letter of introduction and a digital membership card in the app, not a fax from the secretariat. The visiting club can verify standing on the spot, and the visit itself becomes a record: where a member has been, and who has visited home.

Reciprocity is configured club to club, agreement by agreement, so a club can extend access to the partners its committee has actually approved, with the privileges those partners agreed to.

Rooms, courts, the spa, the golf tee sheet, the library reading room, the banquet hall: each is a bookable resource with its own hours, its own capacity, and its own rules for who may book it and how far ahead. A member books from the app; the front desk sees the same calendar.

Double-bookings stop being a front-desk problem, and a facility that is quietly under-used becomes visible to the committee instead of invisible.

The bar and dining room run on a point of sale built for a club, not a restaurant chain: a chit can go straight to a member's house account instead of a card machine, exactly the way clubs have always run a tab. The kitchen gets tickets, the till gets a close, and the member gets one statement at month end, not a drawer full of paper.

Recipes, costing, and stock sit underneath the till, so the dining room's numbers are part of the club's numbers, not a separate business run on a separate system.

Underneath the member-facing app is a full accounting kernel: a general ledger, house accounts standing in for accounts receivable, dues billing, and the postings that facilities, events, and the dining room all write into automatically. A treasurer gets real financial statements, not a reconciliation project every month end.

These are the club's books, and the club's money. Dues are owed by a member to their club and recorded in the club's ledger, and every payment the club collects runs through the club's own payment gateway: QRID never holds or processes the money. The books stay the committee's, the bank account stays the club's.

QRID runs on the KaritKarma Business Kernel, the same accounting and operations engine used across KaritKarma's business platforms. A club gets enterprise-grade books without needing an enterprise finance team to run them.

A club that joins QRID keeps its own name, its own domain, and its own public site, built and themed to its identity. Members sign in once across qrid.club and move between every club they belong to; each club's own domain carries that club's public face and its club-scoped member app.

Underneath, every club runs on the same kernel: the same accounting, the same booking engine, the same governance module, configured per club rather than rebuilt per club. A new club onboards onto infrastructure that already works, instead of a bespoke build.