Every club secretary and lodge secretary recognises the moment. Someone who has held a role for years announces they are stepping down, and the person taking over inherits a personal email account full of attachments, a spreadsheet nobody else can interpret, and the sinking feeling that the real record of how things work left the room when their predecessor did. The organisation does not stop, but it staggers.

The fragility is not a character flaw in the person who left. It is a structural problem: when records live on a personal device, when access means one login that only one person holds, when institutional memory is stored in a single head rather than somewhere findable, any departure becomes a crisis. The sections below describe what Daviah does about each part of that problem — and, plainly, what it does not.

Member records that do not live on a personal device

The first thing a new officer needs is a reliable list of who belongs to the organisation — not a spreadsheet last saved by someone who has now left, but a current record with a history behind it. The office keeps each person's record with a dated history of changes, so the record exists independently of whoever added it.

When a person closes their own sign-in account, the organisation keeps its records with that person's name removed from them. The data does not walk out the door with the administrator who is leaving.

Officer history that answers the question 'who was responsible then?'

One of the most disorienting things about inheriting a role is not knowing who to ask about a decision made two or three years ago, because there is no record of who held the role at that time. Officer terms are kept year by year, so the organisation can always see who held each role in past years.

This matters not just for accountability but for practical continuity. When a new officer is trying to piece together why something was done a certain way, knowing who was in post at the time — and being able to look at what was recorded during their term — is a starting point.

A minute book that does not belong to one person

Minutes are often the most complete record of what an organisation decided and why. When they live in a personal document folder, they are effectively inaccessible to anyone the outgoing officer did not think to copy in. Meetings are recorded with a minute book that moves from draft to submitted to approved, and approved minutes can be amended with a recorded reason.

The minutes are stored in the office, findable by any administrator. An incoming officer does not need to ask anyone's permission to read what was decided before they arrived.

An audit trail that records what happened, not just what is true now

Member records show the current state of things. The audit trail shows the story behind that state: changes are written to an append-only trail, so they cannot be quietly revised after the fact. For an incoming officer trying to understand why a record looks the way it does, this is the difference between a snapshot and a history.

Waiving, voiding and correcting charges is the treasurer's decision and is recorded with a reason in the audit trail, so the treasurer who inherits the books is not left guessing at what an earlier correction was for.

Inviting the committee in, without sharing a single login

Much of the fragility that builds up around a single officer comes from a simpler problem: only one person has access. An administrator can invite other people to help run the organisation, each with their own account and their own named role.

There are seven roles — administrator, presiding officer, secretary, treasurer, officer, website editor and member. Someone can be given a website editor role that lets them edit the site without access to the money or member records. Distributing access this way means the organisation is not held together by one person's continued involvement.

Documents the right people can find — now and after a handover

Governing documents, standing orders, historical correspondence: when these live in a personal inbox or a private cloud folder, they are only as findable as the goodwill of whoever holds them. Documents are private by default and can be shared with officers, with members, or on the public site — so the organisation decides who can see what, not the individual who uploaded the file.

An incoming officer who needs the constitution, the previous year's accounts or the rules for a particular process does not need to ask someone who may have already left.

Reports and exports the next person can actually use

Reports on membership, officers, attendance and dues are counted live from the records and do not depend on anyone having prepared them in advance. Members, dues, payments and officers can be exported to CSV at any time — and if an organisation stops paying, its CSV exports still work. An incoming officer does not arrive to find the records locked behind a subscription dispute they inherited alongside the role.

What Daviah does not do here

It is worth being direct about the limits. Daviah keeps records, minutes, officer history and an audit trail. It does not produce a handover guide, a procedural manual or a checklist for the incoming officer. The knowledge of how things are done — the unwritten practices and judgement calls that accumulate in a long-serving secretary — does not transfer automatically. Daviah can preserve what was recorded; it cannot record what was never written down.

A new officer with no predecessor, and no one to ask, will find the records accessible but will still need to work through them. The platform gives them the materials; it does not do the orientation for them.

How this plays out for clubs

For a club, single-person dependency usually builds up around the Secretary or Membership Secretary: they hold the Member list, the Subscription records, the login to whatever system the club uses, and often the relationship with the bank. When they leave, the new Secretary inherits not a handover pack but a mess — duplicate records, payments that were never reconciled, a website login nobody has the password for.

The club-specific guide on this pain goes deeper into what each part of the office does for the Secretary, the Treasurer and the Membership Secretary in turn — including how Member records, Subscription history, minutes and documents each play a role in making the organisation less fragile.

How this plays out for lodges

For a lodge, the handover problem is sharpened by the weight of tradition and the expectations of the Jurisdiction. A new Secretary who cannot find the previous year's Dues records, cannot produce a clean Membership list for the Grand Lodge return, and has no minute book to consult is not just inconvenienced — they are unable to meet obligations the Lodge has to its governing body.

The lodge-specific guide on this pain covers how officer history, the minute book and the audit trail each answer the particular pressure a new Secretary faces, including what happens when there is genuinely no predecessor to ask.

Questions

What happens to the records when an outgoing officer closes their account?

The organisation keeps its records. When a person closes their own sign-in account, their name is removed from the records, but the records themselves remain intact and accessible to the remaining administrators.

Can more than one person have administrator access at the same time?

Yes. An administrator can invite other people to help run the organisation, each with their own account. You can give different people different roles — secretary, treasurer, website editor and so on — so each person can only see and do what their role allows.

How does the audit trail help an incoming officer?

Changes are written to an append-only audit trail and cannot be revised after the fact. An incoming officer can see what changed in the records and when it changed — and for financial corrections, what reason was given. That gives them a history to work from, not just a current snapshot.

Does Daviah produce a handover document or procedural guide for incoming officers?

No. Daviah preserves the records, minutes, officer history and audit trail. It does not generate a handover guide or onboarding support for an incoming officer. The records are there to consult; the platform does not interpret them or provide orientation.

Can records be exported after a handover?

Yes. Members, dues, payments and officers can all be exported to CSV at any time, including when the organisation is on a lapsed plan.

Can a new officer find documents without asking the previous one?

Documents are stored in the office with visibility settings the organisation controls. An officer-level document is accessible to any current officer, not just the person who uploaded it, so access does not depend on the previous officer's cooperation.

Read next