Off-Board an Employee in FCX HR

Modified on Thu, Dec 29, 2022 at 4:11 PM

Close Employee

Begin off-boarding an Employee by changing the Status of their Employee card to "Closed."



Closing the Employee card automatically closes SOME associated records, but not all. Notably, "User" is unaffected. It is therefore often necessary to take several additional steps to finish offboarding the Employee.


Other Cards Auto-Closed via Closing Employee Card

Card (or Object)
Addl. Action to Take/Not TakeDetails
Login
NoneClosure revokes Mobile App and Web Doc Portal access if it was enabled.
Location (Emp. Home)NoneNote that this applies regardless of whether the Emp. Home Location was "Authorized" or "Unauthorized."


Take Manual Action on Other HR-Related Cards

The following HR-related records should be checked/updated upon an Employee's departure:


HR Cards Unaffected by Closing Associated Employee Card

Card (or Object)Action to Take/Not TakeDetails
Employee CostDo NOT Close

Should not be closed as this may interfere with calculation of Financial Distributions. (FC)

TK ConfigurationDo NOT Close
AssetReassign
Reassign Assets to reflect change in Holder (note anything not returned).
CertificationShould CloseTo avoid being sent Notifications when Employee's Certs. start expiring.
Notification SubscriptionUnsubscribeNote that this only applies to static subscriptions, not ones where the Employee is subscribed by Role (via dispatch, etc.) (FC)
UserEmail Fieldclix Support and Billing and request deactivate userYou MUST take this step to remove the user from your billing statement


Take Manual Action on Non-HR-Related Cards


IMPORTANT
Future Time-Off Time Cards must be deleted during offboarding to prevent payroll problems!
For more information,
 see here.


Non-field employees, in particular, can have many other associations in FCX that should be checked/updated where applicable:


Other Employee Associations to Edit for Offboarding
Card (or Object)AssociationAction to Take/Not TakeDetails
Dispatch (Future)Main Assignee or Crew MemberRemove/replace assignment
For accuracy
ProjectOwnerReassignTo grant access to substitute
ScenarioDefault Role AssigneeRemove/replace assignmentFor correct TC routing, etc.
Default Milestone ResponsibleRemove/replace assignmentFor accuracy
BP
BPOUse "Replace in BPs" button on Employee card (See Below)For correct TC Routing, etc. Note that only Project Owners, PLMs or Admins can make this change.
Role assigneeUse "Replace in BPs" button on Employee card
For correct TC routing, etc. 
Allowed-to-Allocate TableRemoveFor accuracy
Calculation SpecificationProfit Center
ReassignFor Financial Distributions
Calculation SpecificationTime Card ReviewerReassignFor correct TC Reviewer calculation
Office/Dept.Dept. HeadTemp: User Substitution
Later: Reassign
For correct TC routing, etc.
Other Emp. CardsSupervisorTemp: User Substitution
Later: Reassign
For correct TC routing, etc.
MarketMarket LeadRemove/ReassignFor accuracy
Asset CategoryCategory ManagerTemp: User Substitution
Later: Reassign
For Asset-related Notifications
VIM Inv. CategoryFLA or SLATemp: User Substitution
Later: Reassign
For correct VIM Inv. approval routing
VendorResponsibleReassignFor correct VIM Inv. approval routing
SiteResponsibleReassignFor accuracy


Replace in BPs

You can use the "Replace in BPs" button on the Employee card to replace the Employee in Project Role assignments and BPO assignments. Note that this doesn't affect Scenario default Role Assignments:



Update Milestone Responsible in Created BPs

"Replace in BPs" will take care of BP Role assignments but it WON'T change cases where an Employee was assigned as Responsible for Milestones.

One way to quickly change Milestone Responsible is to use the "Update Milestone Responsible in Created BPs" button on the Scenario card. This works if you want every instance of a Milestone under a Scenario to be assigned to someone else. IF you need instances to be assigned to one person and others to another person, you will have to change those assignments one-by-one.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article