Skip to main content

LSTAR Technician Performance

Published: 2026-11-03 Revised: 2026-11-03

What this report does​

Shows each technician's LSTAR score for a single day: their total points, their Hero Day streak, and which of the six LSTAR standards they missed and by how much. One row represents one technician's day.

Use this report for a daily check on how your crew's workday lined up with your site's schedule. For trends over a month or quarter, use the LSTAR & Time on Tools tab in Insights.

The report is under Reports > Other. For how the score is calculated, see LSTAR.

When to use it​

  • Reviewing yesterday's work at the start of the day.
  • Seeing which technicians started late, ran long on breaks or lunch, left early, or fell short of their component target.
  • Spotting a technician whose Hero Day streak has ended, or who hasn't had a Hero Day in a while.

Parameters​

ParameterDescriptionRequiredHow it filters
Report DateThe day to report onYesOne day only, midnight to midnight in your facility's time zone
Technician(s)One or more techniciansYesOnly the selected technicians appear. Use Select All to include everyone
Work PerformedOne or more Work Performed valuesNoOnly technicians who chose one of the selected values at check-in on the Report Date appear. Leave it blank to include everyone

Work Performed decides who appears, not which inspections count. When you filter on a Work Performed value, the technicians who chose it are shown with all of their inspections for the day.

Columns​

ColumnWhat it showsFormat / Notes
Tech NameThe technician's nameText
Work PerformedThe Work Performed the technician chose at check-in for that dayText; more than one value is separated by commas; blank if none was chosen
Total PointsThe technician's LSTAR score for the day0–100
Hero DaysThe technician's Hero Day streak, or how long since their last Hero DayWhole number; see Hero Days below
First CompWhether the first inspection started on time✓ if met; otherwise the time the first inspection started (for example, 7:42 AM)
AM BreakWhether the morning break was within the limit✓ if met; otherwise the length of the break in minutes
LunchWhether lunch was within the limit✓ if met; otherwise the length of lunch in minutes
PM BreakWhether the afternoon break was within the limit✓ if met; otherwise the length of the break in minutes
Last CompWhether the last inspection ended late enough✓ if met; otherwise the time the last inspection ended (for example, 3:10 PM)
# CompsWhether the daily component target was metBlank if met; otherwise the number of components inspected
# LeaksLeaks found that dayInteger
# PPM > 0Inspections with a reading above backgroundInteger
Excess GapsGaps long enough to count as a break, beyond the AM break, lunch, and PM breakInteger; does not affect the score
# No GPSInspections recorded without a GPS locationInteger

The report header shows your facility, when the report was run, and which technicians and Work Performed values you selected.

What's included and excluded​

Included:

  • M21 and AVO inspections performed on the Report Date.
  • Technicians with at least one M21 or AVO inspection that day.

Excluded:

  • OGI and Cooling Tower inspections.
  • Repair attempts, and components recorded as Unable to Monitor.
  • Technicians who did not inspect that day, or who have not checked in yet.

How key values are calculated​

Total Points

The sum of the points for each standard the technician met. Each standard is all or nothing. The targets and point values come from Settings > Quality Signals. See LSTAR for how breaks, lunch, and the daily component target are worked out.

Hero Days

A Hero Day is a day the technician met all six standards (a score of 100).

  • A positive number is the technician's current Hero Day streak, counting back from the Report Date: the number of Hero Days in a row, in workdays. A day with no inspections, such as a weekend, does not break the streak.
  • A negative number means the Report Date was not a Hero Day. It shows how many days it has been since the technician's last Hero Day. For example, -4 means their last Hero Day was four days before the Report Date.

The column looks back 30 days, as the note on the report says. A technician with no Hero Day in that period shows -31.

# Comps

The number of different components the technician inspected. A component inspected twice counts once. It is compared with the daily target for the Work Performed the technician chose that day.

Tips and common questions​

  • "A technician has a ✓ for lunch but took a long break at noon." If the gap was under 60 minutes, or ended after 2:00 PM, Chateau counted it as a break rather than lunch. Check the AM Break or PM Break column.
  • "A technician has a ✓ for every break but didn't take any." A technician who works straight through meets the break and lunch standards, because nothing went over the limit.
  • "A technician I selected isn't on the report." They had no M21 or AVO inspections on the Report Date, they haven't checked in yet, or they didn't choose one of the Work Performed values you filtered on.
  • "Work Performed is blank." The technician didn't choose a Work Performed at check-in, or checked in on a different day. Their day is scored against the Valve + Nonconnectors target, or the Connectors target if they inspected a connector.
  • "The score doesn't match what the technician remembers." The times come from the handheld's clock and from the technician selected in Chateau Mobile. Check both.

Output format​

One row per technician for the Report Date, sorted by Total Points (highest first), then by Hero Days. Suitable for on-screen viewing, PDF, and Excel export.

  • Tech Inspections — each technician's daily inspection count and first and last inspection times, by analyzer.