Close viewing distance changes what an outdoor LED display specification must prove. At short range, pixel-level defects, uneven brightness and coarse low-brightness grading become visible to pedestrians, so tender clauses hold up when written as verifiable minimum requirements with named evidence. This guide shows European AV consultants and specifiers how to define the viewing scenario, write display, environmental and acceptance clauses, and require a supplier response format that keeps outdoor LED display quotes comparable before award.
This guide is written for AV consultants, specifiers and project teams preparing tender documents for outdoor LED displays installed at close viewing distance: storefront fascias, urban facades, pedestrian zones and transport hubs. It explains how to convert viewing conditions into verifiable specification clauses, which performance, environmental and acceptance requirements to document, and what evidence a supplier should provide with each response. A copyable minimum requirements template is included for direct use in RFP and tender documents.
Why Close-View Projects Need a Different Drafting Logic
An outdoor LED display can pass delivery inspection and still disappoint in a city-center installation. The reason is viewing distance. A roadside screen is read from 30 metres or more, where individual pixels blend together and small defects stay hidden. A storefront screen, a facade display above a pedestrian route or a transport-hub screen is read from 3 to 8 metres, close enough to expose pixel structure, uneven brightness between modules, banding in dark scenes, surface glare and color shifts between cabinets.
Specifications copied from billboard practice inherit a wrong assumption: that acceptance happens at a distance. A screen can meet all quoted numbers and still look flawed to a passing pedestrian.
This is why LED screen tender requirements for urban, close-view projects need a different drafting logic. Three clause styles appear in real tenders:
- Marketing targets. Phrases such as “high brightness” or “high image quality” describe an intention. A supplier can claim compliance while delivering widely different hardware.
- Minimum requirements. A testable threshold with a measurement method, for example a brightness value with a declared measurement condition, or an ingress protection code with a named test standard. Suppliers either meet the threshold or state an exception.
- Response promises. Statements a bidder makes about future behavior, such as spare-part availability. These belong in the commercial section, backed by documented commitments.
Only the second style produces comparable bids. The rest of this guide applies that principle clause by clause, in the order a specifier meets them.
Define the Viewing Scenario First
Each performance clause depends on how close people stand to the screen and how they read it, so the scenario belongs at the top of the template, ahead of hardware numbers.
Record as specification preconditions:
- Closest realistic viewing distance, in metres, measured from the nearest public position where a person can stand.
- Typical viewing distance, where most of the audience spends most of the time.
- Audience state. Pedestrians standing and reading, passing foot traffic, slow road traffic or passengers in a dwell area all read content differently.
- Content type. Full-motion video, text-heavy information, brand graphics or mixed schedules.
- Mounting height and vertical offset. A screen mounted above eye level is read at an angle, which changes effective image quality at the edges.
- Ambient light conditions. Direct sun exposure, reflected light from opposite facades, and night operation with dimming.
These preconditions do two jobs. They let bidders propose a suitable configuration, and they let you evaluate proposals against the same scenario instead of against generic datasheet values.
Pixel pitch comes after the scenario, because it is a derived value. Common pixel pitch viewing distance guidance only gives a rough range; content type and audience state narrow it down. A workable clause states the viewing scenario, then requires the bidder to declare the proposed pixel pitch and justify it against that scenario. For most close-view urban installations, common practice places suitable pitches roughly between P2.5 and P4, with finer pitches justified by detailed content or very short distances. Treat the range as a starting point for discussion and confirm the final value per project, because pitch interacts with budget, module layout and viewing angle.
Display Performance Clauses
Write each performance clause as a minimum threshold plus a verification method. A threshold that lacks a named verification method tends to get renegotiated during delivery.
Pixel Pitch and Resolution
Require the bidder to state the active display area in millimetres and the resulting resolution, calculated for the actual enclosure opening. Close-view projects often have odd architectural dimensions that rarely fit a clean module grid, so the specification should require a pixel map of the proposed layout. This avoids accepting a nominal pitch value that produces gaps or stretched content in the real active area.
Brightness and Dimming
State the required brightness as a minimum value with a declared measurement condition, and add an automatic dimming requirement for night operation. Urban close-view screens face both midday sun and dark evening streets, so the dimming range matters as much as the peak value. Commonly specified ranges for sun-exposed urban installations sit between roughly 4,500 and 6,000 nits, but the correct value depends on orientation, shading and local conditions, so confirm per project. Verification: manufacturer datasheet plus a measured reading at commissioning.
Refresh Rate and Grayscale
Camera-friendly refresh rates matter when broadcast, filming or frequent smartphone capture is expected; 3,840 Hz is a common specification point for that purpose. Grayscale depth matters more at close range at night, where coarse low-brightness grading shows as banding in dark content. Include both clauses only when the content scenario calls for them, and state the test condition for each.
Viewing Angle
Pedestrians often see a facade screen from the side, so viewing angle matters more here than on a roadside screen. Require declared horizontal and vertical viewing angles, and ask the supplier to state the measurement definition behind the figures, because angle values vary with the definition used.
Environmental and Structural Clauses
Ingress Protection, Front and Rear Separately
Ingress protection is defined by IEC 60529, which uses a two-digit code: the first digit covers solids, where 6 means dust-tight, and the second covers water, where 5 means low-pressure jets and 6 means powerful jets. Two details matter for tender drafting. An “X” in a code position means that property was untested, and jet protection plus immersion protection are separate tests, so an immersion rating alone says little about jet performance.
Require front and rear IP ratings as separate line items, each referencing IEC 60529 and the tested configuration. Outdoor LED enclosures are commonly specified at IP65 or higher on the front; the rear value should match the actual mounting condition, such as a ventilated rear against a facade. Verification: test report naming the standard and the tested configuration.
Operating Temperature
State the expected ambient temperature range for the site and require the declared operating range of the complete assembly. Datasheets list wide temperature ranges, but the requirement should come from the site climate, confirmed per project.
Electromagnetic Compatibility
For a European LED screen RFP, EMC clauses carry legal weight. Multimedia equipment falls under EN 55032 for emissions and EN 55035 for immunity, which replaced the older AV and IT equipment standards, and EN 55032 distinguishes Class A (industrial environments) from Class B (residential environments, with stricter limits). Harmonic current and flicker limits are covered separately by EN 61000-3-2 and EN 61000-3-3. Write the clause as: compliance with the applicable EMC standards for the installation environment, evidenced by test reports from an accredited laboratory, with the class declared.
Structure and Wind Load
Structural design, wind load and fixing design belong to the project engineer under local codes. The specification should name the responsibility boundary and require the bidder to declare screen weight, fixing points and any load assumptions used.
Acceptance Evidence Clauses
Acceptance clauses decide whether a specification can be enforced, and they are the weakest part of most generic LED screen RFP templates in Europe. Require, as a minimum:
- Test reports from accredited laboratories for the claimed IP rating, EMC class and safety compliance, each naming the standard and the tested configuration.
- Calibration records for brightness and color uniformity, captured after final assembly of the delivered configuration.
- Sample or mockup verification for close-view projects, viewed at the closest realistic distance under day and night conditions before full production.
- Brand disclosure for major components, including LED lamps, driving ICs, power supplies and the control system. A clause that requires named components rules out vague equivalents.
- Reference projects with location, application, screen area, pixel pitch and installation date, with consent to contact.
The EU declaration of conformity deserves its own clause. Under EU rules, the manufacturer, whether based inside or outside the EU, is responsible for the conformity assessment, the technical documentation and the signed DoC, which must identify the product, the applicable legislation and the harmonised standards used. A component carrying CE marking covers only that component; the party placing the finished display on the market issues the DoC for the whole product. The tender should require the DoC before delivery and allow verification against the declared standards.
Finally, require a line-by-line supplier response: for each specification line, the bidder marks Comply, Comply with comment, or Exception, with the offered value stated. This single formatting requirement makes quotes comparable and exposes deviations early.
Commercial Scope Clauses
Keep the commercial section short and factual:
- Spare parts. A stated percentage of modules and a list of power and control spares, delivered with the screen.
- Warranty and response. Duration, coverage and the documented response commitment for on-site faults.
- Documentation. As-built drawings, manuals, calibration records, the DoC and test reports, in the project language.
- Training. Sessions for the operating team, with duration and participant count stated.
Copyable Minimum Requirements Table
Use this LED display specification template as the tender annex. Fill the target column per project; the verification column stays fixed.
| # | Parameter | Minimum Requirement (confirm per project) | How to Verify | Supplier Response |
| 1 | Viewing scenario | Closest / typical distance, audience state, content type declared | Specified in tender; bidders design against it | Scenario confirmation |
| 2 | Active display area | Width x height in mm, from the enclosure opening | Pixel map for the actual layout | Declared resolution |
| 3 | Pixel pitch | Proposed value justified against scenario | Pixel map plus datasheet | Declared value and layout |
| 4 | Brightness | ___ nits minimum, declared measurement condition | Datasheet plus commissioning measurement | Meets / exception |
| 5 | Dimming | Automatic dimming range for night operation | Dimming curve in documentation | Declared range |
| 6 | Refresh rate | ___ Hz, if camera use is expected | Datasheet with test condition | Meets / exception |
| 7 | Grayscale | Declared processing depth, low-brightness behavior stated | Grayscale test content on mockup | Declared value |
| 8 | Viewing angle | Horizontal / vertical, with fallback definition | Datasheet stating the definition | Declared values |
| 9 | IP rating, front | IP6X-5 or higher per IEC 60529 | Test report naming standard and configuration | Meets / exception |
| 10 | IP rating, rear | Matched to mounting condition per IEC 60529 | Test report | Meets / exception |
| 11 | Operating temperature | Site climate range, complete assembly | Declared range per configuration | Declared range |
| 12 | EMC | EN 55032 class declared, EN 55035 immunity, EN 61000-3-2 / -3-3 | Accredited lab test reports | Class and reports |
| 13 | DoC | EU DoC issued by the party placing the product on the market | Document before delivery, standards verifiable | Provided |
| 14 | Spares | ___ % modules plus power and control spares | Delivery checklist | Provided list |
Common Specification Mistakes
- Copying a datasheet into the tender. Datasheets describe one configuration under one condition. A specification should state the required outcome and the verification method, then let suppliers declare their configuration.
- Specifying brightness as a single peak number. Peak brightness says little about night operation. Pair the peak value with a dimming requirement and a measurement condition.
- Writing one IP code for the whole screen. Front and rear face different exposures, and the code applies to the tested configuration. Split the line item and require the test report.
- Accepting component certificates as system compliance. A CE-marked component covers itself only. The finished display needs its own DoC and evidence, issued by the party placing it on the market.
Conclusion
The value of a close-view outdoor LED specification is decided before any bid arrives. The viewing scenario turns subjective image quality into testable clauses; minimum thresholds with named verification methods keep suppliers comparable; acceptance evidence, from IP and EMC reports to the EU DoC, ties the delivered screen to the tender text. Drafted this way, the specification protects the project through delivery, commissioning and the years of night operation that follow. To discuss display configurations for a specific close-view urban project, contact the Unishine team with your specification draft.
FAQ
What should be in an outdoor LED display specification?
Scenario preconditions, performance minimums with verification methods, environmental clauses referencing named standards, acceptance evidence requirements and a supplier response format. The specification defines what counts as proof, and leaves configuration choices to the bidders.
How do you specify pixel pitch for close viewing?
Start from the closest realistic viewing distance, audience state and content type, then require bidders to propose and justify a pitch against that scenario. Common urban close-view practice falls roughly between P2.5 and P4, confirmed per project, with the pixel map for the actual active area required as evidence.
Which certifications should a European LED tender require?
EMC compliance under EN 55032 and EN 55035 with the class declared, harmonic and flicker compliance under the EN 61000-3 series, evidence of conformity with applicable safety legislation, and the EU DoC issued by the party placing the product on the market. Test reports should come from accredited laboratories and name the tested configuration.
How do you verify specifications before award?
Require the line-by-line response format, check claimed values against the named test reports, confirm the pixel map against the enclosure opening, and use references and, for close-view projects, a mockup viewing at the closest realistic distance.
