Skip to main content
GullySystem
A practical guide

Pilot a ready product on one branch or one production cell first

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

Pilot on one branch or one production cell for a fixed period. Pick a typical site. Run the same records on old and new systems; agree pass marks in writing before day one and set a decision date. Roll out only after the pilot meets those marks.

Pick the site that will teach you most

Skip your easiest branch. Skip your worst as well. Pick one that is typical, with a manager who will report problems honestly and early, because a pilot at a site that hides errors teaches nothing.

For a multi-branch group, choose a branch with the full mix of work, including the awkward cases that head office hears about. For a plant, choose a cell that runs a complete flow, from issue of material to the finished count.

Name one owner for the pilot. That person needs the authority to say yes or no, and the time to read the daily difference sheet; a committee will not do. Nor will a vendor.

Run the same records on both systems

Decide which records are entered twice. Keep the list short, or staff will drop it by day three. Daily takings, the recall list, root canal sittings booked, the shift’s scrap count and one counted box of composite resin are usually enough.

Give the double entry a time limit. Two weeks is plenty. Beyond that the team resents the extra work, the old register gets filled in from memory, and the comparison stops meaning anything at all.

At close each day, one person compares the two totals and writes the difference on a sheet, with its cause. Differences are the best output of the whole pilot.

  • Daily cash, card and cash book totals
  • Recall list or batch roll call
  • One box of composite resin or one bolt size counted at close
  • Cartons packed and rework tags per shift
  • Each difference with its cause and initials

Set pass marks before day one

Pass marks stop the decision from turning into an argument; write them down before the pilot starts and have the owner sign them. Each one must be something a person can check with a tick.

Good marks are concrete. Totals match on every day but one. A receptionist books a returning patient in under a minute, a shift supervisor closes the count without a calculator, and nobody calls the vendor for a routine task. Write yours that plainly.

Add one mark for the vendor. How fast did they answer when something broke? Log each issue with the time raised and the time fixed; the answer is then a number and not an impression.

  • Totals match on all but one day
  • Booking time under a minute at the front desk
  • Month-end collection report prints without spreadsheet fixes
  • Chairside assistants and supervisors finish tasks unaided
  • Vendor reply time logged per issue

Two pilots in practice

Take a dental group with two branches. Run the pilot at the smaller branch, the one with the busier lab link. Appointments, treatment plans, instalment payments, OPG referrals and crown orders to the lab all run on the new system while the old diary stays open beside it. Chairside staff test it hardest.

Now a tuition centre with morning and evening batches. Pilot the evening batch first. It has more late fee payers, more missed roll calls and the mock test series. Keep the morning batch on the old fee receipt book until the pass marks are met.

For a plant, pick the packing cell, where the count is easy to check by eye. Issue each job on the new system and on the paper traveller together; compare the carton count and the rework tags when the shift ends.

Fix the decision date and the next step

Put the decision date in the diary at the start. At that meeting, compare results against the pass marks one by one. There are three outcomes. Yes. No. Or yes after named fixes and a second, shorter pilot.

If it is yes, plan the next site from what the pilot taught you. Reuse the cleaned masters and the approved print formats, and borrow a trained staff member from the pilot site as a floor guide for the first week.

Today, name the pilot site. Then write down three pass marks.

Pilot plan sheet

Plan sheet in blocks: pilot site and owner, records entered twice, start and end dates. Next come five pass marks with a tick column and an issue log with raised and fixed times. A decision box holds the date, the verdict and the signatures. It fits on one page.

Open a blank worksheet to print

Questions owners ask

How long should a pilot run?

Long enough to cover one full cycle, such as a month-end close, a fee instalment due date or a complete production order; two to four weeks is common.

Do we really need to run both systems together?

For records that carry money or stock, yes; parallel entry exposes rounding, missed sittings and lost receipts that a demo never will; keep the list short.

What if the pilot site fails a pass mark?

Find the cause first. Fix and re-test the failed item rather than restarting everything, unless the fault lies in the data load.

Who should be the pilot owner?

Someone with the authority to approve or stop the rollout, and the time to read the daily difference sheet.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements