Six lines to write into the brief for a recurring data pull (source, period, fields, what to do when the source changes, output name and a sanity range) so later runs stay comparable with the first.
A three-stage plan for checking a routine (everything, a sample, then the signals), with written rules for what counts as a clean run and what sends the routine back a stage.
A five-rung ladder for following up on replies you are waiting for, with dates, reasons and a clear stopping point, plus what to keep for yourself when you hand it off.
Five habits that make a missed scheduled routine visible: a stated due time, a result every run, a count at the top, one named person who notices and a plan for when it is late.
A six-step checklist for stopping a recurring job you no longer need: announce a date, pause instead of delete, revoke its access and leave a short note for whoever finds the archive.
What to put in an away note for work that keeps moving while you are gone: what keeps running, what pauses, what can be decided without you, what must wait, and when you will look at the results.
Five questions for scheduling a recurring job backwards from when you need the result: where you will look, when you will review it, how long it runs, when inputs settle, and when to revisit the schedule.
Why the first thing to delegate should be a boring, recurring chore with a clear finish line, and a five-step order for setting it up before you schedule it.