Delivery Attendance Has a Different Shape

Most attendance thinking assumes a person arrives somewhere, stays, and leaves. Delivery work breaks that assumption in the middle. A rider reports to a hub, collects their load, and then spends the shift moving continuously across an area before returning — or not returning at all if they close out from their last drop.

This produces a specific set of failures. Attendance marked at home before leaving. A shift recorded as complete when the rider stopped after their third-last delivery. Riders working across two hubs in a week with no single record of hours. High attrition meaning constant onboarding, so any system requiring lengthy setup per person fails on volume alone.

The design that works separates the two questions. Presence at shift start is verified strictly at the hub, where you control the location and can require face and geo-fence checks. Movement during the shift is treated as visibility rather than as attendance verification. Conflating the two produces systems that either fail constantly in the field or verify nothing at all.

• Riders report to a hub, then move continuously — attendance is not one location
• Marking from home and closing out early are the two most common failures
• Riders working across hubs need one record of hours, not one per hub
• Verify strictly at the hub; treat mid-shift movement as visibility, not verification

Anchoring the Shift at the Hub

The hub is where verification belongs, because it is your location and every rider passes through it at shift start. Attend Mitra lets you define the geo-fence on the shift with the hub's coordinates and a radius that covers the yard and loading area rather than just the building footprint — an over-tight fence at a busy hub generates override requests every morning.

Face verification at check-in confirms the rider who is being paid is the rider who reported. In an industry with high turnover and substitution, this matters more than in most. Enrollment takes under a minute, which is the practical requirement when you are onboarding riders continuously rather than in an annual intake.

Mock-location detection on Android is not optional for delivery operations. GPS-only attendance is easy to defeat with a freely available app, and in a workforce where marking from home is the single most common issue, an unprotected geo-fence provides false confidence rather than control.

• Define the geo-fence around the hub including yard and loading area
• Face verification at check-in prevents substitution at shift start
• Enrollment under a minute keeps up with continuous rider onboarding
• Mock-location detection closes the marking-from-home loophole
• Set radius realistically or you will process override requests every morning

Offline Marking and the Reality of Coverage

Riders lose signal — in basements, in lifts, in gated complexes, in patches of the city where coverage is genuinely poor. An attendance app that only works online will fail at clock-out for a meaningful share of shifts, and every one of those failures becomes a manual correction.

Attend Mitra supports offline clock-in and clock-out with the event queued on the device and synced when connectivity returns. Because an offline event cannot use a live server timestamp, the captured time is bounded rather than accepted blindly, and the feature must be enabled deliberately at platform, company, and shift level. For delivery shifts, enabling it is usually the right call; for a head-office shift in the same company, it is not.

Where a rider ends the shift away from the hub, the same combination applies: the clock-out is recorded with its location, so a shift closed out twelve kilometres from the last drop is visible in the log rather than invisible in a spreadsheet.

• Offline clock-out prevents a category of manual corrections every week
• Offline events use bounded captured times rather than unverified device clocks
• Enable offline mode for delivery shifts, not company-wide by default
• Clock-out location makes early close-outs visible in the log

What the Hub Manager Sees

At 8 a.m. a hub manager needs one number: how many riders are actually here against how many were rostered. The manager app gives that directly — scheduled count, clocked-in count, late count — so the gap is known before load allocation rather than discovered during it.

The team map shows riders positioned in-zone or out-of-zone, and a manager can request a location refresh for a specific rider. In a business where a missing rider means undelivered orders, replacing an unanswered phone call with a positive location check changes the morning materially.

Rosters matter as much as monitoring. Delivery operations run varying shifts across weekdays, weekends, and peak periods. Attend Mitra lets you build recurring patterns once, save reusable roster presets for standard staffing shapes, and keep next week in draft until it is confirmed — then publish the whole week at once so riders are not reacting to a schedule that changes every few hours.

• Scheduled versus clocked-in count before load allocation, not during it
• Team map and per-rider location refresh instead of unanswered calls
• Recurring shift patterns defined once for standard delivery cycles
• Reusable roster presets for weekday, weekend, and peak staffing
• Draft and publish the full week so riders see a stable schedule

Turning Verified Hours Into Payouts

Delivery payroll usually combines a base component with variable elements, and hours are what everything else is checked against. When hours come from verified check-ins rather than hub registers, the monthly reconciliation between operations and finance largely disappears.

Attend Mitra computes payroll runs from the same attendance and leave records, applies overtime as a configurable pay component, derives loss of pay from unapproved absence rather than manual entry, and applies EPF, ESIC, professional tax, and TDS settings. Payslips are generated as PDFs and riders access their own in the app, which removes a constant stream of requests in a workforce that turns over quickly.

For riders who work across multiple hubs, one employee record carries all their shifts, so hours consolidate automatically instead of being assembled from separate hub sheets. The bank transfer file with account numbers and IFSC codes is generated from stored details, which is what makes paying a large, changing rider base practical.

• Verified hours remove the operations-to-finance reconciliation each month
• Overtime as a configurable component; loss of pay derived automatically
• Riders self-serve payslips in the app instead of requesting them
• One employee record consolidates hours across multiple hubs
• NEFT bank transfer file generated from stored account and IFSC details