Set up recurring tasks and calendar events so weekly check-ins, monthly touches, and annual reviews happen without you having to remember them.
This lesson explains the recent calendar and task update that lets users create recurring tasks and recurring events. It highlights the key difference between tasks and events: tasks have one due date and time and do not check for conflicts, while events check for scheduling conflicts.
Open a contact, add a task, and toggle 'Recurring'. Choose the interval and end condition. That's it.
Events work the same way and appear on your connected calendar. Use them for standing partner meetings, weekly team huddles, or quarterly reviews.
This lesson covers a recent improvement to the calendar and task experience: the ability to create recurring tasks and recurring events. Instead of manually entering the same reminder or appointment over and over, you can create it once, turn on recurrence, choose the repeat timing, title it, and save it. The item then appears on the calendar according to the schedule you selected.
The update applies to both tasks and events, but the transcript makes an important distinction between the two. A task has a single due date and time. It is useful for a reminder or action item that needs to be completed, but it does not check for conflicts with scheduled events. An event, by contrast, is part of the schedule and will check for conflicting schedules. That difference matters when deciding whether the item you are adding should be treated as a to-do or as a calendar appointment.
The process is designed to be simple. You start by creating either an event or a task. If the item needs to repeat, you toggle recurrence on. Then you select when it should repeat, such as the first day of the month, a custom schedule, or every weekday from Monday through Friday. After you add a title and save, the recurring task or event is added to your calendar.
Recurring work is common in mortgage and borrower management workflows. Even when the transcript does not list specific use cases, the value of recurrence is clear: many reminders and meetings happen on a repeated schedule. Without recurrence, users would need to create the same task or event multiple times. That increases manual work and makes it easier to forget an instance or create inconsistent entries.
Recurring tasks help when the item is an action that needs attention at a due date and time. Because tasks do not conflict with scheduled events, they can sit on the calendar as reminders without blocking appointment availability. This makes them different from events, which are intended to interact with the calendar schedule and check for conflicts.
Recurring events matter when the item is truly a scheduled calendar event. Since events check for conflicting schedules, they are better suited for time that should be protected or reviewed against other events. The transcript specifically calls out this scheduling behavior, so choosing the right type of item is the most important decision before setting up recurrence.
The improvement also matters because it is available in more than one place. The transcript notes that events and tasks can be configured in the calendar or in individual borrower files. That gives users flexibility. If you are already working in the calendar, you can create the item there. If you are working in a borrower file, you can configure the task or event directly from that context.
The workflow begins with the creation of a task or event. The system treats these as related but different calendar items. A task is tied to one due date and time. It is not described as checking availability or creating conflicts with events. An event does check for conflicting schedules, which means it is the better choice when calendar availability matters.
Once you are in the create flow, recurrence is controlled by a toggle. Turning the toggle on tells the system that this is not a one-time task or event. After recurrence is enabled, you choose when the item should repeat. The transcript mentions several recurrence options: first day of the month, custom, and every weekday Monday through Friday. These examples show that the tool supports both common schedules and a custom option when the repeat pattern needs to be more specific.
After selecting the repeat pattern, you title the item and save it. Saving completes the setup and places the recurring task or event on the calendar. In the example described in the transcript, choosing a daily or weekday-style pattern results in the task happening every day on the calendar.
The same general configuration is available from two areas: the calendar and individual borrower files. The transcript does not describe different behavior between those locations, so the core idea is that both entry points allow users to configure tasks and events.
1. Decide whether the item is a task or an event. If it is an action item with a due date and time, create a task. If it is a scheduled event that should check for conflicts, create an event.
2. Open the area where you want to create it. You can start from the calendar, or you can configure tasks and events from an individual borrower file.
3. Choose to create a new event or a new task. This puts you into the creation screen for that item type.
4. Turn on the recurring option. The transcript describes this as a toggle. If the item should repeat, toggle recurrence on before saving.
5. Select the recurrence timing. Pick the schedule that matches the need, such as the first day of the month, a custom pattern, or every weekday from Monday through Friday.
6. Add a clear title. The title should make it easy to recognize the task or event when it appears on the calendar.
7. Save the item. Once saved, the recurring task or event will appear on the calendar according to the schedule you selected.
8. Review the calendar. After saving, confirm that the recurring item is showing as expected, especially if you selected a daily, weekday, monthly, or custom schedule.
Start by choosing the correct item type. This is the most important best practice because tasks and events behave differently. A task has a due date and time, but it will not conflict with scheduled events. An event checks for conflicting schedules. If the item represents something that should be protected on the calendar, create an event. If it is simply a reminder or to-do item, a task may be the better fit.
Use recurrence only when the item truly repeats. A recurring option is helpful, but it should match the real workflow. If something only needs to happen once, leave recurrence off. If it happens every weekday, use the weekday option. If it happens on the first day of the month, select that pattern. If the repeat schedule is less standard, use the custom option mentioned in the lesson.
Give the task or event a title that is easy to understand at a glance. Since the item will appear repeatedly, the title should be specific enough that you know what it refers to without opening it. A clear title helps keep the calendar usable, especially when repeated items begin to accumulate.
When creating an event, be mindful that it checks for conflicts. That is a benefit, but it also means the event should be created only when the time needs to be treated as a scheduled calendar commitment. For reminders that do not need to block time or check the schedule, use a task instead.
Finally, use the entry point that fits your workflow. If you are planning your day or week, the calendar is a natural place to create recurring items. If you are already inside a borrower file and need to add a task or event connected to that borrower context, configure it there.
One common mistake is treating tasks and events as interchangeable. They are related, but the transcript makes the difference clear. Tasks have a due date and time and do not conflict with scheduled events. Events check for conflicting schedules. Choosing the wrong type can make the calendar less accurate.
Another mistake is forgetting to turn on recurrence. If you create a task or event but do not toggle recurrence on, the item will be created as a one-time entry rather than a repeating one.
Users may also select a repeat pattern too quickly. For example, every weekday Monday through Friday is different from a monthly option like the first day of the month. If the schedule does not match the real need, the calendar will fill with entries on the wrong days.
A final mistake is using vague titles. A recurring item appears multiple times, so a generic title can become confusing. Even though the transcript only says to title it and save it, a clear title is important for everyday use.
Suppose you need an action item to appear on your calendar every weekday. You would start by creating a task, since the transcript describes tasks as items with a single due date and time that do not conflict with scheduled events. In the creation screen, you would turn on the recurring toggle. Then you would choose the every weekday Monday through Friday option. After that, you would add a title and save the task. The task would then appear on your calendar according to that weekday schedule.
If instead you are creating a repeating appointment that should be checked against the existing schedule, you would create an event. You would again turn on the recurring toggle, choose the repeat timing, give it a title, and save. Because it is an event, it checks for conflicting schedules.
The same idea applies whether you start from the calendar or from an individual borrower file. The transcript confirms that both events and tasks can be configured in those places.
The update adds a simple way to create recurring tasks and recurring events. The key is to choose the right type of item first. Use a task for a due-date-based action item that will not conflict with scheduled events. Use an event when the item should check for calendar conflicts.
To create recurrence, start a new task or event, turn on the recurring toggle, select the repeat timing, add a title, and save. Options shown in the lesson include first day of the month, custom timing, and every weekday Monday through Friday. You can configure these items from the calendar or from individual borrower files, making the feature easy to use wherever you are working.
Decide whether you need a task or an event. A task has a single due date and time and will not conflict with scheduled events. An event checks for conflicting schedules.
Start creating the item from the calendar or from an individual borrower file, depending on where you are working.
Use the recurring toggle to make the task or event repeat instead of creating it as a one-time item.
Choose the schedule that fits the item, such as the first day of the month, a custom option, or every weekday Monday through Friday.
Enter a clear title so the recurring task or event is easy to recognize when it appears on the calendar.
Save the task or event to add it to the calendar on the recurring schedule you selected.
Review the calendar to make sure the recurring item is showing on the expected days and times.
The lesson covers a recent improvement to the calendar and tasks that allows users to create recurring tasks and recurring events.
A task has a single due date and time and does not conflict with scheduled events. An event checks for conflicting schedules.
When creating the task or event, turn on the recurring toggle, select when it should repeat, add a title, and save it.
The transcript mentions the first day of the month, a custom option, and every weekday Monday through Friday.
Yes. The lesson states that events and tasks can be configured in the calendar.
Yes. The lesson states that events and tasks can also be configured in individual borrower files.
No. The transcript explains that tasks have a single due date and time and will not conflict with scheduled events.
Use an event when the item is a scheduled calendar item that should check for conflicting schedules.
[00:00] The next thing I wanted to go over with you guys is the most recent improvement we've done to the calendar and the tasks. [00:10] So you can come in to create an event or a task. The primary difference being a task is they have a single due date and time. [00:20] They won't conflict with scheduled events, whereas events will check for conflicting schedules. [00:30] So if you need to create a recurring task or recurring event, come in here, just toggle it on, select when you want that to go, first day of the month, custom, every weekday, Monday through Friday. [00:43] You can come in here, title it, and save it, and then you've got your task happening every day on your calendar. [00:53] So that's the most recent update that I wanted to go over with you guys is, again, the events and the tasks. [01:02] You can configure those all in the calendar or in the individual borrower part and files. So that's what I wanted to go over. Thanks, everyone.