Scheduled task availability, exact timing, recurrence limits and event-triggered workflows depend on plan, app and workspace. Do not place passwords, account numbers or sensitive personal data in task titles or instructions.
1. Define one future outcome
Write the action in one sentence: remind me, send a daily summary, check a condition, or react to a supported event. Keep the task narrower than a normal open-ended chat.
2. Specify schedule and timezone
Give the date, recurrence and time zone when timing matters. For monitoring, define how often checking is useful and what condition is worth notifying you about.
3. Create the task and inspect the confirmation
After ChatGPT creates it, read the task card or Scheduled entry. Confirm the prompt, next run, recurrence and any conditions instead of assuming the natural-language request was interpreted perfectly.
4. Enable the right notification channel
Check Settings → Notifications and allow push or email as needed. On mobile, grant the operating-system notification permission before depending on a reminder.
5. Review, pause or delete stale tasks
Use Scheduled to edit the instruction, change cadence, pause a monitoring task or delete one you no longer need. Keep active tasks intentional so important notifications are not buried.
Create a recurring task that checks this condition every weekday at 9:00 AM in my local time. Notify me only when the condition is met. In the notification, include what changed, the evidence, and the date checked.
Scheduling without a timezone; asking a monitor to notify on every run; assuming a Project task can access every uploaded file; creating sensitive shared-task text; never testing notification permissions.
Finish check
The task has a precise instruction, known schedule or condition, a working notification channel and an obvious place where you can pause or edit it.