The School RFP Checklist for LED Display Procurement
A working checklist for writing an LED display RFP that actually protects the district, covering spec requirements, timeline constraints, warranty language, and the total-cost-of-ownership questions most RFPs never ask.
Most LED display RFPs are written once and copied forever
A lot of school procurement documents for LED displays get inherited from a template written for a different venue, a different climate, or a different era of panel technology, then get copied forward project after project with minimal updates. The result is an RFP that asks vendors for a warranty period and a price, but never asks the two or three technical questions that actually determine whether the winning bid is the right product for the room. This checklist is built around the questions that belong in every school LED display RFP, organized the way a facilities director or purchasing officer would actually work through them.
Viewing distance and pixel pitch: get this wrong and nothing else matters
Pixel pitch (the distance in millimeters between LED clusters) determines how close a viewer can stand before individual pixels become visible, and how far they need to be for the image to look seamless. An RFP that specifies a pixel pitch without reference to actual viewing distance is asking vendors to guess, or worse, letting the lowest bidder guess in the direction that's cheapest for them.
Require the closest viewer distance in writing
The RFP should state the closest realistic viewing distance for the installation, front-row bleacher seating, the nearest classroom desk, or the closest point pedestrians pass a lobby display, so bidders spec pixel pitch against a real number instead of an assumption.
Ask bidders to show their math
Require each bidder to state the pixel pitch they're proposing and the minimum comfortable viewing distance that pitch supports, so the district can compare proposals on a like-for-like basis rather than trusting a vendor's brightness claims at face value.
Indoor vs. outdoor: the IP rating question that gets skipped
An IP (Ingress Protection) rating describes how well an enclosure resists dust and water. Indoor gym and classroom displays don't need the same rating as an outdoor stadium board exposed to rain, humidity, and temperature swings, but an RFP that's silent on IP rating leaves the door open for a bidder to substitute indoor-rated components into an outdoor application to hit a lower price.
| Environment | What the RFP should require |
|---|---|
| Indoor classroom / hallway | Standard indoor enclosure rating; no water/dust ingress requirement beyond normal indoor conditions. |
| Gym / auditorium | Indoor-rated but should specify tolerance for ambient humidity from HVAC cycling and occupancy load. |
| Stadium / outdoor marquee | Outdoor IP rating explicitly required in writing, along with a stated operating temperature range covering the district's actual climate extremes, not just a generic "weatherproof" claim. |
Nits requirements for daylight-visible outdoor boards
Nits measure brightness. An outdoor board that looks great in a vendor's evening demo video can wash out completely under direct afternoon sun if it wasn't specified for daylight visibility. The RFP should require a minimum nit rating appropriate to the installation's sun exposure, not just "outdoor rated," and should require the bidder to state the actual nit output of the proposed panel, not a marketing range.
Indoor gym or auditorium
Typically requires enough brightness to stay legible against gym lighting and window glare, generally in the hundreds to low thousands of nits depending on the space's ambient light.
Outdoor stadium or marquee
Needs enough brightness to remain readable in direct sunlight, which is meaningfully higher than indoor requirements. The RFP should require the bidder to confirm daylight readability, not just peak nit output on a spec sheet.
Installation timeline constraints around the academic calendar
An RFP that doesn't address the academic calendar risks a bid that assumes standard commercial installation timing, which rarely fits a school's actual constraints. Build these into the requirements, not just the "nice to have" section:
- Stated installation window: require bidders to confirm installation can be completed within your actual break period (summer, winter intersession, or a defined non-instructional window), not just a general lead-time estimate.
- Manufacturing and freight lead time, in writing: require a specific number of weeks from contract execution to on-site delivery, since this is the number most likely to push an installation into the school year if it's vague.
- Noise and access restrictions: for gym, hallway, or classroom installs during a partial-occupancy period, require a plan for containing dust, noise, and site access around active school operations.
- Commissioning and staff training date: require a specific date for final commissioning and hands-on training for AV or facilities staff, not an open-ended "training provided" line.
Warranty and service-response-time requirements
A warranty length by itself doesn't tell a district what happens when a panel fails during a Friday night game or a Monday morning assembly. The RFP should require specifics:
Warranty scope and length, in writing
Require the bidder to state exactly what's covered (panels, power supplies, structural mounting, control systems) and for how long, rather than accepting a general "manufacturer's warranty applies" statement. A 3-year warranty with ongoing support for as long as the district owns the panels is a real, verifiable example of the kind of specific commitment an RFP should be able to hold a vendor to.
Service response time, quantified
Require a stated response-time commitment for service calls, not just "prompt service." Ask whether the vendor has a physical service presence in your region or relies entirely on remote diagnostics and third-party technicians, since that materially affects how fast a real repair happens.
References and track record questions
Every RFP should require verifiable references, but the questions asked of those references matter more than the fact that references were provided at all. Useful questions to require:
- How long has the manufacturer been producing LED panels, and where are they manufactured?
- Does the vendor have a physical office or service presence in the region, or is support entirely remote?
- Can the vendor provide references specifically from K-12 or higher-ed installations, not just commercial or event-industry clients?
- What does the vendor's actual proposal process look like? Does it include a personalized proposal with a mockup, full specs, and a cost breakdown, or just a line-item quote?
A vendor with a real, describable process, for example: a free no-pressure quote request, followed by a personalized proposal with a mockup, specs, and cost breakdown, then installation, then support backed by a real warranty, is easier for a purchasing committee to evaluate on paper than a vendor who can only describe their process in generalities.
The questions that matter more than sticker price
The purchase price on a bid tab is the easiest number to compare and the least complete one. An RFP that only scores on sticker price will systematically favor the bidder who left the most out of their quote. Require every bidder to answer these in writing:
Installed cost, not panel cost
Does the quote include mounting, structural work, electrical, data/control cabling, and commissioning, or only the panels themselves?
Expected panel lifespan
What is the panel's rated operating hour lifespan, and what does that mean in realistic calendar years given the district's actual daily usage pattern, not a generic 24/7 assumption?
Post-warranty support cost
What happens, and what does it cost, if a repair is needed after the warranty period ends? Is there an ongoing support relationship, or does the district need a new vendor relationship entirely?
The content management and access questions that belong in every RFP
A display is only as useful as the system controlling what's on it, and this is another area where a bare-bones RFP tends to go silent. Require bidders to answer these directly rather than leaving control-system detail to be discovered after the contract is signed:
- Who can update content, and how: does the proposed control software allow athletics staff, communications staff, and AV/IT staff appropriately scoped access, or does every content change require a vendor service call?
- Integration with existing systems: does the display need to pull live data from an existing scoreboard console, a scheduling system, or an emergency notification system, and has the bidder confirmed compatibility rather than assuming it?
- Licensing and ongoing software cost: is content management software a one-time cost, an annual license, or bundled into the support agreement? This belongs in the total-cost-of-ownership conversation, not a footnote discovered at renewal time.
- Training for the actual end users: require a specific commitment to train the staff who will operate the display day to day, not just the installation crew who hands it off.
Weight the scorecard so price isn't the only variable that wins
Many public procurement policies require price to carry meaningful weight in an evaluation, but "meaningful" doesn't have to mean "dominant." A scorecard that allocates a defined percentage to technical compliance (does the proposed pixel pitch and brightness actually match the stated viewing distance and environment), a defined percentage to vendor qualification and references, and a defined percentage to total cost of ownership, alongside price, gives an evaluation committee a documented, defensible basis for choosing something other than the lowest bid if the lowest bid doesn't actually meet the spec. Publish the weighting in the RFP itself, not just internally, so every bidder knows technical fit and long-term cost are being scored, not just the number on the bid tab.
It's also worth requiring bidders to respond to each checklist item individually, in the same order the RFP presents them, rather than accepting a general narrative proposal. A side-by-side compliance matrix, pixel pitch, IP rating, nits, installation timeline, warranty terms, service response time, TCO answers, each with a bidder's specific response next to it, turns a subjective "which proposal feels more thorough" evaluation into a much faster, more defensible comparison for a purchasing committee or board.
Two habits that quietly weaken an otherwise good RFP
Copying a template built for a different venue
An RFP written originally for a classroom rollout, then reused for a stadium board with only the dollar amount changed, tends to be silent on exactly the things that matter most for outdoor installs: IP rating, daylight nits, and wind-load mounting requirements. Every RFP should be reviewed line by line against the actual venue, not just copied forward from the last one.
Treating higher-ed and K-12 procurement as identical
University and college procurement often runs through a separate purchasing department with different thresholds, approval chains, and sometimes a preference for multi-year master service agreements over a single-project RFP. A district assuming the same document and timeline will work for both a K-12 gym board and a university stadium project is likely to hit friction that a venue-specific and buyer-specific RFP would have avoided.
Related resources
For a deeper look at how module technology affects the specs in this checklist, see our LED display module technology guide. If you're scoping a gym or auditorium project specifically, our Gym & Auditorium Video Boards page walks through the Imagine tier spec range referenced above. And if this RFP is for a stadium board, see Stadium & Outdoor Video Boards for outdoor-specific brightness and IP-rating guidance.
Want a second set of eyes on your RFP before it goes out?
Request a free, no-pressure quote and we'll help you check your spec language against the venue before you publish the solicitation.
Request a Spec & Quote