ScoutRoute AVIV
Document pedestrian access where it happens.
AVIV ScoutRoute is an accessible mobile app for collecting pedestrian access data in the field. Participants answer map-based quests about sidewalks, crossings, curb ramps, bus stops and barriers, adding photos or notes when the campaign calls for them.
- Map-based field quests
- Project workspaces
- Structured answers, photos and notes
ScoutRoute in action
Collect, review, and use field observations.
An organizer defines the workspace, area and quest set. In the field, participants open the map, select a nearby quest and record what they can observe. Contributions can then be reviewed in ScoutRoute Workspaces.
- 1Open the assigned workspace
Open the workspace and route assigned for the activity.
- 2Answer what is observable
Record the feature, condition, photo or note requested by the quest. Do not guess.
- 3Review before broader use
Organizers or designated reviewers check contributions for the campaign’s intended use.
Choose a pathway
How do you want to use ScoutRoute?
Start with the job you need to do. Each pathway uses the same field-collection foundation but calls for a different setup, review process and set of supporting materials.
Document completed pedestrian features before project closeout.
ScoutRoute can create a structured field record of completed work. A project-specific workspace and quest form guide collectors through the pedestrian features the agency needs to verify.
An agency or project team needs consistent, location-based documentation before accepting and closing a project.
What the work looks like
Configure a project workspace and quest form for the features in scope.
A contractor or designated collector records answers, photos, and notes.
The agency reviews submissions and requests corrections where needed.
After review, the agency can use the accepted field record in its own closeout or data-maintenance process.
ScoutRoute supports the field documentation and review handoff; it does not replace engineering inspection or the agency’s formal acceptance process.
Resources and next step
Help internal teams contribute to one reviewed record.
Organizations with several departments or field teams can use shared quest forms, team workspaces, and review roles to combine approved field information for broader internal use.
Related field information is scattered across separate tools, reports, or teams.
What the work looks like
Define the questions, team workspaces, and review roles.
Each team collects observations for its assigned area or work.
Designated reviewers check contributions before wider sharing.
Combine approved information for the organization’s intended use.
Field submissions can be reviewed before they are shared beyond the team or used more broadly.
Resources and next step
Document community experience before and after a project.
ScoutRoute can support two related community assessments around the same project. Before implementation, participants document barriers, experiences, and desired changes. After implementation, they return to the area and document how the completed change is experienced.
You need a repeatable community record alongside the technical project record, not only a one-time walk audit or construction checklist.
What the work looks like
Before the project, collect location-based experiences, barriers, and desired changes.
Keep the route, questions, and participation plan for the follow-up.
After implementation, return and record reactions to the completed change.
Review the two rounds alongside the project’s technical record.
ScoutRoute collects the community observations. It does not, by itself, determine whether a project succeeded or replace a formal accessibility evaluation.
Resources and next step
Organize a walkabout around the same routes, questions, and field method.
ScoutRoute can organize a field activity around assigned routes and a defined set of pedestrian-access observations. This can include school walkabouts, Safe Routes to School activities, GAAD events, and community mapping challenges.
You are planning a time-bounded field activity and need consistent routes, participant guidance, and a way to combine observations.
What the work looks like
Define the area, priority features, and quest set.
Set up the workspace and brief participants on roles, safety, and what not to record.
Collect observations in pairs or teams along assigned routes.
Review contributions and close with a group debrief.
Challenge-style events can add team assignments or a leaderboard. Careful observation matters more than speed.
The app stays the same. The setup depends on the job.
General resources
ScoutRoute guides and access.
ScoutRoute user manual
Installation, workspaces, the map interface, completing quests, settings and quest types.
Open the manual (opens in a new tab)TCAT ScoutRoute page
The current TCAT overview of ScoutRoute, accessible-first field collection and the types of quests available.
View the TCAT page (opens in a new tab)App access and testing
TCAT’s current access page for platform availability and testing information.
Check app access (opens in a new tab)Plan a ScoutRoute campaign
Start with the campaign, not the app.
Tell TCAT the location, audience, collection goal and intended use of the data. The team can help determine the right workspace, quest set, review roles and existing materials.
Contact TCAT about ScoutRouteuwtcat@uw.edu