When a lodge secretary can't figure out the software, the call goes to the Grand Lodge office. That moment is so familiar nobody questions it. It's also where a quiet, expensive problem lives.
It's a Tuesday afternoon. The lodge secretary in a small lodge three hours from Grand Lodge headquarters can't figure out how to run the arrears report. They've been fighting the software for twenty minutes. They do what they always do: call the Grand Lodge office.
Somewhere in that office, a paid staff member puts down what they were working on and tries to help.
That moment, perfectly normal and widely accepted, is where the problem lives.
Under the typical grand lodge software support model, the chain runs like this:
The software vendor supports the Grand Lodge. Specifically: the Grand Secretary, maybe the Grand Webmaster, and a handful of people who went through onboarding. Those are the people the vendor knows by name. Those are the calls the vendor takes.
The Grand Lodge is then responsible for supporting the subordinate lodges. So when a lodge secretary, treasurer, or membership chair has a question, the call comes back to the Grand Lodge office. A staff member there picks up. An administrator. A program coordinator. Maybe a Grand Secretary's assistant.
That staff member tries to help based on what they remember from their own training. In that moment, they're running a help desk.
Here's the structural problem: those staff members were never hired or trained to run a software help desk. They learned the system the same way the lodge secretary did. They're passing along the best answer they have, filtered through what they remember from their own training, while also doing the jobs they were actually hired to do.
This isn't a criticism of Grand Lodge staff. It's a structural problem built into the support model itself. Lodge secretary software help is being provided by people who were never hired or trained to provide it.
The cascade is predictable, and most Grand Lodge officers can name parts of it from memory:
Questions don't get fully answered. They get %em managed. The secretary asking about the arrears report gets a workaround that addresses today's question and not the underlying gap. The workaround works until it doesn't.
Errors compound. A lodge secretary uses the wrong field for two years. Reports come out a little off. Nobody catches it until an audit, or a transition, or a situation where the data has to be exactly right and isn't.
Training never reaches the front lines. The people who use the software daily (lodge secretaries, treasurers, membership chairs, registrars) get whatever Grand Lodge staff can pass along, working from the same partial training they received themselves.
Grand Lodge staff spend time they don't have answering questions they weren't hired to answer. Their actual work, the work the jurisdiction is paying them to do, gets pushed to the edges of the day.
And the system itself, which was bought to do far more than it currently does, sits underused. Not because the platform can't do the work. Because the lodge users haven't been given the support to use it fully.
There's a structural reason for that, too. The vendor never needed to design the platform to be self-supporting, because the vendor's support model presumed somebody else (your Grand Lodge staff, your overworked secretaries) would absorb the questions. Software designed for admin-tier expertise stays opaque to volunteer users, by default. The under-use isn't an accident. It's the predictable result of a product that was never built to teach itself.
In February 2026, at the Conference of Grand Masters of Masons in North America, one major membership software provider announced a new Professional Services support tier, starting at $1,250 per month, $15,000 a year, to provide end-user support.
Read that carefully. End-user support (the support that lodge secretaries and officers actually need) is now a paid add-on.
This isn't a product enhancement. It's a public acknowledgment that the base product does not include the support the people who actually use the software actually need. Every current client of that vendor now has a choice. Pay significantly more for professional support, or keep absorbing the cost themselves: office-staff budget and volunteer time spent on software answers from people who aren't software experts.
For Grand Lodge leaders reading the announcement at CoGM, it forced a question many had never quite put into words: %em When our lodge secretaries call us for software help, who are we exactly? Are we running a help desk?
The answer, for most Grand Lodges, is: yes, quietly, they have been. For years.
There's a different version of this. It looks like this.
Lodge secretaries and officers have a direct line to people who built and run the software. People whose entire job, every day, is to know the system inside and out. Questions get answered confidently, not passed along filtered through three layers of memory. The answer is the answer.
That includes how-to questions. "How do I run the arrears report?" "How do I update a member's contact information?" "Why isn't my dues renewal notice going out?" Those aren't questions that should bounce up to the Grand Lodge office and back down again. Lodge users should be able to reach the vendor directly and get a real answer from someone who knows the system.
Training extends all the way to the lodge level. Not just to the Grand Lodge staff who attended onboarding. Live sessions, scheduled frequently enough that the Junior Warden who took over the membership records last fall has somewhere to learn the system, and somewhere to call when they're stuck. Real people who know the software, in the room with the people who need to learn it.
When a new secretary takes over from the one who's been doing it for fifteen years, the support they need is there from day one. Not dependent on what the previous secretary remembered to pass along. Not dependent on what the Grand Lodge happens to recall about a system they don't use daily.
Frankly, it's not complicated. Software answers come from the software company. Organization answers come from the Grand Secretary, or your equivalent. The lodge secretary's questions don't all belong in the same place, because they aren't all the same kind of question. Right now, in most jurisdictions, both kinds of questions land in the Grand Lodge office, and only one of them belongs there.
Here's the question to take back to the next executive committee meeting, or the next conversation with your Grand Secretary:
When lodge secretaries call with software questions, who answers? How confident are those answers? How much time does it cost the Grand Lodge office over the course of a year, and what is that time actually costing your jurisdiction, in distraction, in compounding errors, in capabilities never used?
And if you've signed up for a Grand Body support arrangement with your software vendor, separately priced and added on top of your subscription, the question gets sharper. Are you getting the right answers from that arrangement, in a timely fashion, when your lodge secretaries actually need them? Or are the answers still coming back through your Grand Lodge office anyway, just with a higher bill attached?
There's a deeper question worth raising at the same table. Many of the questions a lodge secretary needs answered aren't really software questions at all. They're jurisprudence questions. Questions about how your jurisdiction's rules apply in a particular situation. What counts as a quorum. When a transfer is permissible. How a disciplinary matter affects a member's standing. How a dispensation is granted. Those questions belong with your Grand Secretary or your Committee on Jurisprudence, not with a vendor support desk. A software vendor can tell you how the system works. It cannot, and should not, tell you how your jurisdiction works.
The Grand Lodges that have thought carefully about this are asking these questions before they sign the next contract. Not after.
Groupable's help desk reaches every level of your jurisdiction (lodge secretaries, officers, members) as a standard part of the relationship, not a separately priced tier. How-to questions, troubleshooting, onboarding a new secretary: any user can reach us directly. We also run ten live training sessions every month so your people can learn the system from a real person, not a help article. The goal isn't to be a better outsourced brain. It's to give the organization the tools to keep its own. If you'd like to see what that looks like in practice, we'd be glad to show you.
Request a Demo