When a cleaner leaves your business, their next visits may already be scheduled. There may also be unfinished time records, a delivery assigned to them or a follow-up task waiting for action. Treat the handover as three separate checks: work coverage, outstanding administration and account access. Use the existing JobLog24 screens for these checks rather than assuming there is one automatic leaving process.
1. Agree who owns the handover
Record when the employee stops carrying out work and when their access to the organisation should end. Assign a person to check the handover. List the affected sites, open jobs and outstanding actions. The planner needs to know what must be covered; the office needs to know which final records still require review.
For a routine handover, ask the employee to complete their last entries while connected, then confirm that the office has received them. If access must end immediately, do not delay that decision to wait for missing entries. Record the gap and have the responsible person investigate it separately. Data saved on a device is not proof that the office has received it.
2. Review individual visits and recurring assignments
Open the schedule by employee from the agreed handover date. Check each affected visit for its date, site, times and status. Use the available editing action to assign the replacement. Confirm that person can take the work and review the rest of their day before saving. An empty space in a calendar is not evidence of availability.
Next, review the templates for recurring work. Changing one visit does not automatically change every future assignment. Choose the effective date deliberately when changing a recurring arrangement. Check existing exceptions and look beyond the current week. Keep completed work associated with the person who actually carried it out.
Switch to the site view and ask the replacement to check their own schedule. Confirm they can see the correct jobs and instructions. Arrange physical access to the building separately under the site agreement. Assigning a job in the app does not hand over a key or confirm that the replacement knows the entrance.
The weekly schedule shows jobs by employee, with sites, times and absence in the same view.
JobLog24 with example data.3. Find the less visible commitments
Review open tasks associated with the employee and the affected jobs or sites. Update the responsible person, due date and status as appropriate. Mark a task complete only when the action has actually happened. Recording that an employee is leaving does not transfer responsibility for a client follow-up.
Check assigned supply deliveries separately. Open the request details, confirm the assigned delivery person and arrange who will carry out the delivery. Ask that person to check their delivery list while connected. Reassigning a delivery is not the same as confirming it has arrived at the site.
4. Review final work records before processing hours
Open the last work orders and compare their status, recorded time and notes. Resolve missing or unusual entries before processing hours. Do not create another job simply to work around a missing record. Include the original work order number in the follow-up so the office can find the correct visit.
Use the office hours approval process, then check the payroll report for the intended period. An employee completing a job is not the same as the office approving its hours. The report supports your payroll handover; it does not make a salary payment or carry out a complete final pay calculation.
5. Deactivate the correct organisation account
Open the employee details through Staff and use the available account action to deactivate their access to this organisation. Check the person and organisation before confirming. Changing a role is a different action from deactivating an account. For an invitation that has never been accepted, use the invitation withdrawal action instead.
Check the result with an internet connection. Previously loaded information may remain visible on an offline device. When the app contacts the server and checks access again, changes without valid access are rejected. Do not describe deactivation as an immediate wipe of everything visible locally. Verify the account status and the result of signing in again through your agreed administration procedure.
Example: the last shift is on Friday
Illustrative example: a cleaner finishes at two sites on Friday. The office checks the final time records. The planner reassigns Monday’s visits, then checks the recurring templates and an existing exception for Thursday. An unfinished follow-up task receives a new owner.
At the agreed time, the administrator deactivates organisation access and checks the account status. On Monday, the planner confirms the replacement can see both visits in their own schedule. The handover is complete only after work coverage, outstanding records and access have each been checked.
Common questions
Does removing scheduled visits also end account access?
Do not assume it does. Check the organisation account separately, along with recurring templates, open tasks, deliveries and final hours.
Should completed jobs be reassigned to the replacement?
Keep completed work associated with the original employee. Change future assignments deliberately and review any work still in progress separately.
Will an offline screen disappear immediately?
Previously loaded information may remain visible locally. The app checks current access when it reconnects to the server. Check account status and connected access rather than relying on an old screen.
Handboek 1.4 / roadmap 1.1 / review 2026-11-06