Manual attendance works until someone disputes a day. Then you are reconstructing it from memory, a phone screen and a supervisor's note. My Attendance captures the record at the moment it happens, so the reconciliation step disappears.
A register signed by hand
Leave requested over chat
Work chased verbally
Documents on personal phones
Nothing here is a separate product stitched together. A task, a leave request and an attendance record all resolve to the same employee and the same company, so reporting never disagrees with itself.
Check in and out with approximate location, reported accuracy and device details, so presence is verified at the site the person is posted to.
Breaks are started and closed against the same attendance day, with location captured both ways, and roll up into the daily sheet.
Casual, sick, paid, unpaid, emergency, half-day or other. Requests go to the managers and admins of your company and come back with a remark.
A four-stage board with urgency, importance, assignees and per-person tickets, so a manager can see progress without asking for a status update.
Assignments, edits, status changes, reminders and leave decisions are mailed automatically, and every attempt is logged so you can prove it was sent.
Folders and files with private, team, selected or public sharing, so procedures and formats live somewhere durable instead of a chat history.
Attendance patterns by company and period, present and late counts, and a compact monthly grid that reads clearly on a phone.
Purchase orders with vendor, firm, item, quantity and rate, kept per company and available to the vendors you authorise.
Employee, manager, administrator and super administrator, each scoped to the companies they are allowed to see — enforced on the server.
01
Staff check in at the site. Late arrivals are measured against that company's own schedule, not a single global start time, because a plant and an office do not open at the same hour.
02
Work gets assigned on the board with a priority and a reminder. Assignees move their own ticket forward, and both sides get an email when something changes.
03
Attendance, leave and work output are already reconciled. The sheet your manager signs is the same data the system recorded, not a reconstruction.
A record nobody looks at changes nothing. My Attendance pushes the important moments to the right person and keeps a delivery log, so a missed approval stops being a he-said-she-said.
A leave request reaches the managers and admins of that applicant's company. If a company has no manager configured, it escalates to a super administrator rather than vanishing silently.
Each message is written to a delivery queue before it is sent. If mail is unavailable it is retried automatically, and the notification log shows who was mailed, when, and what failed.
The application, its database and its file storage run on managed servers operated for Swan Fintech Private Limited. There are no advertising or analytics trackers in the interface, and the mail integration is authorised to send only — it cannot read anyone's inbox.
Notifications are delivered through Gmail with a single send-only scope. No read, search or delete permission is requested, and the credential never reaches a browser.
Every screen filters by the companies assigned to the signed-in user, and the check runs on the server. Hiding a button is not treated as access control.
Field staff mostly see this on a handset, so the grids, sheets and approvals are built for a narrow screen first.
Accounts are created by your organisation's administrator. Register to request access, or read what each module does before you decide.
My Attendance is operated by Swan Fintech Private Limited. See the Privacy Policy for what data is held and why, and the Terms of Service for the rules that govern use.
