Solo Community Enterprise Pricing About Blog Request a Demo

Introducing Credentials Tracking: Know Who's in the Room at Your Next Grand Session

A new in-app module for Groupable customers running credentialed meetings. Define which offices need to be represented, check members in, log proxies, issue ballots and voting fobs, tally votes, and watch a live report of who's represented and who isn't. All without leaving the platform your jurisdiction already uses.

The Saturday-morning sign-in table.

Every Grand Session starts the same way. A long folding table at the entrance. A stack of printouts run off Friday night. A box of name tags, a Sharpie, a pile of yellow highlighters, and whatever combination of laptops, tablets, and paper your committee is set up to work with.

Members arrive in waves. Names get checked off. Proxies, written on the back of dues cards or printed on jurisdictional letterhead, get matched to the lodges they cover. A runner walks the latest tally up to the dais every fifteen or twenty minutes, where someone reads the count and writes it on a whiteboard.

While that's happening, the questions leadership needs answered are still in motion. How many locals have a quorum represented right now? Is District 5 over-proxied? Did we hit the threshold to open ballot? Which locals haven't sent anyone, and is there still time to call them?

A smoothly operating credentials committee is genuinely impressive work, whether they're running it on clipboards and Sharpies or on the most current tools available. That work is the foundation the rest of the session is built on, and we like making it easier. Less time at the sign-in table. The information the committee needs at their fingertips. Progress reports during the session and final reports at the close, both at the click of a button.

The information has always existed; it just hasn't been pulled together in real time. Now it can be.

What Credentials does.

The Credentials module gives Grand Bodies a single place to manage every moving part of a credentialed meeting, from the moment a member walks up to the sign-in table to the moment the last vote is recorded.

Define which offices need to be represented for a given event. Specify the slate per local: Master, Senior Warden, Junior Warden, Treasurer, Secretary, whatever your jurisdiction's code requires. The system knows what "fully represented" means for your session before the first member walks in.

Check members in on arrival, and record the office they hold. A credentials clerk uses Groupable on a tablet or laptop at the sign-in table. A member walks up, says they're representing Anchor Lodge No. 47 in the Senior Warden's office. The clerk taps the entry, or scans the barcode on the member's dues card to pull the record up instantly. The local's seat at the session (its representation slot, not a chair in the room) is now filled; the live count on the dais just moved.

Log proxy assignments when a member cannot attend. Written proxies get entered as proxies, not as direct attendance. They count toward representation, but they're flagged differently. That distinction matters more than it looks. A contested proxy is a much shorter conversation when it's timestamped in a system instead of reconstructed from a stack of slips.

Issue ballots and assign voting fobs at check-in. Every credentialed member gets a ballot number, recorded against their name and the office they're filling. If your jurisdiction uses electronic voting fobs, the fob is assigned to the member at the same moment, in the same workflow. No separate sign-out sheet, no second clipboard, no reconciling two lists at the end of the day.

Tally votes and produce a defensible count. When a vote is called, the system already knows who is credentialed to vote, which fob is assigned to which member, and which proxies count toward which totals. The tally is produced automatically against the credentialed roster, with every ballot, fob, and proxy attributed. The count that gets read into the minutes is the count the system produced, with the underlying detail preserved.

Watch a live report showing check-in status, proxy coverage, ballot and fob assignments, and representation by local, with drill-down to individual unit detail. The Grand Master and the credentials chair can see, in real time, exactly which locals are fully represented, which are proxy-only, and which are absent. The same data the credentials committee is collecting is the same data leadership is looking at, without a runner walking it across the room.

A walk-through at a Grand Session.

7:45 AM. Credentials clerks set up at the sign-in tables. Each clerk has a tablet logged into Groupable. The session was pre-configured earlier in the week with the slate of offices and the list of locals expected to send representation.

8:00 AM. Members start arriving. Physical or digital dues cards come out, barcodes get scanned, and the records pop up on the clerk's tablet without a name-search lookup. Each member is checked in by name and office, issued a ballot number, and handed a voting fob if the jurisdiction uses them. The system records the exact office the member is filling, the ballot number, and the fob ID, all in the same workflow.

8:30 AM. The Grand Master pulls up the live report from the dais. 60% of locals have a quorum represented. 18 locals are still entirely absent. Two locals are over-represented and the system flags it. The Grand Secretary makes a note to call the absent locals before the morning recess.

9:30 AM. The floor opens. The credentials report is no longer a piece of paper read into the minutes. It's the same live data everyone on the dais is already looking at, projected on the screen behind the East if the session is set up for it.

11:15 AM. A vote is called on a question of charter. Members vote with their assigned fobs. The tally is produced automatically against the credentialed roster, with every ballot, fob, and proxy attributed. The Grand Secretary reads the count straight off the system, and every detail underneath it (who voted, who was credentialed but didn't, which proxies counted) is preserved for the record.

After the session. Every check-in, every proxy, every filled seat at every local is in the historical record. Year-over-year comparison becomes possible without retyping anything. Which locals consistently under-send? Which districts are growing or shrinking? Those questions used to live in a banker's box; now they live in a query.

Not just the annual session.

The annual Grand Session is the obvious case, and it's where the module earns its keep. But Credentials is in the app, usable any day of the year, for any meeting where it matters who's in the room and who's eligible to vote. Quarterly communications. Special sessions. District meetings. Trustee meetings. Foundation board votes. Disciplinary proceedings. Anything credentialed.

If you're coming from the MORI Attendance App, this is now integrated into Groupable and available year-round. Same accuracy, more power, easier proxy registration. The tools speed up check-in, ballot issuance, and fob assignment in a single pass at the table.

If you're coming from a manual process (printouts, highlighters, runners to the dais), check-in moves at the speed of a tap instead of a handwritten check-off. The line at the sign-in table will be shorter than you've seen it.

Why this matters beyond the session.

The day-of benefit is obvious: the credentials committee's job gets easier, and leadership sees what's happening as it's happening. The deeper benefits are slower to notice and harder to lose, once you have them.

Quorum decisions become defensible. When the floor questions whether quorum was met for a particular vote, the answer is in the system, with a timestamp.

Vote counts become defensible too. Every ballot, every fob, every proxy is attributed against the credentialed roster the system was already maintaining. A contested count stops being a debate and starts being a query.

Equity of representation becomes visible. Locals that didn't send anyone are visible during the session, not after, when there's still time to call them.

Proxies become an audit trail. Every proxy is recorded, attributed, and timestamped. Disputed proxies stop being a question of memory and start being a question of record.

Sessions become comparable across years. Patterns that take a decade to see by feel show up clearly when the data is in one place. Which locals are slipping. Which districts are growing. Which offices are routinely going unfilled.

Each of those deserves its own post. This is the introduction.

How to turn it on.

Credentials is available now, on request, for current Groupable Enterprise customers. Email support@groupable.com and we'll enable it for your jurisdiction and walk your credentials chair through setup before your next session. There is no separate Credentials subscription, no add-on tier, and no per-clerk fee. It's part of Enterprise.

For Grand Bodies that don't yet use Groupable: Credentials is part of the Enterprise tier alongside the rest of the platform, including the shared Groupable Inbox for your officer team and Grand Body staff. If you're evaluating a platform for your jurisdiction's session management, request a demo and we'll show you Credentials as part of the broader walkthrough. ( See current pricing. )

Ready to make your credentials committee's job easier?

If you're already a Groupable Enterprise customer, email support@groupable.com and we'll turn on Credentials for your jurisdiction. If you're evaluating Groupable for a Grand Body, we'd love to walk you through the module live, and get into the harder questions about quorum, proxies, and representation that a blog post can't fully cover.

Request a Demo