<\/p>\n
We build employee management apps on Power Apps and Dataverse \u2013 time tracking, leave requests, sick leave, and task management in one place, with a live dashboard for managers. Built inside your Microsoft 365 tenant, handed over as yours, and designed to work equally well on a shop-floor tablet, a phone, and a desktop.<\/p>\n
\u0417\u0430\u043f\u0438\u0442 \u043d\u0430 \u043e\u0446\u0456\u043d\u043a\u0443<\/a><\/p>\n <\/p>\n Most small and mid-sized teams run this on a mix of paper timesheets, a shared Excel file, and verbal requests to the office. It works, until someone forgets to update the sheet, a manager approves leave nobody recorded, or a new hire has no idea what they’re supposed to be working on today. The tools to fix this are already included in your Microsoft 365 licence \u2013 they just need to be built into one connected app instead of staying scattered.<\/p>\n Clock-in and clock-out happen on paper, in a spreadsheet, or not at all. Overtime and undertime hours get calculated manually at the end of the month, if they get calculated at all. Nobody has a real-time view of who’s actually on site right now.<\/p>\n A holiday request is a WhatsApp message or a verbal “is it okay if I take Friday off?” Remaining leave balances live in someone’s head or an outdated spreadsheet. Sick leave gets reported by phone call and never makes it into any record a manager can look back on.<\/p>\n Work gets assigned verbally in the morning and tracked nowhere. By the afternoon, the manager can’t say what’s done, what’s in progress, and what got missed \u2013 and neither can the employee, three days later.<\/p>\n <\/p>\n We build one Power Apps canvas app, backed by Dataverse for clean role and permission handling, that covers attendance, leave, tasks, and a manager dashboard \u2013 with Power Automate handling the approvals and notifications behind the scenes. Modular by design: start with the core, add modules later without rebuilding what’s already working.<\/p>\n Clock in, clock out, and log breaks from a phone, tablet, or PC \u2013 no separate hardware, no separate login. Typical capabilities include:<\/p>\n Holiday requests, approvals, and sick leave in one place instead of scattered across messages and phone calls. Typical capabilities include:<\/p>\n Tasks assigned by management, tracked by everyone, forgotten by nobody. Typical capabilities include:<\/p>\n A single screen that answers “what’s going on right now” \u2013 for the employee and for the manager. Typical capabilities include:<\/p>\n <\/p>\n We start by mapping which modules you need from day one and which can follow later, how your Microsoft 365 licensing supports Dataverse, and the exact rules for overtime, leave accrual, and approvals. This is documented and agreed with you before development starts \u2013 getting the rules right up front avoids rebuilding them later.<\/p>\n The app is built directly in your Microsoft 365 tenant on Dataverse. We share a working version once the core screens are functional, and incorporate your feedback before finalising the logic and approval flows. You see progress before sign-off, not just at sign-off.<\/p>\n You test the app against real working days \u2013 clocking in, requesting leave, assigning and completing tasks. We manage test case creation, coordinate execution, and track and resolve any defects before go-live.<\/p>\n Full handover including screen-by-screen documentation of the app logic, the Dataverse data model, and the approval flows behind it. Your team gets admin rights and the app is yours \u2013 hosted in your tenant. Includes 3 months of defect remediation. Ongoing support available as a retainer.<\/p>\n <\/p>\n Not every team needs every module on day one. We typically recommend starting with the modules that replace the most manual work first, then adding the rest once the core app is in daily use:<\/p>\n <\/p>\n We work on a Time & Material basis. You pay for days actually worked at a fixed day rate \u2013 no fixed-price guesswork, no hidden costs.<\/p>\nAttendance, leave, and tasks live in three different places \u2013 and none of them talk to each other.<\/h2>\n
Attendance tracked by hand, or not at all<\/h3>\n
Leave requests without a system<\/h3>\n
Tasks assigned, then forgotten<\/h3>\n
What’s in the app.<\/h2>\n
Time Tracking<\/h3>\n
\n
Leave & Absence Management<\/h3>\n
\n
Task Management<\/h3>\n
\n
Calendar & Dashboard<\/h3>\n
\n
\u042f\u043a \u0446\u0435 \u043f\u0440\u0430\u0446\u044e\u0454.<\/h2>\n
1. Requirements & Data Model<\/h3>\n
2. \u0421\u0442\u0432\u043e\u0440\u044e\u0432\u0430\u0442\u0438 \u0442\u0430 \u0437\u043c\u0456\u043d\u044e\u0432\u0430\u0442\u0438<\/h3>\n
3. \u0423\u043f\u0440\u0430\u0432\u043b\u0456\u043d\u043d\u044f UAT<\/h3>\n
4. \u041f\u0435\u0440\u0435\u0434\u0430\u0447\u0430 \u0442\u0430 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0456\u044f<\/h3>\n
Start with the core, add the rest later.<\/h2>\n
\n
\u041f\u0440\u043e\u0437\u043e\u0440\u0435 \u0446\u0456\u043d\u043e\u0443\u0442\u0432\u043e\u0440\u0435\u043d\u043d\u044f.<\/h2>\n