Why your scheduled AI task has no memory

Written By Becca Hinchman

You spend an hour teaching an AI agent about your job. Your clients, your busy season, the way you name your files, the thing you always forget on Tuesdays. It gets it. It's SO good.


Then you set that same work up as a Scheduled Task that runs every Monday at 6am. Monday comes. The output is generic. It asks you a question you already answered. It names a file that doesn't exist.


Nothing is broken. You just ran into the single most important thing to understand about automating anything with AI, and almost nobody explains it up front.

Every scheduled task run is a stranger

A chat and a scheduled task are two different things, even when they're the same tool.


In a chat, the conversation is the memory. Everything you said thirty minutes ago is still sitting right there.


A scheduled task doesn't get that. Every run starts as a brand new session with no memory of anything you have ever discussed. It knows two things and only two things: what is written in the prompt, and what it can read in the files and accounts you connected.


If it isn't in the prompt or in a file, it does not exist.

The test that fixes it

Write the Scheduled Task prompt as if you're explaining the job to a competent stranger who has never met you and never will.


Not a dumb stranger. A sharp one. Someone who will do excellent work the moment they know what you know, and who cannot ask you a single follow up question.


That means the prompt carries all of it:


  • The actual name of the calendar. Not "my calendar," because you have four.

  • The actual name of the board, the doc, the folder.

  • What counts as normal. "A quiet week" means nothing. "Fewer than three booked sessions" means something.

  • What to skip, and why.

  • What to do when something is missing or broken, not just what to do when everything works.


Here's the difference in one line.


What doesn't work: "Check my calendar for next month and build me a content plan."


What works: "Read the Photo Editing and Conference Schedule calendars for the next 30 days. Read the Photo Editing board for open cards. Build a content plan where every piece does one of three jobs: shows work I'm actually doing, answers a question clients ask before booking, or sells what I need booked six weeks out. If a shoot date is missing from a card, flag it instead of guessing."


The second one is longer. That's the whole point. You are paying in words ONCE so you don't pay in disappointment every Monday & have to start from scratch over and over again.

The other half: give it something to read

Some things are too long to live in a prompt, and some things change every week. Those go in a file.


I keep a running notes doc. Anything I want my scheduled tasks to know about goes in it. New pricing, a client situation, a decision I made, a thing I learned. Then the prompt names that doc directly and tells the task to read it first.


Now I'm not rewriting prompts every time something changes. I'm updating one document, and every task that reads it gets smarter at the same time.


That's the actual system. Not a clever prompt. A prompt that knows where to look for answers and clarity.

What to do this week

Open the one automation you set up and were disappointed by. Read the prompt out loud, pretending you have never met yourself.


Every time you hit a spot where you'd have to ask a question, that's the gap. Fill it. Run it again.


Most "AI doesn't work for me" is really "AI didn't know what it needed to know," and that one is fixable in about ten to fifteen minutes.


That example above is one prompt I updated with clarity. I have a whole system built this way, and it is about to open. Get on the waitlist at https://beccapaige.com/playbook


Becca Hinchman