Introduction
FTE Tree helps you manage positions, and employees provide context for who currently fills those positions. Employee records let you maintain basic employee information and compare it with the positions an employee is assigned to. Employee fields can use effective start dates, so you can track changes over time.
Employee fields
If there are additional fields you'd like to track for your employees, your organization administrator can add employee custom fields in settings.
-
Employee name: Enter the name of the employee. This value is required and does not need to be unique across your organization.
-
Employee number: FTE Tree assigns each employee an organization-scoped employee number, such as
EMP-0001. This is a display reference used for imports, manager hierarchy references, search, and reporting. FTE Tree stores the underlying integer sequence number, so the prefix, hyphen, and leading zeros are display formatting. Employee numbers are not reused after an employee is deleted. -
External employee ID: This optional value identifies the employee in your HRIS or another external system when your organization enables external employee IDs. When used, nonblank external employee IDs must be unique across your organization.
-
Positions: These are the positions the employee is assigned to. The employee may be assigned to more than one position at a time. Use the Positions tab on the employee record to add an approved position assignment and review current or historical assignments.
-
Status: This value is required. It can optionally have an effective start date, or be left blank to indicate the value has always been active. The default value of 'Active' is required and helps determine whether an employee counts as actively assigned to a position. Additional options can be added through the employee status values for your organization. Each status value controls whether employees with that status count as active.
-
Base wage rate: Enter the base wage rate of the incumbent. You can optionally provide an effective start date, or leave it blank to indicate the value has always been active. This value is used for incumbent cost comparisons and to show the range penetration of the pay grade where appropriate. If an incumbent is assigned to a position but does not have a base wage rate, FTE Tree uses the position's wage rate for cost calculations. If the position wage is also blank and job-code defaults are allowed, incumbent cost can fall back to a direct or inherited job-code default wage. See Position calculations and examples for the full wage-source priority.
Offboarding employees
Offboarding is an HR operations workflow for employees who leave the organization or should no longer fill approved Operating Budget positions. It is separate from ordinary department management and requires the Offboard employees permission.
The offboarding form requires an effective date and does not prefill one. Enter the date the employee should stop filling assigned positions, then preview the impact before confirming. The preview shows current Operating Budget positions that will become vacant, future Operating Budget assignments that will be cleared, and scenario references that should be reviewed separately.
When confirmed, FTE Tree creates an inactive employee status value at the selected effective date, can mark the employee unavailable for future assignments, and creates vacancy rows for affected Operating Budget incumbencies. Historical incumbent rows are retained, so past assignments remain available for audit history and reporting. Scenario incumbencies are not changed by offboarding because scenarios may represent draft plans or future replacement options.
If your organization has enabled audit event notes for employee offboarding, the form may also show a note field, a note choice field, or both. These notes are stored with the employee offboarding audit event.
Comments
The Comments tab on each employee detail page provides a place to have conversations about the employee record. You can create comments, reply to existing conversations with threaded replies, and mention other users in your organization to notify them. Mentioned users receive both an email and an in-app notification.
Commenting on employees requires the View employees permission. For more details about how comments, threaded replies, and mention notifications work, see Messages and notifications.