Every club has one. The person who knows where the constitution is, which members have paid, what was decided at last year's AGM and how the subscription rate was set three cycles ago. They are irreplaceable — and that is exactly the problem. While they are there, the club runs. When they step back, through burnout, a change of circumstances or simply the ordinary rotation of Committee roles, the person who follows them inherits a collection of spreadsheets on a personal laptop, a folder of PDFs in a private email account and a set of passwords nobody else knows. The handover is a disaster, not because anyone meant it to be, but because the knowledge was never in a place the club owned.

Daviah does not solve every part of this. There is no formal process for handing over access or responsibilities from one person to the next, and no structured way to capture the departing officer's knowledge before they go. What it does do is keep the records — member records, officer history, meeting minutes, documents and the full audit trail — in one place that belongs to the club, not to the individual who happened to be running it at the time.

Member records that do not live on a personal device

When member information lives in a spreadsheet on one volunteer's laptop, the club's knowledge of its own people is hostage to that one device. Daviah keeps each member's record in the office — with a dated history of changes to each record — where anyone on the Committee with the appropriate role can look at it.

When the Membership Secretary changes, the new person does not start from a printout that is six months out of date. They open the office and the records are there, current, with a history of what changed and when. Nothing has to be transferred from a personal account because nothing was stored in one.

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

Clubs are asked this question more often than they expect — by auditors, by their Association, by members disputing a decision made two years ago. Without a record of who held which role in which year, the answer is whatever anyone can remember.

Officer terms are kept year by year in Daviah, so the club can always see who held each role in past years. The public site's Officers page draws from those same records, so it reflects the current Committee without anyone updating it separately. When roles change in the office, the page changes with them.

This does not mean the incoming officer understands the context behind past decisions — that is a limitation Daviah does not overcome — but it does mean the club has a reliable record of who was in post and when.

Minutes that are approved, stored and findable

Meeting minutes are institutional memory in their most formal sense. They record what was decided, by whom and when. When they exist only as a document in one person's email drafts, they are effectively lost to the club — present in theory, unreachable in practice.

Daviah keeps a minute book that moves from draft to submitted to approved, and approved minutes can be amended with a recorded reason. Past meetings and their approved minutes sit in the office, accessible to the Committee, without anyone having to remember where the file was saved.

Attendance can be taken from the office at the meeting itself, so the record of who was present is kept alongside the minutes.

Documents the right people can find after a handover

A club's constitution, policies, insurance documents and financial records are among the files most likely to be lost when one person steps away. If they were saved to a personal cloud account or emailed to a predecessor's inbox, they may simply not be findable by the person who needs them next.

Documents in Daviah are stored in the office and can be shared with officers, with all members, or on the public site — but they are private by default. Visibility is set deliberately. When the Committee changes, the documents do not move with the outgoing officer; they stay where they are, visible to whoever now holds the appropriate role.

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

One of the quieter problems with single-person dependency is that the current state of a record tells you nothing about how it got there. Was that subscription waived? Who corrected that member's address? Without a history, the next Committee member has to take the record on trust.

Changes to records are written to an append-only audit trail. Corrections to charges — waiving, voiding and correcting — are recorded with a reason in the audit trail. The audit trail cannot be edited after the fact.

This is not a complete answer to the problem of context: the audit trail records what changed, not the reasoning behind every decision. But it does mean the incoming officer has more to work with than a spreadsheet with no history.

Inviting the Committee without sharing a single login

One reason everything ends up in one person's hands is practical: if only one person has the login, only one person can do the work. Sharing the login is the informal solution most clubs land on, and it creates its own problems — nobody knows who made which change, and removing access when someone leaves means changing the password and telling everyone else.

An administrator can invite other people to help run the club. Each person has their own account with their own role. There are seven roles, each named in the club's own words. The Website Editor role lets someone update the site without access to member records or financial information. When a Committee member's term ends, their access ends without affecting anyone else's.

Reports and exports the next person can actually use

Even with good records, the incoming officer needs to be able to see what is in them. Reports on membership, officers, attendance and dues are counted live from the records. Members, dues, payments and officers can be exported to CSV.

This means the new Treasurer or Secretary does not need to be handed the previous person's files — the numbers are in the office, and they can pull a current report or export from the moment they take on the role.

The CSV export does not cover every record type — documents, minutes, events and media are not included in an export — so for those, the office itself is where the incoming officer needs to work.

What Daviah does not do

It is worth being plain about the limits. Daviah does not provide a formal process for handing over access or responsibilities from one person to the next. There is no handover checklist, no notification sent to the incoming officer explaining what they have inherited, and no structured way to capture the departing officer's knowledge before they go.

Onboarding a new Secretary or Treasurer to understand the full context behind past decisions — why a particular member's subscription was waived, what the Committee discussed before reaching a decision — is a human process that the records in Daviah can support but not replace.

The officer history and the audit trail mean the incoming officer has more to work with than they would from a personal email account. But the conversation, the handover meeting and the passing of judgment from one person to the next are not things any software can do for you.

Questions

If the outgoing Secretary closes their account, what happens to the records?

When a person closes their own sign-in account, the club keeps all its records. That person's name is removed from the records, but the records themselves remain in the office.

Can the incoming Treasurer see what subscriptions were raised and corrected before they took on the role?

Yes. The office keeps a record of subscriptions raised and payments recorded, and corrections to charges are recorded with a reason in the audit trail. Reports on dues can be run from the records as they stand.

Can we give the new Website Editor access to update the site without giving them access to member records?

Yes. The Website Editor role allows someone to edit the site without access to member records or financial information.

Does Daviah have a formal handover process that transfers access from one officer to the next?

No. Daviah does not provide a formal handover process. The incoming officer needs to be invited by an existing administrator, and responsibilities are assigned through roles. The records are there for them to work with, but the process of transferring knowledge is something the Committee needs to manage itself.

Can we see who held the Treasurer role three years ago?

Yes. Officer terms are kept year by year, so the club can look back and see who held each role in past years.

What if the previous Secretary stored the club's documents in their personal cloud account?

Daviah does not retrieve documents from personal accounts or external cloud services. Documents need to be uploaded to the office manually. Once they are there, they are stored in the club's office with the visibility settings the Committee chooses, and they remain there when roles change.

Read next