Location Based Attendance for Yoga Studio Staff on WhatsApp

It's 6:10 AM. The 6 AM Hatha batch is on the mat, but the instructor isn't. The front desk person is calling, the WhatsApp group is pinging "reaching in 5 mins," and the owner — who should be reviewing this month's trial-to-membership conversions — is instead trying to figure out if this is a genuine traffic jam or the third late arrival this month from the same trainer. There's no record, just memory and mood.

This is the actual cost: not the ₹500 you might dock from a salary, but the 20 minutes of owner attention every single working day, spent chasing "who's in today" instead of running the studio. Add a second location (many Bhubaneswar and Pune studios now run a morning batch at one branch and evening at another), and the same trainer's attendance across two addresses becomes impossible to verify by memory alone. By month-end, the register is a mix of guesswork, WhatsApp screenshots, and a hurried Excel sheet built the night before payroll.

This guide walks through a location based attendance for yoga studio setup that runs entirely inside WhatsApp — no app to install, no biometric machine at the door — covering what it does, how it works with real sample chats, what it costs, and how to get it live in two days. The exact build is on the offer page.

What a Attendance Bot actually does for a Yoga Studio

For a yoga studio, "staff" isn't one category — it's instructors who may teach at two branches, a front-desk/reception person, a housekeeping staff who opens the studio before anyone else, and sometimes a nutrition or Ayurveda consultant who visits twice a week. Each has a different shift pattern, and each is a different kind of attendance headache.

• Location-verified check-in: staff send their location on WhatsApp at clock-in; the bot confirms they're within the studio's geofence (typically 100–150 metres, wide enough for parking but tight enough to stop a "check-in from home" jugaad) before marking them present.
• Shift broadcast: batch changes (a 6 AM class merged into 6:30 AM during low winter footfall, or an extra Sunday workshop slot) go out automatically to the relevant staff group, so nobody finds out from a client instead of from the studio.
• Leave request flow: an instructor messages "leave kal, ghar mein kaam hai" and the bot logs it, tags the owner or manager for approval, and updates the shift roster so a substitute can be arranged before the batch, not during it.
• Monthly attendance export: a clean sheet at month-end with check-in time, location match status, and leave days per staff member — ready for payroll, no manual reconciliation of ten WhatsApp chats.

How it works, step by step

1. Studio owner sends a WhatsApp message to Bharat AI Saathi describing staff count, number of locations, and shift pattern.
2. We map the studio's actual batch timings (early morning, evening, and any weekend workshop slots) into the shift schedule.
3. Studio location(s) are set as geofence points — if there are two branches, both get separate check-in zones.
4. Staff are added to a WhatsApp broadcast list; each gets an onboarding message explaining how to check in.
5. Daily: staff send location pin at arrival, bot verifies and logs it, replies with confirmation and that day's batch schedule.
6. Leave requests and batch changes flow through the same chat — no separate app or spreadsheet touch needed by staff.
7. On the 1st of each month, the owner receives the attendance sheet automatically, formatted for payroll.

Two real patterns this handles:

Customer: Mam 6:30 wali class hai kya aaj ya 6 hi hai? Bot: Aaj 6:30 AM hai, Hatha batch. Regular timing 1 hafte baad se resume hoga.

Customer: I'm running 10 minutes late for my 7 AM shift, stuck at the signal near Master Canteen Bot: Noted — logging you as arrived once you check in with location. I've alerted the front desk to hold the batch briefly.

A typical week, before and after

What it costs and what is included

The setup fee is roughly what a studio might spend on one late-arrival-related client complaint or one payroll correction cycle. If it recovers even one missed substitute-arrangement scramble or saves the owner those daily 20-minute chases, the monthly care plan cost is already justified — the rest is time and stress you get back.

Setup timeline

Day 0

You have a 20-minute call with us: staff count, branch locations, shift patterns, and any existing WhatsApp broadcast groups. We confirm geofence points for each studio address.

Day 1

We configure the check-in flow, shift schedule, and leave logic against your actual batch timings. You review the onboarding message that will go out to staff and approve wording (studio name, branch names).

Day 2

Staff receive onboarding messages and start checking in live. We monitor the first day's check-ins with you to catch any geofence radius issues (too tight near parking, too wide near a neighbouring shop) and adjust immediately.

What you need to have ready

• List of staff with WhatsApp numbers (instructors, front desk, housekeeping, any visiting consultants)
• Exact studio address(es) for geofence setup — including second branch if applicable
• Current batch/shift timetable, including weekday vs weekend variations
• Any existing leave policy (advance notice required, substitute arrangement process)
• Payroll cut-off date so the monthly export timing matches your cycle

Doing it yourself vs done-for-you

DIY spreadsheets are genuinely fine for a one-person, single-location studio with two or three staff — the overhead of any tool may not be worth it yet. The gap shows up once you have multiple branches or more than four or five staff on rotating shifts.

Mistakes yoga studios make with this

• Setting geofence radius too tight: a 30-metre radius fails for staff parking a bit away; widen to 100–150m so check-ins don't falsely fail.
• Not accounting for weekend workshop staff: guest instructors for a one-off Sunday workshop get left out of the roster and check in manually elsewhere — add them for that day only.
• Treating leave requests as informal chat: if leave messages aren't tagged for approval, they get buried in a busy group chat — the structured flow prevents this.
• Ignoring the monthly export until payroll day: reviewing it mid-month catches attendance disputes early instead of at the worst possible time.
• Forgetting to update geofence after a branch relocation: if a studio moves address, old geofence data stays live unless updated — flag this to us immediately in the care plan.

FAQ

Does this need staff to install a new app?

No. Everything runs inside WhatsApp, which staff already use. There's no separate app to download or learn.

What happens if a staff member's phone GPS is inaccurate indoors?

We set a reasonably wide geofence radius specifically to accommodate GPS drift near buildings. In our experience this handles most cases; occasional manual override by the owner covers the rest.

Can it handle two studio branches under one setup?

Yes. Each branch gets its own geofence point, and the monthly export separates attendance by location.

Is staff data stored securely?

Location data is used only to verify check-in against the geofence and isn't stored beyond what's needed for the attendance record. You own the data and can request deletion anytime.

What if we want to stop the service later?

There's no lock-in. You can discontinue the monthly care plan anytime; the setup itself keeps working as configured until you choose to stop.

How is this different from just using WhatsApp groups manually?

A regular group has no verification, no structured leave flow, and no automatic export — it's just chat history. This setup adds location-verification, structured logging, and a payroll-ready sheet on top of the same WhatsApp interface staff already use.

Next step

Message us on WhatsApp with your business type (yoga studio), city, and what's currently leaking — late instructors, multi-branch confusion, or messy payroll reconciliation. Check the full scope on the offer page, or see our general process on how we work. Built by Bharat AI Saathi.