Scheduling and Workflow

Operations: Deliver and run the business

Most service businesses we work with have a version of the same morning. The owner starts the day with a plan, the first job runs long, a customer calls with something urgent, and by ten o’clock the plan is a suggestion. By the afternoon everyone is reacting.

The schedule was built on the best case, and the best case rarely happens twice in one week.

A schedule is a promise, not a wish

When you give a customer a date and time, you are making a promise on behalf of your whole business. So the real question about scheduling is how many promises you can keep, whatever number of jobs you could squeeze in.

Build the schedule from the realistic case. If a job usually takes four hours, book it for four and a half, or book it for four and leave the half hour open after it. The driving between jobs is part of the job. The cleanup is part of the job. Leave room for the phone call that turns into twenty minutes. If your work in the lesson on capacity planning gave you a working number, use it here. The buffer looks like empty time, and it is what makes the rest reliable.

Also decide what kind of work goes where. Some tasks need your full attention and some can be interrupted. Put the first kind in protected blocks and cluster the second. A quote can wait an hour. A crew standing around waiting for a delivery cannot.

Workflow is the path a job takes

Scheduling answers when. Workflow answers what happens, in what order, and who moves it forward. Take any job and write down its stages, such as booked, confirmed, materials ready, scheduled, in progress, finished, invoiced, paid. Those are the columns of a simple board, on a whiteboard, a spreadsheet or in software.

What matters is that every job is visible in exactly one column at all times. If you cannot tell in ten seconds where each job stands, you are holding the workflow in your head, and your head is also holding a dozen other things.

Look for the places where jobs wait. Jobs rarely stall in the doing. They stall in the gaps: waiting for a deposit, waiting for a material, waiting for a callback, waiting for someone to notice the work is finished and the invoice has not gone out. Each waiting point needs an owner and a rule, such as “materials are ordered the day the deposit clears” or “the invoice goes out the same day the job closes.”

This is also where the promise you made in your marketing gets kept or broken. A customer does not see your workflow. They see whether you arrived when you said, and whether the next step happened without them having to ask.

Small habits that hold it together

• Confirm every appointment a day ahead, with a simple message.
• Set aside a fixed time each week to look at the next two weeks.
• Keep one place where the schedule lives, so there is never a second version.
• When something slips, tell the customer early and give the new time.

None of that needs expensive tools. A shared calendar and a board cover most small businesses. Software helps once the volume grows, but a messy process in software is still a messy process.

Your next step

Choose your most common type of job and write out its stages from booked to paid. Next to each stage, write who moves it forward and what the rule is when it waits. Then open next week’s calendar and check that every job has travel time and a buffer. Change one booking that is too tight.

Drawing the workflow for one type of job takes an hour or two, and reviewing your calendar for buffers takes about thirty minutes. A whiteboard or spreadsheet is free. Scheduling software often runs a modest monthly fee, and it is worth choosing only once you know what your process needs it to do.