📋 Lesson 5.3: Scheduled & Due-Date Commands, and Run Budgeting

Automating on a Clock: Scheduled Commands

A Rule waits for you to do something; a button waits for you to click; a scheduled command waits for a time. You set it once — "every Monday at 8am," "the first of every month" — and Butler runs the actions on that clock forever, whether you're at your desk or on a beach.

You'll find them in ⚙️ Automation → Calendar (Trello calls scheduled commands "Calendar commands" because they run on a calendar cadence). You can schedule:

• Daily — every day at a set time (e.g. a morning "sort my Today list").
• Weekly — a chosen day and time (e.g. Monday 8am reset, Friday 5pm archive).
• Monthly — a day of the month (e.g. the 1st: create this month's recurring cards).

Here's the workhorse weekly cleanup, shown in the scheduled-command mock:

And a Monday-morning "reset" that stages your week before you even open the board:

Due-Date Commands: Before, On & After

Due-date commands are a special, wonderfully useful flavor of scheduled automation: instead of a fixed clock, they fire relative to each card's due date. This is how you build reminders that actually land when they're useful — not a generic 9am ping, but "the day before this card is due."

Find them in ⚙️ Automation → Due Date. You choose an offset:

• Before the due date — "1 day before," "2 hours before" (reminders and prep).
• When the due date arrives — right at the deadline.
• After the due date — "1 day after," to flag things that slipped (overdue triage).

A gentle day-before reminder that also surfaces the card:

And an overdue-triage command that flags anything that slipped past its date:

Recurring Tasks That Recreate Themselves

One of the most-requested things in any task tool: "make this task come back every week." Trello has no single "repeat" checkbox on a card — instead you build the behavior with a scheduled command, which is more flexible once you see it. The trick is to have Butler create a fresh card on a cadence.

That single command replaces the chore of remembering, retyping, and re-checklisting a recurring task forever. The same pattern powers monthly invoices, quarterly reviews, a daily standup card — anything with a rhythm.

Run Budgeting: The Honest Math

Here's the part nobody explains clearly, so let's do it properly. Butler is free on every plan — but the volume of certain runs is metered. Get this straight and you'll never be surprised by a stalled automation.

What counts as a Workspace command run (and what doesn't)

• ✅ Counts: each time an automatic Rule fires. Each time a scheduled command runs. Each time a due-date command fires (once per qualifying card).
• 🆓 Effectively free: personal card/board button clicks. That's the loophole from Lesson 5.2 — routines you click yourself don't draw down the meter.

The monthly Workspace allowances, as of early 2026 (always confirm at trello.com/pricing):

Do the arithmetic — a worked example

Imagine a personal board on Free with these automations. Let's estimate a month (call it ~4.3 weeks):

• Weekly Friday cleanup (scheduled): 1 run/week × 4.3 ≈ 4 runs/mo.
• Monday reset (scheduled): ≈ 4 runs/mo.
• Recurring "Weekly review" card (scheduled): ≈ 4 runs/mo.
• "Move to Done" cleanup Rule: say you finish ~5 cards/day × ~22 workdays ≈ 110 runs/mo.
• Day-before due reminder (due-date, per card): say ~3 dated cards come due each week × 4.3 ≈ 13 runs/mo.

Total ≈ 4 + 4 + 4 + 110 + 13 = 135 runs/month. Comfortably under 250 — Free is genuinely fine for a personal board. Notice what dominates: the event Rule that fires on every finished card, not the tidy weekly schedules. That's the usual shape.

A Maintenance Routine That Runs Itself

Let's assemble everything from Module 5 into one calm, self-maintaining board. This is the payoff — a board that tidies, stages, reminds, and recurs on its own, using cheap schedules and free button clicks for the heavy lifting.

Behind that calm board:

• Monday 8am (scheduled): stage the week — move This-Week cards into play, drop a "pick your top 3" comment.
• Every Monday 7am (scheduled): recreate the recurring "Weekly review" card, due Friday, with its checklist.
• 1 day before due (due-date): label "due soon," bump to top — that yellow badge on the invoice card appeared on its own.
• Move-to-Done Rule (event): the "Book the flights" card got its green label and done badge automatically.
• 📥 Archive Done button (click, free): you clear the pile whenever you like, at zero run cost.

That whole system costs on the order of ~150 runs/month — well within Free. Your board now genuinely runs itself.

🎯 Project: A Monday Reset + a Due Reminder

You'll add the two time-based automations that most boards benefit from, then estimate what they cost you each month so budgeting stops being mysterious.

Scheduled command:
  Every Monday at 8:00 AM,
    sort list "Today" by due date (ascending),
    post comment "New week — pick your top 3."

Due-date command:
  1 day before a card is due,
    add the yellow "due soon" label,
    move the card to the top of its list.

Sample monthly cost:
  Monday reset:        1/wk  × 4.3  ≈   4 runs
  Due reminder:  ~4 cards/wk × 4.3  ≈  17 runs
  ------------------------------------------------
  Total                             ≈  21 runs  (well under 250)

Best Practices for Scheduled & Due-Date Commands

✅ Do's

• Batch recurring chores into schedules. One daily command that processes a whole list beats a Rule firing per card.
• Use due-date "before" offsets for prep, "after" for triage. A day-before nudge and a day-after flag cover most needs.
• Estimate before you build big. A ten-second "how many cards will this touch?" saves a month of surprises.
• Prefer buttons for anything you can time yourself — free runs, full control.

❌ Don'ts

• Don't run a heavy command hourly "just in case." Match the cadence to the real need — most maintenance is weekly, not hourly.
• Don't forget due-date commands fire per card. Fifteen cards due tomorrow = fifteen runs.
• Don't ignore the run log. If automations quietly stop, you've likely hit the cap — check usage first.
• Don't build a recurring card without a template. A blank recurring card is half the value; attach the checklist.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You've completed the automation module — the flagship of this course. You can now trigger Butler three ways: on events (Rules), on demand (buttons), and on time (scheduled and due-date commands). More importantly, you understand the economics: what costs a run, what's free, and how to keep a rich set of automations humming under a Free cap. Your board really does run itself now.

❓ Common Questions at This Stage

🔭 Looking Ahead

With automation mastered, Module 6 broadens your board's abilities: Power-Ups — the add-ons that bring calendars, card repeaters, voting, and integrations to Trello — and then wiring Trello into Slack, Google Drive, and GitHub. Same spirit as Butler: make the board do more of the work.

✅ Before the Next Lesson

• Keep your scheduled and due-date commands running and watch them fire over a week
• Tally your board's total monthly runs once, so budgeting feels concrete
• Write your Learning Journal entry — your full automation inventory and cost

📚 Additional Resources

• Scheduling Butler commands (Atlassian docs)
• Butler usage & command runs — how the meter works
• trello.com/pricing — current run limits (as of early 2026)