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.
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. Contributions are committed to the selected TDEI Workspace through a changeset so the project can review them before using them in its work.
Define the question
Start with a specific collection goal and questions that can be answered from the field.
Set up the workspace
Configure the project area, app-enabled workspace, access group, coverage, and quest definitions.
Prepare participants
Give people a safe route, clear roles, and the project access they need before they begin.
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 replace engineering inspection, formal acceptance, or a formal accessibility evaluation.
Four ways to use ScoutRoute
1. Contractor closeout
Use a structured field record before project closeout to help an agency review pedestrian features and conditions. Define the questions and area in advance, assign the field work, and keep a review step with the responsible agency. ScoutRoute can support documentation; it does not replace engineering inspection or formal acceptance.
2. Internal organizational data
Create shared quest forms and team workspaces for recurring field observations. Assign review roles, establish a consistent process, and combine approved field information with the organization’s other records.
3. Pre/post community assessment
Before implementation, document barriers and desired changes. After implementation, return to the area and record what people observe. The comparison can inform discussion and follow-up, but it does not by itself determine success or replace a formal accessibility evaluation.
4. Team challenge or walkabout
Plan a walkabout, school walkabout, Safe Routes to School activity, Global Accessibility Awareness Day event, or community mapping challenge. Give teams assigned routes, safety guidance, and a group debrief. Careful observation matters more than speed.
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.
Plan a campaign
Start with a small area
Choose a route or set of features that participants can observe safely and consistently.
Write answerable quests
Ask about details visible at the feature. Include an Unknown or skip path when an answer may not be determinable.
Agree on review
Decide who reviews contributions, what counts as sufficient evidence, and how approved information will be used.
Read the ScoutRoute user manual or contact the TCAT team about a campaign.
Participants can use the participant page for installation links and the field workflow. This organizer page intentionally does not include app-installation links.