Understanding myTap Alerts

The Needs Attention panel on the Historical Reports page flags stops where the scan pattern suggests a problem with the sign. myTap Reports checks two things:

  • Possible Damaged Signs: a stop that used to get regular scans has suddenly gone quiet.
  • Possible Miscoded Signs: riders scanning for a stop are consistently far away from it.

An alert is a reason to look, not proof of a problem. Check the stop, or ask a driver or field staff to look at the sign, before ordering a replacement.

Start here

  1. Look at the badge at the top right of the page. No open alerts (green) means there's nothing to look at. Otherwise it shows the count, e.g. 5 open alerts. It's amber for 1 or 2 alerts and red for 3 or more.
  2. Scroll to Needs Attention. Each row shows a severity, the stop name and ID, whether the scans were QR or NFC, and one line explaining the finding.
  3. Click View on map to see where the stop is. Then decide whether to visit the stop, and click Acknowledge once it's being handled.
The header badge when there are open alerts.
The Needs Attention panel with examples of every alert type.

Quick reference

What you see What it means Go to
▼ CRITICAL under Possible Damaged Signs, finding -100% vs baseline · 0.0/day recent vs 4.0/day baseline No scans at all at that stop, from that source, in the last 7 days Possible Damaged Signs
▼ CRITICAL under Possible Damaged Signs, drop of 85% or more Scans almost stopped Possible Damaged Signs
▼ WARNING under Possible Damaged Signs, drop of 70% to 84% Scans fell sharply Possible Damaged Signs
▼ CRITICAL under Possible Miscoded Signs, finding median 1.42 mi over 27 located scans Riders are typically a mile or more from the stop Possible Miscoded Signs
▼ WARNING under Possible Miscoded Signs, median between 0.25 and 1 mile Riders are typically a few blocks from the stop Possible Miscoded Signs
No anomalies detected in this period. or None found in this period. Nothing to look at No alerts
(2 acknowledged) under a column Alerts you've already acknowledged in this browser Acknowledging alerts

Possible Damaged Signs

What it checks

For each stop, QR and NFC are checked separately. The scan rate over the last 7 days is compared with the rate over the 28 days before that (the "baseline"). These windows count back from the moment the page loads in 24-hour steps. They aren't calendar days like the 7d button.

  • The stop must have had at least 20 scans of that type in the baseline, so quiet stops aren't flagged by chance.
  • An alert appears when the recent daily rate is at least 70% below the baseline daily rate.
  • ▼ CRITICAL: the drop is 85% or more, or there were no scans at all in the last 7 days.
  • ▼ WARNING: the drop is between 70% and 84%.

How to read the row

Example: ▼ WARNING · West Park Ave at North Burrowes St #6 QR · -76% vs baseline · 0.7/day recent vs 3.0/day baseline

  • -76% vs baseline: the scan rate fell by 76%.
  • 0.7/day recent: an average of 0.7 scans per day over the last 7 days.
  • 3.0/day baseline: an average of 3.0 scans per day over the 28 days before.
  • The two small bars on the right compare baseline (left) with recent (right) at a glance.
  • The QR or NFC label tells you which part of the sign to check. A stop can appear twice, once for each.

Common causes

  • The sign, QR sticker or NFC tag is damaged, faded, covered, vandalised or missing.
  • The sign was taken down or moved during construction, or the stop is closed or detoured.
  • For NFC: the tag was replaced or reprogrammed, or is no longer readable.
  • For QR: QR scans are matched to the nearest stop by location, so a drop can also mean a QR sign nearby was removed.

What's normal

  • Seasonal drops. School and university breaks, holidays and service changes can cut ridership at a stop for a week or more. If a stop serves a campus that's on break, the alert is expected and clears once ridership returns.
  • A sign that was just installed can't trigger this alert until it has 20 scans of baseline.

What to do

  1. Click View on map to confirm which stop it is.
  2. Rule out a known reason (detour, closure, break period).
  3. If there's no known reason, have the sign checked. Make sure the QR code is clean and not torn, and test-tap the NFC tag with a phone.
  4. Click Acknowledge so the row moves out of your open list while it's being handled.

How it clears

Once scans return to normal, the alert drops off by itself, usually within a few days, because the last 7 days are compared each time the page loads. A stop that stays closed keeps alerting until its old busy period falls out of the 28-day baseline, about 5 weeks in all.

Possible Miscoded Signs

What it checks

For each stop and source, it looks at the last 60 days of scans that have a reliable rider location. That means the rider allowed location and the phone's accuracy was within about 150 meters (500 ft). It then measures how far the rider was from the stop.

  • The stop needs at least 10 such located scans.
  • An alert appears when the median distance is 0.25 mile (about 1,300 ft) or more and at least three-quarters of the scans were 0.125 mile (about 660 ft) or more away. A few riders who scan and then walk off don't trigger it. Most riders have to be far from the stop.
  • ▼ CRITICAL: median distance of 1 mile or more.
  • ▼ WARNING: median distance between 0.25 and 1 mile.

How to read the row

Example: ▼ CRITICAL · Curtin Rd at Visual Arts Building #356 QR · median 1.42 mi over 27 located scans

  • median 1.42 mi: half of the riders were more than 1.42 miles from the stop when they scanned.
  • over 27 located scans: the number of scans with a reliable location that the figure is based on.

Common causes

  • A QR code has been put up somewhere that isn't a stop, such as a poster, a building lobby or a park-and-ride kiosk. Its scans get matched to the nearest stop, which may be some distance away.
  • The stop's location in your stop list is wrong, so riders standing at the real stop look far away.
  • Riders are scanning a photo or printout of the code away from the stop.
  • For NFC: a tag programmed for one stop has been mounted at another. NFC taps don't use location today, so this alert normally appears for QR.

What to do

  1. Click View on map and check that the stop dot is where the stop actually is.
  2. If the dot is in the wrong place, ask your scheduling or GIS team to correct the stop's location in your stop list. The change reaches myTap with the nightly stop refresh.
  3. If the dot is right, look for QR codes posted away from stops near the area on the heatmap, and check the sign at the stop.
  4. Click Acknowledge once it's being handled.

How it clears

This alert looks back 60 days, so it clears slowly. Once the cause is fixed, the far-away scans have to make up less than half of the located scans in the 60-day window. Depending on traffic at the stop, that can take several weeks.

No alerts

The panel when there are no alerts.
  • No anomalies detected in this period. appears when neither check found anything. The header badge reads No open alerts.
  • None found in this period. under one column means that check found nothing, but the other one did.
  • Despite the wording, the alerts don't follow the date range buttons. Damaged-sign alerts always use the last 7 days against the 28 days before, and miscoded-sign alerts always use the last 60 days. Changing from Today to 90d doesn't change the alerts.
  • A new agency, or a new sign, has no alerts until enough scans build up.

Acknowledging alerts

After acknowledging an alert, with the acknowledged list shown.
  • Acknowledge moves the row out of the open list. A link such as (1 acknowledged) appears under that column. Click it to see those rows again, and click Hide acknowledged to fold them away.
  • The header badge counts only alerts you haven't acknowledged.
  • Acknowledging is saved in your browser only. Colleagues still see the alert, and you'll see it again on another computer or browser, or after clearing your browser data.
  • Acknowledging doesn't fix or close anything. If the scans recover, the alert disappears by itself.
  • An acknowledgement is kept for that stop and source. If the same stop alerts again weeks later, it appears under (N acknowledged), not as a new open alert. Open the acknowledged list now and then to check it.
  • There's no un-acknowledge button. To show all alerts as open again, clear this site's data in your browser (it also clears the short-lived report copy).

View on map

View on map zooms the heatmap to the stop.

View on map scrolls down to the Geographic Heatmap and zooms in on the stop. Hover over the stop dot to confirm its name. For a miscoded-sign alert, compare the dot with where the scans are glowing for the date range you have selected.

When to contact Avail support

  • A Possible Damaged Signs alert for a stop where the sign has been checked, works when tested, and the drop has no known reason.
  • Many stops alert at the same time with no service change, which may point to a wider problem.
  • Include the stop name and ID, the source (QR or NFC), the exact finding text, and a screenshot of the row.

Related Content

Was this article helpful?

Articles in this section

New to the Help Center?
Review the Help Center guide
Help Center Feedback
Have a suggestion for new content or how we can improve the Help Center? Let us know!