Scheduled Dates
Last updated: November 20, 2026
Some dates come back on their own: a contract renewal, an anniversary, a payment date. A scheduled date is a date field that follows a repeating schedule instead of a date someone types. You give the record a start date and a repeat, and the field shows the date the schedule gives it. As time passes, Lextree moves the field to the next one, so nobody re-enters it each term.
Turning a date field into a scheduled one
An admin chooses which date fields can do this. In Custom Fields, a Date field has a Can repeat on a schedule option, and the admin picks what the field shows:
- Shows the next date on the schedule displays the upcoming occurrence, counting today.
- Shows the most recent date on the schedule displays the latest occurrence that has already arrived, counting today.
Some modules ship with such a field, for example a Renewal date on contracts, leases and IP licenses. A field can’t be switched off while records still carry a schedule on it, and a calculated field can’t repeat on a schedule.
Putting a date on a schedule
On a record whose date field allows it, tick Repeat this date on a schedule. The field stops being a date you type. You set:
- a Start date, the first occurrence;
- how often it repeats: every so many days, weeks, months or years, with the same repeat controls a calendar event uses, including the last day of the month for monthly repeats;
- when it Ends: Never, On date, or After occurrences.
An evergreen term of 30 days repeats every 30 days, and a lease that rolls over monthly repeats every 1 month. Under the field, a caption restates your rule in words. The date can’t be typed over while the box is ticked; edit the start date or the repeat to move it. When you view the record, the field looks like any other date with the schedule spelled out below it.
Stopping a schedule
There are two ways, and they differ.
- End it when the arrangement itself is over, such as a terminated contract or a final payment. Leave the box ticked, set Ends to On date, and enter the last real date. A field showing the next date then goes blank when nothing remains, while one showing the most recent date holds on to the last real occurrence. The history stays.
- Remove it by unticking the box. The field turns back into a typed date that keeps whatever it last displayed, and the schedule’s history is deleted.
End a schedule when you want the history kept. Remove it when the field should never have had a schedule.
The nightly move
Every night Lextree checks scheduled dates and advances any whose current occurrence has gone by. A field showing the next date steps to the following occurrence; a field showing the most recent date steps to the one that has most recently arrived. Lextree records the change as made by System, the same way it records a recalculated field.
The advance counts as an edit to the field. A reminder or suggestion rule watching it fires once for each cycle, and any calculated field that reads it updates. The move creates nothing by itself. Events, timeline entries and suggestions appear only through rules your admin configured. If the field’s module is turned off, its schedules wait and pick up again when the module comes back.
Timeline entries
An admin can set a timeline rule to record an entry for each occurrence a scheduled date has reached, so a yearly renewal leaves a Renewed entry every year. These entries are badged Generated and follow the schedule: end or correct the schedule and the entries follow. A record’s page shows its most recent 100 entries, and a line under the timeline says how many older ones aren’t shown.
Importing scheduled dates
Import templates add two columns after each scheduled date field’s own column:
| Column | What goes in it |
|---|---|
| The field’s own column | The start date, the first occurrence |
| Field: Repeat | Daily, Weekly, Monthly or Yearly, or a rule such as FREQ=DAILY;INTERVAL=30 |
| Field: Ends | Empty means never; otherwise a count of occurrences, or a final date written YYYY-MM-DD |
A repeat needs a start date: a row with one and no date is rejected, and mapping a Repeat column without the field’s own column keeps Continue disabled. Ends does nothing without a repeat, and a row with a date but no repeat imports as an ordinary date. A field with no Repeat column in its template doesn’t have the option turned on. See Data Tools for the wizard.
Bulk editing scheduled dates
In the bulk edit drawer of Data Tools, a scheduled date field takes an action instead of a date:
- Repeat on a schedule gives every selected record the repeat you choose, starting from that record’s own current date. A record with no date has nothing to start from and is skipped.
- End the schedule on closes each selected record’s existing schedule on the date you give and keeps its history. A record that has no schedule on the field is skipped.
Afterward the confirmation counts the skipped records and gives the reason.