Budget and buying
Church Sound System RFP Questions
Quick answer
Require a written coverage prediction showing every seat within 6 dB of the room average before you accept any proposal. A quotation that lists equipment without predicting coverage is a parts list, not a design, and it cannot be compared against a competing bid.
Churches usually evaluate AV proposals by comparing equipment lists and prices, which is exactly the comparison that cannot be made meaningfully. Two proposals with identical loudspeakers can produce completely different results depending on where they are placed and what they are aimed at, and the cheaper one is often cheaper because it has not done that work.
The questions below shift the evaluation from what is being sold to what is being delivered. They are written so a building committee with no audio background can ask them and can tell a substantive answer from an evasive one. Pair them with the budget proportions at the cost breakdown so you can also sanity check how the money is distributed.
On this page
The one question that matters most
Ask for a written coverage prediction: a drawing of your room showing predicted sound level at seat level across the whole seating area, with every seat within about 6 dB of the average. Any competent integrator produces these routinely using modelling software and the manufacturer data for the loudspeakers they are proposing. It takes them an hour.
The prediction tells you what the equipment list cannot. Whether the back row gets enough level. Whether the front rows the mains fly over are covered or abandoned. Whether the outer seats in a wide room fall outside the pattern. Whether the design needs front fill or delay speakers that are missing from the quotation. It converts a shopping list into a design you can hold someone to.
An integrator who will not produce one, or who says it is unnecessary for a room this size, is telling you they have not done the design work. That is the single most useful piece of information you will get during the process, and it costs nothing to ask for.
The questions, and what a good answer looks like
Send these in writing and require written answers, so the responses can be compared side by side.
The single most revealing requirement is a written coverage prediction showing every seat within 6 dB, because it converts an equipment list into a design that can be held to account.
| Question | A good answer | A warning sign |
|---|---|---|
| What coverage does this design predict at every seat? | A drawing showing level at seat level, every seat within about 6 dB | "It will be fine", or a refusal to model the room |
| How are the front rows covered? | Front fill loudspeakers specified and priced in the proposal | No mention of the front rows at all |
| What is the reverberation time of this room and does it need treatment? | A measured or calculated figure with a target for our service style | Acoustics not mentioned, or treated as our separate problem |
| Who engineers the flown loudspeaker attachment points? | A named structural engineer or certified rigger, with rated hardware | "We will find something in the ceiling to hang it from" |
| What electrical work is required and who does it? | A load total, a circuit count, and a licensed electrician named | Electrical treated as out of scope with no load figures given |
| How many wireless channels will work in this building? | A spectrum scan at our location with a coordinated frequency plan | A channel count quoted from the manufacturer maximum |
| What is the training and handover plan? | Named sessions, documentation, labelled system and a default scene | Training offered as an optional extra after installation |
| What happens if it does not perform as predicted? | A commissioning standard and a remedy written into the contract | Performance described only in marketing language |
Require written answers rather than a conversation, because written answers can be compared between bidders and referred back to if the finished system does not perform. Verbal assurances are not a specification.
Scope questions that prevent change orders
Most disputes on church AV projects are about scope rather than quality, and they are preventable with four specific questions. Who supplies and pulls the cable, and is conduit included. Who makes good the ceiling, walls and decoration after installation. Who is responsible for structural engineering and its cost. And who is responsible for the electrical work and any panel capacity issues that surface.
Each of these has landed on a church unexpectedly often enough to be worth naming in the document. The answer may legitimately be that the church is responsible, which is fine when it is known at budget time and expensive when it is discovered mid-project. Get it written down either way, and budget for it at building a church AV budget.
Running the process
- Write down the problem and the room before contacting anyone. Seat count, room dimensions, service style, the specific complaints with the current system, and what the building will be used for in ten years. A vendor cannot design without this and will otherwise design for a generic church that is not yours.
- Send identical written requirements to every bidder. Same room information, same questions, same required deliverables including the coverage prediction. Proposals responding to different briefs cannot be compared, and the differences will be presented as advantages when they are actually scope gaps.
- Require the coverage prediction as a condition of bidding. Not as a nice to have. It is the deliverable that distinguishes a design from a parts list, it takes a competent integrator about an hour, and refusal to produce one is itself the answer to whether design work has been done.
- Ask for references from churches of similar size and style. Then visit one during a service rather than on a weekday. Hearing a system in use with a congregation present tells you more than any specification, and the host church will speak frankly about the process afterwards.
- Convert every proposal into the seven budget percentages. Loudspeakers, amplification, console, wireless, wired microphones, monitoring and infrastructure. A proposal weighted heavily toward the console and light on loudspeakers is selling the wrong system regardless of the brands involved.
- Check what is excluded, line by line. Cable, conduit, making good, structural engineering, electrical work, acoustic treatment, training and warranty terms. The cheapest proposal is frequently the one that has excluded the most, and the exclusions only become visible when you compare them deliberately.
- Write commissioning and acceptance into the contract. Define what the system must demonstrably do at handover: coverage within the predicted tolerance, gain before feedback margin on the preaching channel, and a documented tuned state saved as a console scene. Then hold the final payment against it.
Evaluate the integrator, not just the proposal
The document is a proxy for the people, and the people are what you are actually buying. Four things distinguish an integrator worth hiring, and none of them appears in an equipment list.
Do they ask about the room before proposing equipment? An integrator who sends a quotation without asking about service style, seat count, the specific complaints and how the building will be used in ten years is selling from a catalogue. The questions they ask you are more informative than the answers they give.
Do they tell you anything you did not want to hear? A good proposal frequently includes an inconvenient truth: that the room needs acoustic treatment, that the budget is in the wrong proportions, that a 4K camera is unnecessary, or that the problem is the preaching microphone rather than the system. An integrator who agrees with everything is managing you rather than advising you.
Do they handle the church you will be, not just the one you are? Ask what happens when the volunteer team turns over entirely, because it will. The answer should involve documentation, a locked default state and training rather than a support contract that makes you permanently dependent.
Will they be there in five years? Ask how long they have worked with churches, what happens if the person who designed your system leaves, and whether anyone else in the company could support it. A system that only one individual understands is a risk regardless of how good that individual is.
Questions about after the installation
The proposal that wins should be the one that is still good in five years, and three questions test that. What is the warranty on equipment and on labour, and who administers a claim. What is the support arrangement when something fails on a Sunday, and what is the realistic response time. And what documentation is handed over: a system diagram, an input list, labelled cabling and a saved default console scene are the minimum.
Ask also what happens when your volunteer team turns over, because it will. A system that only the integrator understands is a system the church does not own. Training, documentation and a locked default state that a volunteer can always return to are what make the difference, and they are covered at how to train church sound volunteers and church AV maintenance schedule.
Sources
- Standard AV design practice on coverage prediction and seat to seat level variation
- Loudspeaker manufacturer application guidance on coverage modelling and pattern control
- Budget proportions derived from the dependency order of loudspeakers, amplification, console and infrastructure
Frequently asked questions
What should a church ask for in a sound system proposal?
A written coverage prediction showing every seat within about 6 dB, a named approach to the front rows, a position on room acoustics, structural engineering for anything flown, electrical requirements with load figures, a wireless frequency plan based on a scan at your building, and a training and documentation plan. Require written answers so bids can be compared.
How do we compare two AV proposals with different equipment?
Convert both into the seven budget percentages and compare the shares rather than the brands. Then compare the coverage predictions, which show what each design actually delivers in your room. Finally compare exclusions line by line, because the cheaper proposal is frequently the one that has left more out.
Is a coverage prediction really necessary for a small church?
Yes, and it is quick for a competent integrator to produce. Small rooms have coverage problems too, particularly wide shallow ones where a narrow pattern loudspeaker leaves the outer front seats uncovered. The prediction takes about an hour and converts an equipment list into something you can hold the supplier to.
Should the church or the integrator handle electrical work?
Either, provided it is written down before the project starts and a licensed electrician does the work to local code. What causes disputes is leaving it undefined, so the load totals and circuit count appear only once installation begins. Ask for the load figures in the proposal regardless of who is contracting the electrician.
What should be in the handover documentation?
A system diagram, a complete input list, labelling at both ends of every cable, the tuned state saved as a named console scene, the frequency plan for wireless, warranty documents and contact details for support. Without these the church does not really own the system, and the next volunteer team starts from nothing.
Researched, not professional advice. This page is compiled from published manufacturer specifications, operator manuals, FCC rules, published standards and owner-review consensus, not hands-on testing. Sound system design, rigging loudspeakers overhead, and any electrical work are jobs for a qualified professional: have flown loudspeakers and their attachment points signed off by a structural engineer or a certified rigger, and have all wiring done by a licensed electrician to your local code. Wireless microphone rules change, so confirm the current FCC position before buying. As an Amazon Associate we earn from qualifying purchases.