How a lodge keeps attendance without a paper roll

Take attendance from the same meeting you already used for the summons and the dining count, then store it on the member so the lodge can see a year, and several years, without retyping a sheet.

That is the whole job. Mentoring conversations, a resignation that should not have been a surprise, and whatever return the lodge already prepares all get easier when the history exists. None of those uses is a reason to invent a second book.

A successful lodge treats the roll as part of closing the night, not as optional paperwork if someone remembers the clipboard. Paper on the night is fine. A paper sheet that never reaches the member is how the year disappears.

A paper attendance roll is often accurate for the evening. It is useless three years later. The sheet is in a Secretary box, a past Master's loft, or a scan that nobody named. When the lodge later asks who has drifted, the answer is a hunch.

Retyping the sheet into a spreadsheet once a year is how errors multiply. Names are spelled two ways. A visitor is marked as a member. A brother who dined but did not sit the meeting is counted as if he sat. The next officer inherits a file he does not trust, so he starts again.

The operational failure is not the paper itself. Paper on the night is fine. The failure is that the night never becomes a member history. Resignations then look sudden. Mentors telephone into a vacuum. Anyone preparing a return the lodge already files has to reconstruct the year from memory.

A shared drive full of unnamed scans is not a history either. If the file is called Attendance or Scan 3, a successor still has to open every image and guess which meeting it belongs to. The test is still the same. Can he open one member and see the year, or must he reconstruct the year from a box?

Attendance belongs on the meeting, then on the member. The summons already named the date, the place, and the sitting list. The RSVP already collected a planned answer. After the night, the roll should update that same record, not open a second book with a second spelling of every name.

If the Secretary types the roll into a document that never touches the member, you have only moved the clipboard onto a laptop. Next year the document is as lost as the sheet. A PDF of last installation's register is still a file someone has to remember exists.

Keep visitors and guests on the meeting so they do not pollute member history. Keep apologies as a state, not as a missing tick. A blank is not an apology. A blank is work you have not done.

One source of truth means the brother who was there is the same row the Steward used for dining and the same row the Treasurer used if the lodge charged. Three lists with three versions of the night is how committee arguments start. The summons and RSVP guide on this site stays on the week before the night. This page is the write-back after it.

A planned yes is useful. It is not the roll. Brethren change plans. Some send no reply and still arrive. Some reply for dining and do not sit the meeting, or sit the meeting and do not dine. If you copy the RSVP list into the night's record as if it were attendance, the history is already wrong.

Capture sitting the meeting and dining as separate answers on the way in, then mark who actually came after the night. The Steward's count and the attendance roll are related. They are not the same list. A kitchen cover is not a tick on the roll. A tick on the roll is not a plate.

How the lodge opens, works, and closes is not this page's subject. Who was present, who dined, and who sent an apology are organisation facts. Record those. Leave the rest in the lodge.

Chase non-replies before the night if you want a better plan. Still take the roll after the night. Planning software that never gets a write-back is only a nicer clipboard. A product that lets a brother confirm from the summons is still collecting a plan unless someone later marks who was actually there.

Guests sit on the meeting, with a name. They do not sit on a member history they do not have. A guest who is marked as a brother is how the roll becomes fiction, and how a later year-count looks healthier than the sitting list.

Visitors from other lodges belong on that night as well. They are hospitality for the evening, not a reason to invent a second membership row. If your process cannot tell a visitor from a sitting member, the year you later export will mix two different jobs.

An apology is a state you record. It is not a missing tick, and it is not a dining no the Steward can treat as a kitchen fact. A brother who apologised is not the same as a brother who vanished. If you invent apologies at year end to tidy the file, the history will look complete and still be a lie.

Do not treat silence as an apology. Do not treat a dining yes as presence. Do not treat a guest as a member. Those three mistakes are how a paper sheet, and a digital sheet that copies it, both fail the handover test.

Once attendance sits on the member, the lodge can see a pattern without a forensic weekend. A brother who has missed a run of meetings is visible. A brother who always dined and has suddenly stopped is visible. That is a reason for a mentor or an officer to telephone, not a reason to publish a league table.

Resignations rarely surprise the brother who left. They surprise the lodge that was not looking. Attendance history is one fair signal. Dues history is another. Neither is a crystal ball. Both beat a hunch in January. The members-at-risk guide on this site stays on that next action. This page only needs the rule that the signal is fiction if the roll never reached the member.

This article will not invent UGLE or Provincial return rules, forms, or deadlines. Those belong to the bodies that publish them. If your lodge already prepares a return, years of attendance on the member is how you stop retyping a paper book into that return. The form is theirs. The history is yours to keep well. We will not tell you what to file, or when.

Mentoring is the other quiet use. A new member whose attendance has thinned is a conversation, not a dashboard trophy. The record should be good enough that the mentor is not guessing which nights were missed. Keep the wider lodge out of that conversation. A roll that becomes a public ranking has stopped being a register.

Treat attendance as the last step of the meeting record, not a Saturday chore. The night has a list, a mark, and a write-back. If any of those live on a different clipboard from the summons, the night does not close. It just ends.

The night can look tidy and the year can still be lost. A Secretary who keeps the roll in his head, or in a private folder, has closed the evening for himself. He has not closed it for the lodge.

Write the year as if the next Secretary will open it with no handover meeting. The sitting list that was mailed. Who replied. Who sat. Who dined. Who sent an apology. Who was a guest. If those answers need last year's phone, the lodge does not have a register. It has a volunteer.

Corrections belong on the same record. A past night that was marked wrong should be fixable by someone the lodge has already trusted with the roll. A history nobody can correct becomes a history nobody trusts, so the next officer starts a new sheet.

Who may take the roll is a lodge decision. This page will not invent an office for it. The operational rule is narrower. One list, one night, one write-back, and a successor who can still see it.

The Working Tools is a secretary operating system. We re-checked the public homepage, features page, and pricing page on 7 September 2026. Pricing is £5.00 a month per lodge, extra lodges at £3.00 a month, and a 30-day trial. An annual payment option is published. Delegates do not pay extra.

The same public site lists creating and managing events, tracking attendances, creating table plans, and generating a summons. The features page says the event planner has invitations and attendance built in, that membership records include attendance, and that reporting can show per-meeting attendance and attendance over time. It also publishes an easy handover to a successor. That is a fair cheap digital register if the lodge wants a secretary desk and is happy to keep money and Gift Aid elsewhere. Those pages did not describe Gift Aid or GASDS reclaim. We will not invent it. Confirm on their walkthrough whether a planned reply and the night's roll are different states, and whether a successor can open one member's year without exporting a folder of nights.

Lodge Master 5 (lodge-master.co.uk) loaded for us on 7 September 2026. The public page describes tracking attendance for meetings and festive boards, members and non-members filling preferences, hosting the summons, a public sign-up link, dietary requirements, attendance reports for the DC, WM, Treasurer, and Secretary, export to Perfect Table Plan, and Stripe. It did not publish a price. Contact on the page is john@lodge-master.co.uk. In their own words, a +1 guest must register as a visitor until the next major release. We will not add a member-history write-back their page does not state. Ask whether those attendance reports live on the member, or only on the night.

Lodgical (lodgical.app) is a web-based membership system for Secretaries and Treasurers. On 7 September 2026 the public site listed Membership, Meetings, Officers, and Summonses for Secretaries; a Summons Reply, Member Record, and Member Account for members; and Bank Accounts, Subscriptions, and Dining Dues for Treasurers. They offer a demonstration lodge with two years of sample data, and a live trial with your own lodge data. Price was not published on the pages we checked. We will not add an attendance product their site did not state. Ask whether the night's roll writes back to the member record they publish, or only sits on the meeting.

Lodge Manager (lodgemanager.co.uk) publicly describes membership information, sending lodge material, meeting reminders, a multi-lodge view for members, and a prompt for who still needs a postal copy. On 7 September 2026 the public homepage, and the /pricing path, did not confirm a price. An older line about yearly fees could not be reconfirmed. Do not quote a Lodge Manager price in committee from this page. We will not add attendance features we did not see.

Buy a cheap secretary desk if the pain is the Secretary's hours and the lodge is happy to keep money elsewhere. The Working Tools at £5.00 a month is a rational buy for a register, a summons, and a table plan, especially if their published attendance-over-time reports are the history the next Secretary will actually open. Lodgical is a rational look if you want members to reply to a summons and you are willing to ask how the roll is stored, once you have asked them for a price they do not publish. Lodge Master 5 is a rational look if the brief is festive-board attendance reports beside a hosted summons. Lodge Manager may be enough if the brief is membership records, reminders, and a postal chase list.

That is not faint praise. A lodge drowning in paper sheets is allowed to buy the tool that publishes a digital register. Stay honest about the edge. If unpaid dining, a bank that does not match, and unclaimed Gift Aid are the actual complaints, you are buying a different job. The compare page for The Working Tools on this site stays on that distinction: a secretary OS versus a lodge OS.

Some lodges will run a cheap register and a separate payments habit for a while. If you try that, keep one source of truth for who sat and one for who has paid. Two lists with two spellings of every name is how the Secretary and the Treasurer argue in the car park. The festive-board software guide on this site stays on the dinner. The Treasurer and Gift Aid pages stay on the money. This page only needs the rule that the roll and those other jobs should not invent a second sitting list.

Once the lodge owns the roll, software is a way to stop it living in one brother's box. LodgePay treats the meeting as the spine: date, location, meeting type, agenda, attendance. From that record the Secretary can view, edit, print, and send the summons. Send history is kept. Members open a tokenised public link or the member portal. The meetings and summons page on this site is that desk.

RSVP and the roll sit on that same record, and they are not the same mark. Sitting the meeting and dining are captured separately. Guests, dietary notes, payment status, and apologies sit on one event. When attendance is taken, it feeds the member history. That is the same record the Secretary used for the summons and the Steward used for dining numbers. Nobody copies names into a second book. Years of data sit on the member without anyone retyping a sheet.

Over time the lodge can see who has drifted. On Complete, LodgePay's published name for that later work is members-at-risk insights: brethren drifting from attendance, dues, or engagement. We are not claiming a crystal ball. If the roll was never written back, the insight is a hunch with a chart.

If the lodge also wants the night's money and Gift Aid on the same meeting, dining can sit beside the RSVP. Card payments go through Mooov. Standard processing fees pass through at cost. Gift Aid uses the declaration already on the member. The lodge files the HMRC pack. LodgePay does not take the reclaim. A typical 30-member lodge illustration already on the Gift Aid and pricing pages is £1,125 a year (£225 from dues, £900 from eight festive boards) plus GASDS on cash up to £8,000. Those figures assume the nights were recorded. A paper yes never became a line, so it cannot be reclaimed.

Published prices, as on the pricing page: Essentials from £149 a month billed annually (or £169 monthly), Complete from £229, Group from £349, Province from £2k a month plus £35 per lodge (typically £4,500 a month). Those figures do not write the roll. There is no setup fee.

If you only need a cheap digital register, The Working Tools may be enough. We will not trash it. If you want festive-board attendance reports and a hosted summons, read Lodge Master 5 and ask John. If you want members to reply inside a Secretary and Treasurer desk, ask Lodgical for a price. If the roll must stay on the same meeting as the summons, the dining count, and the member, book a LodgePay walkthrough and ask the questions at the end of this page. If nobody writes the night back, the software will store an empty year.