> ## 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. # Routines: Work That Runs Without You Asking > Routines are standing instructions Amy runs on a schedule: the morning briefing, the Monday pipeline review, the monthly market digest. Describe the outcome once and it arrives on time, in your channel, from then on. Routines A routine is work you'd otherwise ask for again and again. 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 routine is delegation you only have to do once. ## What a routine is A routine breaks down multi-step tasks into smaller tasks 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 routines 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 routine, breaks the work into steps, sets the cadence and your timezone, and adds a step that delivers the result to your channel. If a routine 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 routine 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 routine appears under your live routines page. 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 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 * **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 routine can't take an action you didn't intend while you're not watching. Routines that only read and report (briefings, drafts, digests, reviews) run start to finish on their own. Routines 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 routine 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 routine that waits in Review until you approve or discard it. Nothing leaves your account without your approval. * **Test before it's live.** Run a routine as a test and see the output before setting the routine 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 routine runs for exactly as long as you want it to. Routines are personal by default. A routine 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 Routines in your workspace and use **Create Routine** to build one in a chat panel without leaving the page. ## Managing your routines Everything you've built lives in one place, split three ways. Routines running on their schedule. Open one to read its steps, edit them, change the cadence, or pause it. Routines 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 routine before you add another. You can manage routines from chat too, in any channel: ```text title="Copy and send to Amy" wrap theme={null} Show me my routines. ``` ```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 routine goes live, especially the first time it will send or write something. * If a routine 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 is a routine waiting to happen. ## Recipes you can make recurring Every [recipe](/recipes) below works as a one-off, and works better on a schedule. Open one and use the prompt in its **Make it a routine** section, or just tell Amy the recipe name and the cadence you want. ### Daily Every weekday morning, before you open your inbox. Each morning, a briefing on everyone you're meeting that day. Daily news, signals, and leadership moves across your watchlist. End of day, follow-ups drafted for every meeting you had. A first-pass read on anything new that landed in your pipeline. A short read on the channels you couldn't follow live. ### Weekly Monday morning: what moved, what stalled, what needs you. What your competitive set shipped, hired for, and said publicly. Missing fields found and filled before they become a problem. Friday afternoon, a ready-to-send summary of the week. Who moved roles this week, and what it means for you. What you committed to and haven't closed yet. Who raised, how much, and from whom, in your sectors. The companies growing fast enough to need you. ### Monthly Who you've gone quiet on, and a reason to reach out. A refreshed read on a market you need to stay current in. [View all recipes →](/recipes) ## Next steps Ready-made workflows you can schedule in seconds. Connect the tools your routines need before you activate them. Choose where your routines deliver: email, Slack, or Telegram. Store the preferences and formats your routines should follow. *** Want a hand turning your recurring work into routines? Book a free session with an Amy expert and we'll build the first few with you.