To build your own scheduling and dispatch software, you need four things: a clear way to assign each job to a person or crew, support for recurring visits, a day view that shows who is going where, and a version your crew can read on a phone. Get those right and you have most of what a service company needs from a schedule. Everything else is extra.
This guide walks through each piece and the decisions you will make along the way.
Start with how your day actually works
Before you build anything, write down how scheduling works today. Not how it should work. How it does work.
Ask yourself:
- Who decides which tech or crew gets which job?
- Do jobs have fixed times, or time windows ("between 8 and 12")?
- How long does a typical job take? Does it vary a lot?
- Do you schedule by person, by crew, or by truck?
- What happens when a job runs long or a customer cancels?
The answers shape everything. A salon books by chair and by the hour. A landscaping company books by crew and by the day. A plumber books by tech, with emergencies jumping the line.
Who goes where
The core of dispatch is simple: every job has a date, a time or window, and someone assigned to it.
What to store on each scheduled visit:
- Customer and service address
- Date and start time (or time window)
- Expected length
- Assigned tech, crew or truck
- What the job is (from the quote or job record)
- Status: scheduled, on the way, in progress, done
Keep the assignment visible. When the office moves a job from one tech to another, both techs should see the change.
Crews vs individuals
If you send crews, decide whether you assign the crew or the people. Assigning a crew ("Crew A") is easier day to day. Assigning people gives you more detail for payroll and tracking. Many companies assign a crew and let the crew lead note who showed up.
Recurring visits
Recurring work is the backbone of many service companies: weekly lawn care, biweekly house cleaning, quarterly pest control, yearly furnace tune-ups.
A good recurring setup lets you:
- Set a pattern (every week, every 2 weeks, every month, every spring)
- Pick the usual day and the usual crew
- Change one visit without breaking the whole series ("skip this week, they're on vacation")
- End the series when the customer stops
The common mistake is creating recurring visits by copying them by hand, months ahead. When something changes, you end up editing twenty entries. Build the pattern once and let each visit come from it.
The day view
The day view is the screen your office lives on. It answers one question: who is doing what today?
| Design choice | Option A | Option B |
|---|---|---|
| Layout | One column per tech or crew | One list, sorted by time |
| Best for | 3 or more techs, lots of moving jobs | 1 to 2 crews, simple days |
| Shows gaps | Easy to spot open time | Harder to spot |
| On a phone | Too wide, use a list instead | Works well |
Most companies want columns at the office and a simple list on the phone. That is fine. They can be two views of the same schedule.
Other things worth having on the day view:
- Unassigned jobs in a separate pile, so nothing is forgotten
- The address on each job, so the office can spot bad routing
- A quick way to mark a job done
You will notice what is missing: automatic route optimization, GPS tracking and live maps. Those are nice in large fleets. For a small company, an office person who knows the area and can see the addresses usually does a better job.
Making it work on a phone
Your crew will not use a schedule they cannot read in the truck. Plan for phone use from the start:
- Show "my day" first. A tech wants their own jobs, in order, not the whole company's schedule.
- Put the important stuff on top. Address, time, customer name, access notes.
- Big buttons. "Start" and "Done" should be easy with one thumb.
- Notes and photos from the field. Let the tech add what they found.
If the tech can open their phone in the driveway and see the gate code and what the job is, you have saved a phone call to the office. Multiply that by every job, every day.
Connect the schedule to the rest of the job
A schedule on its own still means retyping. The customer's address should come from the customer record. The job description should come from the accepted quote. When the job is done, the invoice should start from it. Read quote to invoice without retyping for how that chain works, and build your own CRM for the customer side.
Building it with Alori
Alori is an AI app builder for service companies. Scheduling and jobs are two of its built-in modules, and they connect to customers, quotes and invoices in the same app. Apps work at the office and on a phone.
You describe your business in plain words. For example:
Lawn care, 3 crews. Most customers are weekly or every two weeks, April to October. I need a day view by crew and a simple list for crew leads on their phones.
If something is unclear, Alori asks a couple of multiple-choice questions, like whether you schedule by crew or by person. Then it builds the app in your words. Later, you can change it by asking: "add a time window to each visit" or "show unassigned jobs at the top of the day view." Changes are tried on a copy first while your team keeps using the live schedule.
If you are moving off a whiteboard, see replace spreadsheets and whiteboards for a step-by-step plan.
Frequently asked questions
Do I need route optimization?
Probably not if you have a few crews working a local area. Your office staff can see the addresses and group jobs sensibly. Route tools matter more when you run many vehicles across a wide area.
How do I handle emergency jobs?
Keep a way to add a job for today and assign it fast. Then look at the day view to see who has a gap or who is closest. A clear day view makes emergencies much easier to slot in.
What is the best way to handle recurring visits?
Set the pattern once, then let each visit be created from it. Make sure you can change or skip a single visit without editing the whole series.
Will my crew actually use it?
They will if it saves them calls and fits on their phone. Show only their jobs, put the address and access notes first, and keep the buttons simple.
See your schedule built your way
If your schedule lives on a whiteboard, in group texts or in a tool that does not fit how you dispatch, try building one around your business. Alori is free to start, with no credit card and no account needed to try. Describe how your day works.
