Download text

Try it in Mement

  1. Open the record’s editor and expand Date & Time.
  2. Choose the calendar mode and the starting date or time.
  3. Open Repeat and choose a useful preset or Custom. Configure its interval, calendar position, or available By item trigger.
  4. Add an end date when the series has a known finish, then inspect the schedule summary and save.
  5. When handling repeated work, read whether an action concerns one occurrence or all occurrences.

Translate a routine into a rule

For a weekly report, create a Task, choose its first scheduled day and useful reminder time, then select a weekly rule. Presets also cover daily, weekdays, weekends, every two weeks, monthly, quarterly, every six months, and yearly repetition. Use Custom when the pattern needs more detail.

Tasks, Lists, Projects, and Areas support calendar repetition. A repeating List can group checks you perform again; a repeating Project or Area retains its contained structure. Choose the type that reflects what you will repeat, then inspect its children before applying a container-wide action.

You can also receive a recurrence suggestion from a Task’s title when no rule is selected. Applying it sets the proposed recurrence and a scheduling baseline. Review those values just as you would after entering the rule manually.

Use custom intervals and positions

Custom calendar rules support intervals in hours, days, weeks, months, and years. If the hourly choice is unavailable, check whether several reminder times are selected. For example, choose an interval of two weeks and select specific days, such as Monday and Thursday, or repeat a payment monthly on its intended day.

You can also choose a position within a larger calendar period and count from its beginning or end. For example, repeat on the last day of each month or on chosen days in a particular week of that month. The second week of a month and the second Monday of a month can fall on different dates; read the rule summary to check which one you selected.

In the Gregorian calendar, a rule for the 31st has no occurrence in a month without a 31st; the next valid month supplies the next matching date. The website’s recurrence example illustrates simple date patterns; the app’s custom editor also offers the richer rules described here.

An end date limits how far the repeated plan continues. For a temporary course or project, set that finish rather than leaving the series indefinite. Reopen the saved record to verify the interval, days of the week or day of the month, and ending condition.

Check the Solar or Lunar calendar mode before choosing the date. Solar is Gregorian and Lunar is Hebrew; their months and boundaries differ. The calendar guide explains the selector and Habit period rules in more detail.

Custom repeat hides the unit selector when there is only one choice. Direction is hidden for hours and Solar months; Lunar months retain From start/From end.

Let another Task’s event cue the reminder

Task editors also offer By item in custom recurrence. Choose whether another Task’s creation or completion should trigger the rule. You can narrow the event by text, date, tags, place name, priority, or, for completion, a particular source Task. All or Any controls how the active conditions combine.

For example, configure “Check for a reply” to respond when you complete the selected “Send the quote” Task. A matching event schedules a reminder for the existing active target Task. It does not create another Task or complete the follow-up for you. Use a calendar rule when the reminder should follow dates rather than another Task’s event.

Distinguish this occurrence from the series

A recurring Task appears as repeated work while remaining governed by its recurrence rule. Mark the work you have finished done, and read the recurrence-specific actions before deleting anything. Delete only occurrence and Delete all occurrences affect different amounts of work.

If one meeting is cancelled but future meetings remain, use the action for that occurrence instead of deleting the series. If the routine itself has ended, inspect the rule or choose the series-wide action that matches your intention. In a repeated container, also review its contained records because normal hierarchy actions can cascade.

Choose a Habit when you want to measure behavior

A repeated Task works for a deliverable such as “Send the weekly report”. A Habit works for behavior with a tracking goal and history, such as reading a target number of pages in a week or limiting daily caffeine.

Habits have their own schedule, goal period, entries, and reminders. You can use repeated Tasks and Habits together; a Task’s recurrence rule does not configure a Habit’s rhythm. After travelling, review important timed reminders and the relevant calendar instead of assuming every kind of schedule shifts identically.

The Habit editor also has recurrence presets and custom calendar rules, including selected days of the week and positions counted from the start or end of a period. Set these alongside the Habit’s goal period and up to five reminder times. Its setup guide walks through the controls and examples; the By item mode described above belongs to Task editors.

Before you finish

  • The starting schedule, interval, and weekday or month day express the intended pattern.
  • Any end date matches when the routine should stop.
  • You checked whether a completion or deletion action affects an occurrence or a whole container or series.

Continue exploring