Mistakes People Rarely Talk About

In professional ProAV, it’s common to discuss gear, loudspeaker coverage, DSP platforms, network protocols, and venue architecture. Much less often do we address the root cause: a poorly written specification can undermine any engineering concept, turn a venue into a constant client of rental companies, and create years of technical debt. 

We reviewed a number of implemented projects across Central Asia and consolidated the hands-on experience of Sound Creations engineers to highlight the most common mistakes in audio system specifications—and how to avoid them. 

When Things Go Wrong from the Start: A Typical Scenario 

Many engineers know this story: a new venue—whether a museum, a hybrid stage, or a technology-heavy art space—gets a modern sound reinforcement system. The equipment is solid, the architectural approach looks efficient, and initial tests pass. 

Then the first major production arrives. Artists move through the audience area, the stage configuration changes, the show requires flexible routing, and some sources run in a surround format. 

And suddenly it becomes clear that: 

• the installed loudspeaker system does not cover the new configuration; 
• routing does not scale to new use cases; 
• the DSP cannot be reconfigured properly; 
• the audio network has no spare ports / connection points; 
• coverage becomes unpredictable; 
• the venue must urgently bring in rental gear and “build out” the system manually. 

As a result, the budget is spent on firefighting, while the originally installed system works only for a single scenario—the one described in the specification and used as the basis for the design. 

Common Specification Mistakes That Cost Real Money 

As Sound Creations engineers—who regularly participate in end-to-end AV projects—note, even one mistake in the technical specification can lead to serious limitations as early as the first events. 

1) Specifying Power (kW) Instead of Sound Pressure Level (SPL) 

“Need a 10 kW system” is one of the most persistent legacy phrases. 

Power consumption does not describe achievable SPL, system efficiency, or performance in the room. A system may draw 10 kW and still fail to deliver sufficient SPL—especially in the low-frequency range or over long throw distances. 

SPL (Sound Pressure Level) is the measurable and modelable indicator of what the audience actually hears in the venue. 

That’s why an audio system specification should define: 

• target SPL at a reference height: 1.2 m (typical seated ear height) or 1.7 m (typical standing ear height); 
• allowable coverage variance (commonly ±3 to ±6 dB, depending on the use case); 
• required frequency range for the system; 
• STI (Speech Transmission Index) targets for speech-focused events. 

Engineering reality: a system drawing 1 kW can outperform a “10 kW speaker” due to higher sensitivity, controlled directivity, phase coherence, enclosure design—and, crucially, correct placement and aiming so the system operates where it delivers maximum efficiency. 

2) Missing Architectural Drawings and BIM / 3D Models 

Legacy inventory plans (e.g., “as-built” or registry drawings) are often not suitable: they can be schematic, may not include accurate volume data, and are frequently produced before final finishes. In many cases, measurements are taken manually without specialized surveying tools. 

Without accurate drawings, an engineer: 

• cannot build a correct 3D model of the space; 
• risks errors in delay calculations and coverage prediction; 
• lacks an objective basis to assess room acoustics—RT60, reverberation behavior, and material properties that affect speech intelligibility and articulation loss.

This is especially critical for complex geometries: balconies, mezzanines, niches, varying ceiling heights, canopies, and orchestra pits. Sports venues are a separate risk category—operators often lack reliable data on structural load capacity and do not have the corresponding drawings or models. 

Specifications often say “concerts and events” without describing the actual scenarios that drive design decisions, such as: 

• whether the venue hosts immersive performances; 
• whether a 360° / in-the-round stage is used; 
• whether artists move through the audience area; 
• whether distributed monitoring / foldback in the room is required; 
• whether temporary configurations are expected (additional delay lines, front-fills, outfills, mobile stages); 
• likely artist (rider) requirements; 
• whether the venue is a musical theatre or a drama theatre (very different priorities for speech vs music); 
• whether a sports venue must handle a concert today and a hockey game tomorrow. 

Without defined use cases, the system is typically designed for one “default” setup—and everything else becomes a rental workaround. 

4) Ignoring DSP and Audio Networking Infrastructure 

One of the most common mistakes of recent years is pairing high-end loudspeakers with an inflexible DSP platform. Typical consequences include: 

• routing cannot be adapted to different event formats; 
• no true remote control and monitoring; 
• no presets for multiple stage and room configurations; 
• lack of support for required audio networking standards (e.g., Dante, Milan AVB, AES67); 
• inability to integrate temporary systems cleanly. 
• A great loudspeaker system on an inflexible DSP is like a top-tier car without a steering wheel.

Conclusion: A Solid Audio Specification Means 10–15 Years of Stability and Lower Cost 

A mistake at the specification stage almost always results in: 

• a system locked to one scenario; 
• constant workarounds; 
• additional costs and retrofits; 
• poor adaptability to modern formats; 
• dissatisfied audiences and artists. 

A well-written audio system technical specification is the foundation for a flexible infrastructure, a versatile sound system, a stable AV network, and a venue’s long-term operational success over the next 10–15 years. 

A sound system is not just “equipment.” It is an engineering ecosystem. And it doesn’t start with loudspeakers, DSP, or even budget—it starts with a competent technical specification.