From manual to autopilot: promoting rules with confidence

There’s a delicate moment in every automation: the point of taking your hands off the wheel. At first you run the rule yourself, check the result, and sleep easy. But that wasn’t the goal — the goal was the folder tidying itself, without you. The question is: when can you trust it? The answer isn’t a date on the calendar; it’s a journey with three clearly marked stops. This guide walks the promotion of a rule from manual testing to full real-time autopilot, using the exact labels of the three triggers, so you climb one step at a time — never a leap in the dark.

The trigger is the rule’s “when”#

Every rule answers three questions: when it acts, which files it acts on, and what it does. The first — the when — is the trigger, and you pick one per rule on the When to run step (step 3 of the wizard), in a selector with three options. Those options define how much autonomy the rule has. And the secret to a calm promotion is simple: climb one trigger at a time, earning trust at each level before moving to the next.

Stop 1 — Manual: the rule that acts only when you say#

The exact label is “Only when I say (manual)”. Every new rule is born this way, and it’s no accident: it’s the safest trigger there is. The rule sits stored, quiet, and does nothing until you click “Run now”. Nothing happens behind your back.

This is where every test should start. Build the rule, click “Simulate effect”, and read the preview — “Preview — nothing is actually changed” — to see, line by line, what would happen. Matches? Click “Run now” and watch the real application. Do this a few times, on different days, with different files landing in the folder. Each clean run — where the result is exactly what you expected — is a vote of confidence the rule keeps banking.

How many runs? There’s no magic number. The yardstick is your own peace of mind: once you already know, by heart, what the rule will do before you click, it’s ready for the next step.

Stop 2 — Periodic: the rule that works on a schedule#

The exact label is “Every so often (periodic)”. This is the perfect middle ground between manual and real time. The rule starts running on its own every N minutes — you set the interval in the “Every [N] minutes (and once when the app opens)” field — and also once every time you open the app. The scheduling is remembered between sessions: closing and reopening the program doesn’t reset the clock.

Why promote to periodic before real time? Because it gives you autonomy without haste. The folder tidies itself, but in spaced-out waves, which leaves you plenty of time to notice anything odd between one run and the next. It’s the ideal trigger for routine cleanups: “every hour, gather the loose PDFs in Documents/PDFs”, “once a day, send to the Recycle Bin whatever has been in Downloads for more than 90 days”. Nothing that needs to happen the very instant it arrives — it just needs to happen regularly.

To promote, just edit the rule, open the When to run step, and switch from “Only when I say (manual)” to “Every so often (periodic)”. Let it run like that for a few days. If it keeps getting things right on its own, you’ve got proof the rule can handle autonomy.

Stop 3 — Real time: the rule that acts on the spot#

The exact label is “Automatically, when a file arrives (real time)”. This is the top of the ladder — the rule watches the folder and acts the instant a file lands in it. It’s the trigger that makes Downloads organize itself while you download things, with no wait at all. It’s the closest thing to Hazel’s “magic” on the Mac, which we cover in the post is there a Hazel for Windows.

Because it acts immediately, it’s the trigger that deserves the most accumulated trust — which is why it’s last on the journey. If you got here with the rule having succeeded on manual and periodic, real time is just formalizing a trust that already exists. A quiet safeguard keeps working for you: batches that are too large wait for you to apply them manually, for safety — the automatic side prefers not to do a lot at once without you watching. So real time handles the everyday flow and leaves the avalanches for your review.

And, as always, every automatic action shows the “🤖 Autopilot acted” notice with the “Undo” button beside it. Even at the top of the ladder, the safety net stays spread out below.

The journey, in short#

1. Manual — “Only when I say (manual)”. Build, simulate, run by hand, check. Bank clean runs.
2. Periodic — “Every so often (periodic)”. Let it work on a schedule, with room to observe.
3. Real time — “Automatically, when a file arrives (real time)”. Let it truly fly, with “Undo” always at hand.

You don’t have to pass through all three — for Downloads, many people jump straight from manual to real time as soon as they trust it. Periodic is the bridge for those who prefer to climb slowly. What matters is the order: each step only after the previous one has proven the rule is trustworthy.

Before you promote, a quick checklist#

• Have you already simulated the rule and did the preview match your expectation?
• Has the rule run a few times on manual without surprises?
• Is the destination right (check placeholders like {year} and {month-name} in the simulation)?
• Do you know where to undo if you need to (the Run history and the autopilot toast)?

Four yeses? Go ahead and promote. If this is your first contact with the build, simulate, and undo cycle, it’s worth reading the anatomy of a perfect file rule first.