> ## Documentation Index > Fetch the complete documentation index at: https://oximy.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Scheduled work > Run a thread on a recurring schedule without starting it by hand. A schedule runs a skill on its own, on a cadence you set or when something happens. Use it for work that repeats: a weekly report, a daily check, a monthly cleanup. This page covers setting one up and what to expect once it's running. ## Create a schedule Pick the skill the schedule should run. The skill carries the instructions; the schedule just decides when to run it. Decide what starts the run: a time you set, or an event that happens elsewhere. See below for both. Add a short prompt describing what you want done on each run. This is where you say anything specific to this schedule that the skill itself doesn't already cover. Give the schedule a name that tells you and your teammates what it's for at a glance. Toggle notify to hear about each run as it finishes, instead of checking back later. ## Time-based and event-based triggers A schedule can start on a **time-based** trigger or an **event-based** trigger. * **Time-based**: pick a cadence (every weekday, daily, weekly, monthly, or custom), a day, and a time. The schedule runs on that clock, on its own. * **Event-based**: the run starts when a tracked event occurs, instead of at a fixed time. Use this when the work should happen in response to something, not on a timer. ## Require approval before each run Turn on **Require approval before each run** if you want to review the run before it goes out, every time. With it on, the schedule prepares the run and waits for your sign-off instead of sending it automatically. Leave it off and each run completes on its own, on the cadence or event you set. ## Where to go next How admins oversee and control recurring scheduled work across the workspace. Reusable instructions a schedule runs on each trigger.