Guide

Map your church's tech in one afternoon

Every church has one person who knows how the sound and video actually work. Sometimes it's a volunteer, sometimes it's the pastor, and too often that knowledge lives in only one head. When that person is out sick, on vacation, or moves away, Sunday gets nervous.

That was us. We had racks full of gear, cables nobody wanted to trace, and a vague sense of what plugged into what. So we tried something simple: we photographed all of our racks and gear and had AI build an inventory list from the photos. Then we had it turn that list into a system map. It took an afternoon to get a first draft we could actually use, and that draft has become the document we hand to anyone who helps in the booth.

Here's how we did it, what worked, and what to watch for.

Why bother

An inventory sounds like busywork until you need it. Ours has already helped us:

Step 1: Photograph everything

Walk the building with your phone. Don't worry about pretty pictures. Worry about readable ones.

If you have invoices from an install, pull those out as well. We fed in an installer's invoice, and it filled in details the photos couldn't, like exact amp models.

Step 2: Ask AI to build the list

Upload the photos (in batches is fine) to an AI assistant that can read images. Then be specific about what you want. Something like:

"These are photos of our church's AV racks and gear. Build an inventory table grouped by location: quantity, make and model, and notes on what each unit does. Copy any labels exactly as written. If you can't read a model number or aren't sure what something is, say so in the notes instead of guessing. At the end, list everything that's still missing or unconfirmed."

That last sentence matters most. Ask it to tell you what it doesn't know.

Grouping by location (front-of-house, booth rack, stage, video, network, hallways) made our list much easier to check, because you can stand in one spot with the list in hand and look.

Step 3: Check it like you'd check a volunteer's first schedule

AI is very good at reading model numbers off a faceplate. It's less good at knowing what you actually installed versus what was quoted, or how things are wired behind the wall. Treat the first draft as a draft.

A few things we saw:

Walk the building once with the draft. Fix what's wrong, and write down what you can't answer.

Step 4: Keep a "still missing" list

At the bottom of our inventory is a short section called Still missing: lighting fixtures we hadn't listed yet, a couple of camera models, whether there's a separate streaming computer, and so on. Our handoff document later grew this into a numbered list of unknowns, each with a line on why it matters.

This is the most useful page we have. It turns "we should really document the tech someday" into a to-do list a volunteer can knock out on a Saturday.

Step 5: Turn the list into a system map

Once the inventory was reasonably right, we asked the AI to draw how it all connects: audio from stage to console to processor to amps to speakers, video from cameras and slides to the switcher to screens and the stream, and which computer controls what.

One rule made the map trustworthy: solid lines are confirmed, dashed lines are assumed. The AI drew everything it could infer, but anything nobody had verified stayed dashed. When someone confirms a connection on a walkthrough, the line becomes solid. You can see at a glance which parts of your system you actually understand.

We had it written as a text-based diagram (Mermaid), so it lives in the same document as the inventory and is easy to update. Any diagram tool works, though.

Step 6: Wrap it into one handoff document

Finally, we pulled the inventory, the system map, our upgrade notes, and a Sunday checklist into one overview document for whoever runs tech. It opens with a simple rule: anything stated plainly is confirmed, and anything marked "assumed" or "TBD" isn't. It also says up front that no passwords or credentials go in it. Keep those in a password manager, not a document that gets passed around.

A few tips

Get the template

We made a simple spreadsheet template with the columns we wish we'd started with: location, quantity, make, model, serial, what it does, what it connects to, the label on the gear, where the info came from, and whether it's confirmed.

Download the church tech inventory template (CSV). It opens in Excel, Numbers, or Google Sheets.

Give it an afternoon. You won't get everything, but you'll get most of it, and you'll know exactly what's left.

More guides → · Browse all the blueprints →