A congregation has a security problem most buildings do not: it has to be open to strangers on schedule and closed the rest of the week, and the people managing it are volunteers with other jobs. Nearly every walk we do turns up the same two findings — a key ring nobody can account for, and midweek entries with no record.
The work is mostly administrative made physical. Credentials instead of keys, a schedule that opens the sanctuary doors and keeps the offices and childcare wing closed, and coverage on the lot and the two corridors where things actually go missing.
Every volunteer departure over a decade. Credentials make that a deletion instead of a rekey.
AV equipment, instruments, tools. Almost always through a door left unlocked after an event.
The wing that must be reachable by parents and nobody else, on a different schedule than the building.
Doors are never locked against people inside. Lockdown capability is specified so it cannot violate that.
Hardware height, clear width and intercom reach at the doors the congregation uses.
Occupancy and assembly requirements drive the hardware, and we file where filing is required.
Scoped to the property, not a per-unit rate card. These are the factors that move the number, in the order they usually matter.
Then nothing goes on the sanctuary doors. The credentials go on the offices, the AV room and the childcare wing, where the loss and the liability actually are.
Which is why the system has to be simple enough to hand over. One admin, a printed procedure, and a phone number when something is odd.
It can be phased, and there are grant programs for houses of worship in California. We will scope to what a grant will fund and write it that way.
Midweek theft from the AV room and no record of after-hours entries. We credentialed the four staff doors, put the childcare wing on its own schedule, and covered the lot and two exterior corridors.
Yes. The schedule opens what should be open and keeps the rest closed, automatically, without anyone remembering to.
California has funded nonprofit security programs in recent cycles. We will write the scope so it fits an application.
Yes, from a browser, with permissions limited to what you want them to change.
Name, phone and ZIP. We walk it before we price it.
