Skip to main content

Wayfinding Planner - Before You Begin

Intro to WFP: what it does and doesn’t, data safety, learning curve, typical workflow, inputs, outputs, and current limitations.

Vladimir avatar
Written by Vladimir
Updated this week

What Wayfinding Planner Is

The Wayfinding Planner (WFP) application helps you create and update the Sign Schedule (also known as BoQ), the Message Schedule, and the Sign Location Plan, keeping them consistent throughout all stages of the project design cycle.

It is essentially designed to support you in:

  • Building a wayfinding system model by:

    • Defining pedestrian path network

    • Defining signage locations

    • Generating sign messages

    • Creating sign type schedules

  • Iterating and refining the model easily to achieve the most effective navigation system

  • Maintaining consistency across the project lifecycle by adapting on the fly to changes in:

    • Pedestrian path network and space configurations

    • Target Point (endpoint) names

    • Sign face locations, orientations, and quantities

What Wayfinding Planner Is Not

  • WFP is not a graphical design tool
    All graphic design should be done in dedicated software such as Adobe Illustrator or similar applications. WFP is not integrated with those tools.

  • WFP is not AI-driven (yet)
    All decisions are made by you, based on your expertise, skills, and experience.

Data safety notice

WFP never stores or transfers project data anywhere except to the location you specify when saving the project file. Your project data always remains on your computer unless you explicitly choose otherwise.

Learning Curve

We believe the learning curve is gentle: WFP is designed to be intuitive and straightforward, especially for people with wayfinding design background.

That said, we recommend starting with the Core concepts, then continuing with User interface to learn how to use the interface, and then switch to Getting Started for a practical guide to quickly get up to speed.

Watch It in Action

Typical Design Process

A typical workflow involves modeling the levels with path networks, designating key points, attaching sign faces to those points, and generating messages.

Input

  • Location plans for each Level in png / jpeg / webp / svg format (e.g. floor plans)

  • Desired Sign Types (descriptions, ID prefixes)

Output

Steps

  • Create a new project in the app

  • Define sign types

  • Define levels, import drawings, and calibrate them (optional but strongly recommended)

  • For each level:

    • Create the path network: define path points and segments

    • Assign target points and decision points

    • Add sign faces (Identification, Direction, and Navigation)

      • Adjust sign face quantities, locations, and orientations to optimize the design

      • Observe messages regenerating automatically

      • Add manual messages if needed

  • Export project reports:

    • Sign Schedule (BoQ)

    • Message Schedule

    • Sign Location Plan

Known Constraints and Limitations

  • An Undo/Redo feature is currently under consideration.

Next steps

Did this answer your question?