Build One Repeatable AI Routine

If an AI task helped once, you can make it easier to repeat by writing down what you supplied, what you asked for, and what you checked. You do not need to build an app to do that.

Choose something small and familiar: a weekly volunteer update, a meeting follow-up, or a first draft of a routine email. Your experience matters because you know what a useful result should contain.

Define the job in one sentence

Here is a workable example: “Turn my weekly project notes into a short update that I will check and send to the group.”

That statement identifies the input, output and person responsible for the final message. “Manage my entire workweek” leaves too many decisions unspecified.

If you have not yet found a useful task, begin with one everyday application of AI before trying to make it a routine.

Use the same input headings

For the weekly update, collect your notes under these headings:

• Completed: work that is actually finished.
• In progress: work still underway.
• Blocked: what cannot proceed and why.
• Help needed: the question or decision for the group.
• Confirmed owners and dates: who has agreed to what.

Write “none” or “not confirmed” where appropriate. Do not fill an empty section with guesses just to make the template look complete.

Save a prompt you can reuse

Turn the notes below into a group update of no more than 150 words. Use the headings Completed, In progress, Blocked, and Help needed. Include only facts in the notes. Preserve confirmed names and dates. Do not turn a proposed task into a commitment. Flag conflicting information or a missing deadline beneath the draft. Do not send the update.

Paste the current notes underneath it. Keep the template separate from last week’s information so an old date or completed task does not accidentally enter the new draft.

For workplace or client material, use an approved tool and include only information needed for the task. Do not assume a familiar prompt makes a new upload appropriate.

Test ordinary and awkward cases

The three fictional cases below let you check the same instructions without supplying personal notes. Copy the whole exercise into one new text chat, or read it here and compare each case with the worked answers.

Copy the complete three-case exercise

For each fictional case below, write a separate group update of no more than 150 words. Use the headings Completed, In progress, Blocked, and Help needed. Use only that case’s notes; do not mix cases. Preserve quantities, agreed owners and dates. Keep proposals, missing details and conflicting dates visible. Write “not stated” when the notes do not support a heading. Keep the note number beside each point so I can check the source. Return drafts in this chat only; do not send, schedule or change anything.

Case A — clear notes:
A1: Lee finished two draft flyers.
A2: Morgan agreed to choose one by Friday.
A3: Printing waits for Morgan’s choice.
A4: The group needs someone to bring a display stand; nobody has agreed.

Case B — missing details:
B1: Lee is still revising the flyer.
B2: No review date has been agreed.
B3: Printing waits for the final flyer.
B4: Nobody has agreed to handle printing.

Case C — conflicting dates:
C1: One note proposes a meeting on Tuesday at 10 a.m.
C2: Another note proposes the same meeting on Wednesday at 10 a.m.
C3: Neither time is confirmed.
C4: Nobody has agreed to check which date is intended.

Do not invent calendar dates, a time zone, a person or a deadline. A polished draft must not make an unresolved point look settled.

Check these three situations separately:

1. A normal week with clear tasks and dates.
2. A week with an unfinished task and no agreed deadline.
3. A week where two notes give different dates for the same event.

The draft should preserve the missing information in the second case and flag the disagreement in the third. If it quietly chooses a date, change the instructions or keep that part manual.

Check the real result every time. Reusing a prompt does not guarantee identical wording or error-free output.

Give the routine a clear finish

Before sending, compare the draft with your notes. Check each commitment, remove unnecessary personal information, and confirm the recipients. If another person uses the routine, write down who reviews and sends the result.

Over several uses, note the total time spent preparing, correcting and checking the update. Also ask whether readers understand it. A fast first draft that needs extensive repair may not be saving effort.

Automate only a step you understand

A saved prompt is a reusable instruction, not a scheduled process. Asking a chat to “do this every Friday” does not establish that a working automation exists.

If you later connect tools, define the trigger, access permissions, destination, cost and failure notification. Keep a review step before messages are sent until you have evidence that the process behaves appropriately. For now, a simple routine you can explain and check is a useful result.

Featured photograph by Aaron Burden on Unsplash.