Industries
Religious Facilities
A congregation's building is nearly empty most of the week and completely full for a few hours — the whole problem is timing service around gatherings without ever being present during one.
Request a free assessmentAn empty building, then a full one
Most commercial spaces have a broadly steady occupancy. A congregation’s building is close to the opposite: quiet or empty for much of the week, then completely full for a few hours, sometimes with a mid-week pattern of smaller groups layered on top.
That makes a fixed weekly schedule structurally wrong. It applies the same effort to a Thursday when eight people used the building as to a Monday following a service with four hundred. The work needed after a gathering is substantial and the work needed between them is minimal — and no interval-based table expresses that.
The building’s own calendar drives the schedule instead. Service concentrates after gatherings and before the next, and our staff are never present during one.
The peaks the model cannot see
Predictive cleaning reads usage history well, and usage history is precisely what fails here. Major holidays, festivals and observances bring attendance several times above normal with nothing in the preceding weeks to indicate it. Funerals and weddings arrive with days of notice at best.
So this is a sector where we ask for the calendar rather than pretending the forecast covers it. Known dates are entered in advance and service is planned around them. Between those, the usage-driven model handles the ordinary variation — which for many congregations means genuinely less service on quiet weeks, and that is a cost saving rather than a shortfall.
The spaces, and their different rules
The sanctuary or worship space. Flooring, seating and pews, surfaces, general condition. Ritual objects, altar areas and anything of religious significance are not handled by our staff unless your leadership specifically instructs otherwise — and where they do, that instruction is recorded per account so it survives a change of staff on either side. The default is deliberately conservative: it is easier to extend a scope than to undo having touched something that should not have been touched.
Fellowship halls and multi-purpose rooms. Turnover after events, which is the most variable scope in the building and usually the most urgent, since the same room is often needed again within a day.
Classrooms and childcare. These run on a fixed high-touch minimum that usage data can raise and cannot lower — the same protection applied in schools. A nursery used by twenty small children does not get less cleaning because last week was quiet.
Restrooms. Frequency matched to gathering size, which sensors handle well where they are installed since attendance is the one thing that varies most.
Working alongside volunteers
Many congregations already have volunteers doing part of the work, and the arrangement works well when the boundary is written down.
We scope explicitly what we cover and what stays with volunteers, so nothing falls into the gap where each party assumes the other has it — which is the actual failure mode, not the division of labour itself. Supply and access arrangements are set up around whoever is doing each part.
Cost, stated plainly
Congregational budgets are usually tight and often scrutinised by a committee. Scope is built from what the building needs against what the budget supports, and the usage-driven model happens to suit this sector unusually well — concentrated service where the load actually is, very little on quiet weeks, and a record in Standards showing exactly where the hours went.
How you verify it
Delivered is not the same as proven
Every service below reports into CleanVision, so the work leaves a record you can audit — not a promise you have to trust.
-
Scheduled around the calendar you keep
Services, study groups, funerals, weddings and community use — the building's calendar drives the schedule, and cleaning is never present during a gathering.
-
Peaks are entered, not predicted
A holiday season triples the building's use with no warning in the usage history. Known dates are entered in advance, because this is a case the model cannot read.
-
Childcare areas run on fixed protocol
Nursery and classroom spaces follow a high-touch minimum that usage data cannot lower, the same constraint applied in schools.
Common questions
No. Service is scheduled around gatherings, and the building's own calendar drives the schedule rather than a fixed slot. For most congregations this means work concentrated in the days after the main gathering and before the next.
Entered in advance, because they are the case usage history cannot anticipate — attendance can be several times normal with nothing in the preceding weeks to signal it. Additional service before and after is planned into the calendar rather than adjusted afterwards.
Frequently, and it works better when the boundary is explicit. We scope what we cover and what volunteers handle, so nothing sits in the gap where both parties assume the other has it. Supply and access arrangements are set up to suit whoever is actually doing each part.
Yes — flooring, seating, surfaces and the general condition of the worship space. Ritual objects, altar areas and anything with religious significance are not handled unless your leadership specifically instructs otherwise, and that instruction is recorded per account.
Scope is built to what the building actually needs and what the budget supports, which is a more honest conversation than a standard package. Many congregations need concentrated service around gatherings and very little between them, and the usage-driven model suits that pattern well.
Excellence isn't a promise — it's a guarantee
Request a free assessment of your facility and see what a proactive operation catches that a reactive one bills you for later.
Talk to Protex