FeaturesHealth & SafetyIntegrationsCountriesPricingResourcesLog inStart free trial
SKEDS / Resources / Scheduling
Scheduling

Excel job scheduling template (and the honest signs you have outgrown it)

By the SKEDS Team · 22 June 2026 · 5 min read

Every trade business schedules in a spreadsheet at some point, and the ones that say otherwise are lying or huge. Done well, Excel runs a small operation for years. This free template is the done-well version: one row per job with customer, site, crew, date, start, duration, a calculated finish time and a status dropdown. Below it, equally honest: the specific signs that the spreadsheet has become the most expensive free tool you own.

Download the template

Download the free schedule template

No email required. Status dropdowns included; finish times calculate from start and duration.

Excel (.xlsx)

Duplicate the sheet for each week and archive old ones rather than deleting; the history becomes your demand data. The status column uses a dropdown of Unassigned, Scheduled, En route, In progress, Done and Cancelled, which are the same states a dispatch board uses, so the mental model transfers if you upgrade later.

How to run a week from this sheet

Sort by date then start time each morning and the sheet reads like a run sheet. Filter by the assigned-to column to see one person's day. Keep one non-negotiable rule: the spreadsheet is the single source of truth, and a job that is not on it does not exist. Most spreadsheet scheduling failures are actually dual-source failures, where half the jobs live in a text thread and the sheet quietly loses authority.

Colour by status if it helps, but resist building macros. Every hour spent programming Excel is an hour spent building a worse version of software that already exists; Microsoft's own compatibility documentation hints at the maintenance tax that accumulates around elaborate workbooks.

The honest signs you have outgrown it

  • The sheet has an owner. One person is the only one who can safely edit it, and their holiday is an operational risk.
  • Field staff call to ask what is next. The schedule cannot travel, so the phone becomes the API and the office becomes the bottleneck.
  • Two people edited it at once. A job vanished in a conflicted save and a customer waited on an empty driveway.
  • Evidence lives elsewhere. Photos on phones, signatures on paper, hours in another sheet; the schedule knows the plan but nothing about reality.
  • You schedule around memory. Which crew has the gate code, who is licensed for the switchboard, who is nearest; the sheet holds none of it.

Two or more of those and the spreadsheet is costing more than software would. The going rate for real scheduling tools is lower than most spreadsheet holdouts assume; several, including SKEDS, have genuinely free tiers.

What the upgrade actually changes

The upgrade is not prettier rows, it is the schedule becoming live. In SKEDS the same columns you just downloaded become a drag-and-drop dispatch board: jobs move between crews with a mouse, every change appears on the assigned technician's phone immediately, multi-day jobs stretch across the days they cover, and the map shows who is where. The evidence problem dissolves because photos, hours and signatures attach to the job rather than orbiting it. Import is not a project either; the template's columns map straight onto a job record, and the Starter plan is free, so trying it costs a lunch break. If you want the wider market view first, our roundup of the best job scheduling software compares the field honestly.

Getting the most from the spreadsheet while it lasts

A few disciplines stretch the spreadsheet's useful life by a year or more. Archive weekly, never monthly, so a corrupted file costs you days of history instead of a quarter. Keep a customers tab in the same workbook with phone numbers and access notes, and reference it rather than retyping, because retyped details are where wrong-address mornings come from. Add a simple week number column so you can filter history when a customer says you were here in March. And put the workbook somewhere synced and backed up; the schedule is the single most operationally expensive file you own, and a van break-in that takes the laptop should not take the week's plan with it.

Finally, write down the rules that live in your head: which crew handles which suburbs, who holds which licence, which customers need a call before arrival. The spreadsheet cannot hold that knowledge, but a page of notes beside it can, and it is the difference between a schedule anyone can run for a week and one that collapses when you get the flu.

Frequently asked questions

Can I use Google Sheets instead of Excel?

Yes, and the shared-editing conflicts get better while every other limitation stays. Import the template into Sheets and the formulas and dropdowns carry across.

How many jobs a week can a spreadsheet realistically handle?

The ceiling is less about job count than about coordination: one dispatcher, one van and thirty jobs is fine; three crews and fifteen jobs is already painful, because the problem is concurrent editing and field access, not rows.

Will I lose my history if I move to software?

No. Keep the old workbooks as archives, and most tools including SKEDS let you import customers and open jobs so the switch happens over a weekend, not a quarter.

Found this useful? Share it

Someone in your trade group chat is asking this exact question.

Key takeaways

  • A disciplined spreadsheet with one source of truth runs a small operation fine.
  • Statuses in the template mirror a dispatch board, so the habit transfers.
  • The outgrowing signs are coordination failures, not row counts.
  • The upgrade makes the schedule live on every phone, with evidence attached.
Just Skeds it.

Stop running the job from a spreadsheet

Schedule your crew, run jobs from the van, and invoice the moment they are done. Free for one user, forever.

Start free trial