How do I build a complete AI workflow for one recurring task?

Watch the briefing

Watch the full video on YouTube

Full briefing transcript

The weekly community-room handover is a recurring job, not a single magic prompt. A neat draft can still invent a key collection or turn a tentative booking into a commitment. Build a small loop instead: safe input, structured draft, explicit checks, and an owner's decision before release. Our room, notes, and outputs are fictional.

The loop is an editorial workflow, not a tested guarantee of reliability or saved time. Our invented source notes cover the week beginning November thirtieth. The main room has a confirmed craft booking on Tuesday, six until eight. A Friday discussion booking is tentative, with time unconfirmed.

Eight folding chairs are in storage. The spare key has been requested, but collection is unconfirmed. A heating concern has been reported to the owner; no repair completion is recorded. The handover reader is next week's room coordinator.

First, prepare safe input. For this teaching version, we use invented room notes with no names, phone numbers, access codes, or private visitor records. In real work, use only information you are permitted to share and include what affects the handover. Give the notes a date and version so the draft can be checked against the right source.

Do not paste an entire private booking file when a permitted, narrower description would suffice. Second, request a draft with confirmed arrangements, pending items, and next checks. Preserve tentative status and unknown timing. Do not invent completed repairs, key collection, or booking confirmations, and do not contact anyone.

Our deliberately bad mock says Friday is confirmed at seven, the key is collected, and heating is repaired. Those polished claims fail because the input establishes none of them. A clear request does not remove the need to inspect output. Third, compare the corrected illustrative handover with every source fact.

Confirmed arrangements show Tuesday's craft booking, six until eight, and eight stored chairs. Pending items retain Friday's tentative booking and unknown time, unconfirmed key collection, and heating repair not recorded. Next checks ask the coordinator to confirm those unresolved matters with the responsible people. Check dates, numbers, status words, and whether the draft claimed any action occurred.

Finally, the owner decides whether the reviewed draft is ready for its intended recipients. A remaining uncertainty can be acceptable if clearly labeled and assigned for follow-up; it must not masquerade as a completed action. The draft does not itself authorize sending, changing bookings, or arranging repairs. Save the source version, prompt, reviewed text, and corrections.

When new facts arrive, update the source and repeat the affected checks before an authorized release. Use input, draft, checks, and owner decision as the repeatable loop. For this handover, dependability means keeping confirmed and unresolved work distinct and preserving the evidence behind the final message. Start small, test real cases when authorized, and revise the routine when new problems appear.

This completes the series' basic workflow: drafting assistance can organize the work, while a responsible person keeps judgment and meaningful action.