Use routines so drafts are ready when you wake up

Up to now, your businesses move only when you're in the chair. Chapter 5 is about the hours you're not: evenings, weekends and the night. Routines let your team do planned work on a timetable and leave it ready for you.

What a routine is

A routine is a job a Bot picks up on a schedule, like every morning at six or every Friday afternoon, without you asking again. The key design choice is to have routines prepare, not act. They draft, check and organize. Sending, buying and publishing happen later, when you're there to say yes.

What belongs on the night shift

Good routine jobs happen regularly, follow roughly the same steps, and produce results that can wait for you. In the book's story: weekly research on what parents are searching for, the Friday email assembled on Wednesday night so the draft is waiting Thursday morning, a numbers summary on Sunday night, and the morning inbox sort.

The briefing Bot

After a week, the results are scattered across pages. So you add a briefing Bot that runs last each morning, reads every running page and writes one short briefing: what got done, what's waiting for approval, anything stuck or strange. It can read and summarize. It can't approve, send or spend.

Checklist

1. Go through your job cards and mark the regular, repeatable jobs.
2. Schedule them so drafts are ready before you start your day.
3. Order them like a relay: research, then writing and editing, then numbers, then the briefing last, with some slack between.
4. Add a standing rule to ask first before sending, posting, buying or deleting.
5. Keep one approval queue: a list of finished drafts kept by a manager or the briefing Bot.
6. After a week, read the briefings and fix the order where things show up late.

Why not approve at 3 a.m.

When a routine or another Bot asks for approval while you're away, that request can expire after a short while, and the action doesn't happen. That's a safe default, but it means a night shift shouldn't depend on approvals. Build it to leave finished drafts instead, and don't assume every send stops for approval on its own.