Almost every church has tried a sign-out sheet on a clipboard by the sound desk. It works for about six weeks. Then someone takes a microphone at 7am for an outreach event, the sheet gets knocked behind the rack, and by Christmas nobody can say whether the church owns two wireless handhelds or three.
The difficulty is not that volunteers are careless. It is that church equipment moves through the hands of people who are there for two hours a fortnight, who are not paid, and who cannot be told off. Any system that relies on diligence will fail. It has to rely on being quicker than not bothering.
Why church equipment is a harder problem than it looks
- The team rotates. The person who set up the system leaves the rota, and their replacement never learned it.
- Nobody owns anything. In a business, kit is assigned to an employee. In a church, the projector belongs to everyone, which in practice means to nobody.
- Ministries borrow across boundaries. Youth borrows a speaker from worship, lends it to the community lunch, and the trail ends there.
- It leaves the building. Camps, outreach, weddings, someone’s house for a repair.
- There is no IT budget to replace it quietly. A lost radio mic is a line item somebody has to explain to a treasurer or a board.
What a working system actually has to do
| Question | What it means on a Sunday |
|---|---|
| Who has it? | A person’s name, not “youth”. Ministries do not lose things; people do. |
| When is it back? | Before next Sunday, or it is a problem at 10:29am. |
| What did it cost? | For insurance, and for the board meeting where somebody asks what the A/V is worth. |
| What happened? | A dated record. This is the one that settles a disagreement without anybody having to be accused. |
Building it so a rotating team can actually use it
1. Number everything, visibly
A label on the case and on the item: MIC-03, SPK-01. Volunteers cannot
be expected to distinguish two identical radio mics, and “the good one” is not a record.
The number is what makes a handover unambiguous in four seconds.
2. One row per item, with the columns a treasurer will ask for
Tag, item, category, make, model, serial number, status, condition, who has it, ministry, storage location, purchase cost, purchase date, service or PAT-test date, notes. The serial number matters more than it feels like it does — it is the first thing an insurer asks for.
3. Check-out has to take seconds
This is the whole game. If signing a microphone out takes longer than walking off with it, people will walk off with it, and they will not be wrong to. Whatever you build, the handover step has to be doable one-handed while carrying a speaker.
4. Keep a log, and never overwrite it
When something changes hands, add a line: date, item, action, from, to. Then update the status. The list says where things are now; the log says how they got there. Overwriting a cell destroys the only evidence you have, and in a church the evidence matters less for blame than for jogging somebody’s memory.
5. Make one person responsible for the file, not for remembering
A rotating team needs a single owner of the system — usually the A/V coordinator — whose job is to keep the file honest, not to personally know where everything is. That distinction is what survives their eventual handover.
6. Put the service and test dates in the same place
Portable appliance testing, ladder inspections, battery replacement schedules. These are dates on the same rows, not a separate system, and colour-coding anything due inside 30 days means nobody has to remember to check.
Do not build a system that needs training. If explaining it to a new volunteer takes more than one sentence, it will not survive the next rota change. “Scan the label, type your name” survives. A twelve-field form does not.
What about a shared Google Sheet?
It is a reasonable starting point and it is free, so try it before you spend anything. Two things tend to go wrong. First, everybody has edit rights, so eventually somebody sorts the sheet with only one column selected and scrambles it. Second, a plain sheet has no log, so it inherits the flat-list problem: you can see the present, never the past. If you go this route, lock the structure and add a second tab for the log.
When a spreadsheet is the wrong answer
- Several people need to update it simultaneously from different places. A synced file does not merge two edits; one of them is silently lost.
- You run a venue, not a church. If gear is going out on paid hire with contracts and deposits, you want rental software with a booking calendar.
- You genuinely have hundreds of items moving weekly. At that volume the scanning workflow is the product, and dedicated software is built around it.
For a church with one or two services, a handful of ministries and a store room, none of those usually apply.
A ready-made version
Everything above can be built from a blank spreadsheet on a wet afternoon, and if that sounds fine, do it. We also sell it already built: one Excel file with a dashboard on top that signs gear out to a volunteer in a click, keeps the log, tracks service dates, and totals what the A/V is worth for the treasurer. No account, no logins to hand round a rotating team, and it works with the church wi-fi down.
It is $79 once, and there is a live demo you can click through without buying anything or handing over an email address.