How to Handle Facility Requests from Church Staff

It starts with a text. Then a note under the door. Then a voicemail. Then someone stopping you in the hallway on Sunday. Before long, your "to-do list" is scattered across three phones, a notepad, and your memory — and something important has been forgotten.

The way maintenance requests come in is one of the most controllable variables in how well a facility runs. A simple, consistent intake process changes everything: what gets done, in what order, and whether staff feel like their requests are heard.

The intake method doesn't matter as much as the consistency. A shared email address, a QR code form on the wall, a software work order system, or even a physical binder at the front desk — any of these works if everyone uses it.

• Choose one channel and clearly communicate it to all staff
• Make it easy — if it requires more than 60 seconds to submit, people will default to texting you directly
• Resist the urge to accept requests through other channels, even when it feels easier in the moment
• If someone approaches you in the hallway, say "I want to make sure I don't forget — can you put that in the system?" This isn't rude; it's professional

For churches that want the easiest possible option for congregation members or staff who aren't tech-forward, a QR code on the wall in each building zone works well — scan, fill in a short form, done.

A good request has enough information to act on without a follow-up conversation. At minimum:

• What specifically is the problem? ("The light is broken" is less useful than "the overhead light in Classroom 3 flickers and sometimes doesn't turn on")
• Where exactly is it?
• How urgent is it — does it affect an event this week?
• Who submitted it, in case you need to follow up

If your intake method is a form, build these fields in. If it's an email address, ask people to include location and urgency in the subject line.

Most frustration with facility management isn't about speed — it's about silence. People submit a request and never hear anything back. They don't know if it was received, if it's in progress, or if it was forgotten.

• Acknowledge every request within one business day, even if it's just "received, this is on the list"
• Give an honest timeline, not an optimistic one. "I'll get to this in the next two weeks" is better than "soon" or not responding at all.
• Update the requester when work is complete — a quick "the light in Classroom 3 is fixed" closes the loop and builds trust.
• If a request is going to take longer than you initially said, proactively update the person — don't wait for them to follow up.

Not every request can be fulfilled, and not every request should be. Some things are low priority. Some are outside the budget. Some are outside your scope.

Saying no doesn't have to create conflict. A few phrases that help:

• "I have that on the list — I'm not going to get to it in the next month, but I'll circle back." (Honest deferral)
• "That's outside what I'm able to do — let's talk to [name] about whether to bring in a contractor." (Scope referral)
• "I can do X, but not Y with the current budget. Which matters more?" (Trade-off framing)

What makes these work is that the person knows their request was heard and has a clear next step, even if the answer isn't what they wanted.

The best time to set expectations is before a problem arises. At the beginning of a year or when you're new to a role, consider sharing a brief overview with staff:

• How to submit a maintenance request
• What the typical response time looks like
• What kinds of requests go to the top of the queue (safety, ministry-critical)
• What the process is for urgent issues outside business hours

It doesn't need to be long. A one-page handout or a five-minute mention at a staff meeting is enough. But having that shared understanding prevents most of the frustration that comes from mismatched expectations.