Skip to main content
Punctuality Monitoring is an optional feature that tracks whether your deliveries arrive within their planned time window. After each delivery run, the system compares when each stop was actually completed against when it was planned — giving you a clear picture of how reliably your team is delivering.
Punctuality Monitoring is turned off by default. You need to enable it in your settings before it starts tracking.

Turning it on

Go to Settings > General > Drivers and enable Punctuality Monitoring. Once enabled, you’ll also see two threshold settings:
SettingDefaultWhat it controls
Late Threshold15 minutesHow many minutes past the planned time before a delivery is marked as Late
Very Late Threshold30 minutesHow many minutes past the planned time before a delivery is marked as Very Late
You can adjust these to match your expectations. A shop in a busy city centre might set tighter thresholds (10 and 20 minutes), while a rural shop covering a large area might set looser ones (20 and 45 minutes).
Start with the defaults and adjust after a week or two of data. If almost everything shows as “On Time”, your thresholds might be too generous. If most deliveries show as “Late”, they might be too tight — or your runs might be overloaded.

How it works

Punctuality analysis happens automatically — you don’t need to do anything beyond enabling it.
  1. Your driver completes a delivery run using the Digital Florists App
  2. At each stop, the app records the actual arrival time when the driver marks the delivery
  3. When the run is marked as Complete, the system compares each stop’s actual time against the planned time
  4. Each stop gets a punctuality rating, and the run gets an overall score

Punctuality ratings

Each delivery stop receives one of these ratings:
RatingWhat it means
On TimeThe driver arrived within the planned window, was early, or was less than the late threshold (default: less than 15 minutes late)
LateThe driver arrived past the late threshold but within the very late threshold (default: 15 to 30 minutes late)
Very LateThe driver arrived beyond the very late threshold (default: more than 30 minutes late)
SkippedThe stop was skipped — either carded or returned to shop

The punctuality score

Each completed run gets an overall punctuality score — a percentage showing how many stops were delivered on time.
Score = On-Time Stops ÷ Scored Stops × 100
Stops that were skipped or didn’t have enough data are excluded from the calculation, so they don’t unfairly drag the score down. The score is colour-coded for quick reading:
  • Green (80% and above) — most deliveries arrived on time
  • Amber (50–79%) — room for improvement
  • Red (below 50%) — a significant number of deliveries were late

Viewing punctuality results

On a completed run

Open any completed delivery run and you’ll see a Punctuality section (only visible if monitoring is enabled and data is available). This shows:
  • The overall score as a percentage badge
  • A summary — how many stops were on time, late, very late, or skipped
  • The average deviation — on average, how many minutes early or late your driver was
  • Duration comparison — how long the run actually took vs how long it was expected to take
Below the summary, there are two views: Stop Details — a table showing every stop with:
  • The recipient name and address
  • The planned arrival time
  • The actual arrival time
  • The deviation (how many minutes early or late)
  • A colour-coded status badge
Route Map — an interactive map showing:
  • The driver’s actual GPS trail as a blue line
  • Colour-coded pins for each stop — green for on time, amber for late, red for very late, grey for skipped
  • Numbered markers showing the stop sequence
  • Click any pin to see the planned vs actual times for that stop
The route map is especially useful for spotting patterns — for example, if all the late deliveries are in one area, there might be a recurring traffic issue or access problem.

In your analytics

When Punctuality Monitoring is enabled, a Driver Punctuality section appears in your Analytics under the Delivery insights. This shows performance across all drivers over your selected date range:
MetricWhat it tells you
Average ScoreEach driver’s average punctuality score across all their runs
On-Time %What percentage of their stops were delivered on time
Late %What percentage were late (but not very late)
Very Late %What percentage were significantly late
Runs AnalysedHow many completed runs were scored for this driver
This makes it easy to compare drivers and spot who might need support, a route adjustment, or fewer stops per run.

What affects punctuality

Understanding what impacts punctuality helps you improve it. Common factors:

Too many stops per run

The most common cause of late deliveries. Every stop takes time to find, park, deliver, and photograph. If a run has 15+ stops, the later ones are almost guaranteed to be late. Try keeping runs to 8–12 stops maximum.

Unrealistic time windows

If customers book timed slots (e.g., “between 10am and 11am”) and the route can’t physically get there in time, those stops will always show as late. Review your delivery slots and make sure the windows are achievable.

Traffic and geography

Rush hour, roadworks, rural routes — all affect drive times. The route optimiser accounts for road distances but can’t always predict traffic. If certain areas consistently show late deliveries, consider putting those addresses on earlier runs.

Stop sequence

Route optimisation puts stops in the most efficient order, but it’s not perfect. If your driver knows a quicker route, they can adjust — and you can drag-and-drop stops before they head out.

Driver habits

Some drivers mark each delivery as soon as they arrive. Others deliver several stops and then mark them all at once. The second approach makes punctuality data inaccurate because the recorded times don’t reflect actual arrival times. Encourage drivers to mark each stop straight away.
Punctuality data is only as accurate as the timestamps recorded by the driver. If a driver delivers flowers at 11am but doesn’t mark the stop until 11:30am, the system records the later time. Make sure your team understands this.

Tips for improving punctuality

Check your average stops per run in Delivery History. If it’s consistently above 12, try splitting into two smaller runs. Two runs of 8 stops are almost always more punctual than one run of 16.
The route optimiser already prioritises timed slots, but you can manually move them to the top of the run if needed. Getting the time-sensitive deliveries done early avoids the knock-on effect of running late.
If your same-day cutoff is too late, your driver might be rushing. Bringing the cutoff forward by even 30 minutes gives your team more breathing room.
If the same address keeps showing as late, add a note — maybe it takes 10 minutes to get through a gated community, or the customer always wants a chat. Account for that in your planning.
If your scores are consistently low despite your best efforts, your thresholds might be too tight for your delivery area. There’s no shame in setting a 20-minute late threshold instead of 15 — the goal is useful data, not perfect scores.

Common questions

No. It’s completely optional and turned off by default. Many shops run perfectly well without it. It’s most useful if you have multiple drivers and want to track consistency, or if you offer timed delivery slots and want to make sure they’re being met.
No. Punctuality monitoring is purely informational — it records and displays data but doesn’t change how orders, delivery runs, or notifications work. Customers don’t see punctuality scores.
Punctuality analysis only runs on delivery runs completed after you enable the feature. Past runs won’t be retroactively scored.
Yes. Disabling the feature hides the punctuality sections from run details and analytics. Your existing data is kept — if you re-enable it later, you’ll still see the historical scores.
Stops without a planned arrival time (for example, if route optimisation wasn’t used) are marked as No Data and excluded from the score calculation. They don’t affect your punctuality percentage.
Yes. The Driver Punctuality table in Analytics respects your date range filters. Set the range to see how punctuality has changed over time.
Yes. If a driver arrives before the planned time, it’s always counted as On Time. Only late arrivals are penalised.

What’s next?

Delivery Runs

Create and manage your delivery runs.

Delivery History

Review past runs and driver performance.

Delivery Slots

Configure your time slots and same-day settings.

Analytics

See delivery trends alongside your other business metrics.
Last modified on March 11, 2026