Skip to main content

Events

Last updated: November 20, 2026

Events are the dates that matter — filing deadlines, renewal dates, board meetings, review milestones. An event attaches to a record and sends reminders ahead of time so nothing slips. To see your events, use the Calendar; this page covers creating and configuring them.

Adding an event to a record

Adding events requires Editor access to the record’s module.

  1. Open the record and expand the Calendar section.
  2. Click add (+) to create an event.
  3. Enter the event name, its date and time, and an optional description. An event is All day by default. Turn that off if you want a start and end time instead. Whichever you pick, the event can run over several days.
  4. Set a recurrence pattern if it repeats: tick Repeat this event, then choose an interval and a unit of days, weeks, months, or years, such as every 2 weeks. Set when the repeat Ends: Never, On date, or After occurrences (up to 999). A date field can also repeat; see Scheduled dates. For a monthly repeat that should land on the last day of every month, choose a start date that is the last day of its month and tick On the last day of the month. A monthly repeat that starts on the 29th, 30th, or 31st otherwise skips the months without that day, and a yearly repeat from 29 February runs in leap years only. The form tells you when a pattern skips.
  5. Add one or more reminders and invite anyone who should be notified.
  6. Save.

Reminders

Each event can carry several reminders, each with its own timing — for example, 90, 30, and 7 days before a deadline. Reminders arrive in-app (the notifications bell) and by email, according to each recipient’s preferences. On Business and Enterprise plans, reminders also go by email to email-only recipients outside Lextree. An individual reminder can also repeat — say, daily for the final week. On a repeating event, Lextree sends the reminders before every occurrence, for as long as the event repeats.

Invitations

The person who creates an event can invite other users to receive its reminders. Invitees get the same notifications without needing to find the event themselves. On Business and Enterprise plans, you can also pick email-only recipients who have no Lextree account; see Email-Only Reminder Recipients.

Recurrence vs. event templates

There are two ways to handle repetition:

  • A recurring event is one event that repeats on a regular schedule — a monthly board meeting, a weekly check-in.
  • An event template is a reusable, pre-filled event definition. Use templates when the same kind of event recurs across different records, or when a single obligation needs several events at different intervals (for example, patent maintenance reminders at 3.5, 7.5, and 11.5 years).

Event templates

Admins manage event templates in Settings → Calendar Event Templates. A template pre-fills the event name, default recipients, reminder schedule, and recurrence, so creating the event is quick and consistent. Templates can also include suggestion triggers that prompt the right people to create an event automatically — for example, a set number of days before a date field, or whenever a record is created or changed. See Event Templates for the admin configuration steps, Automation Setup for the full trigger configuration — guard conditions, and how it pairs with automatically filled fields and timeline states — and Automations for how those suggestions reach you and how to accept or decline them.

Events vs. workflows

Events are strictly date-based reminders — they don’t track whether anyone acted. When you need to track who did something and when, use a workflow (a workflow with a due date creates a linked event automatically). On a workflow-generated event, marked Workflow due date, you can still change the reminders from the Calendar, but its title, description, schedule, recurrence, and recipients come from the workflow. You can’t delete it or detach it on its own — it lives and dies with the workflow that created it.

Who can create and see events

  • Viewing an event requires access to the record’s module.
  • Creating or editing an event requires Editor access to that module. Viewer users can see events but not change them.

On Enterprise plans, an event follows its record: if the record is restricted to groups, only members of those groups and people with All records see it. Reminders still go to the people named on the event. See Access.

Search