Rehire Tracking
Last updated: October 6, 2026
Rehire Tracking records multiple employment periods on a single person profile in. When someone leaves and returns, Bridgit preserves their prior employment period and calculates company tenure across all periods, excluding the gaps between them.
Key capabilities:
Store more than one employment period (hire date and termination date) per person
Create periods automatically when a person is deactivated and reactivated
Add past employment periods manually at any time
Display Cumulative Company Tenure on profiles with more than one period
Map rehire date, original hire date, and termination date from your HRIS on reactivation
Eligibility/Prerequisites
All users with Edit People permissions
Note: Automatic period creation from an HRIS requires an active integration whose payload includes rehire date, original hire date, and termination date, and requires those fields to be mapped in Bridgit
How to Use
How periods are created automatically
Deactivate a person's profile. Bridgit closes the current employment period using the termination date.
Reactivate the profile when the person returns. Bridgit starts a new employment period using the rehire date.
Open the profile to view the person's tenure. Once a profile has more than one period, the tenure label changes to Cumulative Company Tenure.
Adding a past employment period manually
Use this workflow to record employment history that occurred before the person was tracked with multiple periods.
Open the person's profile from People in the main navigation
Underneath Employment Dates, select Add Past Employment Period
Enter the hire date and termination date for the period, and a description (optional)
Save your changes
Bridgit recalculates the Cumulative Company Tenure using all periods on the profile.
Using rehire tracking with an HRIS integration
If your HRIS sends rehire date, original hire date, and termination date, Bridgit uses this data to construct historical periods when a person is reactivated.
Confirm that your integration maps the rehire date, original hire date, and termination date fields
Reactivate the person through your integration
Review the profile to confirm that each employment period and the Cumulative Company Tenure value are correct
Common Workflows
Seasonal or project-based workers: A person is laid off at the end of a season and returns the next year. Deactivate the profile at layoff and reactivate it on return. Bridgit keeps both periods and adds them together, so the off-season gap does not count toward tenure.
Union labor that cycles in and out: A person has worked for your company across several projects over many years. Add each past employment period manually, then use reactivation for future returns. Cumulative Company Tenure reflects every period.
Correcting an existing profile: A profile has a single hire date that was overwritten with a rehire date, or an original hire date that inflates tenure. Add the missing past period with its correct hire and termination dates so tenure reflects actual time employed.
Common Questions
Q: Are gaps between employment periods counted in tenure?
No. Cumulative Company Tenure adds up the time within each period and excludes the time between them.
Q: Why does my tenure label say "Cumulative Company Tenure"?
The label changes when a profile has more than one employment period. It indicates that tenure is calculated across the person's full history, not only their most recent start date.
Q: Do I need to stop using my custom tenure field?
Custom fields previously used to track cumulative tenure are not updated automatically. Review them against the tenure shown on the profile before you retire or remove them.
Q: Does this work with my HRIS integration?
Yes, if your integration sends rehire date, original hire date, and termination date and those fields are mapped. Bridgit constructs historical periods on reactivation without manual entry.
Q: Can I edit or delete an employment period after adding it?
Yes, select the three at the end of the employment period you wish to remove. Click Delete Employment Period. Employment dates can be edited by clicking directly on the date you wish to adjust.
Best Practices
Add past employment periods for returning employees before relying on tenure in reports or planning
Deactivate and reactivate profiles for returning employees instead of overwriting the original hire date
Reconcile any tenure-related custom fields against Cumulative Company Tenure, then retire duplicates to avoid conflicting values
For integrated accounts, verify the HRIS field mappings before reactivating returning employees
Need Help?
Contact the Bridgit support team through the Support option in the top navigation bar, or reach out to your Strategic Account Manager directly.