Identify the employee and request
Use a record selector, a plain-language request type, current and requested values, dates, and a short reason.
Give distributed and frontline teams focused mobile self-service for changes, leave, documents, qualifications, acknowledgments, and follow-up—while reviewers keep control of decisions.
Employees can submit a change or leave request from a phone, while managers keep the decision and employee history in the connected workspace.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Sign in to inspect fictional sample records. Install a copy before adding employee access, confidential information, or your own HR rules.
A useful employee app reduces the steps required to make a clear request while preserving the context the reviewer needs.
Use a record selector, a plain-language request type, current and requested values, dates, and a short reason.
Allow a supporting document or note when appropriate without making every employee collect administrative fields.
Assign the manager or HR owner who can approve, return, or reject the request with an explanation.
Let the employee see whether the request is waiting, returned, approved, rejected, or applied and what they must do next.
Not every HR field belongs on a phone. These tasks usually do.
Submit a controlled change instead of editing a master profile with no review history.
Request dates, nominate coverage, share the handoff plan, and complete a return-to-work check.
Upload a requested file, acknowledge a policy, or correct evidence that a reviewer returned.
Add completion evidence, describe a blocker, and keep the next renewal or action date visible.
The mobile app should make the next action obvious and set the right expectation.
| Mobile task | Employee sees | Reviewer sees | Completion |
|---|---|---|---|
| Request a data change | Current value, requested value, date, reason | Employee record, evidence, impact, decision fields | Accepted value applied and status updated |
| Request leave | Dates, type, coverage and handoff | Team impact, coverage, policy context | Decision recorded and return check completed |
| Submit a document | Document request, due date, upload | Document type, status, correction notes | Evidence verified or correction requested |
| Record qualification evidence | Requirement, expiry, file, note | Role requirement, restriction, verification | Evidence verified and next review scheduled |
| Complete follow-up | Action, due date, result or blocker | Review context and expected outcome | Owner verifies completion or resolves blocker |
Mobile convenience should not broaden access by accident.
Use a request when the value affects access, reporting lines, employment state, payroll handoff, or another controlled process.
Show the employee enough to understand the task and status, while keeping unrelated employee records out of the mobile view.
Make downstream application and verification visible so the user does not assume an approved request is already complete.
Administrators can simplify the mobile form without redesigning the desktop records and management views behind it.
A mobile employee action can be adjusted in minutes while the underlying employee history and management dashboard remain connected.A useful phone experience makes a specific request or decision easy while protecting unrelated employee records and specialist HR functions.
Let an employee request a personal detail change, leave, document update, or qualification review with only the context needed for that action.
Payroll calculation, benefits administration, bulk exports, and broad employee-directory editing belong in the products and roles that own them.
Verify field length, uploads, task notifications, permissions, connectivity, and manager decisions with the phones and accounts the workforce will actually use.
It should let employees and managers complete high-frequency tasks such as profile changes, leave, documents, acknowledgments, qualification evidence, approvals, and follow-up while showing a clear status and next action.
This page does not claim offline operation. Test connectivity, browser or app behavior, file upload, notifications, and the exact devices your workforce uses before rollout.
Jodoo can route workflow tasks to reviewers. Configure the decision fields, task view, permissions, and notifications for your process, then test the real mobile path with the roles that will use it.
Usually not. Provide only the person’s own request, document, task, or status unless the role legitimately needs broader team information.
No. The demonstrated workspace focuses on employee requests and operational follow-up. It does not claim GPS surveillance, biometric attendance, or offline capture.
Open the mobile forms, test the request and review path, and remove every field the employee does not need at the moment of action.
Open the mobile employee app