← Blog Guides

Indoor Wayfinding RFP Checklist: Requirements, Questions, and Evaluation Criteria

Writing an RFP for indoor wayfinding software means balancing dozens of requirements — from map editing to analytics to accessibility. This checklist gives procurement teams a structured framework based on real-world evaluation criteria and proven indoor navigation technology.

Why wayfinding RFPs fail

Most indoor wayfinding procurements start with a vague requirement like "we need a digital map for our building." Without specific evaluation criteria, organizations default to the vendor with the best demo or the lowest sticker price — neither of which predicts long-term success.

Gartner's 2025 Technology Procurement survey found that 43% of facility technology purchases fail to meet expectations within two years, with the top reason being "requirements not clearly defined during procurement." A structured RFP prevents this by forcing both buyers and vendors to align on specifics.

The checklist below covers functional requirements, technical requirements, vendor questions, and evaluation scoring criteria. Adapt it to your organization's size, industry, and specific wayfinding challenges.

Functional requirements checklist

Map management: can you upload your own floor plan images? Does the platform support multiple buildings and multiple floors per building? Can non-technical staff add and edit markers without developer involvement? Is there a visual map editor with drag-and-drop marker placement?

Visitor experience: do visitors need to download an app, or does wayfinding work in a standard web browser? Can visitors search for locations by name? Does the system show a "You are here" indicator? Does the search work across multiple floors and buildings?

QR code support: does the platform generate QR codes for physical placement? Can QR codes be printed in bulk? Does scanning a QR code open the map at the correct location without requiring an app?

Multilingual support: can the interface display in multiple languages? Can marker names and descriptions be translated? Does the system detect the visitor's browser language automatically?

Accessibility: does the visitor-facing map meet WCAG 2.1 AA standards? Is the search function keyboard-accessible? Are screen readers supported for location names and descriptions?

The cost comparison between digital signage and QR wayfinding can help set budget expectations for different approaches.

Technical requirements checklist

Hosting and infrastructure: is the platform cloud-hosted (SaaS) or on-premise? What is the uptime SLA? Where is data stored geographically? Is the platform SOC 2 compliant?

Integration: does the platform offer a REST API for programmatic management? Are there webhook notifications for events like marker updates or scan activity? Can maps be embedded via iframe in existing websites and intranets? Is there SSO support (SAML, OAuth)?

Performance: what is the map load time on mobile devices? Does the platform work offline or in low-connectivity areas? What is the maximum supported map image resolution?

Scalability: how many buildings and maps can a single account support? Is there a limit on markers per map? What is the maximum number of concurrent visitors?

Security: is data encrypted in transit and at rest? What is the data retention policy? Can customer data be deleted on request? Is there a vulnerability disclosure program?

Questions to ask vendors

Implementation: what is the typical implementation timeline from contract to live deployment? Do you provide onboarding support? Can we import existing floor plans without redrawing them?

Total cost of ownership: what are all fees beyond the subscription price? Are there per-building fees, per-scan fees, per-user fees, or setup fees? What happens to our data if we cancel?

References: can you provide references from organizations similar to ours in size and industry? What measurable results did they achieve?

Roadmap: what features are planned for the next 12 months? How do you prioritize feature requests from customers?

Support: what support channels are available (email, phone, chat)? What is the average response time for support tickets? Is there documentation and a knowledge base for self-service?

The wayfinding software comparison guide provides additional evaluation criteria across leading vendors.

Evaluation scoring framework

Create a weighted scoring matrix to evaluate vendors objectively. Recommended weight distribution:

Visitor experience (25%): ease of use for visitors, no app requirement, search quality, mobile responsiveness, multilingual support.

Map management (20%): self-serve editor quality, bulk operations, multi-building support, update speed.

Total cost of ownership (20%): subscription cost, implementation cost, hardware requirements, ongoing maintenance cost, hidden fees.

Integration and technical fit (15%): API availability, embed options, SSO support, compliance certifications.

Vendor stability and support (10%): company size, funding, customer references, support quality, SLA.

Analytics and reporting (10%): scan tracking, search analytics, exportable reports, dashboard quality.

Score each vendor 1-5 on each criterion, multiply by weight, and sum for a total score. This removes subjective bias and makes the selection decision defensible to stakeholders.

Red flags to watch for

Mandatory app downloads: any vendor that requires visitors to install a mobile app will see dramatically lower adoption rates. Statista reports that 68% of consumers will not download an app for a one-time visit. Browser-based wayfinding is the standard visitors expect.

Hardware lock-in: vendors requiring proprietary beacons, sensors, or kiosks create long-term dependency and ongoing maintenance costs. Ask explicitly what hardware is required versus optional.

Per-scan pricing: some vendors charge based on the number of QR code scans or map views. This creates perverse incentives — you are penalized for success. Flat-rate pricing from platforms like QRCodeMaps (from $99/month) ensures costs are predictable.

No self-serve map editor: if you need vendor involvement to update a room name or move a marker, every change takes days instead of minutes. Self-serve map editing is essential for organizations where layouts change frequently.

No analytics: wayfinding without analytics is a black box. You cannot improve what you cannot measure. Ensure the platform provides scan counts, search logs, and zero-result tracking at minimum.

RFP template and next steps

Structure your RFP document in five sections:

1. Organization overview: describe your buildings, visitor volumes, and current wayfinding challenges. Include the number of buildings, floors, and estimated daily visitors.

2. Functional requirements: use the checklist above, marking each item as required, preferred, or optional.

3. Technical requirements: specify integration needs, compliance requirements, and infrastructure preferences.

4. Vendor questions: include the questions listed above plus any organization-specific queries.

5. Evaluation criteria: share the scoring weights so vendors understand your priorities.

Set a realistic timeline: two weeks for vendor responses, one week for demos, one week for reference checks, and one week for final decision. Total procurement cycle: five to six weeks.

QRCodeMaps is designed to score well on the criteria that matter most — no app requirement, self-serve map editor, built-in QR generation, and flat-rate pricing with no hardware dependencies. Start a free trial to evaluate against your specific RFP requirements.