Gavel Suite

Lodge work is sacred. The administrative work around it shouldn't take an evening every week. Gavel Suite is the day-to-day toolkit for the officers and members of a fraternal lodge — Masonic, Elks, Moose, Odd Fellows, Knights of Columbus, and anything chartered along similar lines.

What it is

Gavel Suite is modern operations software for fraternal lodges. Calendar, dues, member records, communications, and an AI assistant that answers procedural questions out of your own bylaws and proceedings — not a generic LLM that's never read your obligations.

It is not a replacement for your Grand Lodge's system of record (Grand View Systems, MORI, or otherwise). Those remain canonical. Gavel Suite sits alongside, plays nicely with what's there, and exports cleanly when an upstream system needs the data.

The architecture targets a multi-tenant SaaS, with strict tenant isolation enforced at the database via Postgres Row-Level Security — each lodge's data stays inside its own walls.

What it does well

Configurable terminology, one product. The same Gavel Suite serves a Masonic Lodge, an Elks Lodge, and a Moose Lodge. Each picks a profile at onboarding; the labels follow. Trestleboard, schedule, calendar — whatever you call it in your tradition, that's what the interface says.

Hybrid AI privacy — the part that matters. Non-ritual documents (announcements, minutes, public bylaws, dues correspondence) use cloud LLMs for quality. Ritual-marked documents stay on infrastructure under the tenant's contractual control — embeddings, retrieval, and generation never touch a cloud LLM. The fail-closed default protects what belongs inside the lodge room.

The boring parts, handled. Dues tracking with auto-reminders. Member records with attendance, dates, degree progression. Officer rotation calendars. Communications that don't require the Secretary to maintain a personal email list.

Hosted by default. Self-hosted for the enterprise tier. Grand Lodges that want their own deployment can license a Docker Compose bundle and run it on their own infrastructure.

Who it's for

Lodge Secretaries and Treasurers who spend more hours on the records than on the work.

Worshipful Masters / Exalted Rulers / Noble Grand / Grand Knight — the officer running the lodge for the year, who needs to plan twelve months of meetings, dinners, degrees, and community work without losing the thread.

Members who want to know what's on the calendar without calling the Secretary.

Grand Lodges and supreme bodies looking for software that respects the structure of their order rather than retrofitting a generic CRM.

What it looks like in practice

A Connecticut Blue Lodge onboards onto Gavel Suite. The Secretary imports the current roster from the Grand Lodge's MORI export. The Worshipful Master enters the trestleboard for the year. The Treasurer turns on dues auto-reminders. The AI assistant ingests the lodge's bylaws and proceedings — marked as ritual content, so processing stays on tenant infrastructure. A Brother asks "what's the rule on visitors at a stated communication?" and gets the answer cited to the lodge's own bylaw.

What it's not

It's not a replacement for the Grand Lodge system of record.

It's not a public-facing community management tool. Lodge content stays inside the lodge.

It's not a one-size-fits-all CRM bolted onto a fraternal vocabulary. The terminology, the privacy posture, the calendar structure — all of it is built knowing what a lodge is.

Status

Pre-alpha — documentation-and-design phase. Connecticut single-lodge POC is the first launch target, followed by CT-statewide rollout, then multi-state. Tech: .NET 10 core API + Next.js 15 PWA frontend + Python 3.12 AI microservice. Reach out if your lodge is interested in being part of the POC.