A new system arrives pre-filled with sample rooms, sample staff and sample bookings so it does not look empty. It also means nobody can tell whether anyone has actually started. Here is how to tell real use from a full-looking screen.

When you open a new system for the first time, it is rarely empty.

There is a sample venue. Two sample staff. A price list. A few bookings, dated this week, sitting in the calendar so the screen has something on it.

⚠️ That is a deliberate choice by whoever built it, and it is usually a kind one. An empty screen is discouraging. A screen with something on it shows you what the thing is for.

It also makes one question impossible to answer: has anybody actually started using this?

The short version

Sample data makes a new system look started when nothing has happened
From the outside, a seeded account and an active account are identical
The test is not "is there data" but "was any of it created after day one"
We checked our own: of nine venues who signed up through our form, one had entered real work
Whoever provides your system can answer this in a minute if you ask precisely

Why it matters to you, not just to them

What a full screen suggests	What it may actually mean
Somebody set this up	The system set itself up
We are using it	Nobody has opened it since day one
The trial is going fine	The trial is going nowhere

⚠️ If you are the owner and somebody else did the setup, you cannot tell these apart by looking. The screen looks the same either way.

One: the test that separates them

Every record carries a creation time. Sample data all carries the same one — the moment the account was made.

Seeded    everything created within a minute or two of signup
Real use  things created hours, days, weeks later

⇒ That is the whole diagnosis. Spread over time means a person; all at one instant means a machine.

How to ask for it

"Of everything in this account, how much was created
 more than an hour after the account was opened?"

⚠️ "More than an hour" is the useful phrasing. It excludes the setup moment and includes anybody who came back the same evening.

Two: we ran this on ourselves

We offer a free trial of our own system and it seeds sample data on signup. We had never checked what that hid.

Venues who signed up through our form since the seeding began:  9
Of those, venues where somebody entered a real booking:         1

⚠️ Eight accounts looked populated and were not. Every one had a venue, staff, a price list and five bookings on screen — all created at the moment of signup, none since.

What we could not conclude

It is tempting to say the sample data caused it. We looked at the period before seeding existed, as a comparison.

Before seeding  3 venues signed up, 1 entered real bookings
After seeding   6 venues signed up, 0 entered real bookings

⇒ Suggestive, and far too small to be proof. Two thirds were stalling before the sample data existed, so the sample data is at most part of it.

⚠️ We are reporting a measurement, not a conclusion. The honest version is: the gap between signing up and doing real work was already large, and we had no way to see it.

Three: the same shape in your venue

This is not only about software trials. It applies to anything that arrives pre-populated.

A booking system with sample rooms
A rota tool with example shifts
A price list loaded from a template
A supplier catalogue somebody imported

⚠️ Each of those looks configured. Whether anybody has adjusted them to your actual venue is a separate question, and the screen will not tell you.

The failure mode

Staff assume the setup is real
They work around the parts that are wrong
The wrong parts stay wrong for months

⇒ A price list that is nearly right is more dangerous than an empty one, because nobody questions it.

Four: what to check after any setup

Whether a supplier set it up, a staff member did, or it came pre-filled.

One   Are the venue and room names ours, or examples?
Two   Are the prices ours, or a template?
Three Are the staff real people?
Four  Is anything in here dated after the day it was installed?

⚠️ Four is the one that catches everything else. If nothing was touched after installation day, nobody has checked any of the above either.

Five: the first real record is the milestone

For any new system, there is one moment that matters more than the others.

The first time somebody puts real work into it

⇒ Not the setup. Not the training. The first genuine booking, shift, or sale entered because it happened, not to try the system out.

Why it is the milestone

Before it  the system is a demo somebody is evaluating
After it   the system is holding something you need back

⚠️ Almost nobody abandons a system after that point, because leaving now costs them their own data. Before that point, leaving costs nothing.

⇒ So if you are rolling anything out, the question at the end of week one is not "have they been trained." It is "has anybody put real work in yet."

Six: how to get people past it

The gap is usually not reluctance. It is that nothing forced the moment.

Training shows how it works
Nobody said when the first real entry happens

What works

One   Name a date. "From Monday, all bookings go in the system."
Two   Pick one shift, not one person. Everybody on Monday night.
Three Stop the parallel record. Two systems means neither is trusted.

⚠️ Three is the hard one and the decisive one. As long as the paper sheet still exists, the paper sheet is the real system and the new one is homework.

⇒ On the related problem of new arrivals who never quite finish starting: the guest who stopped halfway.

Seven: clearing the samples

If your system came seeded, decide what to do with the samples.

Leave them   confusing later - "whose booking is this?"
Delete them  clean, but the screen looks empty again
Rename them  worst - they become half-real

⚠️ Deleting is usually right, once somebody has entered one real record. Until then they serve their purpose, which is showing what a filled screen looks like.

⇒ Whatever you choose, do it deliberately and on a date, so the answer to "is this real" is never "I'm not sure."

The sample that outlived its welcome

Samples age badly in one specific way: they sit in date ranges.

A sample booking dated "this week" at install
Six months later it is still there, dated six months ago
⇒ it now appears in your historical reports

⚠️ Sample bookings quietly join your numbers. A revenue total that includes four demo bookings is wrong by four bookings, forever, and nobody will ever find them by looking at a report.

Where this bites hardest

Monthly revenue      - the samples have prices on them
Staff performance    - the samples are assigned to somebody
Occupancy and rates  - the samples fill rooms that were never filled

⇒ If you have ever had a figure that was "slightly off and nobody could explain it," this is one of the places to look.

Numbers worth keeping

One   For each system: date installed
Two   Date of the first record created by a person, after installation
Three The gap between them, in days
Four  How many systems you have where Two has not happened yet

⚠️ Four is the uncomfortable one. Most venues have at least one tool that was set up, demonstrated, and never actually used.

⇒ On checks that exist on paper but stopped happening in practice: the check that quietly stopped.

The card for the office

────────────────────────
  Is this system actually in use?

  1. Is anything in it dated after installation day?
  2. Are the names and prices ours, or examples?
  3. When was the first real record entered?
  4. Is there still a paper version running alongside?

  A full screen is not a used screen.
────────────────────────

Common objections

"There's loads of data in there"

⚠️ Check when it was created. All at one instant is a machine; spread over days is a person.

"The supplier set it up properly"

⇒ They set up what they could without knowing your venue. Your names, your prices, your rooms are the part only you can confirm.

"We're still in the learning phase"

⚠️ A learning phase with no end date does not end. Name the Monday.

"We'll clear the samples later"

⇒ Later is when somebody asks whose booking that is. Clear them the day the first real record goes in, and note that you did.

"Our reports would show if something was wrong"

⚠️ Only if somebody opens them. A report that takes too long to load stops being opened long before anybody notices the numbers are off — the shape covered in the report that takes too long to open.

"It's just a trial, it doesn't matter yet"

⇒ It matters most in a trial, because a trial where nobody enters real work tells you nothing about the system — only that nobody got started.

What to do this week

One   Pick one system you rely on.
Two   Ask: what is the newest thing in here, and who created it?
Three If the answer is "installation day", nobody has started.
Four  Name a date and one shift. Stop the parallel record.
Five  Clear the samples once one real record exists.

Summary

Sample data makes a new system look started when nothing has happened
Creation times separate them: one instant is a machine, spread out is a person
We checked ourselves: 1 of 9 signups had real work entered
The milestone is the first real record, not the training
The parallel paper record is what keeps the new system a demo
A full screen is not a used screen

Nobody looks at a full screen and asks whether any of it is real. That is exactly why it is worth asking.

The Screen That Looks Used