Running a Corporate Health Camp as a Fixed-Window Batch Job

A health camp is a batch job with a hard window

An office screening does not run for weeks. It runs from 9:00 to 4:00 in a borrowed conference room, with a fixed number of staff, a fixed number of machines, and a client who expects a report two days later. Every slot you publish is a slice of that window, and an unused slice cannot be carried forward.

That framing is what makes corporate health camp booking an operations problem rather than a forms problem. You are allocating a finite resource across a single day, under capacity constraints you cannot change once the van is loaded. The rest of this post walks the flow the way we build it: capacity model, pre-camp confirmation, on-site states, the no-show pool, and what happens after everyone goes back to their desks. The product side is at swiq.services.

Corporate health camp booking needs two capacity layers

Layer one is the company: 300 employees, 180 opted in, 40 confirmed. Layer two is the floor: one BP station, one phlebotomy table, one ECG machine, two technicians. Booking systems that only model layer one happily confirm 180 people for a floor that can process 110.

Publish slots as the minimum of both layers. A slot exists when there is staff time, station time and a free position in the sequence — not merely when the calendar cell is empty. Then split by track: fasting blood work in the morning block, non-fasting consults in the afternoon, and a short re-test lane for anyone who needs a second reading. Two tracks on one floor is still one shared queue, so allocate the shared stations first and derive the tracks from what remains.

Pre-camp: consent, fasting and the confirmation chain

The failure that ruins a camp usually happens 48 hours before it, when three people show up fed. Treat the pre-camp window as its own state machine: invited → slot_booked → consent_signed → fasting_acknowledged → confirmed.

A corporate health camp booking invite chain is only as strong as its last unanswered message, so each transition needs one message and one reply. Slot confirmation first, then a reminder that states the fasting window in plain hours ("nothing but water after 10 pm"), then a final message the morning of the camp that asks for a one-tap confirmation. Anything unconfirmed at the cutoff goes back into the pool. Our clinic appointment booking checklist has the general sequence for appointment links; camps add only the fasting and consent steps.

On-site flow: check-in, tokens and the throughput ceiling

Walk-ins arrive in clumps — a whole floor at 10:15 because a meeting ended early. Handle it with a token queue at the door rather than a paper list on a table: one counter issues tokens, stations call the next number, and a display shows current position so people can go back to their desks instead of standing in a corridor.

Watch the throughput ceiling, not the clock. If station two is clearing eight people an hour while station one clears three, the queue at station one is your real capacity number. Move a technician or split the panel; do not solve it by telling people to come earlier. Tokens also give you the data to prove where the day stalled — which is what corporate health camp booking looks like on the floor rather than in the spreadsheet.

Edge cases: walk-ins, HR changes and the no-show pool

Expect these five before corporate health camp booking opens, and decide the policy for each before the day starts:

• Extra employees not on the list. Accept if capacity remains; otherwise book into the re-test lane or the waitlist with a promise, never a shrug.
• Slot changes from HR at 8:00 am. Re-run the allocation instead of editing cells — one person moving from the fasting to the non-fasting track changes two counts.
• No-shows. Backfill from a waitlist keyed on track and window, offered in order, with a 10-minute reply window before the slot returns to open.
• Station downtime. Mark it blocked, stop publishing the affected slots, and let the queue re-balance rather than silently over-promising.
• Late arrivals. Give them the next free position with a token, not a re-entry to the front.

A workable backfill policy for the third item is in our waitlist management for clinics guide — same refill logic, different room.

After the camp: reports, recalls and the follow-up funnel

The day ends; the data work does not. Close each record into one of completed, left_early, missed or declined, because a flat "attended" count hides the four people whose BP was never taken.

Then run the follow-up as bookings rather than as a mailing list. Anyone flagged for a repeat reading gets a slot; anyone who missed the fasting panel gets a re-visit offer; abnormal results route to the employer's nominated clinic with a booking link already attached. This is where corporate health camp booking stops being an event and becomes a funnel — and where the basic analytics in your booking tool pay for the day.

About SWIQ

SWIQ is built in Jodhpur, India, for teams that run appointments, camps and walk-in counters on one system. It provides an online booking page, service and staff calendars, tokens for on-site queues, WhatsApp confirmations and reminders, a waitlist for backfilling gaps, UPI payment links where needed, displays for the room, and basic analytics for the report. Plans start at ₹777 per month, with ₹1,777 and ₹2,499 tiers; the first 300 bookings are free, setup takes 2 minutes with no card, and there is a 14-day free trial. Details at swiq.services and the landing page, or WhatsApp [phone].