> ## Documentation Index > Fetch the complete documentation index at: https://docs.amy.vc/llms.txt > Use this file to discover all available pages before exploring further. # Scheduled Tasks: Work That Runs Without You Asking > A scheduled task is a task Amy runs on a cadence you set: the morning briefing, the Monday pipeline review, the quarterly market digest. Describe the outcome once and it arrives on time, in your channel, from then on. Scheduled tasks A task is a piece of work you hand to Amy. A scheduled task is that same work set to a cadence: daily, weekly, monthly, quarterly, or a pattern of your own. Describe it to Amy once, tell her when you want it, and she builds it, schedules it, and delivers the result to your channel from then on. Asking Amy for something is delegation. A scheduled task is delegation you only have to do once. ## What a scheduled task is A scheduled task breaks multi-step work into smaller steps that run on a recurring basis. Amy writes the steps in plain language, each one feeding the next, ending with a step that delivers the finished result to you. You can read every step, edit any of them, change the schedule, or pause the whole thing. Nothing runs that you haven't seen. ## How it works You build scheduled tasks by talking to Amy, the same way you'd brief a colleague. There's no builder to learn and no scheduling syntax to write. Tell Amy what you want and when you want it. She recognises a recurring request and starts building. She names the task, breaks the work into steps, sets the cadence and your timezone, and adds a step that delivers the result to your channel. If a task needs a tool you haven't connected, Amy saves it as a draft and tells you exactly what's missing instead of activating something that would fail. Before anything goes live, the task is reviewed for actions you might not have intended. Low-risk work passes straight through. Anything high risk is held until you've reviewed and confirmed the intended action. Amy confirms the schedule and a summary back to you in chat, and the task appears under your live scheduled tasks. Each run does the work and delivers the result to your channel. Every run is logged so you can see what happened and how many [credits](/pricing) were consumed. ## Schedules You set the schedule in plain language. Amy handles the rest. * **Daily.** Every day, or weekdays only if you give Amy the weekend off * **Weekly.** A named day of the week * **Bi-weekly.** Every other week * **Monthly.** A date each month * **Quarterly.** Once a quarter, for the work you review on a longer cycle * **Custom.** Any pattern the presets don't cover ## Safety checks before anything is sent You stay the decision-maker. Amy never sends, writes, or changes anything on your behalf without your approval, so a scheduled task can't take an action you didn't intend while you're not watching. Tasks that only read and report (briefings, drafts, digests, reviews) run start to finish on their own. Tasks that change something (sending an email, writing to your CRM) are held for your final review before running autonomously. * **Checked before it goes live.** Every scheduled task is reviewed for actions you might not have intended. Anything high risk is blocked until you've reviewed and confirmed the intended action. * **Approved on every run.** A step that sends or writes produces a draft that waits in Review until you approve or discard it. Nothing leaves your account without your approval. * **Test before it's live.** Run a task as a test and see the output before setting it live. * **Run it on demand.** Press run at any time and watch the run progress rather than wondering whether it worked. * **Pause or delete, any time.** A scheduled task runs for exactly as long as you want it to. Scheduled tasks are personal by default. A task you build runs on your account, with your connections, and delivers to you. ## Getting started Describe the work and the schedule in one message. Amy takes it from there. ```text title="Copy and send to Amy" wrap theme={null} Every weekday at 8am, send me a briefing of my inbox priorities, my meetings for the day, and anything still open from yesterday. Deliver it to [Slack, email, or Telegram]. ``` ```text title="Copy and send to Amy" wrap theme={null} Every Monday at 9am, review my open deals in my CRM, flag anything that hasn't moved in two weeks, and send me a summary with what needs a nudge. ``` ```text title="Copy and send to Amy" wrap theme={null} On the first of every month, research the funding rounds and leadership moves in [your sector] and send me a digest. ``` You can also open Scheduled tasks in your workspace and create one in a chat panel without leaving the page. ## Managing your scheduled tasks Everything you've built lives in one place, split three ways. Tasks running on their schedule. Open one to read its steps, edit them, change the cadence, or pause it. Tasks you started and didn't finish, or ones waiting on a connection. Reopen a draft and the conversation picks up where you left it. Every run, what it produced, and the credits it used, so you can see the cost of a task before you add another. You can manage scheduled tasks from chat too, in any channel: ```text title="Copy and send to Amy" wrap theme={null} Show me my scheduled tasks. ``` ```text title="Copy and send to Amy" wrap theme={null} Pause my Monday pipeline review. ``` ```text title="Copy and send to Amy" wrap theme={null} Change my morning briefing to 7:30am and add my calendar for the day. ``` ## Pro tips * Say where you want it delivered. If you don't, Amy defaults to email. * Start with one morning briefing. Add reviews and digests once you've seen what a good one looks like. * Ask for a test run before a task goes live, especially the first time it will send or write something. * If a task lands as a draft, it's almost always a missing connection. Connect the tool and ask Amy to activate it. * Anything you've asked Amy for twice belongs on a schedule. ## Tasks you can put on a schedule Sixteen ready-made tasks in the library work as one-offs and work better on a schedule, grouped by the cadence that suits them: daily briefings and prep, weekly reviews and digests, monthly and quarterly deep dives. Open one and use the prompt in its **Put it on a schedule** section, or just tell Amy the task name and the cadence you want. Daily, weekly, monthly, and quarterly, with what each one needs connected. ## Next steps Ready-made tasks you can schedule in seconds, and the knowledge to go with them. Store the preferences and formats your scheduled tasks should follow. Connect the tools your scheduled tasks need before you activate them. Choose where your scheduled tasks deliver: email, Slack, or Telegram. *** Want a hand putting your recurring work on a schedule? Book a free session with an Amy expert and we'll build the first few with you.