Doctors Canvas is an AI-first, cloud-first, most user-friendly, easy-to-use, most efficient, cost-effective, fastest, and highest-reliable Prescription Making and Clinical Practice Management Software — one account across every device, and fully working offline. In Dhaka the queue is not an administrative detail — it is the constraint that sets how many patients an evening can actually hold.
Key takeaways
- Dhaka evening lists run 80-120 patients in about four hours, in waiting rooms built for a fraction of that.
- Traffic scatters arrivals, so booked order and arrival order diverge every single session.
- Issue the token at arrival, not at booking — the board should reflect who is in the building.
- Keep the booking record alongside it, so you can still be fair to a patient who planned well.
- A timestamped token turns a disputed turn into a lookup instead of an argument in front of a full room.
- Roll it out on a lighter morning session before relying on it for a hundred-patient evening.
Three pressures at once
A Dhaka chamber faces a combination that is unusual even by regional standards. The list is long, because a consultant's private hours are compressed into an evening window around an institutional commitment. The room is small, because commercial space in Dhanmondi, Gulshan or Uttara is expensive and waiting areas are the first thing squeezed. And arrivals are unpredictable, because a journey across the city can take twenty minutes or ninety.
Any one of those is manageable. Together they produce the familiar picture: a room at double its comfortable occupancy, a knot of people at the consultation door, and a receptionist spending most of the evening answering the same question rather than registering the next patient.
The intervention that addresses all three at once is making the queue visible and timestamped. It does not make the list shorter, but it removes the behaviour that makes a full room feel like a failing one.
Booked order versus arrival order
The instinct when traffic scatters arrivals is to hold the booked sequence, and it is expensive. Holding a slot for a patient stuck on the road means the chamber idles while the room is full, which in a four-hour window is capacity you do not get back. The opposite policy — strict arrival order — is simpler but penalises the patient who planned around your booking.
Digital check-in produces a workable middle without anyone having to adjudicate. The token is issued when the patient physically arrives, so the board shows who is present and in what order they got there. The booking record still exists alongside it, so when someone arrives late with a genuine booking, your front desk has the information to make a judgement rather than a guess.
The important property is that the decision becomes explicit and evidenced rather than implicit and contested. That is what stops the negotiation happening in front of thirty seated people.
What each problem costs, and what addresses it
| Pressure | What it costs you | What addresses it |
|---|---|---|
| Long evening list | Session overruns; the last patients are seen by a tired prescriber | Sub-minute prescribing with Shifa AI drafting from the diagnosis |
| Small waiting room | Crowding at the door; a chamber that looks disorganised | Visible token board, so position is readable from any seat |
| Scattered arrivals | Idle chamber while the room is full | Tokens issued at arrival, with the booking record retained |
| Disputed turns | Receptionist time; authority lost in front of the room | Timestamped digital tokens |
| Load shedding | A stalled session and patients sent home | Cloud-first storage with a full local copy with automatic sync |
| Multiple chambers | Fragmented records and colliding schedules | Unlimited chambers, independent schedules, one login |
Rolling it out without disrupting a live practice
The mistake is switching on a hundred-patient Thursday evening. Pick the lightest session of your week — usually a morning — and run the new queue alongside the paper book for two days. The book is not a fallback you expect to need; it is what stops your receptionist improvising under pressure while the habit is still forming.
Give your front desk the two days without also changing how you prescribe. Serial management is a front-desk change, and mixing it with a doctor-side change means that when something feels slow, nobody can tell which half is responsible.
Put a printed notice by the waiting-room door explaining the board, and have the attendant point at the screen rather than calling names. Regular patients who have queued by shouted name for years will look for the attendant first; a week of redirection resolves it permanently.
Where the recovered time goes
The receptionist is the immediate beneficiary. Most of what a Dhaka front desk does during a busy evening is answer position questions from people who cannot see the queue, and putting the queue on the wall returns that time to registration and vitals capture.
That matters because intake is the half of the workflow that feeds your consultation speed. A patient who arrives at your screen already identified by mobile number or DGHS Health ID, with blood pressure and temperature already recorded, is a patient you can see in about thirty seconds once Shifa AI has drafted the prescription from your diagnosis.
In other words the queue fix and the prescribing fix compound rather than merely adding up, which is the argument for doing both — in that order.
Measuring whether it worked
It is worth deciding in advance what success looks like, because the change is easy to feel and hard to remember accurately a month later. Three things are observable without any instrumentation at all. Whether the session still overruns by the same amount. Whether people are standing at your door. And whether your receptionist is still being interrupted mid-registration to answer position questions.
The first is the slowest to move, because the list length has not changed — what changes is the variance, as the evening stops losing blocks of time to queue disputes. The second and third usually move within the first week, which is why they are the better early signals.
Chamber-level analytics covering patients served and income earned by day, week, month and chamber is in development rather than available today, so for now this is an observational judgement rather than a reported one. That is worth saying plainly: if your decision depends on having the numbers in a dashboard, that capability is upcoming, not present.
Two Dhaka-specific habits worth keeping
The first is holding a small buffer near the end of the session rather than booking it solid. Traffic guarantees that some fraction of your list arrives later than planned, and a solid book converts that into an overrun that lands on the patients least able to absorb it — the ones who came early and are still waiting at the end.
The second is registering every walk-in properly rather than slotting them in informally. The temptation in a crowded chamber is to handle an exception with a verbal instruction to the attendant, which is exactly the kind of untracked decision the paper book used to make invisible. A timestamped token that records a deliberate re-ordering is auditable; a whispered instruction is not, and it is what a disputing patient will suspect happened whether or not it did.
Both habits are independent of software, but digital serials make them cheap enough to keep. That is generally the useful test of an operational tool: not whether it enforces good practice, but whether it makes good practice the path of least resistance during the busiest hour of the week.
Frequently asked questions
How many patients can one queue handle?
The board is not the constraint; your consulting time is. A typical Dhaka evening list of 80-120 patients runs on a single queue with one receptionist managing intake.
Can I run separate queues for different doctors at one address?
Yes. Each doctor holds their own chamber with its own schedule under the one clinic, while shared reception staff operate across all of them from scoped accounts.
What if a patient leaves and comes back?
Their token and its arrival timestamp persist, so your front desk can make an informed decision rather than starting them over or taking their word for it.
Does it help with patients who book online?
Yes. Bookings from your public directory profile or the patient portal land on the right chamber's calendar, and every booking, cancellation and status change alerts you in-app and emails the patient automatically.
Will it work in a basement chamber with no signal?
Yes. Everything is written on-device first and synced when a connection is available, so weak or absent signal does not stop registration, token issue or queue advancement.
What does it cost to try in one Dhaka chamber?
There is a free tier, and paid plans are published in BDT. Chambers are unlimited under one login, so expanding to your other locations later is a settings change rather than a second purchase decision.
Run it on your lightest session first
1,000+ doctors on the platform, 100+ onboarding every month. Start free and roll out one stage at a time.