Presence is captured at the moment it happens, with enough context that a disputed day can be settled from the record itself.
Each punch stores the time, approximate latitude and longitude, the reported accuracy, a resolved address and device information.
Breaks and lunch periods open and close against the same attendance day, with location captured at both ends.
A compact grid per company that reads on a phone and prints cleanly for a signature, with the day's status colour-coded.
The failure mode of most leave systems is not the form, it is the routing. A request has to land with someone who can approve it for that specific company.
Choose the leave type, the start and end date and time, and the reason. Half-day, casual, sick, paid, unpaid, emergency and other are all supported.
Managers and administrators of that company see a review queue where they can approve, reject with a reason, or correct the dates on a pending request.
A lightweight board that carries enough structure to replace a status meeting, without asking anyone to maintain two systems.
To do, ongoing, review and complete. Drag a card to move it, and the status change is mailed to everyone on the task.
Urgent and important are tracked separately, so a genuinely pressing item surfaces on the dashboard instead of hiding in a list.
Set a reminder for the person who raised the task and separately for the assignees, repeating daily, weekly, monthly or yearly.
Every assignee gets their own ticket with a progress percentage, their own note, and a remark from the manager, so two people on one task are not averaged together.
Open, in progress and completed counts on the board come from the same query as the dashboard cards, so the numbers cannot disagree.
A manager sees tasks for the companies assigned to them; an employee sees only what they are on.
Nine event types are delivered automatically, and each one is written to a delivery queue before it is sent, so nothing depends on a server being available at the exact second a user clicks.
Task assigned, edited, moved, deleted and reminded; ticket progress and manager remarks; leave submitted, approved, rejected, edited and withdrawn.
Administrators open a notification log showing every message, its recipient, status, attempts and the exact error if it failed, with a retry button.
Nested folders and files with a per-user upload allowance, shareable privately, to a team, to selected people, or publicly through a link you control.
Purchase orders with serialised item lines, vendor and firm records, quantities, rates and remarks, grouped by company.
Companies, ports, teams and job roles are first-class records. Permissions hang off them, which is why adding a site does not require a code change.
Register staff, assign them to teams and job roles, and set which companies and ports each person can see.
Employee, manager, administrator and super administrator, each with a narrower or wider reach over the same data.
Per-company check-in time and contact details, so lateness is judged against the right schedule.
Attendance and leave patterns by company and period, built for a manager who needs the answer, not the raw table.
Ask your administrator for an account, or request one and the team will route it to the right company. Nothing here is a demo dataset — the modules above are what the application runs.
