Who has not received a response?
Maya’s report is waiting for a supervisor. Keep that response visible instead of assuming that submitting the form notified the right person.
Respond when someone is unexpectedly unavailable. Connect the report, urgent work, cover owner, and return follow-up without turning it into a vacation approval.
Sign in to preview. Install with sample data to try your own reports and coverage tasks.
An unexpected absence creates several different questions. A report can be acknowledged while a shift is still uncovered. An expected return date can pass without the person actually returning.
Maya’s report is waiting for a supervisor. Keep that response visible instead of assuming that submitting the form notified the right person.
Noah’s dispatch checks need attention. Creating a coverage assignment is the start of the handover, not proof that someone accepted it.
An expected return has passed for one example report. Contact the employee through the agreed channel and update the record; do not infer a return from the calendar.
Describe a piece of work that another person can accept. “Cover Noah” is less useful than “Complete the morning dispatch checks before the 10:00 handover.”
Link the assignment to the absence report. Record the task or shift, when cover is needed, urgency, and the proposed cover owner.
The selected owner receives an acceptance task. Until they respond, the assignment remains in the awaiting-acceptance queue.
After acceptance, a completion task follows. The supervisor can distinguish “someone agreed to do it” from “the work is finished.”
The app coordinates people and tasks. It does not automatically choose a qualified substitute, optimize staffing levels, or check employment restrictions.
Collect the employee, absence start, who is reporting, a broad category, and urgent work. Allow “return not yet known” so the reporter does not have to invent a date. The employee’s assigned supervisor receives the response task.
See the absence report formA customer-support team needs a queue and handover time; a dispatch team needs a route, loading check, or scheduled handover.
An administrator can change the affected-work fields, urgency choices, supervisor view, and coverage task instructions in Jodoo. The report-to-assignment relationship remains intact.
Before inviting staff, connect real members to the People records and assign the reporting, supervisor, and coverage access groups. Check each role with its own account. The public example uses fictional people and does not certify your organization’s privacy setup.
Use a request, an approval decision, and the relevant leave account.
Inspect the account credits and booked hours, not the number of absence reports.
This is an operational absence and coverage app. Payroll, clock-in attendance, statutory leave cases, medical certification, and automated disciplinary scoring are outside the supplied system.
For recording work performed, explore employee time tracking →
Yes. The report includes an employee or supervisor-on-behalf choice. Assign the supervisor reporting access group deliberately, so staff are not given unrestricted access to one another’s records.
Select “Not yet known” and leave the expected date empty. Keep a responsible supervisor and an appropriate check-in arrangement. Update the same report when the situation becomes clearer.
No. Acknowledgement records the supervisor’s response. Coverage assignments have their own owner, acceptance, and completion tasks, so an unresolved handover is not hidden by an acknowledged report.
No. It coordinates reports, cover, and operational return follow-up. It does not calculate worked hours, statutory pay, payroll deductions, or medical eligibility.
Not automatically. An unexpected report and a policy-governed leave booking are different records. Decide which category and allowance apply through your HR process before introducing any connection between the two systems.