Front desk
Training your front desk on new clinic software A 5-day plan for the receptionist, with sample patients only.
When a clinic's new software goes wrong, it usually goes wrong at the front desk in the first busy week, on the handful of things the receptionist does all day. This is the plan we would use: one task a day, sample patients only, and a clear test before the desk runs alone.
Published · Last reviewed · 12 min read
- Train one desk task a day for five days: search before create, families on one number, tokens, billing with voids, closing the day. Each day ends with the trainee doing it alone on sample patients.
- Never practise on real patient records. The DPDP Act, 2023 asks a clinic to take reasonable security safeguards against a personal data breach, and a breach includes accidental alteration or disclosure. Practice entries in real files are exactly that.
- The desk is ready when it can find any patient by number, put every token in the right doctor's queue, void a wrong bill with a reason and close the day without help, not when five days have passed.
Give the receptionist five days, one desk task per day, practised on made-up sample patients and then done for real with someone watching. Day 1 is searching by mobile number before creating anyone, day 2 is registration and families on one number, day 3 is tokens and the queue, day 4 is billing and voids, day 5 is closing the day and a mock rush morning. The desk runs alone only after a short readiness check, whatever the calendar says.
This plan assumes a 1 to 3 doctor OPD with one or two people at the desk, and any clinic management software that handles registration, tokens and billing. For what the desk does in a normal day, see our receptionist duties and daily checklist. This post is about teaching it on a new system.
What to set up before day one
Training goes badly when the trainer is also fixing the software. Do these first, ideally a few days before the switch.
- Give the receptionist their own login. Shared logins mean nobody can say later who created a duplicate or voided a bill.
- Set up the clinic as it will run: doctors, fees, follow-up fee if there is one, session timings, letterhead and receipt printer. Practising against wrong fees teaches wrong habits.
- Pick one trainer. Usually the owner or the person who has used the software longest. Two trainers with two ways of doing things is worse than one.
- Write a sample patient list on paper (next section). The trainee works from this list, not from the waiting room.
- Decide where practice entries go. Ask the vendor whether there is a demo or test account. If practice has to happen inside the clinic's own account, do it before go-live and agree with the vendor how test entries will be marked and cleared.
- Keep the old system running for the first week: the paper register, the parchi book, the receipt book. The desk falls back to it if the new system is not ready on a busy morning.
Why practice uses sample patients, never real ones
A trainee will create duplicates, edit the wrong name and bill the wrong person. That is what practice is for. Doing it in a real patient's file means a real record is changed, and someone who should not see it may see it. The Digital Personal Data Protection Act, 2023 brings its duties into force on dates the Centre notifies; section 8(5) says a Data Fiduciary (the clinic, which decides why and how patient data is processed) shall protect personal data "by taking reasonable security safeguards to prevent personal data breach". The Act's definition of a personal data breach includes "accidental disclosure" and "alteration" of personal data. Keeping practice away from real files is one of the cheapest safeguards a clinic has. Our DPDP guide for clinics covers the dates and the rest of the duties.
Build a sample list of eight to ten patients that covers the cases the desk actually meets. Keep the names obviously made up and write "SAMPLE" in the address field.
| Sample | What it teaches |
|---|---|
| A returning adult patient | Search by number finds them; no new file |
| Three family members on one mobile number | Picking the right person; adding a family member under the same number |
| A patient who gives a different spelling of their name | Searching by number, not name; correcting the name instead of creating a new file |
| A brand-new patient | The minimum fields: number, name, age, sex |
| A follow-up visit | Marking the visit as a follow-up and charging the follow-up fee, if the clinic has one |
| A patient for the second doctor | Putting the token in the right doctor's queue |
| A patient whose fee is waived by the doctor | Recording a waiver as a waiver, not as a missing payment |
| A bill entered with the wrong amount | Voiding with a reason and re-entering |
Use the clinic's own mobile number for every sample patient. If the software sends tokens or receipts on WhatsApp or SMS, practice messages then reach the clinic's phone and not a stranger's.
The 5-day plan
Each day has the same shape: the trainer shows the task on a sample patient, the trainee does it on the whole sample list, then the trainee does it on real patients during a quiet hour with the trainer beside them. Keep the sessions short and before or after OPD hours where you can. Nobody learns a new screen with twenty people waiting.
Day 1: Search before create
Teach one habit only: the mobile number goes in first, every time. "Number bataiye" before "naam bataiye". The trainee searches each sample patient by number and says out loud what they see: one person, several people on that number, or nobody. Only "nobody" leads to a new file. Then search by a misspelled name and show that it misses the patient a number search finds. This one habit is what keeps duplicate files out.
- Practice: search all sample patients by number; find the returning patient without creating a file.
- Real: during the quiet hour, the trainee searches every patient who walks in; the trainer does the rest.
- End-of-day check: no new file was created for anyone who already had one.
Day 2: Registration and families on one number
Often one phone number covers the parents, the children and often a grandparent. The trainee learns to pick the right person from the list on that number, and to add a new family member under the same number rather than creating a separate, unlinked file. Teach the minimum for a new patient (number, name, age, sex) and that the rest can be filled in when the desk is quiet. Show how to correct a wrong name or age in the existing file instead of starting again.
- Practice: register the new sample patient; add a fourth person to the family number; fix the misspelled name.
- Real: the trainee registers new patients in the quiet hour, reading the details back to the patient before saving.
- End-of-day check: every new patient today has number, name, age and sex, and nobody has two files.
Day 3: Issuing tokens and running the queue
Now the trainee issues tokens in arrival order and moves patients through the queue. Cover each state the desk will touch: waiting, called, with the doctor, done, skipped, stepped out. Practise a patient who steps out to the chemist and comes back, a patient who misses their call, and a priority case the doctor has agreed in advance. In a multi-doctor clinic, spend most of the day on choosing the doctor: a token in the wrong doctor's queue means a patient waits an hour for nothing.
- Practice: issue tokens for the whole sample list across both doctors; mark one stepped out, one skipped, one priority.
- Real: the trainee issues every token for a session while the trainer calls patients.
- End-of-day check: no patient was in the wrong doctor's queue; no skipped patient was forgotten.
Day 4: Billing, receipts and voids with a reason
Teach the three payment modes as three separate habits. Cash: count it, record it, give the receipt. UPI: confirm the payment on the clinic's own phone or QR stand, never on the patient's screen, then record it. Card: the machine slip plus the receipt. Then teach the two things that cause most money arguments later: a waived or discounted fee is recorded as a waiver with the doctor's say-so, and a wrong bill is voided with a written reason and entered again. A bill is never edited quietly. If the software allows silent edits, the clinic's rule still says void and re-enter.
- Practice: bill every sample visit; record the waiver; void the wrong-amount bill with a reason and re-enter it; reprint a receipt.
- Real: the trainee bills every patient in one session; the trainer checks each entry before the patient leaves.
- End-of-day check: every void today has a reason a stranger could understand, such as "entered ₹500, fee is ₹300".
Day 5: Closing the day and a mock rush
The trainee closes the day alone for the first time: cash in the drawer minus the opening float against cash receipts, UPI on the clinic's phone or bank app against UPI receipts, card slips against card receipts. Any gap is written down with a reason today. Our guide to closing the day has the full procedure. Before OPD, run a mock rush: the trainer reads out the whole sample list quickly, one patient after another, and the trainee registers, tokens and bills without stopping.
- Practice: the mock rush on the sample list, then a close on the sample bills.
- Real: the trainee runs the desk for a full session and closes the real day; the trainer only watches.
- End-of-day check: the close matched, or every gap was found and explained before the desk was locked.
A cheat-sheet for the desk
Print this on one page and stick it beside the screen for the first month.
- Number first. Search before you create anyone.
- Several people on one number: pick the right one, or add a family member under it.
- New patient: number, name, age, sex. The rest later.
- Check the doctor before you issue the token.
- Stepped out: mark it, they keep their place. Missed the call: mark skipped, call next when they return.
- UPI: confirm on the clinic's phone, not the patient's.
- Waived fee: record it as waived, with the doctor's name.
- Wrong bill: void with a reason, then enter it again. Never edit quietly.
- Medicine or report questions go to the doctor. The desk does not answer them.
- Close: cash, UPI and card each matched to receipts. Gaps written down today.
What to do on a rush morning in the first weeks
The first Monday after the switch is where training is tested. A new receptionist under pressure goes back to whatever is fastest, and on new software that is usually typing a name and creating a new file. Agree the rules for a rush before it happens.
- Keep the number-first habit even when it feels slow. A duplicate created at 10 AM costs more time at the next visit than the search saves now.
- Take only the four fields for new patients. Address and anything else can wait for the afternoon.
- Token first, bill after, if the clinic collects after the consultation. Do not let billing hold up the queue.
- Write down anything you are unsure about on a slip ("token 14, maybe wrong doctor") and fix it in the first quiet minute. Do not guess and move on.
- If the system stops or the internet drops, switch to the paper register and parchi without waiting, and enter the visits later. Our post on when the internet drops mid-OPD has the backup kit.
- The trainer stays reachable for the first week of busy mornings, even if not at the desk.
How to know the desk is ready to run alone
Do not go by the number of days. Go by whether the trainee can do each of these without help, on real patients, with the trainer only watching.
| Task | Ready when |
|---|---|
| Search before create | A week of supervised work produces no duplicate files (check the patient list for the same number with near-identical names) |
| Families on one number | The trainee picks the right family member without asking and adds new members under the existing number |
| Tokens | Every token goes into the right doctor's queue; stepped-out and skipped patients are not lost |
| Billing | Every payment is recorded with its mode when received; waivers are recorded as waivers |
| Voids | Every void carries a clear reason; no bill was changed any other way |
| Closing the day | The trainee closes alone and either matches or finds and explains every gap the same day |
| Rush morning | One full busy session run without falling back to name-first search or skipping the bill |
If one row is not ready, repeat that day's task only. Voids and the close usually need the most repetition, because a paper receipt book never asked for a written reason or a three-way match.
Common mistakes in the first month, and the fix
| Mistake | How it shows up | Fix |
|---|---|---|
| Duplicate patients | Same number, two files with slightly different names; the doctor cannot see last visit's prescription | Number-first search, every time; merge or correct the duplicate the same day as the clinic's software allows |
| New file for a family member who already exists | Two files for one child, one under each parent's number | Search both numbers the family gives before creating anyone |
| Token in the wrong doctor's queue | A patient waits through another doctor's list | Confirm the doctor out loud with the patient before issuing the token |
| Editing a bill instead of voiding it | The day book total changes with no trace; the close does not match | Void with a reason and re-enter; the owner checks voids at every close |
| UPI recorded before it arrived | UPI receipts exceed what reached the bank | Record UPI only after it shows on the clinic's own device |
| Waiver recorded as unpaid | A dues list full of patients who were never meant to pay | Record waivers as waivers, with the doctor's name |
| Shared login | Nobody can say who made a change | One login per person from day one |
What the front desk should not see or do
Training is also the time to say where the job ends. The desk handles who is registered, who is next and what was paid. It does not read the doctor's clinical notes, does not explain a diagnosis or a medicine, and does not discuss one patient's visit with another person in the waiting room. Under regulation 7.14 of the Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations, 2002, the doctor "shall not disclose the secrets of a patient" learnt in practice, except in a court under a judge's order, where there is a serious and identified risk to a specific person or community, and for notifiable diseases. The desk works in the doctor's name, so the same discretion applies at the counter.
Good software backs this up with roles: the receptionist's login opens the queue, patient details and billing, not the consultation notes. Check this on your own system during day 1: sign in as the receptionist and see exactly what a past visit shows on that login.
Questions
Can the receptionist practise on real patient records?
Avoid it. Practice creates wrong entries and shows records to someone who does not need them. Section 8(5) of the DPDP Act, 2023 asks the clinic to take reasonable security safeguards to prevent a personal data breach, which includes accidental alteration or disclosure. Use a written list of sample patients and the clinic's own phone number.
How long before a new receptionist can run the desk alone?
Go by the readiness check, not the calendar. The 5-day plan teaches one task a day; the desk runs alone once the trainee can search before create, issue tokens to the right doctor, void a bill with a reason and close the day without help.
Should the front desk see the doctor's clinical notes?
No. The desk needs the queue, patient details and billing. Clinical notes stay with the doctor, and regulation 7.14 of the 2002 conduct regulations bars the doctor from disclosing a patient's secrets outside the listed exceptions.
Sources
- Digital Personal Data Protection Act, 2023 (No. 22 of 2023), Gazette of India, 11 August 2023, sections 2(i), 2(u) and 8(5) (accessed 22 Oct 2026)
- National Medical Commission, Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations, 2002, regulation 7.14 (accessed 22 Oct 2026)
This is operational guidance for clinics, not legal advice.
Drafted with AI assistance; every fact checked against the sources listed; reviewed by Shaurya Pratap Singh.