How a lodge website does more than publish the meeting night

The public site should tell the lodge story, name the officers the lodge is willing to show, publish the meeting calendar the public may see, and take an enquiry into a pipeline with an owner. If any of those four fail, the lodge is still running on word of mouth and a Secretary inbox.

A £500 brochure can look tidy for a launch night. It cannot take a late officer change, a new charity line, or a man who writes in on a Tuesday and expects a reply. Those are the failures that matter. Pretty type on last year's meeting night is not a shopfront.

A successful lodge decides the site is an officer job, the same way the summons and the cash book are officer jobs. Someone can publish. Someone owns the enquiry. The rest of the committee can see whether those two things happened this month.

Size is not the argument. A thirty-member lodge still has a name, a hall or a town, a public charity story, and a door a searcher might find. Handover is the argument. If the sitting Secretary is the only person who can change the Master's name, the lodge does not have a website. It has a volunteer with a login.

The usual brochure was built by a brother's contact, a shared template, or a local firm that delivered against a one-page brief and left. The photograph is there. The meeting night is there, sometimes still last year's. The contact form emails a mailbox nobody checks after installation.

When an officer changes, the page stays wrong for months. When a visitor writes, the message sits with three other officers' forwards. When the lodge wants to say what it already raises for charity, someone has to raise a change request with the web firm. That is not a shopfront. It is a laminated card in a window.

The other failure is the opposite: a site so empty that a searcher cannot tell he has found a living lodge. No officers, no calendar, no charity line, no way to write. He closes the tab. The lodge never hears that it lost him.

A third failure sits between those two. The page looks finished, so nobody opens it. The meeting night is last year's. The Master's name is two installations out of date. The charity figure is a number nobody in the current committee would read aloud. The form still works. The reply never comes. A dead page that looks alive is worse than no page, because the lodge believes it already did the job.

Neither failure is a technology mystery. All of them are ownership. If nobody can edit the page this week, the page is already out of date. If nobody owns the inbox, the form is decoration. If the only person who can publish is a firm that last invoiced in 2019, the next officer change will wait until someone finds the invoice.

A PDF on a Province page, or a hall noticeboard photograph, can be enough for a brother who already knows the lodge. It is not a shopfront for a stranger. He cannot ask a question. He cannot see this year's officers. He cannot tell whether the lodge still meets. Treat those as signs that point at a door. Do not treat them as the door.

Keep the public page public. The lodge name, a short history the lodge is happy to print, sitting officers the lodge has chosen to name, the charity story it already tells at open events, the meeting calendar, colours, and a tagline. That is enough for a stranger to know he has found the right door.

Do not put summons wording, dining lists, or member contact details on the open web. Those belong on the private half of the record. Mixing the two is how a lodge either overshares or, frightened of oversharing, publishes nothing useful.

If the lodge has a hall it shares, say where to come and when the public calendar is next open. If it does not welcome walk-ins, say how to enquire and what happens next. Guessing the door is how visitors bounce.

Write the history as the lodge already tells it, not as a generated foundation myth. Dates the lodge prints on a summons or a history night are safe. Claims nobody can stand behind in committee are not. The public site is the lodge speaking. Treat it that way.

Officers on the public page are the officers the lodge has chosen to name. Some lodges print the Master, Secretary, and Treasurer. Some add a Membership Officer or a charity contact. Some print only a role and a form. That is a lodge decision. This page will not invent a rule about who must appear. It will say this: if you name a living person, keep the name true, and give the stranger a way to write that does not dump a private mobile number onto the open web.

The charity story is the story the lodge already tells. Money already raised, a local cause already named, a campaign the Treasurer already recognises. It is not a second slogan invented because a website needed a paragraph. If the lodge files Gift Aid, that is Treasurer work on a different desk. The Gift Aid and Treasurer pages on this site stay on declarations, splits, and the reclaim. The public page only needs a line the lodge is willing to stand behind in daylight.

Colours and tagline are part of the same job. They should match the summons header and the charity leaflet, not a designer's leftover palette. A visitor who later becomes a member should recognise the lodge, not discover a second brand.

A stranger needs the dates the lodge is willing to print: when it meets, where, and how to ask about the next open night. A sitting member needs the year he is entitled to see: the summons, the dining answer, the private feed on his phone. Those are two calendars. Mixing them is how you either overshare or tell the public nothing useful.

The public calendar can be thin and still be honest. Regular meeting night. Town or hall. The next date the lodge is willing to show. A line that says enquiries are by the form, not by turning up. That is a shopfront. A full sitting list, a dining menu, and a guest list are not a shopfront. They are the private half of the year.

When the hall changes, or a date moves, the public page should move the same week. A searcher who finds last March's date will not write to ask whether you still exist. He will assume you do not. The Secretary who already printed the year should be able to correct the public night without raising a ticket.

The member portal is a different article. The member-portal guide on this site stays on summons, dues, receipts, and a card on the phone. This page only needs the split: the stranger sees what the lodge chose to publish. The brother sees what he is entitled to see after he signs in. Do not publish the private feed. Do not hide the public night because you were frightened of the private one.

A successful lodge does not wait for a webmaster to change the Master's name. The Secretary or a named editor updates the section, checks it, and publishes. Handover at installation includes the site, the same way it includes the minute book and the bank mandate.

If only one brother has the old password, the site will rot the year he is busy. Give the job a role, not a personality. Write down who may publish. Keep draft and live separate so a half-written history does not appear on a Thursday afternoon.

The practical test is dull and sufficient. Can the new Secretary change the officer list in the week of installation without emailing a firm? Can he correct the meeting night if the hall changes? If the answer is no, you do not have a lodge site. You have a hostage.

A section-based editor is how that test is met. The home page and the main sections are blocks an officer can open, change, and save. He does not need to telephone a designer to swap a name. He does not need to learn a content-management system that was last documented for a different committee. If the editor still requires a developer to publish a charity line, you have bought another brochure with a nicer login.

Write the permission down. The Secretary may publish officers and the calendar. A named editor may draft history and leave it for the Secretary to release. The Treasurer does not need to edit the history. The Membership Officer needs the form, not the palette. A lodge that gives every officer the same key will either publish by committee argument or stop publishing at all.

Handover is the week the site is most likely to go stale. The new Master is named. The old Secretary is tired. The webmaster is on holiday. If the incoming Secretary cannot open the editor on the Monday after installation, the page will still say last year's names in November. Put the site on the same handover list as the bank mandate. Two officers should be able to publish. One of them will be away.

Some tools will offer a first pass of copy from a prompt. That is useful when the lodge has a blank history section and a pile of old programmes. It is not a licence to publish unchecked text.

An officer still reads every sentence. He removes anything the lodge would not put on a public leaflet. He corrects names, dates, and charity claims. He does not let a generated paragraph invent a foundation story the lodge has never agreed. If the draft is wrong, delete it.

The same rule applies to officer biographies and charity pages. A first pass can unblock a blank screen. It cannot decide what the lodge is willing to say about living people, or how it describes money it has raised. Those are committee facts.

If you would not read the paragraph aloud at a festive board as the lodge's own words, do not publish it. That test saves more embarrassment than any style guide.

Keep draft and published as two states. A half-written history sitting in a draft is work in progress. The same paragraph on the live page is the lodge speaking. If the tool cannot hold a draft, write the text in a document first and paste only what an officer has signed off. Speed is useful. An unchecked publish is how a lodge spends the next meeting apologising for a sentence nobody agreed.

AI-assisted drafting, where a product offers it, is that first pass. LodgePay's website page already says so. It is not a reason to skip the read. It is not a reason to invent a history the lodge has never told. The officer still owns the words.

A man who writes to the lodge has started a process. If that email sits in a Secretary inbox, the process has no owner. The form should create a candidate record with a stage, a name, and a next action. Copying addresses into a spreadsheet is how enquiries die between meetings.

The public site still tells the story. The difference is that interest becomes work. Who replies, when, and what happened next should be visible to the officers who own recruitment, not only to whoever happened to open the mailbox.

Consent belongs on the form. Say that the lodge will contact him about the enquiry. Do not add him to a dining list or a summons list. He is not a member. He asked a question.

Speed matters more than eloquence. A reply in a few days that names a next step beats a perfect letter three weeks later. The pipeline is there so the lodge can see the silence, not so it can admire a board.

The longer note on that first click is already on this site: how a website enquiry becomes work the lodge can own. The rule here is the shopfront half. The form is the last step on a page that already made the lodge legible. A form with no story is a box with a crest. A story with no form is a brochure that cannot take a yes.

Once the card exists, the public stages the lodge already talks about in committee are enquiry, interview, proposer, ballot, and initiation. The candidate-pipeline guide on this site stays on owners, dates, and a log. This page will not describe ceremony or any private step. It will say this: if the first message never became a card, later stages are a hope.

Telephone and dining-room introductions still count. Type them in the same day, with the same fields. A pipeline that only holds web forms will lie about how people actually arrive. Two queues is how someone is asked the same question twice.

Do not put the whole lodge on the notification. The public site is public. The card is not. The wider lodge sees the story you chose to publish. It does not see the inbox.

A shopfront that also tries to be the summons, the dues reminder, and the receipt will either leak private work onto the open web or hide the public night behind a login. Those are two doors on the same record. The stranger uses one. The brother uses the other.

The member-portal guide on this site stays on that signed-in door: upcoming events, the summons, dues, donations, payments, receipts, a digital lodge card, an installable progressive web app, offline for the most-used screens, and a private calendar feed. Officers stay on the admin side. Members are not asked to become webmasters.

This page only needs the split so a committee does not buy the wrong job. If the pain is a dead public door, a member login will not fix it. If the pain is a forwarded summons, a prettier brochure will not fix it. Some products on the market are strong at the login. Some are strong at the Secretary's week. Very few of the public pages we re-checked on 7 September 2026 lead with a branded public shopfront that a stranger can read without signing in.

If you only need brethren to reply to a summons inside a private app, buy that job. If you also need a searcher to find the lodge and write in, you still need the public half. Do not pretend a secure subdomain is a shopfront. It is a door for people who already have the address.

Treat the site as a calendar, not a relaunch every five years. The year has a few dull checks. If those checks happen, the page stays true. If they wait for a redesign, the page is already last year's.

No product writes a history the lodge has never agreed. No product decides which officers appear on the open web. No product replies to a man who wrote in. No product owns the enquiry if the lodge will not name an owner. Those remain lodge work.

A brochure still needs copy, a calendar someone keeps true, and a human who answers the form. A secretary operating system still leaves the public page somewhere else, unless that product's own pages say otherwise. A member login portal still leaves the stranger outside, unless that product publishes a shopfront a searcher can read without signing in. A fuller platform still leaves the lodge to write true copy, to keep draft and live apart, and to answer the card.

The test is still June. Can a successor change the officer list, correct the meeting night, and see who wrote in last month, without telephoning last year's webmaster? If the answer depends on a personal inbox or a firm that last invoiced years ago, you bought a poster.

Named competitors are real. Buy the one that publishes the job you actually have. We re-checked their public pages on 7 September 2026. We will not invent a public shopfront they did not lead with, and we will not trash a cheaper correct tool.

The Working Tools (theworkingtools.co.uk) is a real secretary operating system. The public homepage and features page, checked on 7 September 2026, list member records, summons, minutes, table plans, an Incoming Candidate Tracker, a Treasurer's Cash Book, an Almoner's List, a DC's ceremony planner they name but this page will not describe, expenses, a 90-day planner, assets, handover, and delegates. The pricing FAQ on that homepage listed £5.00 a month, extra lodges at £3.00 a month, and an annual option under Settings, then Subscription. The features page still offered a 30-day trial. That is a serious cheap desk for the Secretary's week. When we checked, those public materials described a private management app and delegate logins, not a branded public lodge shopfront a stranger can read without signing in. We will not invent that. If you already type incoming names into their tracker, you have a list. You still have to decide whether a public form writes there, or whether someone is re-keying.

Emulation Companion (emulationcompanion.co.uk) is a lodge admin product with a members directory, RSVP, attendance and check-in, Treasurer tools, an Almoner welfare diary, a caterer portal, meetings, dining, visitors, and seating. The lodge gets a secure subdomain login, for example wythall.emulationcompanion.co.uk. The public pricing page, checked on 7 September 2026, said there is no charge at present. A lodge can optionally connect its own Stripe account so dining and visitor bookings go to the lodge bank. That is a member and officer login, not a visitor-facing brochure site. We will not invent a public marketing website builder their pages did not state. If the brief is brethren signing in to RSVP and the caterer seeing the kitchen list, this is a rational look. It is not, on those pages, a shopfront for a stranger.

Lodgi (lodgi.org) was reachable on 7 September 2026. The public homepage describes lodge management: members, meetings and summons, bookings and apologies, subscriptions, seating plans, email notifications, document storage, reporting, and Stripe for dining, subscriptions, joining fees, and donations. The published fee is £1 per member per month, paid by standing order, with all listed features included. Those pages describe administration for the lodge and its members. They do not, on the homepage we fetched, describe a branded public shopfront that turns a stranger's enquiry into a pipeline card. We will not add that.

Lodgical (lodgical.app) is a web membership system for Secretaries and Treasurers. Members can log on to reply to a summons and view information of specific interest. The public pages, checked on 7 September 2026, list membership, meetings, officers, summonses, minutes, bank accounts, subscriptions, dining dues, annual accounts, donations, and collections. They offer a demonstration lodge and a live trial. Price was not published. We will not invent one. Members logging on is a private door. It is not, on those pages, a public marketing website.

A £500 brochure from a local firm, or a webmaster who still holds a PDF, is also a real option. Budget for the next officer change, not only the launch night. If the firm cannot hand you a way to edit officers and the calendar, you have bought a poster. If the form only emails a mailbox, you have bought a poster with a button.

The compare page for The Working Tools on this site stays on a wider buying fork: a secretary operating system versus a lodge operating system. This article is the shopfront slice of that fork. A lodge that only needed the Secretary week and bought a public site it will not edit has overpaid. A lodge that needed a stranger to find the door, and bought only a private desk, still has no shopfront.

Once the lodge owns the shopfront job, software is a way to stop that job living in a webmaster's inbox. LodgePay is the tool at the end of that decision, not the opening line. Its website page already states the product facts we are allowed to use: a branded public site with the lodge name, history, officers, charity story, and meeting calendar; per-lodge branding, colours, and tagline; a section-based editor; AI-assisted drafting for a fast first draft; public events and charity campaign pages; and enquiry forms that feed the candidate pipeline.

The member portal is the other door on the same record. Members sign in for events, summons, dues, donations, payments, and a digital lodge card. The progressive web app is installable and works offline for the most-used screens. A private calendar feed and receipts sit there, not on the public page. Do not buy a website because you wanted dues collection, and do not buy a brochure because you wanted candidates.

Pricing, as on the pricing page, splits some of that work by plan. Essentials, from £149 a month billed annually (or £169 monthly), publishes a public lodge website, a member portal and PWA, and a digital lodge card. Complete, from £229 a month billed annually (or £259 monthly), adds the AI assistant for drafting, the candidate CRM and pipeline, charity campaigns, and the rest of that tier. Group is from £349 a month for two lodges, then £119 per extra lodge, with per-lodge branding and site. Province is from £2,000 a month plus £35 per lodge. There is no setup fee. Card payments, if you take them, go through Mooov. Standard processing fees pass through at cost. We will not invent a fee table.

That split matters in committee. A lodge that only needed a public page and a member door may be looking at Essentials. A lodge that also needs the enquiry to become a pipeline card with an owner is looking at the candidate CRM Complete publishes. Do not buy Complete because the homepage looked tidy. Do not stay on a brochure because you were frightened of the fuller plan.

Gift Aid is Treasurer work. It does not decide the shopfront. If someone in committee starts comparing the typical 30-member illustration already on the Gift Aid and pricing pages (£1,125 a year) with Essentials billed annually (£1,788), say the honest line those pages already print: the reclaim does not pay the subscription, and the figure is not your books. Then come back to the door. A stranger who cannot find the lodge will not become a dues row.

If you only need a static page and a phone number, a cheap site may be enough. If you only need the Secretary week, The Working Tools at £5.00 a month may be enough. If you only need brethren to log in and RSVP, Emulation Companion, currently free on its public pricing page, or Lodgical's member login, may be enough. We will not trash those. Use LodgePay if the shopfront, the enquiry-to-pipeline, and the member portal must stay on one record, and if officers must be able to publish without a webmaster. That is the end of the pitch, not the start of the year. If nobody owns the enquiry, a better editor will not create members.