Starting a Clinic in India: A Readiness Plan, Budget and Opening-Day Trial
Plan an independent OPD clinic around service scope, local requirements, startup cash, staffing and a rehearsed patient journey rather than a promised launch date.
Hire a clinic receptionist against a defined job and observed work samples, not only friendliness or previous hospital experience. Specify registration, booking, payment, privacy and escalation responsibilities; budget for coverage as well as pay; and train using synthetic patient cases. Reception should recognise when to seek help without being expected to diagnose, interpret results or use the doctor's credentials.
Solo doctors and small Indian clinics recruiting their first dedicated front-desk employee.
Map the tasks that arrive at the desk during a normal session: walk-in registration, appointment calls, patient identification, queue updates, fees, receipts, directions and follow-up administration. Include opening, closing and interruptions. A job description that says 'manage everything' hides the choices the employee will have to make when several people need help at once.
Separate essential skills from skills that can be taught. Clear communication, careful identity handling, basic numeracy and willingness to escalate uncertainty may matter more than familiarity with a particular software brand. Identify the spoken and written languages the role actually requires, without inferring ability from a candidate's name or background.
Define the handoff to the doctor or another clinical professional. Reception can follow a clinic-approved escalation process for a person who appears unwell or reports a concern, but should not independently diagnose, interpret a laboratory result or recommend treatment. The responsible clinician must define the process and available support for the practice's services.
Give every candidate comparable synthetic situations and explain what is being assessed. Avoid using real patient records in an interview. Observe the person's reasoning and recovery, not only how quickly they click. A fast candidate who selects the first matching name without confirmation creates a different risk from a careful candidate who needs software training.
Ask the candidate to explain a fee card aloud, record an appointment change and respond to a caller asking about a family member's visit. Assess whether they recognise uncertainty and seek the right help. Do not reward improvised promises about refunds, wait times or clinical advice simply because they sound confident.
On a narrow screen, scroll the table horizontally to read all columns.
| Synthetic scenario | What to observe | A useful follow-up question |
|---|---|---|
| Two patients share a name | Checks distinguishing details through the clinic's process before choosing a record. | What would you do if neither match can be confirmed? |
| UPI shows pending | Does not invent success or demand a duplicate payment without checking the process. | Who owns the unresolved payment after your shift? |
| A caller asks about a relative | Uses the approved identity and authority process instead of disclosing immediately. | Which details should stay out of a public or shared conversation? |
| Doctor is running late | Gives an honest status and available choices without guaranteeing an exact time. | How would you update patients who have not arrived? |
| A patient reports a concerning problem | Promptly follows the clinic's escalation route without giving a diagnosis. | Who is available when the usual doctor is not at the desk? |
| An entered amount is wrong | Stops, identifies the record state and seeks the permitted correction. | Would your action differ before and after a receipt is issued? |
Use current local recruitment information and a clear job scope when discussing compensation. There is no defensible national salary figure for every clinic receptionist. Hours, languages, responsibilities, location and employment arrangements differ. Confirm applicable pay, working-time, leave and other employment requirements for the actual arrangement rather than assuming a fictional budget meets them.
For a planning example only, suppose pay is ₹18,000, an agreed allowance is ₹2,000 and the clinic reserves ₹3,000 for relief coverage and training. The planned amount is ₹23,000 per month before any additional applicable obligations or costs not included. The reserve is not an assertion about a statutory contribution or a substitute for leave arrangements.
Calculate the workload during the busy window. In a fictional two-hour peak, 30 registrations at three administrative minutes each use 90 minutes; 20 payments at two minutes use 40; ten calls at two minutes use 20. That is 150 minutes of work arriving within 120 minutes, before interruptions. Faster software may help, but one person cannot sustainably supply 150 minutes within that interval.
Choose a response suited to the bottleneck: move non-urgent administration outside the peak, add defined relief, simplify a duplicated step or change appointment flow. Keep the desk covered during breaks and absence. A receptionist should not have to skip every break because the operating model assumes uninterrupted availability.
Create an individual account with the permissions needed for the agreed role. OWASP's authorisation guidance supports minimum necessary access and request-level enforcement. In the clinic, test that reception can perform its work while restricted clinical, financial or account actions remain appropriately controlled; a hidden menu is not sufficient evidence.
Write down which concessions, reschedules and corrections the receptionist can make directly, which need approval and who answers when the usual approver is unavailable. The limit should be understandable in a real case. 'Ask the doctor for everything' creates interruptions; 'use your judgement for anything' creates unbounded responsibility.
Keep the doctor's login and signing authority separate. A receptionist entering approved administrative information is not the same as authoring or signing the consultation. Train staff to lock shared devices, avoid private data in support messages and handle household contact details through the clinic's identity process. Access should change when duties change or employment ends.
Begin with the exact daily workflow and a small set of synthetic cases. Demonstrate, let the employee perform the task, then ask them to explain the exception path. A training video watched to the end does not establish that a person can find the right record or recover from an uncertain save.
Use a staged readiness record rather than an arbitrary one-day promise. Someone may handle routine registration independently while still needing supervised receipt corrections. Make that boundary visible to the employee and the person covering them. Update the record after observing the relevant task, not just after elapsed time.
Review missed handoffs and errors as process evidence. Was the fee policy unclear, did the screen hide the patient's branch, or were calls arriving faster than one person could answer? Individual accountability matters, but blaming staff for an impossible queue does not fix the operating model.
Give feedback on specific actions and agree a practical correction. Recognise good escalation and careful privacy handling, not only speed or money collected. Avoid targets that encourage unnecessary appointments, suppression of complaints or pressure on patients to accept services.
Check whether the job has expanded beyond the original agreement. Adding inventory, bookkeeping, marketing and clinical assistance to reception changes training and coverage needs. Discuss responsibilities and compensation appropriately, and keep a usable handover for leave or departure. The clinic should not depend on one employee's personal phone or undocumented memory to function.
A fictional clinic interviews a candidate who handles the identity and payment scenarios carefully but works more slowly than the owner hoped. The peak-work estimate reveals 150 minutes of administration arriving within a two-hour window. The owner separates deferred paperwork from immediate desk work and provides a defined relief period, then observes the candidate on the simplified synthetic workflow. The decision is based on demonstrated competence and a feasible job, not an expectation that the employee somehow absorbs the extra 30 minutes. The timing assumptions describe administration only and are not recommended consultation durations or staffing benchmarks.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
Relevant experience can help, but it is not a substitute for observed competence. Use realistic synthetic scenarios to assess identity handling, communication, numeracy, privacy and escalation, then identify the software and workflow training required.
Use the actual local market, hours, languages and responsibilities, and confirm applicable employment requirements. Budget for coverage, training and relevant obligations as well as pay. A fictional example cannot establish a lawful or competitive salary for your clinic.
They should follow the clinic's approved information and escalation process within their competence. Diagnosis, interpretation of results and treatment decisions belong with the responsible clinical professional. Define who is available when the usual doctor cannot respond immediately.
Use individual accounts and appropriate permissions. Shared credentials obscure who acted and can expose clinical or signing authority unnecessarily. Improve the workflow and escalation process instead of sharing the doctor's account.
Readiness depends on the tasks and the person's observed performance. Routine work may be learned quickly, while payment, privacy and exception handling need further practice. Record the actual scope of independent work rather than making a universal time promise.
Updated on . Pay and workload figures are fictional planning examples, not market salary guidance or legal employment advice. Clinical escalation must be defined for the actual practice by the responsible professional. No independent clinical or legal review is claimed.
Technical guidance on least privilege, default denial and request-level checks; not an Indian legal compliance certificate.
Plan an independent OPD clinic around service scope, local requirements, startup cash, staffing and a rehearsed patient journey rather than a promised launch date.
Give a clinic administrator clear decision rights, access limits, spending boundaries and exception ownership without sharing the doctor's login.
Handle pending UPI payments with merchant verification, a named follow-up owner, safe fallback payment and duplicate-credit reconciliation.
Ask Bractis to let a new receptionist complete synthetic registration, fee explanation and pending-payment scenarios under the intended permissions. Observe where the employee needs training, clearer policy or additional desk cover.
Request a clinic demo