The app that runs while nobody is watching

Some of the most useful software a business can have has no screen at all. It wakes at six in the morning, does one job, and goes back to sleep. Nobody logs into it, nobody clicks anything, and when it works, nobody thinks about it.

These are scheduled tasks, and they are the least glamorous and often the best value automation a small business can buy.

What a scheduled task actually is

A small program that runs on a timetable rather than when someone presses a button. Every night, every Monday, the first of every month, every fifteen minutes. On a server it is often called a cron job, after the tool that has been running them for decades.

It is different from a workflow that reacts to something happening, like a form being submitted. A scheduled task acts because it is time to, whether or not anything has changed. That makes it the right shape for anything that is really a routine.

The jobs they are good at

Look for anything in the business that somebody does on a schedule, the same way each time.

• Reminders. Appointments tomorrow, invoices overdue by fourteen days, certifications expiring next month. Checked every morning, sent automatically.
• Reports. Yesterday’s sales, this week’s bookings, the month’s open jobs, assembled and emailed before anyone arrives.
• Reconciliation. Comparing two lists that should match, such as payments against invoices or stock against orders, and flagging only the differences.
• Tidying. Archiving old records, deleting files past their retention period, clearing out test data.
• Copying data along. Taking the day’s records from one system and putting them in another that has no direct connection.
• Checks. Is the website responding, did last night’s backup run, has the certificate got more than two weeks left.

Each one is small. Together they are often hours a week, and they are the hours people resent most, because the work is repetitive and errors are easy.

Why they are cheap

A scheduled task needs somewhere to run, and very little of it. Most ordinary web hosting can run them already, and the cost of a job that runs for thirty seconds a night is close to nothing.

There is no per-user licence, because nobody uses it. It does not get more expensive as the business grows, unless the job itself gets much bigger. And because it does one thing, it is usually short, which makes it quick to build and simple to change.

This is the clearest case where a workflow platform or a licensed automation tool can be more machinery than the problem needs. A nightly job that tidies a file and emails two people does not need a platform. It needs a few dozen lines of code and somewhere quiet to run.

Where they go wrong

The same thing that makes them good makes them risky: nobody watches them.

• They stop, and nobody notices. The reminder emails just stop arriving, and an absence makes no noise. This is the characteristic failure of all quiet automation, and scheduled tasks are its purest form.
• They run on the wrong machine. A job on somebody’s desktop only runs when that desktop is on. A job on a laptop goes on holiday when its owner does.
• They run at the wrong time. Servers often keep time in UTC, so a job set for “nine o’clock” may run at ten in summer. This catches people every year.
• They depend on a password that changes. A job logging into another system with a person’s account stops the day that person changes their password or leaves.

Three situations, worked through

A dental practice where reception phones every patient the day before. A job at eight each morning reads tomorrow’s appointments and sends a text reminder, with replies going to the practice inbox. The receptionist’s morning is given back, and the calls that still happen are the ones that need a person.

An accountancy firm chasing clients for documents. A weekly job checks which clients have outstanding items and sends each one a single, specific reminder listing exactly what is missing. The partners stop writing the same email forty times.

A wholesaler whose stock spreadsheet and web shop disagree. A nightly job compares the two and emails a short list of mismatches. Nobody needs to fix the integration yet. Knowing about the differences by nine each morning removes most of the cost of them.

Five things worth doing

1. List everything someone does on a timetable. Daily, weekly, monthly. Those are the candidates.
2. Run them on a server, never on someone’s computer. Hosting the business already pays for is often enough.
3. Use accounts that belong to the business, not a person, for anything the job logs into.
4. Make each job report something: a short email when it runs, or at least a line in a log someone can check. Silence should mean something is wrong, not that all is well.
5. Set the time zone deliberately, and check the first run after the clocks change.

Common misconceptions

• “Automation means a big system.” Most of the value in small-business automation is in small jobs that run on a timetable. They are the cheapest kind to build.
• “If it is not visible, it is not important.” The opposite is often true. The jobs nobody sees are frequently the ones the business would miss most.
• “Once it runs, it will keep running.” Accounts change, systems update and servers move. Something has to notice when a job stops.
• “We would need our own server.” Most ordinary hosting can run scheduled tasks already. Worth checking before buying anything.

The honest summary

A scheduled task is the plainest kind of software: a job, a timetable and somewhere to run. For routines that happen the same way every day, week or month, it is usually the cheapest automation available, with no licence, no interface and very little to maintain.

Its weakness is that it works silently and fails silently. Built with a business-owned account, run somewhere that is always on, and set up to report what it did, it is about as reliable as software gets.

If someone in your business spends part of every morning doing the same thing they did yesterday, describe the routine. It is often a short job, and one that pays for itself within the first few months.