# Scheduling and reminders

Neo can create one-time reminders and recurring tasks when scheduling is available. A useful schedule makes the timing, timezone, action, and message unambiguous.

## One-time reminders

> Remind me on 22 August at 15:30 America/New_York to review the contract renewal and include the link from this conversation.

Absolute dates are safer than relative phrases for important reminders. If you say “tomorrow” or “in two hours,” confirm the interpreted date and time.

## Recurring tasks

> Every weekday at 09:00 Europe/London, prepare a five-bullet briefing from the approved sources and label it with the coverage date.

Define the recurrence, timezone, start date, end condition, and output. For monthly tasks, clarify behavior for dates that do not occur every month.

## Review before creating

A schedule should have:

- a clear name;
- exact timing and timezone;
- one-time or recurring status;
- a useful message or task definition;
- required inputs or approved sources;
- an owner or destination when relevant.

## Confirm the schedule

After creation, inspect the recorded timing and recurrence. A confirmation should distinguish the intended schedule from what was actually created.

## Manage recurring work

Review recurring tasks periodically. Update or disable automations whose owner, inputs, timing, or purpose has changed. Delete schedules that are no longer needed so outdated work does not continue indefinitely.

## Limits

A reminder is not proof that a later external action occurred. Scheduled work can also fail if permissions, connections, or source availability change. For critical obligations, keep an independent calendar or operational control.