Difference between last day of work and termination date

Hi, 

Just to add to the above, through lessons we have learnt… 

When the last day in office is before the termination date, as a result of an EE wanting to use available annual leave, bob will block the leave request from processing. 

The system views this as gardening leave and as a result doe not allow leave to be captured. 

To work around this, we changed the last day in office field to match the termination date, which then allowed leave to be used, even though the EE was actually no longer in office. 

@Sara Ramos - This is a gap in the design, and it would be helpful if it was possible for the data processor to select the appropriate status i.e.: Employed or Gardening Leave, without the system auto-allocating this, as there often funny situations with EE’s similar to this. Gardening leave system rules could then be invoked on need.

Cheers!

I’m wondering if my understanding of garden leave is correct - when we add a last day of work which is before termination date, for example 14th of March, Hibob will show us the effective date of garden leave in Lifecycle as the 14th and the system access will be deactivated on the14th at the end of day? Or will be it be deactivated on the 13th, before the garden leave start date? Thank you!

​@Sara Ramos is there already an update on this ticket? We experience the same issue as described above.

​@Sara Ramos we found the same as ​@Carol Fairlie. We need to have an accurate last day of work so that we can trigger tasks for returning equipment and arranging handovers etc, but there is no way for us to stop Bob attaching the “Garden Leave” status to those leavers.

For us there is a difference between someone who is in a Garden Leave agreement, vs someone who is taking their remaining annual leave entitlement before their termination date. It’s not appropriate for the Garden Leave status to be attached to employees not in a Garden Leave agreement, even if that field/category is not visible to non-admins, as it becomes an incorrect data point in the system.

We have tried to get around this by creating a custom field for Last Date Worked, but even when we hide the Bob Last Day of Work field in permissions (moved to a separate category which is hidden from all non-admin users) this field still appears in our offboarding flow. We even tried to rename the field but in the offboarding flow it appears with the default out-of-the-box name.

​@Maria Strozynska a lot will depend on your system settings in Bob. 

When Bob places an employee on Garden Leave, this status can then be used to grant/revoke permissions, filter reoprts, etc.. So e.g. our permission groups, visibility of other employee records, and default reports typically apply to or include employees where Lifecycle Status = Employed, once someone is tagged as Garden Leave they are no longer in that group.

I believe there was an update recently where you can now (or potentially due in a future update to be able to) allow employees to request certain types of time off when tagged as Garden Leave. I was trying to find anything in the help centre but couldn’t find info about it. Maybe ​@Sara Ramos and/or one of the Bobbers can help provide more info on this.

HI , I have an issue as we have terminated an employee but I need to change the last day of work. How can I do this? The system will not let me change it? 
thanks!

Hi Everyone! 

Thanks for sharing these insights!

When the Last Day of Work is earlier than the Termination Date, Bob automatically applies the Garden Leave status, which deactivates access at the end of that last working day and blocks additional time-off requests. If your intention is simply for the employee to use remaining leave before their final day, keep both dates the same and record that time as regular time off to avoid the Garden Leave status.

If you need to adjust the Last Day of Work, you can re-trigger the termination flow or remove the termination row in Lifecycle and rerun it.

Thank you!​​​​​​ 😊

Hi everyone 👋

Thanks so much for all the insights shared here! To summarize:

• Last day of work - this is the employee’s final working day.

• Termination date - this is the official date the employee’s employment ends.

If there’s a gap between these two dates, the employee will be placed on Garden Leave during that period. The legal meaning may vary by country or company, but in Bob this means the employee is inactive and cannot access the system.

Regarding date changes after the termination flow has been triggered:

• If the last day of work is in the future, you can re-trigger the termination flow and update the dates.

• If the last day of work has already passed, you’ll need to delete the relevant rows from the Lifecycle table and then re-trigger the flow.

Hope this helps clarify!

Hi ​@Netta Brodsky  - for us, the garden leave should start the day after last working day, is it possible to have it set up this way? 

​@Jagoda Bobrowska If you set the last day of work to 01 April, the Garden Leave status will be effective from 02 April (next calendar day).

Hi there, can an option be added for Gardening Leave or Inactive in these instances? Not all employees who have an earlier last day of work are on gardening leave.

​@Clare Lyons we’ve asked for the same - if you haven’t already, I’d recommend reaching out to your CSM and asking for your name to be added to any feedback or potential future development for this.