How an Almoner keeps welfare records discreet

Keep a case for each matter the Almoner is actually working, put visits and alerts on that case, restrict full detail to the Almoner, let the Master see that a case exists, and show the wider lodge nothing.

Software can hold the case. It should not turn welfare into a lodge newsletter. If the process above is not owned, a nicer screen will not create discretion.

The usual failure is silence. Nothing is written down because the Almoner is kind and busy. When the collar moves, the successor hears three versions of the same story in the car park and none of them is a record.

The other failure is the opposite. Too much is written down in a shared inbox, a paper file left in a cupboard, or a spreadsheet that any officer can open. Discretion dies the first time someone forwards the wrong attachment.

A working process is dull and sufficient. A case exists. It has an owner. It has a date of last contact. Follow-up is visible to the people who need it. Everyone else sees a blank.

Do not write medical narrative into a general notes field. Do not invent a pastoral script. Record what the lodge needs in order to act, and stop. The less colour you store, the less you have to protect.

A case is not a public announcement. It is a flag that work is open. The Almoner sees the member, the situation as the lodge has chosen to record it, the support offered, and the people already involved. That is the product language LodgePay already publishes. This article will not add a plot.

The Master can see that a case exists. That is enough to know the Almoner is working, to ask whether help is needed, and to avoid stepping on a conversation that is already happening. It is not a licence to read every line.

The wider lodge sees nothing. Brethren who are not on the case are not entitled to a digest. Committee curiosity is not a purpose. If someone needs to be brought in, the Almoner adds them. If they do not, they stay out.

Closing a case is as important as opening one. An open list that never ends is how last year's private matter stays on this year's screen. Review what is still live. Archive what is finished. Do not delete history you may need for a lawful request, and do not keep live access for people who have left the role.

Discretion is access control, not a personality trait. The lodge decides who holds the Almoner collar. The system should then enforce what that collar can see, what the Master can see, and what a Secretary, Treasurer, or ordinary member cannot.

A useful rule of thumb, and the one LodgePay publishes: the Almoner sees full case detail; the Master can see that a case exists; the wider lodge sees nothing. That is GDPR-shaped discretion. It is not a ruling from UGLE, and this page will not invent one.

Delegates need their own login. Sharing the Almoner's password so a deputy can "just check" is how a case becomes a forwarded screenshot. When the collar moves, remove the old login the same week. Handover is a permission change, not a rumour in the dining room.

Audit the sensitive actions. Who opened the case. Who added a visit. Who changed access. You do not need a courtroom. You need enough trail that a later officer can see what happened without asking the car park.

Follow-up dies when it lives in a personal calendar. The next Almoner cannot see a private reminder. A visit that was promised and not logged becomes another story that cannot be checked.

Put the visit on the case. Put the alert on the case. The officers who are allowed to see the case can see that someone is due to call, or that a date has passed. Officers who are not allowed to see the case see nothing. That is the whole point of sitting welfare beside the record rather than in a side notebook.

An alert is not a diagnosis. It is a next action: contact, visit, or close. Keep the wording operational. If you need more detail than the next officer requires to act, you are probably storing too much.

Installation night is when welfare usually falls on the floor. The outgoing Almoner means to write a list. The incoming Almoner means to ask. Three weeks later both are busy and the lodge is running on hallway briefings.

A clean handover is a list of open cases, last contact, next action, and who else is already involved. The new Almoner receives access. The old Almoner loses it. The Master still sees that cases exist. Nobody else is copied "for information".

If the lodge has been running from memory, do not reconstruct ten years of private history in a weekend. Open cases for the matters that are actually live. Leave the rest unwritten. Inventing a back catalogue is how you create records you cannot defend.

UK data protection law already expects purpose, least privilege, and a lawful basis for sensitive notes. LodgePay's public GDPR page says some customers may store special category or sensitive personal data in Almoner, welfare, compliance, or mentoring modules, and that those modules should be used only where there is a lawful basis and suitable internal governance. That is the published limit. This article will not add legal advice.

In officer language that means: store what you need to support the member, restrict who can see it, keep an audit trail, and do not paste the same text into a summons draft or a group chat. Subject access and correction requests are possible. A notebook in a drawer cannot answer them. A shared inbox answers them by leaking.

Consent and retention are lodge decisions, not software features to hide behind. If you would not be willing to explain why a line exists, do not write the line.

The Working Tools is a real secretary operating system. On 25 August 2026 its pricing page listed £5 a month per lodge, £3 a month for each extra lodge, and a 30-day trial. It publishes an Almoner's list. This guide will not invent what that list contains beyond the words they use. If a cheap, permissioned list is the whole job, that is a rational buy.

Lodge Master 5, Lodgical, and Lodge Manager appear in the same market. The public facts we already used on the summons article are meetings, menus, a summons host, and Stripe for Lodge Master; summons, subs, dining, and charity-steward work for Lodgical; and membership and summons pricing at £50 or £70 a year for Lodge Manager on the page we verified. We will not award any of them a welfare-case model their public pages did not state.

A paper file and a kind memory are still how many lodges run. They can be discreet in the hands of one careful brother. They fail the moment the collar moves or someone asks for a copy of their record.

Once the lodge owns the job, LodgePay keeps each welfare case as a record: the member, the situation, the support, and the people involved. Visits and alerts sit on the case. Permissions are discretion-aware in the way already published: the Almoner sees full case detail, the Master can see that a case exists, and the wider lodge sees nothing.

Almoner welfare cases sit on Complete, published at £229 a month billed annually, alongside mentor assignment and a full audit trail. Essentials is £149 a month billed annually and does not include this module. Group is £349. Province pricing is a later article. Those are pricing-page figures, not a reason to skip the process above.

That is the end of the pitch, not the start of the year. If nobody owns access and handover, buying a platform will not create discretion.