BlogHow-to

Routines that run themselves

Turn any task you've handed off once into a schedule: daily briefs, weekly screens, monthly sweeps, each ending in a report you can trust.

The renewal radar only protects you if someone runs it every Monday. And the Monday you skip, by an old law of office physics, is the Monday the biggest account's renewal goes quiet.

Recurring work has exactly one failure mode: remembering. Calendars remind, but they do not do, so the reminder becomes another task, the task competes with everything urgent, and "weekly" quietly becomes "when I think of it."

The cost is silent, too. Recurring work rarely fails loudly; it develops gaps, and nobody audits a gap.

From task to schedule

In Agent FM, any handoff you have run once can carry a schedule. Say the cadence in the ask itself, every morning before dispatch, every Tuesday at 9am, once a month before statements go out, and the task becomes a routine: same sources, same output, running without being remembered. The card reads Routine · Mondays 8am, and from then on what arrives is the result, not the obligation.

Watch the first scheduled run the way you watched the first manual one. After that, the report is your window: counts, flags, and what could not be checked, every time. If the first week's report runs long, tighten the ask; routines reward small edits.

Which tasks earn a schedule?

Three tests. The task has the same shape every time: same sources, same output, no meeting required to define it. The value lives in the exceptions: you want the three lanes that moved, not proof that eight were checked. And the judgment sits at the edges: thresholds decided up front, results acted on at the end, nothing in the middle that needs a human hand.

Briefs, sweeps, screens, logs, and reconciles all pass. One-off investigations do not, and that is fine; they stay one-offs. If you have done a task three times the same way, it probably qualifies.

Daily routines suit things that genuinely move every day: markets, queues, boards. Here is a freight desk's dawn check; what arrives is a few lines with the movers flagged.

Every morning at 6am, before dispatch, pull current spot rates for [lanes, e.g. our top 8 dry van and reefer lanes on the Lanes tab] from DAT and Truckstop. Log them in the rate history sheet and compare against the 7 day average. Flag any lane that moved more than [threshold, e.g. 5%] either way. Brief me in a few lines, biggest movers first. Flag any lane where the boards disagreed hard.
Use caseCheck our lanes on the boards before dispatch startsPull rates on our top lanes from DAT and Truckstop and brief me before dispatch.View →

Weekly routines suit pipelines: the sweep, the screen, the shortlist. This one turns Tuesday's applicant pile into a shortlist before you have opened it: a ranked list with evidence, instead of a stack of PDFs.

Every Tuesday at 9am, go through the week's applicants for [role, e.g. maintenance tech for the Cedar Ridge property] on Indeed and the Craigslist post. Screen each against the must-haves: [requirements, e.g. EPA cert, own tools, weekend rotation OK]. Shortlist who clears the bar into the hiring sheet with name, contact, and the evidence they showed. Don't contact anyone yet. Tell me how many you screened, how many made the shortlist, and flag any application you couldn't open.
Use caseScreen the week's hourly applicants into a shortlistScreen the [role] applicants on Indeed against our must-haves and shortlist the interviews.View →

Monthly routines suit the slow clocks: expirations, reconciliations, statements. Things that never feel urgent until the month you missed. Monthly is also the natural cadence for anything with a renewal date attached.

Once a month, sweep the roster tracker and verify every license and cert that expires within [window, e.g. 120 days], through Nursys and the state board sites. Update the tracker with the verified dates, then brief me: who lapses soonest, what's already in renewal, and who hasn't started. Tell me the total checked and flag any record you couldn't verify at the source.
Use caseWatch the roster for credentials about to lapseSweep the roster's licenses and certs and brief me on everything lapsing in [window].View →

The cadence ladder

Match the schedule to the speed of the thing being watched, not to your anxiety about it. Daily for what changes daily, weekly for pipelines and queues that fill on a workweek clock, monthly for expirations, reconciles, and anything tied to a statement cycle. A routine that runs too often becomes noise, and noise gets ignored, which is how monitoring dies in every office that ever bought a dashboard.

Start slower than you think you need, then tighten only when the brief proves too stale. Thresholds tune the same way, one sentence at a time: raise them until the routine stops crying wolf. A routine you trust is one whose silence means something.

Control doesn't loosen

A routine never gains authority the one-off did not have. Read-only stays read-only on the hundredth run, drafts still wait for your OK, and every run ends in a report that says what happened and what could not be checked. You can pause a routine, edit its ask, or open any run and watch it work. A schedule is a convenience you granted, not a leash you handed over.

See also: How to set up a morning brief you actually read for what the daily kind should contain, and How to choose work automation you can trust for the questions to ask before scheduling anything.

The quiet luxury of a routine is that you stop thinking about the task and start reading its results. That is the whole trade, and it is a good one. Choose the recurring task you resent most. Get early access on macOS or Windows; when access opens, make it your first routine.

Related