AVIV ScoutRoute

AVIV ScoutRoute · For organizers

Document pedestrian access where it happens.

AVIV ScoutRoute is a mobile field-data collection app for teams, agencies, organizations, communities, and clubs. Participants answer map-based quests about sidewalks, crossings, curb ramps, bus stops, and other pedestrian features; campaigns can include photos or notes when the workspace calls for them.

Explore use patterns Plan a campaign

Organizers define the area, app-enabled workspace, quest set, and review process for the campaign.

CAMPAIGN WORKFLOW
  1. 1Define
  2. 2Set up
  3. 3Observe
  4. 4Review

Contributions commit to the workspace as changesets.

Project setup

Collect, review, and use field observations

An organizer defines the area, workspace, and quest set. Participants open the map, select a quest, observe the feature, and record the answers configured for the campaign.

  1. 1

    Define the question

    Start with a specific collection goal and questions that can be answered from the field.

  2. 2

    Set up the workspace

    Configure the project area, app-enabled workspace, access group, coverage, and quest definitions.

  3. 3

    Prepare participants

    Plan an appropriate field route, assign clear roles, and provide the project access people need before they begin.

  4. 4

    Review the record

    Use workspace review and your project’s process before treating field observations as evidence for a decision.

ScoutRoute supports field collection and review handoff. It does not establish route safety or replace engineering inspection, formal acceptance, or a formal accessibility evaluation.

Use patterns

Five ways to use ScoutRoute

Choose the path that fits your goal. Open each example for a practical setup and reporting approach.

1. Contractor closeout

Best for: Verify and document pedestrian improvements before a project closes.

Partner example: A contractor or agency field team can record the location, condition, photos, and unresolved issues for crossings, sidewalks and curb ramps.

How to organize: Define the construction limits and required quest types; assign reviewers from the responsible agency; retain observations as supporting documentation. This is not engineering acceptance or compliance certification.

2. Transit team coordination

Best for: Bring field knowledge from separate transit teams into a shared workspace.

Partner example: King County Metro (KCM): teams working on access pathways, stops and related pedestrian infrastructure can use common quests to share observations across internal groups.

How to organize: Agree on common questions, team assignments, permissions and review roles. Use the shared record to reduce repeated surveys and identify issues requiring another team’s follow-up.

3. Jurisdictional plan or priority

Best for: Target data collection to a city, corridor or planning decision.

Partner example: A jurisdiction preparing an ADA transition plan, active transportation plan, Safe Routes to School plan or park-access review can ask teams to verify missing or outdated features.

How to organize: Define the geographic boundary, target assets, questions and data handoff with the jurisdiction. Label observations and limitations before they inform priorities.

4. Agency-led or community-led team challenge

Best for: Run a structured multi-team survey with measurable contributions.

Partner example: Safe Routes to School: a John Stanford International School walk audit can assign teams to nearby walksheds and use the organizer, participant and appendix sheets. Parks and recreation access: teams can document approaches to parks, paths, crossings and nearby stops.

How to organize: Create a project workspace, divide the coverage area, assign quest types and pair roles, brief participants, and set a return and review process. Collect a leaderboard summary for contributions and coverage, then send a reviewed summary to relevant planners.

5. One-time Walk & Talk

Best for: Offer a short, focused activity that invites people to contribute.

Partner example: Move Redmond’s Walk & Talk illustrates an event-based model: participants can collect observations about everyday routes during a guided outing.

How to organize: Select a manageable route and short quest set; test the event QR, give a safety briefing, and debrief the findings. Share a concise event summary and follow-up items after review.

Student groups

High-school clubs and student groups

ScoutRoute can support a structured student walkabout or civic-technology project. Start with a manageable area and a clear question; define roles for route planning, observation, documentation, and debrief.

Participants still need project-group membership, an app-enabled workspace, and the quest set configured for the activity. TCAT can help a club frame a practical collection goal and a review conversation. The app records configured observations; it does not turn a student activity into a formal inspection.

Campaign planning

Plan a campaign

1

Start with a small area

Choose a route or set of features participants can observe appropriately and consistently. Set safety guidance for the activity.

2

Write answerable quests

Ask about details visible at the feature. Include an Unknown or skip path when an answer may not be determinable.

3

Agree on review

Decide who reviews contributions, what counts as sufficient evidence, and how approved information will be used.

Use the ScoutRoute user manual or contact TCAT about a campaign. Participants can use the participant page for installation links and field workflow. This page does not include app-installation links.

Every campaign should end with a useful record. Organizers can request a team leaderboard and collection summary showing participation and the work recorded. Review the results, identify areas covered and remaining gaps, and share the summary and relevant approved observations with jurisdictional planners. Leaderboards count contributions; they do not certify accuracy, completion or ADA compliance. Coordinate report access and sharing with TCAT.

Ready-to-use field materials

Guides for team challenges and walk audits

Use the reusable sheets for field roles, safety and app instructions. Customize the appendix for each event’s contacts, route, workspace and event QR code.

Example event appendix

Download John Stanford example (PDF) · Event QR and contact fields, walkshed map, feature definitions and examples. Replace example event details before distribution.

Set up participant access before the event. Confirm each person has an account, belongs to the correct project group, and can open the app-enabled workspace. Distribute the participant registration and app-installation guide and test your event QR code in advance. Contact TCAT for workspace setup and report handoff.