The clinic in this walkthrough is fictional, and so are its dates. The task setup and the result screen are real ChatGPT screens from that test.
The mistakes that hurt in monthly clinic marketing are rarely technical. A closure date gets confirmed two days late. A revision request sits unread until the pop-up is already live. The desktop banner is checked carefully, and nobody looks at the mobile crop. A reminder that only says “marketing update” won’t catch any of these, because it doesn’t ask about any of them.
So I built the monthly checkpoint with ChatGPT Scheduled Tasks. I wanted to know whether a task that runs on its own could ask the right questions, mark what was still missing, and stay away from anything it shouldn’t touch. This is how I set it up, what the result looked like, and where it stopped being useful.
What a Scheduled Task actually does
A scheduled task is an instruction ChatGPT runs later, once or on a repeating schedule, and then notifies you about. You create it from the Scheduled page in the sidebar, or by asking in a chat. According to OpenAI’s Scheduled Tasks guide, tasks are available on Free, Go, Plus, Pro, Business, Enterprise, and Edu accounts, with limits on how many can be active at once. If Scheduled doesn’t appear in the desktop app, the web version of ChatGPT is the fallback.
The difference from a normal chat matters. A chat waits for you. A task comes to you, by push notification, email, or both, depending on what you choose in Settings > Notifications. For a checkpoint that is easy to forget, that is the whole point.
The task I set up
I chose the 20th of every month at 9:00 AM Seoul time. By the 20th, next month’s plans usually exist but aren’t final. There is still enough time for approvals, design revisions, and a separate mobile check before the 1st.
On the 20th of every month at 9:00 AM in Asia/Seoul, remind me to
prepare next month's clinic marketing update.
Ask me to confirm:
1. closure or reduced-hour dates
2. monthly event details and approved copy
3. desktop and mobile homepage pop-up images
4. customer message copy and send date
5. Google Business Profile holiday hours
If any item is missing, label it "Not confirmed" instead of
inventing a value. End with a short owner-and-deadline checklist.
Do not publish, send messages, or change business hours automatically.
Every line answers one of those failures. The five numbered items are the five places things slipped. The “Not confirmed” rule keeps a blank from turning into a guess. The last line draws the boundary: this task reminds and organizes. It never acts.


Field note: Read the confirmation screen before you trust the task. ChatGPT turns your sentence into a schedule, and the task screen is the only place you can see how it read that sentence. Check the day, the time, the time zone, and the next run time. Writing a time zone name like Asia/Seoul in the prompt, instead of “my time,” is what makes that check easy.
What the result surfaced

The result did what the prompt asked, and the way it did it is what made it useful. Every input I hadn’t supplied was labeled “Not confirmed” instead of filled in. Desktop and mobile creative appeared as two separate items, so the missing mobile crop showed up as its own blocker instead of hiding inside “pop-up images.” And the result said plainly that it had not published anything, messaged anyone, or changed business hours.
What it couldn’t do was just as clear. The task had no way of knowing whether a date was approved, whether a design was final, or whether the public listing was updated. It could only ask. Each checkpoint still needs a person and a piece of evidence:
| Checkpoint | What the task asks for | What a person still has to verify |
|---|---|---|
| Closure dates | Exact dates and hours | Final schedule sign-off |
| Event copy | Approved wording and terms | Brand and compliance review |
| Desktop pop-up | File version and link | Crop, text, and link check |
| Mobile pop-up | Separate mobile file | Readability at real phone size |
| Customer message | Final copy and send time | Approval before sending |
| Google Business Profile | Special hours | The public listing after saving |
Field note: “Not confirmed” is only as honest as the answers you give back. When the reminder arrives, it’s tempting to reply “done” to each item. Answer with the evidence instead: the file version, the approval message, a screenshot of the saved listing. A checklist full of “done” looks like the one full of “Not confirmed.” The difference is whether anyone could check it later.
Three patterns, three different risks
The monthly checkpoint is one of three ways to use tasks, and each needs a different kind of instruction. A one-time reminder is the simplest: you already know the action and the date, so the prompt just needs the exact time, the time zone, and what to check. A recurring checkpoint, like mine, needs a fixed checklist, a label for missing inputs, and a named owner. Without those, it becomes a notification you learn to ignore.
A monitoring task checks a source for changes and notifies you only when something relevant changes. That makes it the riskiest of the three. It needs a specific source, a baseline date, a rule for what counts as a real change, and an end condition. Even then, an alert is a lead to go check, not proof that something changed. I wouldn’t use one for anything legal, medical, financial, or urgent.
The formula I now use for all three looks like this:
Every [schedule + time zone], [action].
Use [input or source].
Return [format and length] for [audience].
Label [facts that must be verified] as "Not confirmed" if missing.
Notify me only when [condition]. Stop when [end condition].
Where tasks stop
A few limits shaped how I use this setup. The most important: a task created inside a ChatGPT Project can’t read that project’s files. OpenAI’s guide says so directly. So if your monthly brief lives in a project, the reminder won’t see it. The task has to ask you for the facts instead of finding them. If you want a place to keep that brief, my Projects vs Memory vs Temporary Chat comparison covers how I organize it.
Tasks can also pause on their own. That can happen when they’ve been inactive, when they need another action from you, or when the chat they belong to is deleted.
Field note: The pause rule is the one that catches people. Clearing out old chats is a normal habit, and deleting the chat that a task belongs to quietly pauses the task. Nothing warns you at the moment it matters. After you clean up your chat history, open the Scheduled page and make sure the monthly checkpoint is still active.
And a task is not an alarm system. For anything that truly can’t be missed, a normal calendar or a dedicated alert tool is still the right choice. The task’s job is to make the forgettable checks hard to forget.
FAQ
Are ChatGPT Scheduled Tasks free?
Eligible Free and Go accounts can use them, but with lower limits on active tasks than paid plans. Check OpenAI’s guide and your own Scheduled page for the current numbers.
Can a scheduled task use files from a ChatGPT Project?
No. A task created in a project can’t access the files stored in that project, so include the facts it needs in the task itself or have it ask you.
Why did my scheduled task stop running?
It may have paused after inactivity, because it needed another action from you, or because its chat was deleted. Open the Scheduled page to check and resume it.
The takeaway
A scheduled task didn’t make my monthly marketing update accurate. It made the gaps visible on the 20th instead of the 30th. That is a modest job, and it’s the right one for it. Start with one low-risk task, write the time zone and the stop rules into it, and read the first result as carefully as the last one.
