‹ Back to LodgeWise ABOUT

Why LodgeWise exists

Built by a working Mason for his own lodge first.

The problem every Secretary already knows

In most lodges, the Secretary is the lodge. He is the institutional memory — the one who knows which brother paid, who hasn't renewed, which Past Master to call when a degree team needs a fill-in. He keeps that knowledge across a combination of spreadsheets, a folder of scanned minutes, a group text chain, and software that hasn't changed its interface since the Clinton administration.

iMember has been the default for many jurisdictions for years. It works — barely. The UI predates smartphones. Imports break. The mobile experience is an afterthought. When the Secretary who set it up retires, the institutional knowledge leaves with him and the new Secretary inherits a system he has no idea how to run.

The problem isn't that lodges lack digital tools. The problem is that the tools weren't built for lodges — they were built for generic membership organizations, then shoehorned in. A Masonic lodge is not a generic membership organization. It has officers, not staff. Degrees, not onboarding workflows. Minutes that are reviewed and approved in open lodge. A Grand Lodge that requires an annual return in a specific format. An obligation of confidentiality that goes far beyond an NDA.

Why a working Mason had to build it

LodgeWise started because the builder needed it for his own lodge. The Secretary of his home lodge was doing what every Secretary does: juggling a spreadsheet, a pile of returned cheques, and a stack of last year's summonses. Something better had to exist. It didn't. So it got built.

Because it was built by someone who sits in lodge, it starts from the right place. The architecture respects the confidentiality obligations that every Master Mason takes. The feature set maps to the actual work: tracking dues, managing the officer line, producing the annual return, sending summonses, coordinating the degree team. Not "membership management for nonprofits, adapted for lodges."

LodgeWise is not a venture-backed SaaS company optimising for user-growth metrics. It is one Mason building a tool he genuinely needs, making it available to other lodges, and keeping it honest.

Three principles that don't bend

BROTHERS, NOT VENDORS

We eat our own cooking

LodgeWise is built by a working Mason who uses it in his own lodge every month. Every feature has to pass one test: "Would this actually help the Secretary on a Tuesday night?" If it doesn't, it doesn't ship.

CONFIDENTIALITY

Esoteric content is never stored

The platform refuses, by design, to store modes of recognition, obligations, ballot tallies, or anything that belongs inside a tyled communication. This isn't a policy — it's an architectural constraint.

OWN YOUR DATA

CSV export, any time

Your lodge's roster, dues history, and event records are yours. Every record is exportable as CSV at any time, with no lock-in and no need to ask permission. If you ever leave, you take everything with you.

Questions about whether LodgeWise is right for your lodge?

Write to the builder

[email protected] · usually responds within a day