Digital Signage RFP Template and Checklist for IT Teams

A well-structured digital signage RFP (request for proposal) is the difference between a competitive, informed procurement and a decision made on whoever had the most persuasive sales rep. This guide gives you a complete RFP framework, the sections to include, the questions to ask vendors, and the scoring criteria that separate capable platforms from ones that will disappoint you in year two.

When to write a formal RFP

A formal RFP is appropriate when: you’re deploying 20+ screens, the annual contract value exceeds £15,000–20,000, you have multiple stakeholders with different requirements, or your organisation’s procurement policy requires competitive tendering above a threshold. For smaller deployments, a structured requirements checklist and direct vendor evaluation may be more proportionate.

RFP structure

Section 1: Project overview

Set the context so vendors understand the scope before responding:

• Organisation name and type (industry, size, number of locations)
• Project summary: what you’re trying to achieve, not what you want to buy
• Current state: what exists now (if anything), what’s working, what isn’t
• Timeline: desired go-live date, pilot dates, decision deadline
• Budget range (optional but useful, vendors who can’t compete on budget will self-select out)

Section 2: Scope and requirements

Split into must-have and nice-to-have. Must-haves are evaluation gates, any vendor who can’t meet them is disqualified. Nice-to-haves are scored.

Sample must-haves for a corporate office deployment:

• Cloud-based CMS with browser-based admin, no desktop software installation required for content management
• Support for [number] screens across [number] locations
• Microsoft 365 / Exchange integration for calendar-driven content
• Role-based access control, site managers can manage their screens only
• Remote monitoring, online/offline status, screenshot preview, alert notifications
• Emergency message override, push to all screens instantly from central admin
• GDPR-compliant data processing, EU data residency or equivalent protection
• Minimum 99.5% platform uptime SLA

Sample nice-to-haves:

• Native Power BI / Tableau dashboard display
• Wayfinding module
• Interactive/touchscreen content support
• AI-assisted content generation
• API for integration with existing enterprise systems
• Multi-language content support

Section 3: Technical requirements

• Supported hardware platforms (existing hardware if applicable, or preferred hardware)
• Network requirements, bandwidth, firewall rules, VPN requirements
• Security requirements, SSO/SAML, MFA, penetration testing cadence, security certifications (SOC 2, ISO 27001)
• Integration requirements, list specific systems: M365, Active Directory, POS, BMS, HR system
• Offline playback, does the player continue operating if the cloud connection is lost?
• Content storage, where are content assets stored? What’s the storage limit per account?

Section 4: Vendor information required

Ask vendors to provide:

• Company overview, founding date, ownership, number of employees, HQ location
• Customer references, 3 references of similar scale and industry, willing to be contacted
• Platform stability, uptime history for the past 12 months (ideally via public status page)
• Security posture, current certifications (SOC 2, ISO 27001), most recent pen test date and findings summary
• Data processing agreement, standard DPA available, or custom required?
• Support model, response SLAs by severity, support channels, hours of operation, escalation path
• Roadmap, what major features are planned in the next 12 months?
• Pricing, full pricing for the specified scope, including all tiers, add-ons, and implementation costs

Section 5: Pricing requirements

Request pricing structured as:

• Software licence: per-screen/per-month, volume tiers, annual vs monthly billing differences
• Implementation and onboarding: professional services hours, remote vs on-site
• Hardware (if vendor-supplied or recommended): itemised per device type
• Training: end-user training, admin training, ongoing training resources
• Support tiers: what’s included in the licence, what’s additional
• 3-year total cost of ownership model

Section 6: Demonstration requirements

Shortlisted vendors should demonstrate:

1. Creating and publishing a piece of content from scratch (tests ease of use)
2. Scheduling content for specific time windows across multiple screen groups
3. Demonstrating the Microsoft 365 integration (or your required integration) in a working environment
4. Pushing an emergency override message to all screens
5. Demonstrating the remote monitoring dashboard
6. Walking through the RBAC configuration

Scoring framework

Score shortlisted vendors across these categories (adjust weighting for your priorities):

Common RFP mistakes to avoid

• Over-specifying hardware, specify functional requirements (brightness, connectivity) rather than model numbers; you may lock out platforms with better-fit hardware alternatives
• Confusing current state with requirements, “we currently use PowerPoint” is not a requirement; “content must support static image, video, and live data widgets” is
• Ignoring total cost of ownership, a £5/screen/month platform that requires £20,000 in professional services to configure is not cheaper than a £12/screen/month platform that deploys in a week
• Not checking references, references from similar-scale, similar-industry customers tell you things a demo never will
• Setting an unrealistic timeline, allow 4–6 weeks for vendor response, 2 weeks for scoring and shortlisting, 2 weeks for demos, 2 weeks for final selection. Rushing procurement produces bad contracts.

After the RFP: contract essentials

Before signing, ensure the contract covers: data portability (can you export your content if you switch platforms?), exit clause for material platform changes, SLA remedies (what happens if uptime SLAs are missed?), and price lock period (avoid surprise mid-contract price increases).

Bottom line

A well-run RFP process takes 8–12 weeks but produces a much better procurement outcome than a rushed vendor selection. The key is separating must-haves from nice-to-haves upfront, vendors who can’t meet must-haves should be disqualified before investing time in demos. For platform shortlisting, start with our digital signage buyer’s guide and our hidden costs guide to build a realistic TCO model.