Analytics

Analytics answers "how are we doing?"

Owner, Manager & Location-manager Where: Analytics 6 min read

Pick a range — Last 7 days, Last 30 days or Last 90 days — and a branch, and turnda shows the numbers that matter, worked out in each shop's own time.

The four KPIs and By-location count PEOPLE. Reports counts SERVICES. Somebody who goes through reception and then a doctor is 1 here and 2 on Reports. Neither is wrong — they answer different questions — but if the two screens ever seem to disagree, that's why.

The exception, and the one thing they agree on By-staff further down is the exception — it counts services too. Both pages measure the average wait the same way now — neither counts the hours you were closed.

The five KPIs

Five headline numbers, each with its own plain definition printed under it, and a trend against the period just before this one. "People arrived" and "People served" are deliberately two different numbers, never the same figure shown twice under two names — arrived counts everyone who joined, served counts only those actually helped, and arrived is always the same as or higher than served.

KPI	What it counts
People arrived	Everyone who joined or checked in during the range, counted once per visit — including those who later left or didn't turn up. Adds up to exactly the same total as the "Arrivals by day and hour" grid further down.
People served	People fully served in the range, each counted once however many stops they went through.
Avg wait	The average wait from joining to service starting — not to being called. Hours you were closed aren't counted, so a queue left overnight isn't read as an all-night wait. On a multi-stop visit it's the whole journey's waiting added together. Served visits only.
Satisfaction	The average star rating, or "No ratings yet".
No-show rate	No-shows as a share of the people who were expected — those served plus those who didn't turn up. Somebody who gave up and left before being called is not counted here — they're in "Where people give up" further down.

Trends compare this range with the same length of time immediately before it — the last 30 days against the 30 before that.

They're coloured by meaning, so a falling wait reads as good and a rising no-show rate as bad.
An exactly level number shows a flat dash and "0% vs previous" in grey, never a green arrow.
When there's nothing to compare against, no trend is shown at all rather than a made-up one.

What went well / to improve

turnda turns the numbers into sentences — a "What went well" list and a "What to improve" list.

"Average wait down 12% vs the previous period (3 min)"
"No-shows high at Green Valley (18%)"
"Strong satisfaction — 4.6★ across 52 ratings"

When there's nothing to flag	What it says
A quiet period overall	"Steady period — no notable swings."
Nothing to improve	"Nothing flagged — keep it up."

The predictions around the app work the same honest way — they learn from your venue's own history (no outside service, no invented numbers), and each stays silent until it has enough of it.

Prediction	Needs about
The wait estimate your visitors see	8 completed visits at that same time of week, spread across at least 3 different days. An extreme figure on thin history shows honestly as "more than a day" rather than a false-precise number.
The busy-time forecast ("Busiest around Friday 5 pm — plan cover for the rush.")	2 weeks of arrival history.
"Higher no-show risk" on a booking	20 resolved bookings on that line.
Smart insights on the dashboard	30 served visits.

So a new venue won't see these yet — and that's normal. They switch on by themselves as you serve.

By location, staff & time

View	What it shows
By location	Served, average wait, rating and no-shows per branch. It only appears when you run more than one.
By staff	"Team member", services completed, average service, rating and share of volume. Counts services, not people — a multi-stop guest is counted at each stop.
Busiest times	A day-by-hour grid of arrivals. Darker is busier; staff the busy hours.

What By-staff is for It's there to celebrate top performers and spot who may need support — not shown to staff themselves. Each person sees only their own numbers, in My Metrics.

Branches in different countries? A range covering several time zones is stretched wide enough to include every branch's whole day, and the page says so. Drill into one branch to see its own dates exactly.

Stations and staffing

This part of the page answers "where is the time going", in three pieces that load separately from the numbers above and from each other — one can fail or be empty while the rest are fine.

Piece	What it shows
By staff · hours and utilisation	Time signed in at a counter, how much of it was spent serving ("Busy"), services done, and "Cut short" — shifts that ended by something other than signing out (taken over, switched, removed, or timed out). Not shown to staff.
By station · occupancy and utilisation	How long each counter was manned and how busy it was. "Handovers" counts the times somebody was bumped off it rather than signing out. Pick a station to see who was there and when, and how each spell ended.
"Where people give up"	"31% of visitors left before being served — typically after about 18 minutes of waiting." Use it to decide your longest acceptable wait; too few so far to tell, and it says that instead of guessing.
"People on, against people arriving"	Arrivals set against how many were on a counter, hour by hour, so you can see where another pair of hands pays for itself — "5 pm is the pinch: 14 arrivals against 1 on a station, and a 22-minute wait."

Two things read as blank and mean different things. A dash in the "Busy" column means nobody was signed in to a counter, so there is nothing to work a percentage out of — it is never shown as 0%.

"Not signed in" is different again It means that person served people without ever claiming a counter, so there's no counter time to measure them against.

The fix is always the same. If a whole section says "Nobody has signed in to a station in this period, so there is nothing to compare arrivals against", ask the team to sign in at their counter when they start serving, and these fill in by themselves.

The four screens, and what each one means

What you see	What it means
A spinner (Loading)	The page waits for your branches before it asks for any figures.
"No activity in this period yet."	That range genuinely had no served visits, no ratings and no arrivals. It offers the thing that fixes it — share your join link. Widen the range or pick a branch that was open.
"Something went wrong" with Try again	It couldn't load. This is not a quiet zero. The operations half has its own retry, so you may see one section fine and the other asking to retry.
"That branch is no longer here"	You followed an old link or bookmark to a branch that has since been removed. Pick a branch above and carry on. Without this, a deleted branch would have looked like a terrible month.

"The account owner has turned this off for managers", with no retry button. That's not a fault — an owner can switch analytics off for managers. There is nothing to try again; ask the owner if you need it back.

An old Compare-places link

If you have an old bookmark or an email pointing at /comparison — the address the Compare-places screen used to live at — it still works. It takes you straight here, to Analytics, where comparing your locations now lives.

There is nothing to update and nothing was removed; the two screens were merged into this one.

Related: Reports & exports · The dashboard · My Metrics