Whether you’re planning to deploy a digital wayfinding solution in a hospital, airport, university, shopping mall or corporate campus, one of the first questions you’ll probably ask is: What information do I need before starting a digital wayfinding project?
Having the right information available early will help you understand the scope of the project, choose the right solution and significantly reduce implementation costs and time.
This guide explains the key information that companies typically gather before deploying a digital wayfinding solution, regardless of the type of building involved.
1. Understand the buildings where you want to deploy the solution
Every project starts with understanding the physical environment. Before thinking about maps, apps or indoor positioning, it is useful to identify the scope of the project.
A good first step is to build a clear picture of the spaces that will be included in the wayfinding experience. That means understanding not only the size of the site, but also how its different areas are organised and connected.
Key information includes:
- Number of buildings and floors.
- Approximate indoor and outdoor surface area.
- Connections between buildings, including indoor and outdoor transitions.
- Public, staff-only and restricted areas.
- Main entrances and access points.
- Parking areas and relevant outdoor paths.
This initial picture is important because two projects with a similar total surface area can have very different requirements. A single multi-floor building, for example, is not the same navigation challenge as a campus made up of several interconnected buildings and outdoor areas.
The goal is to understand where people need to navigate, how those spaces connect and which areas should be included in the experience. This will provide the foundation for defining the maps, routes and navigation experience later in the project.
2. Gather your existing floor plans
Once the scope of the project is clear, the next step is to collect the floor plans and building documentation already available.
These files provide the starting point for creating the digital maps and understanding the layout of each space. Depending on the building, they may include:
- CAD drawings.
- Architectural plans.
- PDFs.
- Existing digital maps.
In practice, plans may contain outdated room layouts, areas that are irrelevant to visitors or levels of technical detail that are unnecessary for navigation. These elements can be reviewed and simplified during the mapping process. At this stage, the priority is to work from the most reliable and up-to-date representation available.
The goal is to generate a clear digital map that helps people understand and navigate the building.

3. Identify the key destinations in your building
Once the building layout is understood and the necessary floor plans have been gathered, the next step is to identify the destinations that users actually need to find.
These destinations are usually represented as Points of Interest (POIs) on the digital map. Depending on the type of building, they may include:
- Offices.
- Meeting rooms.
- Shops.
- Toilets.
- Elevators.
- Reception desks.
- Parking areas.
- Emergency exits.
Not every room or space needs to become a POI. The priority should be to identify the places that are relevant to visitors and useful for navigation. This helps keep the map clear and easy to use, while ensuring that the most important destinations can be searched, selected and used as part of a route.

4. Define the navigation experience
Once the building, maps and key destinations are understood, the next step is to define how users should interact with the wayfinding solution.
Different environments and user needs require different navigation experiences. Some projects may only need an interactive map, while others may require route guidance or real-time indoor navigation. These different levels of navigation involve different functional and technical requirements.
Different environments require different navigation experiences. The right approach depends not only on the needs and preferences of end users, such as who they are, how they move through the building and what information or level of guidance they need,but also on the objectives and requirements of the organisation. These may include improving the visitor experience, reducing navigation difficulties, supporting specific operational processes, integrating wayfinding into existing digital channels or deciding how much autonomy users should have when navigating the space.
As a result, some projects may only need an interactive map, while others may require route guidance or real-time indoor navigation. These different levels of navigation involve different functional and technical requirements.
Questions to consider include:
- Who will use the solution and how frequently? Visitors, employees, customers, patients, passengers or different user groups.
- What are the most common navigation journeys? For example, entrance-to-destination, between departments or between different buildings.
- Do users need to navigate between indoor and outdoor spaces?
- Do different users need different routes or access to different areas?
- Will users access the solution through a website, mobile app or kiosk?
- Should QR codes provide access from specific locations?
If you are not sure which level of navigation your project requires, our What Type of Building Map Do You Need guide explains the differences between an interactive map, route guidance and live indoor navigation. You can also use the Self-Assessment to get an initial recommendation based on your project requirements.
These decisions help define the functional scope of the project and determine which solution will fit your project. This is a particularly important decision because choosing real-time indoor navigation usually has a direct impact on the project scope and budget. Unlike an interactive map or route guidance solution, real-time navigation requires an indoor positioning system capable of determining the user’s location while they move through the building. Depending on the existing infrastructure, this may involve the acquisition and deployment of Bluetooth beacons, the configuration and implementation of the positioning system and its integration with the wayfinding solution or existing digital channels.
For this reason, the required level of navigation should be defined early in the project. It helps avoid introducing unnecessary technical complexity and ensures that the proposed solution is aligned with both user needs and the organisation’s objectives and available resources.

5. Define accessibility and user requirements
At this point, you know where people need to navigate and how you want them to navigate. The next question is whether that experience needs to adapt to different types of users.
Questions to consider include:
- Are step-free or wheelchair-accessible routes required?
- Should users be able to avoid stairs or other specific elements?
- Does the solution need to support different languages?
- Are there specific requirements for people with visual impairments?
- Do visitors, staff or other user groups have different navigation needs?
- Are there areas that should only be accessible or visible to specific users?
The important idea would be that accessibility should be considered when defining the map and routing model, rather than added once the solution has already been implemented.

6. Review your existing digital environment
Once the type of wayfinding solution and its main requirements have been defined, it is important to understand how it will fit into your existing digital environment.
In many cases, a wayfinding solution does not operate independently. It may need to be integrated into existing channels or use infrastructure that is already available.
Consider whether your organisation already has:
- A website or web portal where the map could be embedded or linked.
- A mobile app where wayfinding could be integrated.
- Interactive kiosks or digital signage.
- Existing indoor positioning infrastructure, such as Bluetooth beacons or compatible Wi-Fi infrastructure.
- Systems containing information that may need to be displayed or updated on the map.
- Other platforms or services that may need to exchange information with the wayfinding solution.
Understanding what is already available helps identify potential integrations, avoid duplicating infrastructure and determine what additional components may be required.
7. Define your available budget
Before selecting a solution, it is important to have at least a general understanding of the budget available for the project.
The budget can influence not only the type of navigation experience that can be deployed, but also the project scope, the number of buildings or areas included, the need for indoor positioning infrastructure, integrations and other specific requirements.
An interactive map or route guidance solution generally requires less infrastructure, for example a kiosk, than real-time indoor navigation, which may require the deployment of beacons and the implementation of an indoor positioning system.
You do not necessarily need to have a final budget at this stage. However, establishing a realistic budget range helps prioritise requirements and evaluate which solution provides the best balance between user needs, organisational objectives and available resources.
8. Define your expected timeline
It is also important to understand when the organisation expects the solution to be available and whether there are any fixed deadlines.
The implementation timeline can depend on factors such as the number and complexity of the buildings, the quality of the available floor plans, the amount of information that needs to be prepared, integrations with existing systems and whether indoor positioning infrastructure needs to be deployed.
Specific milestones may also influence the schedule, such as the opening of a new building, an event, a new app launch or a broader digital transformation project.
Defining these expectations early helps determine whether the proposed scope is realistic and which elements should be prioritised.
9. Identify the internal and external resources available
A digital wayfinding project requires some level of involvement from the organisation, although the amount of internal work can vary considerably depending on the solution and the support provided by the wayfinding provider or other partners.
Before starting, it is useful to understand what resources are available internally and what may need to be provided externally.
This may include access to building plans and information, validation of maps and POIs, technical support for integrations, coordination with facilities or IT teams, and management of content.
Understanding the available resources helps define responsibilities and determine the level of external support required during implementation and operation.
10. Consider future changes and updates
A digital wayfinding project should not only reflect how the building works today. Buildings and the information associated with them change over time.
Stores may open or close, departments may move, room names may change, new areas may be added and routes or access restrictions may need to be updated.
Before starting the project, consider:
- How frequently the building and its destinations change.
- Who will need to update maps and POIs.
- Whether the organisation wants to manage these changes internally or rely on external support.
- Whether the solution may need to expand to additional floors, buildings or locations in the future.
Considering these changes from the beginning helps ensure that the solution remains useful after launch and can evolve as the organisation’s needs change.
Summary
Successful digital wayfinding projects begin with understanding the building, the people who use it and the experience the organisation wants to provide.
| Information to prepare | Why it matters |
| Building scope | Defines the size and complexity of the project |
| Floor plans | Provides the basis for generating the digital map |
| Key destinations / POIs | Defines content generation workload |
| Navigation requirements | Determines the appropriate level of guidance |
| Accessibility requirements | Ensures routes work for different users |
| Existing digital environment | Identifies integrations and existing infrastructure |
Before moving into implementation, there are a few principles worth keeping in mind:
- Start with the visitor, not with the technology that seems most advanced or trendy.
- Understand your building before creating the map.
- Decide what information really matters to users.
- Define the navigation experience before choosing the technology behind it.
Gathering the right information before starting does more than make implementation easier. It helps define the real scope of the project, avoid unnecessary complexity and ensure that the final solution addresses genuine navigation needs.
Whether the project covers a single building or a multi-site campus, this preparation provides a stronger foundation for the decisions that follow and makes it easier to choose a solution that can evolve with the building over time.
They begin with understanding the building, the people who use it and the experience the organisation wants to provide.