An effective date answers, “When does this information apply?” It lets FTE Tree keep earlier approved information while showing a later change at the right time.

Before you begin

The date selector never expands access. For example, reviewing positions requires the View positions permission, changing them requires the Manage positions permission, reviewing employees requires the View employees permission, and financial values require their separate labor budget or actual compensation permission for the relevant departments.

Choose the date first

Use the shared effective date control before reviewing a position, assignment, labor budget result, or actual compensation result. A change can appear on one date and not another.

Add a real change

Use a new effective date when the business information truly changes, such as a position moving departments, an assignment beginning, a budget rate changing, or a compensation record starting.

Clear an optional value

On a normal edit form, clear an optional value and choose the date when it should become blank. The earlier value remains in history and applies through the day before that date. The value stays blank until another dated value begins.

This is a dated change, not an end date. In an Update import, a blank cell normally leaves the existing value unchanged; use <clear> only when the downloaded template guidance allows it.

Use an end date for a period

Some information covers a period that can stop without a replacement, such as an assignment, budget rate, or compensation record.

An end date is not included in the period. It is the first date the information no longer applies. Do not enter the last day the information should apply; enter the following day.

For example, an assignment with an effective date of March 1 and an end date of April 1:

  • applies from March 1 through March 31;
  • does not apply on April 1; and
  • allows another assignment to begin on April 1 without a one-day overlap or gap.

If the next assignment begins April 2 instead, April 1 is a gap. This same boundary rule applies when ending a budget rate or compensation record.

Leave the end date blank when no end is known or planned. A blank end date means the period remains open-ended; it does not mean that the record ends today. Add the real end date when it becomes known instead of entering a distant placeholder date.

End date compared with Through date

A Through date is included in the period. It is the last date the information applies.

Intended last included date Date field Date to enter
March 31 End date April 1
March 31 Through date March 31

Therefore, an end date of April 1 and a Through date of March 31 describe the same final included day. The difference is that an end date names the first excluded date, while a Through date names the last included date.

Correct recorded information

Use Correct only when an existing recorded value or date was wrong. Use Void only when that dated entry should never have existed. These actions preserve Activity history while showing the corrected information on the record.

Approved and proposed position values

A proposed position change must be approved and applied before it changes approved position control. Requests submitted directly from Position control apply at final approval. Requests linked to a forecast can remain approved while waiting for the selected group to be applied from the forecast. Once applied, the new value appears beginning on its effective date. See Review and apply a forecast.

Reports and completed results

A report uses the dated information included when it is prepared. Later corrections do not rewrite an older completed report; run it again when you need the corrected result.