Public bidding is supposed to be the fair way to buy things. Write the scope, advertise it, let qualified firms price it, take the best response. On most trades that works. Concrete is concrete. The numbers come back in a tight band, and the band tells you the spec was clear.
AV is the scope where the numbers come back spread across a canyon.
Three responses: one that makes the owner nervous, one that makes the owner happy, and one in between. Same bid set, same site, same deadline. That spread is rarely a sign that one bidder is greedy and another generous. It is a sign that the documents let three honest firms read three different projects out of the same pages — and that gets fixed in the drafting, not in the negotiation.
This installment is for the people on the writing side: architects and engineers producing the documents, district facilities and procurement staff reviewing them, and GCs who have to write the AV scope into a subcontract or respond to somebody else's version of it.
1. Why AV specs come back uncomparable
Most AV bid failures trace to a small handful of drafting habits.
Brand-name-only, with no path to anything else. A spec listing one manufacturer's part numbers, and nothing about what those parts have to accomplish, is a shopping list. Many public owners' procurement rules lean against sole-sourcing a brand, so check yours before you have written forty pages in the wrong form.
Performance language too vague to price. "Provide a complete and operational audiovisual system" is the most expensive sentence in AV specification. Complete according to whom? Operational doing what? Every bidder guesses at the missing half, and the guesses are the canyon. The low bidder guessed small, reading the same sentence you wrote.
AV buried inside another division. AV routinely lands folded into Division 26 with the electrical work, or as a Division 27 line item, or scattered across both plus a note on an architectural sheet — and a bidder who does not open the right section does not price the work. Part 2 of this series maps those boundaries; the spec should say plainly, in one place, which division carries AV and which sections the AV bidder must read.
The drawings and the specification disagree. The floor plan shows a display. The AV sheet shows a projector. The spec book mentions both, with different quantities. Each bidder resolves it in whichever direction is cheapest for them, and nobody is bidding the same room.
Silence on what has to exist for AV to work. Power behind the display, a data drop on the right side of it, backing in the wall, conduit to the podium. If the AV section says nothing, the bidder either prices it and looks expensive or excludes it and looks cheap. Part 1 is about that gap and the change orders living in it.
No closeout requirements. If the spec does not ask for test results, labeling, as-builts, training, and a warranty path, the bidder who includes all of it is bidding against one who does not. The owner pays the difference later from a different budget line.
2. Writing a biddable spec: performance first, products second
Start with what the room has to do, then let the equipment follow. For each space, say what success looks like in terms somebody can verify on site:
- What gets displayed, and from where. Sources, expected resolution, and whether a guest laptop has to work.
- Who has to see it, and from where. "Readable from the back row of a 36-foot classroom" is a criterion; "75-inch panel" is a guess that happens to be a number.
- Who has to hear it. Speech intelligibility across the seated area, not a speaker count.
- Who operates it. A teacher with no training, a technician, a volunteer on a Saturday. This decides the control system, and it is almost never stated.
- What it connects to. The district network, a bell or paging system, an existing head end. Integration with an existing system is the scope item most often discovered after award.
- Where it physically lives. Mounting location, height, rack location, and what the wall and ceiling are made of if you know.
Then specify products as a basis of design: a named model that meets the criteria, plus the salient characteristics anything else would have to match. That phrase is doing real work — it is the difference between "or equal" meaning "anything with a screen" and "or equal" meaning something a reviewer can evaluate.
Keep the salient list short and testable. For a display: diagonal, native resolution, brightness, input complement, touch capability if required, mounting standard, warranty term. Seven lines, and a reviewer can hold an alternate against it in ten minutes. A twelve-page list of every feature on one datasheet is a brand-name spec wearing a performance costume, and bidders recognise it immediately.
3. Make the approved-equal process real
An "or equal" clause with no process attached is where good bids go to die: the bidder cannot tell whether an alternate will be accepted, so they either price the named product — and you have a brand-name spec after all — or price the alternate and hope.
Put the mechanics in the documents: substitution requests due a stated number of days before bid; a required submission (datasheet, a line-by-line comparison against the salient characteristics, any differences in mounting or power, warranty terms, and what else has to change); one named reviewer and one ruling date; and approvals issued by addendum, so everyone bids the same set. That last point keeps the process defensible, and it costs nothing.
Then name the submittals you want after award, because "submit product data" produces a stack of PDFs nobody can check: product data organised by the spec's own numbering; shop drawings with rack elevations, signal flow, and device locations coordinated against the architectural plans; mounting details for anything structural, with weight and backing called out; a proposed test plan, room by room; and sample closeout documentation, so you see what their package looks like before the end of the job rather than at it.
On repeated rooms, require a mockup: one classroom built out and demonstrated before the rest are released. It is the cheapest insurance on a multi-room rollout. The mockup is where you learn the drawing's panel height puts the touch surface out of reach for a fifth-grader. Learning that once costs a day; learning it ninety times costs a change order.
4. Draw the scope line inside the documents
The highest-value page in an AV specification is the one saying who buys and who installs each item. It is also the page most often left out. Make a table, and name the responsible party for every element:
- Line voltage power at each device and at the rack.
- Conduit, sleeves, back boxes, and pathway — frequently split, and the split belongs in writing.
- Structural backing for wall-mounted devices, which has to happen during framing.
- Network cabling, patching, and switch ports — often the district's IT department rather than any contractor on site.
- Network configuration and addressing — almost always the owner's IT staff, and almost never scheduled.
- Millwork cutouts, podium fabrication, and credenza ventilation.
- Lifts, floor protection, and after-hours access.
- Owner-furnished equipment, and who receives, stores, and warrants it.
Then be careful with allowances. An allowance suits genuinely undefined work — an unknown number of relocated outlets in an existing building. It is a poor tool for work you simply have not specified, because it invites every bidder to carry the same arbitrary number and tells you nothing about who understands the job. Where quantity is the only unknown, unit prices are better: a per-classroom price for a defined package, a per-drop price for added cabling, an hourly rate for after-hours work. Those compare in a way a lump sum never does.
5. The pre-bid site visit and the questions nobody asks
On an existing building, a real pre-bid site visit is worth more than another ten pages of specification. Open the rooms. Open a ceiling tile. Let bidders see the wall construction, the existing rack, the actual distance from the mounting location to the nearest outlet, and the state of the pathway they are being asked to reuse. A walkthrough where everyone stands in a corridor looking at a door is a formality, and formalities do not reduce spread.
Expect the good bidders to ask awkward questions, and treat them as a gift:
- What is behind this wall, and has anybody verified it?
- Is the existing conduit usable, or is it full?
- Who owns the network drops, and when will they be live for testing?
- What are the access hours, and does that include summer and weekends?
- Is there owner-furnished equipment, and where is it now?
- What does "substantial completion" mean for AV on this job, specifically?
Answer all of it by addendum, in writing, to everyone — a question answered in a hallway to one bidder is an advantage you did not mean to give. And if a question exposes something the documents got wrong, the addendum is a cheap fix; the same discovery after award is a change order. One more line worth adding to the instructions to bidders: require each response to list its exclusions and assumptions. A bid with no exclusions has not been thought about, and a bid whose exclusions you can read is a bid you can compare.
6. Evaluating responses when low price is not the whole story
Many public procurements come down to price among responsive, responsible bidders — and both of those words are defined by the bid documents. Decide what they mean for AV before the responses arrive, and say so. Your procurement office will tell you which evaluation structures are available to you; ask before you design one.
Worth stating as requirements rather than hoping for:
- Relevant experience — comparable projects, not years in business. Occupied campuses, multi-site rollouts, work phased around an academic calendar. A firm that does beautiful boardrooms has not necessarily worked around a bell schedule.
- References you actually call. Two or three recent projects of similar size, with a contact who was on site. Ask about the closeout and the service response, not the install.
- Licensing and insurance, verified rather than filed. Ask your own procurement and risk staff what this project requires — it varies by owner, scope, and jurisdiction — and state it plainly rather than leaving bidders to interpret.
- Who is actually on site. Are the technicians the bidder's own W-2 employees or subcontracted day labor, and how many simultaneous crews can they field? On a campus with badging, that is an accountability question before it is a staffing one.
- Background screening and badging. If the site requires it, require it in the bid. A firm that has never done it will discover the lead time at the worst moment.
- A named project manager for the duration. Rollouts fail on coordination long before they fail on technology.
- Closeout deliverables, priced in. Test documentation, labeling, as-builts, an asset list with serial numbers, warranty registration, manuals, training hours. Part 6 is the detail of what good looks like; omit it and you are comparing a bidder who included it against one who did not.
- Service after turnover. Response time, who answers, for how long. A system is a ten-year commitment, and the bid is the only moment you have leverage over year two.
When the spread is still wide after all that, read the low bid against its exclusion list rather than against the other bids. Nine times in ten the gap is not sharper pencils — it is a scope item somebody left out, and finding it before the award is the whole point of asking for the list.
7. Schedule realism on a school calendar
AV is the last trade in and the first one blamed, and on a school job the calendar does not negotiate. A bid set that is unrealistic about schedule produces either a bid with a contingency buried in it or a bid that will fail, and you cannot tell which from the number. So put the real constraints in the documents:
- Actual access windows, including instructional-day restrictions, testing weeks, and anything that closes the building.
- When the network will be live — AV cannot be commissioned against a network that is not up, and this dependency slips more often than any other.
- When rooms will genuinely be AV-ready: walls finished, power on, pathway complete, backing in, room secure. Part 3 covers that checklist and why releasing a room early costs more than releasing it late.
- A commissioning and training window with its own duration, not a footnote on the last day of install.
- Phasing, if the building turns over in sections.
- Whether after-hours and weekend work is expected — because a bidder who priced days against one who priced nights is not a comparison.
Then leave room for long-lead items. A specification written a year before installation is quoting a market that will have changed, and the approved-equal process is your release valve — one more reason to make it work.
The short checklist
Before an AV scope goes out for public bid:
- Does every space have performance criteria somebody could verify on site?
- Is equipment a basis of design with a short, testable list of salient characteristics?
- Does the approved-equal process have a deadline, a required submission, a named reviewer, and a ruling by addendum?
- Does one page say which division carries AV and which sections the AV bidder must read?
- Is there a table naming who buys and who installs power, pathway, backing, and network?
- Have the drawings and the specification been read against each other for conflicts?
- Are allowances limited to genuinely undefined work, with unit prices where only quantity is unknown?
- Will the pre-bid visit open the rooms and the ceilings?
- Will every question be answered by addendum to all bidders?
- Are bidders required to list exclusions and assumptions?
- Are experience, references, licensing, insurance, crew makeup, and badging stated as requirements?
- Are closeout deliverables and a training allotment specified, so they are in everyone's number?
- Does the schedule carry real access windows, a real network-live date, and its own commissioning window?
Thirteen questions. Working through them takes an afternoon. Not working through them is how a project ends up with three bids, a canyon between them, and no defensible way to pick.
The common thread
A good public AV bid is not the one that attracts the lowest number. It is the one where the numbers mean the same thing. Performance criteria so a bidder knows what they are being asked to achieve. An approved-equal path so competition is real instead of decorative. A scope table so nobody guesses at the trade boundary. Closeout requirements so the deliverable is a working system rather than mounted equipment.
Write it that way and the award is easy, because the evaluation already happened — on paper, before the bid opened, where it is cheap.
How ASC works with design teams, districts, and GCs
ASC has provided AV subcontractor services to prime contractors, general contractors, and AV resellers for over three decades, which means we have read a lot of AV specifications from the responding side. We know which sentences produce a spread and which ones produce comparable numbers.
We can review a draft AV specification and scope table before it goes out and tell you where bidders will diverge, what the drawings and the spec book disagree about, and which dependencies — power, pathway, backing, network, access — will come back as questions or change orders. On the responding side, we price AV scopes for GCs and resellers under their brand, with the exclusions written down, and we do not compete for their client. Our crews are W-2, licensed, and insured, with certificates available before the first job.
Got an AV scope heading out to bid? Send us the documents — we'll read them the way a bidder will, tell you what we see, and quote the scope in 24–48 hours.