Performance · Working guide
A better weekly performance review
By FleetVerity · Published · 2 min read
A useful review ends with a small number of clear decisions. Start with the reporting period and its coverage — not the grade alone.
1. Confirm what the numbers cover
Write down the reporting week, the comparison week, the latest source date and the number of drivers assessed. Separate missing records from zero events. If one week covers fewer drivers or fewer opportunities, note that before you interpret a change.
2. Pick the most useful questions
What changed materially? Which drivers or events contributed? Which recurring issue needs a closer look? Which improvement deserves recognition? Keep measurements with different units separate.
3. Inspect before you interpret
Open the supporting records. A count, a rate, an Amazon tier and your own rubric's grade describe different aspects of a result — check which one you are reading. Record uncertainty, and invite the driver's context instead of guessing intent.
4. Agree on the next step
Name an owner, define one practical next step and choose a review date. Hold the conversation where the driver can respond. If the evidence is missing, the next step is to resolve the data gap.
5. Review after enough exposure
Compare like periods and comparable opportunities. Track the action, the driver's response and the next measurement separately. A message that was sent is not proof of a sustained change in performance.
A simple meeting output
Observation → supporting record → driver context → agreed action → owner → next review. Keep the record short enough for the next manager to understand.
General management guidance. Adapt it to your company's approved procedures, and keep decisions that need judgment with authorized people.