A double-booked engineer. A van sent across town when a closer one was free. A job that slipped because it never made it off the whiteboard. If you run a field service or workforce-heavy business, scheduling rarely fails in one big way. It’s the steady drip of missed appointments, dispatchers ringing round to assign work, and admin time spent reconciling what was planned against what happened.
I build job scheduling and dispatch software around how your business assigns, sends out and tracks work: your job types, your rules, and the back-office tools you already run. This page covers the dispatch board and the scheduling behind it. If you need the full field service platform with assets, parts and service contracts, that’s on the field service management page.
If you’re a fairly standard field team of 20 to 200 people with conventional workflows, an off-the-shelf tool is often the right answer, and I’ll tell you that. This page is about the cases where it isn’t.
Where off-the-shelf scheduling software falls short
Packaged scheduling and dispatch tools cover the common case well. The friction shows up at the edges:
- Rigid workflows. Multi-stage sign-off, skill tiers and separate service territories, flat-rate alongside time-and-materials pricing, and jobs whose scope grows once the engineer is on site often can’t be modelled. The tool makes you change your process instead of supporting it.
- Calendar sync runs one way. Changes made in Google Calendar or Outlook don’t flow back to the board, so engineers get double-booked anyway.
- Integration gaps. Many tools offer one-way sync to accounting, a low API rate limit, or no native connector at all. The fallback is a Zapier workaround with a few hours’ lag, or someone re-keying data by hand.
- Per-user pricing that scales against you. Affordable for a small team, but grow to 50 or 100 field staff and it becomes one of your largest fixed costs, with the meter never switching off. Franchise and multi-company operations often pay per location with no consolidated view.
- Contract lock-in. Some UK vendors tie you into multi-year terms, which is painful when your operation changes faster than the contract allows.
- Dated interfaces and clunky mobile apps. If technicians find the app awkward, they don’t update job status, and your dispatch board stops reflecting reality.
- Weak reporting and audit trails. Standard reports rarely match how you measure utilisation or cost, BI tool exports are often missing, and audit logging can fall short of what regulated sectors need.
- Data residency. Several major tools default to US hosting. For regulated work, or businesses that simply want UK or EU data residency, that’s a real problem rather than a footnote.
Each time, the software sets the shape of the work, so a parallel set of manual processes grows up alongside it.
How I build it differently
I map how work moves through your business before anyone writes code: how a job is raised, assigned, dispatched, completed, approved and invoiced, and where it currently breaks. Whether you run a fleet of mobile engineers, project crews across sites, or shift teams across locations, the system gets built around that.
You pay once for development instead of paying SaaS fees indefinitely. For larger workforces, where per-user pricing has become the expensive option, a fixed-fee custom system that supports 100-plus users without a per-seat multiplier usually changes the maths.
The system connects to the tools you already run: accounting, CRM, payroll, payment processing, SMS and email, and mapping APIs for routing. Getting these working as one setup, with two-way sync rather than one-directional exports, is a large part of the job.
UK rules go in from the start: GDPR and the Data Protection Act, working time regulations, driver hours where transport is involved, and the audit trails regulated sectors need.
The build is modular, so new service lines, pricing models, or workflow changes can be added without a painful migration or a platform switch.
The person you talk to builds it. I write the code myself, bring in a trusted specialist where a job needs one, and train your team in person where it helps.
If First Gear shows an off-the-shelf product or an open-source platform would serve you better, I’ll say so and can help you set that up instead.
What the software does
Every build is shaped to your operation. A typical scheduling and dispatch system covers:
A dispatch board with drag-and-drop scheduling and conflict detection, so a dispatcher sees the day at a glance: jobs pending, jobs in progress, who’s running late, and where each person or van is.
Job and work-order management: each job carries its address, appointment window, status, priority, skill requirements, linked customer, notes, photos, and the custom fields your work needs.
Automated assignment that takes availability, skills and certifications, and location into account, so the right person lands on the right job instead of the nearest free name.
A technician mobile app for viewing the day’s jobs, clocking on and off, updating status, extending the scope and requesting materials when a job grows, and capturing photos and signatures, offline where signal is poor. Photos, notes and customer sign-off are timestamped, so a job record holds up if it’s ever used as evidence in a warranty claim or a dispute.
Route optimisation that cuts travel time and fuel by ordering multi-stop days sensibly, with re-routing when a job runs over or a new one comes in.
Customer communication: automated arrival-window notifications, reminders and delay alerts by SMS or email, with PECR consent handling. Reminders are one of the cheapest ways to cut missed appointments, and a branded tracking link looks better than a generic portal.
Recurring work: standing contracts such as weekly cleaning, monthly maintenance and annual inspections generate their own visits, with travel-time buffers and on-call rotas respected.
Working time and compliance checks for rest periods, the 48-hour average week, break entitlements, contract terms, and driver hours, flagged before a schedule is published.
Skills and certification tracking, so only qualified people are assigned to jobs that need a ticket, with alerts before mandatory certifications expire.
Reporting and dashboards on utilisation, jobs completed, SLA performance, and cost, with exports to Excel, PDF and BI tools.
Multi-site control for businesses coordinating regional teams or several depots from one place.
Role-based access control matched to your org structure, plus an append-only audit trail for compliance and settling disputes.
How the build runs
First Gear (5 days). I talk to people across the business, dispatchers, field staff, finance, to document how work flows today, where the friction is, and what good looks like, and build a working prototype. Requirements, integration points, and success metrics get nailed down here. This is also where unusual business rules surface, before they can derail a timeline.
Development. I build with mainstream, well-supported technology, typically .NET Core and React, with React Native for the mobile app, and run weekly demos so you steer the build from working software, not documents.
Testing and deployment. QA includes user acceptance testing with your team. I handle the technical side of going live, including data migration and a parallel run alongside your existing system so cutover doesn’t risk a day’s jobs.
Training and support (ongoing). Training is shaped to each role, field staff need a couple of hours on the mobile app, dispatchers and admins need more, backed by a 30-day fix guarantee and the first month of hosting free, with monthly plans available after that.
Extra integrations become later fixed-price phases. I take on three builds a month, so each one gets my attention. Builds most often slip on underestimated data cleanup and business rules that surface late, which is why First Gear goes looking for both.
What it costs
Custom development costs more upfront than a SaaS subscription. Over a few years, for the right business, the total cost usually favours owning it.
- A SaaS scheduling tool charges per user per month, plus setup, integration, add-on and often payment-processing fees. For a sizeable field workforce that’s an annual cost that never stops and rises with headcount.
- Most builds cost £2k–£10k, fixed in the build plan. A focused first release covers core scheduling, the mobile app, a dispatch board and basic reporting.
- Route optimisation, two-way integrations, offline mobile and a compliance audit trail come as later phases.
- After launch you own the software and its IP. There’s no per-seat meter, no vendor lock-in, and no multi-year contract to escape if your business changes.
Where the crossover sits depends on your headcount, your add-ons and how unusual your workflows are. Tell me what you pay now and how many people use it, and I’ll give you scoped pricing for your situation and a straight view of whether a build is the right call at all.
Some tools are cheap at small sizes. Connecteam’s scheduling plans are free up to 10 users and, billed yearly, start at $29 a month for the first 30 users plus $0.80 for each extra user, up to $99 plus $4.20 per extra user on its top published plan (checked October 2026). At those prices a build rarely wins on licence cost alone. It wins when your dispatch rules, pricing or integrations don’t fit the tool.
Industries I build scheduling software for
This works for UK businesses that assign work to people and need it to land in the right place at the right time:
Field service trades such as plumbing, electrical and HVAC: dispatching engineers by skill and location, with emergency call-outs rebalanced against planned maintenance across the day.
Construction and commercial services: scheduling labour and subcontractors across multiple sites, managing crew rotations, and tracking certifications and equipment allocation.
Facilities management and building services: planned and reactive maintenance across a property portfolio, with SLA tracking so inspections and response times aren’t missed.
Healthcare and home care: coordinating visits by carers and clinicians, matching staff to patients by capability and location, with GPS check-in and check-out as visit verification. Patient data sensitivity and UK data residency often make this a strong candidate for a custom build.
Transport and logistics: driver and delivery scheduling built around driving-hour limits and rest periods, with route planning and real-time tracking.
Retail and hospitality: weekly rosters across locations for full-time, part-time and seasonal staff, with shift swaps and labour-rule compliance.
Manufacturing: staffing production lines across shifts and tracking the certifications each role requires.
Security services: guard tours and shift cover across sites, with lone-worker check-ins and incident logs.
Local government and emergency services: shift cover across council services and 24/7 rotas that account for on-call duty and mandatory rest.
Each build gets the sector-specific adjustments it needs, from HSE-compliant logging on a construction site to working time enforcement for a 24/7 rota.
Common Questions About Custom Job Scheduling Software
When does custom job scheduling software make sense over an off-the-shelf tool? ›
For a straightforward field service team of roughly 20 to 200 people with standard workflows, a SaaS tool like Deputy, Commusoft or Connecteam is usually the sensible choice, and I'll tell you so. Custom starts to pay off when you have non-standard logic the SaaS can't model (multi-stage approvals, commission or dynamic pricing, unusual job types), heavy integration needs with legacy back-office systems, strict UK data residency requirements, or a headcount where per-user pricing has become the most expensive line in your operations budget.
What's the difference between job scheduling and job dispatch software? ›
Scheduling decides when a job happens and who it's planned for, usually days or weeks ahead. Dispatch is the same-day part: sending the job to an engineer, re-assigning it when one runs over or an emergency comes in, and tracking it to completion. Appointment tools like Calendly or Acuity only do the booking; field service platforms do both plus invoicing. The system I build covers scheduling and the dispatch board together, because the board is where a plan meets the day.
What's the typical development timeline? ›
A focused MVP covering core scheduling, a technician mobile app, a dispatch board and basic reporting usually goes live within a month. Route optimisation, two-way accounting integration, offline mobile and a compliance audit trail follow in later phases, each about a month long. Multi-site rollouts or deep legacy ERP integration take longer.
How do you handle updates and changes after launch? ›
Every build includes a 30-day fix guarantee and the first month of hosting free. After that you can move to a monthly plan or take it in-house; I build with documented, mainstream technology so your own IT team can maintain it. Because the system is modular, new service lines or workflow changes can usually be added without a platform migration.
Can you integrate with our existing accounting, CRM and other systems? ›
Yes. Common integrations include accounting (Xero, Sage, QuickBooks), CRM, payroll and HR systems, payment processing (Stripe), SMS and email for customer notifications, and mapping APIs (Google Maps, HERE) for routing. Where a SaaS tool gives you one-way sync or no native connector at all, I build two-way integration so data isn't re-keyed by hand. Calendar sync with Google and Outlook runs both ways too, so a change made in someone's calendar reaches the board.
How do you migrate data from spreadsheets or our old system? ›
I import customers, sites, job history and open invoices, and keep the links between them (customer to job to engineer to invoice), because broken links are where most migrations go wrong. Time for deduplication and address cleanup goes into the plan from the start, since messy data is usually the bottleneck.
What about data security, GDPR and audit trails? ›
I build to UK GDPR and Data Protection Act 2018 standards: encryption in transit and at rest, role-based access control, consent handling for technician location tracking, and data-erasure workflows. Customer SMS and email notifications carry consent handling under PECR. Job and timesheet history is kept on an append-only audit trail suitable for the 6 to 7 year retention most businesses need. Hosting can be UK or EU based, on your cloud account or on-premises, so data residency is never in question.
Will the software enforce working time and labour rules? ›
Yes. The system checks what matters for your sector: minimum daily rest, the 48-hour average week, break entitlements, contract terms, and driver hours and rest periods where transport is involved. Rules are configured to your operation rather than a generic template, and the system flags conflicts before a rota is published rather than after.