Configure an evaluation step with a due date calculated per staff member from a date on their profile — rather than a single fixed calendar date for the whole cycle.
If you're new to creating evaluation cycle steps, start with Creating and Editing Steps in an Evaluation Cycle.
Jump to:
What Rolling Due Dates Are
Rolling Due Dates give you the option to calculate a step's due date from a date on each staff member's profile — not from a single fixed calendar date. Common use cases:
Probationary new hires who need a first evaluation 30 days after their hire date.
Staff in a rolling cohort who should be evaluated at a consistent interval from a promotion or reassignment date.
Rather than building a separate evaluation cycle for each cohort, you configure one step with a rolling due date rule — for example, "30 days after hire date" — and KickUp calculates each staff member's deadline from their own anchor.
Evaluation Reference Dates (ERDs)
The date on each staff member's profile that KickUp uses as the anchor is called the Evaluation Reference Date (ERD). Before you add a rolling due date to a step, confirm that the staff members in your cycle have an ERD set.
Where ERDs come from:
Scheduled staff file import (most common) — The ERD can be a column in your regular staff file import, typically hire date.
CSV upload — A CSV mapping staff IDs to reference dates.
Setting a Rolling Due Date on a Step
Navigate to the Edit page of the evaluation cycle.
Click the Steps page.
Click Add Step — or open an existing step to edit it.
Configure the Step Name, Step Description, Assignee, and other standard settings. (For details on standard step settings, see Creating and Editing Steps in an Evaluation Cycle.)
Under Due Date, choose the option that lets you configure a rolling date instead of a fixed calendar date.
Set the offset — how many days, weeks, or months after each staff member's ERD the step is due. For example: 30 days after ERD.
Click Save in the top right of the step editor.
[Screenshot: rolling due date configuration in the step editor]
Each staff member in the cycle now has a due date calculated from their own ERD. A staff member with a hire date of June 15 will see a deadline 30 days later; a staff member with a hire date of August 1 will see their deadline 30 days after that.
Good to Know
Weekends are excluded from the calculation. If a calculated due date falls on a Saturday or Sunday, the deadline shifts to the prior business day.
Staff without an ERD won't get a calculated due date. In places where the staff-level due date would normally appear, you'll see "no reference date" instead. The cycle's progress bar flags this proactively with a warning. Both surfaces are designed to make data gaps easy to spot before deadlines become critical.
Fixed calendar dates are still available. Rolling due dates are one option — you can still set a fixed calendar date on any step.
Notifications carry over. Existing evaluation due date notifications work as-is for rolling steps. KickUp sends a notification when a step is due tomorrow, due today, one day overdue, or one week overdue.
Anchoring to dynamic values is not currently supported. Rolling due dates calculate from a static ERD on the profile. Anchoring to values that change over time (for example, "last evaluation completed") is not currently supported.