Skip to main content

Updating the Original Start Date

  • September 29, 2025
  • 6 replies
  • 597 views

Sara Ramos
Bobber

Need to fix an incorrect Original Start Date for an employee?

Here's how to do it safely without disrupting their historical employment timeline.

In HiBob, there are two start date fields—and they work differently:

  • Start Date – Reflects the start of the employee’s current employment. You can update this directly from their profile:
    Profile → Actions → Change work details → Change start date
  • Original Start Date – A system-calculated field that reflects the employee’s very first employment with your company. This can’t be edited directly.

The Original Start Date is pulled from the earliest "Employed" row in the employee’s Lifecycle table. If someone was rehired, the Start Date updates to reflect the new employment, but the Original Start Date stays tied to the first record.

Why can’t I just edit the Original Start Date?

Because it’s meant to preserve historical accuracy—for tenure tracking, compliance, and reporting. If this field were editable, it could cause data conflicts across systems and reports.

Workaround: How to update the Original Start Date

If the Original Start Date is incorrect, you can update it by temporarily adjusting the employee’s Lifecycle history:

  1. Go to the employee’s profile > Lifecycle tab
  2. Find the earliest “Employed” row—this sets the Original Start Date
  3. Temporarily delete all rows after it (terminations, rehires, changes, etc.)
  4. Go to Actions > Change work details > Change start date, and enter the correct date
  5. Rebuild the Lifecycle by re-adding the rows you removed, with the correct dates and details

Before you start

This process rebuilds the entire Lifecycle table, so proceed with caution:

  • Be sure to manually restore all lifecycle events after updating the date

For rehired employees:

  • Start Date = current employment
  • Original Start Date = first employment (unless adjusted using this workaround)

If you’re unsure whether to proceed, check with your HRIS admin or contact HiBob Support to confirm the safest approach.

 

6 replies

Hi Sar.

Is there a way to trigger a task list automatically when a start date is changed or a report? I know that the fields are automatically changed, but for the stakeholders in the pre-onboarding process, they often need to be notified fast. Or do we need to contact them and give them the information outside of Bob?

/Nanna


Sara Ramos
Bobber
  • Author
  • Bobber
  • February 12, 2026

Hello ​@Nanna Ring Damgaard This is a great question, I’m happy to clarify 🤓

At the moment, there is no automatic notification or task trigger when a start date is changed.

What happens instead, depends on how the task list was set up, for example:

  • If the task list is auto-scheduled based on the start date, then any scheduled tasks will adjust automatically to the new date.

  • If tasks were alread triggered, they will not automatically update or notify the stakeholders again.

  • If the task list was triggered manually, changing the start date will not trigger anything new.

So if stakeholders need to be notified quickly after a start date change, you’ll need to cancel the existing scheduled tasks in Manage Tasks and re-trigger the task list from the employee profile with the new start date.

However, this may also resend emails or recreate tasks that were already completed, so it needs to be handled carefully.


Trine  Langholz

We implemented HiBob a litte less that a year ago, so I am not able to delete any further rows in “Lifecycle” - I only have one pr employee. My challenge is that I have some employees who are registered with a start date from the time they got a full time employment. This is their legal correct date in terms of rights and tenure. They have previously been student assistents so they want it to be visible that they have worked here earlier - maybe it can also be used to celebrate anniversaries. What do I do in this situation?  


Hello ​@Sara Ramos,

I have a question as we would like to keep our records correct regarding start dates and original start dates when it comes to acquisitions. 

We recently acquired a company and we would like the original start dates to match the date the employees signed their legacy contracts in the acquired company. The start date should reflect the acquisition date - the day we legally purchased their mother company and they formally joined our company. How do I process this? Once I edit the ‘start date’ it changes the original start date and the start date mirror this data. I’m unable to have two different details.

Would you be able to help please?


Hello ​@Sara Ramos,

I have a question as we would like to keep our records correct regarding start dates and original start dates when it comes to acquisitions. 

We recently acquired a company and we would like the original start dates to match the date the employees signed their legacy contracts in the acquired company. The start date should reflect the acquisition date - the day we legally purchased their mother company and they formally joined our company. How do I process this? Once I edit the ‘start date’ it changes the original start date and the start date mirror this data. I’m unable to have two different details.

Would you be able to help please?

 

Hi Frederik, we are experiencing the same issues, have you found a solution? This is an important nuance because it affects all our global reporting. We have attempted to create a separate Continuous Service Date field, but there is no way to link this to the Tenure calculations which appear on employee profiles and HR and manager dashboards. We were advised to terminate employees the day before the acquisition date and then rehire them on the day of the acquisition, which would achieve the correct Original Start Date and Start Date. However, this also affects our Dashboards as the Terminations, which are not real, appear, and so is not a viable option.

 

@Sara Ramos, any support you can provide would be appreciated.


Hi ​@Tom Edwards,

What we did in the end, we created custom field ‘Legacy Start Date’ as terminating and rehiring would hugely affect our statistics and dashboards regarding headcounts, FTE calculations etc.

We use the acquisition date as original start date as that will truthfully reflect our FTE increase and avoid artificial terminations to have compliant ESG reporting.
I used the ‘Legacy Start Date’ as an anchor event for tasks that include benefits for example 5 years into service grants additional day of annual leave → here we just receive notification along with employee and we have to make manual adjustment. I have this custom field available only for relevant site, not all employees. 

Unfortunately, there is no other solution for this at the moment, HiBob doesn’t have same functionality for this like Workday. I would definitely not suggest termination and ‘rehire’ action. Hope this help you!