From Planning to Dispatch: Scheduling in TeamPoint

11.09.26inPlatform Capabilities

Written by

Rosie Cottell

HOME/KNOWLEDGE CENTRE/from-planning-to-dispatch-scheduling-in-teampoint

Platform Capabilities11.09.26

From Planning to Dispatch: Scheduling in TeamPoint

TeamPoint helps service businesses plan, allocate and adapt work using connected calendar, map and mobile scheduling tools. From planned maintenance and reactive jobs to skills, availability, travel time and reporting, scheduling stays connected to the wider job information so teams can make better decisions as the day changes.

Scheduling jobs in a service business is challenging, and each of our customers handles it differently. TeamPoint works with businesses across a wide range of industries, and over the years we’ve gained a lot of practical experience in helping customers plan, allocate and manage work in ways that suit how their business operates.

It is a complex problem that has to be solved every day. A scheduler may be balancing planned maintenance, reactive call-outs, surveys, multi-day work, recurring contracts, different teams, different skills, customer commitments and the inevitable changes that happen throughout the day. A job that looks straightforward can become difficult very quickly if the right person is unavailable, the next appointment is several hours away, another urgent job comes in, or information has not been updated across the office and mobile team.

TeamPoint brings those different parts of scheduling together within the same job management platform. Work can be planned in a calendar, allocated using skills and availability, viewed geographically, dispatched to operatives, updated as work progresses and analysed afterwards through reporting.

The aim is not to make every scheduling decision automatically. It is to give the people planning the work enough information to make good decisions quickly, while keeping the job, customer, site and operational information connected throughout.

Plan work around the way the business actually operates.

For forward planning, TeamPoint provides a calendar-based scheduling tool where schedulers can choose the period, the work they want to plan and the operatives they want to work on the job. The calendar can be viewed across a day, three days, a week or a month depending on how far ahead the planner needs to work. TeamPoint can also surface unscheduled jobs due within the next 14 days, helping upcoming work remain visible before it becomes urgent.

Rather than loading every unscheduled job into one enormous diary, the planner can narrow the workload first. Jobs can be filtered by criteria including due dates, job type and postcode, while operatives can be grouped into smaller planning teams and filtered using tags or skill sets.

TeamPoint weekly scheduling calendar showing operatives with skill tags, colour-coded jobs across the week, travel times, job durations and leave blocks.

Calendar based scheduling.

That matters in practice. A maintenance company might have 80 visits due during the next few weeks, but the scheduler may only want to plan the North West team for the coming five days. They can bring that relevant work into view, look at what is already booked and build the plan without being distracted by every other job in the business.

The same schedule can handle work that lasts a few hours, several days or needs more than one person. A job can be copied across multiple days or allocated to several operatives where a larger team is required.

TeamPoint also allows Jobs, Surveys and Holidays to be created directly from the Scheduling page. If a scheduler already knows that an engineer needs to carry out a survey on Thursday, for example, they do not have to leave the diary, create it elsewhere and then come back to allocate it. The work can be created quickly and assigned from the same planning area.

Businesses managing a larger volume of survey work can also use a separate Survey Calendar, which can be filtered by Job Type, People and Division.

Match jobs to operatives with the right skills and availability.

Within most businesses, different operatives have different strengths. TeamPoint can use operative tags and skill-set information when work is being allocated. Those tags can reflect the way an individual business operates, helping planners narrow down the available people according to the skills, qualifications, roles or other criteria that matter for that job.

So, a roofing contractor may want to distinguish between operatives experienced in pitched roofing, single-ply membranes, leadwork or reactive repairs, and use those skills when deciding who is suitable for a job. A facilities business might have separate electrical, plumbing and general maintenance teams. A drainage company may want to distinguish engineers who work on different service types or have people who cover specific geographical areas. Instead of relying on one person remembering all of that information, it can be stored and the relevant people can be filtered and compared within the scheduling process.

TeamPoint scheduling calendar showing operatives with skill tags, scheduled and dispatched jobs, travel times and annual leave availability.

Skills & Availability

Subcontractors can also be included when planning and allocating work, where they are set up as scheduling resources, allowing external resource to sit alongside the internal team where the business uses both.

Availability is equally important. Holidays, sickness, training days, working hours and non-working periods can be represented within TeamPoint so planners have a clear picture of who is available to work. If Jason needs to finish at 3pm every Thursday to pick up his children from school, that can be recorded for everyone to see rather than being held in the scheduler’s head.

Importantly, TeamPoint deliberately keeps the scheduler in control. Availability information is there to inform the decision rather than turn every rule into a hard block where the computer says “No!”. That matters in the real world; there are times when things are not ideal and a planner may need to make an exception.

Visually plan workloads and avoid over allocation.

A full diary can look efficient until travel time, job duration and existing commitments are considered together.

Within the scheduling calendar, TeamPoint shows the total planned hours for each operative. If the total goes above the realistic daily workload, the hours are automatically highlighted in red, giving the planner a quick visual indication that the day needs another look.

Plan work around geography and travel time.

TeamPoint includes map-based scheduling tools in addition to the calendar-based scheduling tool, giving planners a clearer geographical picture of where the work is and the last known mobile location of their operatives. For reactive work, the map can show jobs geographically alongside an operative’s last known mobile location. That makes it easier to see who is already nearby and determine who is realistically best placed to take on the job. The same information can be useful for planned work too. If an operative is running ahead of schedule and there is a short maintenance visit nearby, the planner can see whether it makes sense to fit it in.

TeamPoint map-based scheduling view showing an operative’s route, scheduled jobs and nearby reactive work across the Manchester and Liverpool area.

Map base Scheduling

Travel-time calculations use Google Maps, and the calendar can also calculate expected travel time between jobs that have already been allocated. This helps planners compare options more realistically. Two operatives may both have space for another job, but one may already be working a few miles from the customer while the other would need a significant detour. Looking at travel as part of the scheduling decision can help reduce unnecessary driving and make better use of the working day. Once the work has been completed, TeamPoint can also report actual travel time and compare it with the estimated travel time used during planning.

Schedulers can also filter unscheduled work by postcode and see where related jobs have already been allocated. For businesses managing a large volume of planned maintenance, this makes it much easier to group work in the same area rather than treating every appointment in isolation.

Prioritise emergency reactive work without losing sight of the initial plan.

Many of our customers, particularly in sectors such as drainage and utilities, have to manage planned and reactive work at the same time. TeamPoint has evolved to support these different types of work within the same operational environment.

Planned maintenance usually needs to be completed within an agreed service period, but there may be some flexibility over exactly when the visit takes place. Reactive work is different. A blocked drain, electrical fault or urgent site issue may need attention immediately. A recall can create the same pressure, for example where an operative has attended a job but needs to return with a different part, specialist equipment or another engineer.

Reactive jobs can carry a response time and can be scheduled either from the calendar or through a dedicated map-based scheduling view. This gives the planner a quick way to look at the urgent job, see who is already working nearby and decide who is realistically best placed to respond.

TeamPoint also includes a Job Priority tool with five priority levels. A business might choose to categorise urgent reactive or recall work as Highest priority, while routine PPM visits sit at a lower level. Those priorities can be set around the way the individual business operates, and schedulers can then search for unscheduled work by priority and bring the most important jobs into the plan first.The Reactive Tracker brings Reactive and Recall jobs together with their current status. This means a new emergency call-out and an urgent return visit already waiting to be dealt with can be seen as part of the same operational picture rather than managed in separate places. The Reactive Tracker shows current reactive jobs grouped into ascending bands of hours, helping the office see which jobs have been waiting longest and where attention is needed.

This makes it easier to respond when the day changes without losing track of everything else that still needs to happen. A planned service visit does not disappear because an emergency job has taken priority. It remains visible within the wider workload and can be moved, reassigned or rescheduled as required.

That wider visibility also helps other people in the office understand what is happening, even if they have just picked up the situation and were not involved with the job from the beginning.

Recurring Service Contract jobs can be created automatically ready for scheduling.

Within TeamPoint, office staff can record how often work is due under a Service Contract and when it needs to be carried out.

For example, a maintenance visit might be required four times a year, in March, June, September and December. There is an option called Auto Run within the Service Contract section and, when it is enabled, TeamPoint checks live Service Contracts each day and automatically creates the jobs required for the next two months, ready for the scheduling team to allocate.

TeamPoint Service Contract screen showing Auto Run enabled for recurring PPM visits, with jobs set to generate automatically for scheduled service months.

Auto Run Feature

This cuts admin time by removing the need for someone to create every recurring visit manually and gives planners visibility of upcoming work before it becomes urgent.

The work does not always need to be tied to one fixed appointment date. A service can sit within an agreed service window, giving the scheduling team flexibility to fit it around geography, capacity and other commitments while still keeping the contractual requirement visible.

For a business managing hundreds or thousands of commercial sites, that becomes especially valuable. The challenge is not just booking an engineer; it is making sure every required visit is created at the right time, remains visible and can be organised into a practical workload.

Build large schedules automatically

For businesses managing hundreds or thousands of recurring or planned jobs, placing every visit into the diary individually is a time consuming scheduling task. TeamPoint’s optional automated batch scheduling tool is designed for this type of high-volume work.

A scheduler can select a group of jobs and define the period in which they need to be completed. The scheduling window can be entered manually or determined from the earliest start and latest due dates within the selected jobs.

Before anything is changed in the live schedule, TeamPoint checks the selected work and available operatives and identifies any issues that would prevent the schedule being built. In the example shown here, 114 jobs and 35 workers are validated with no issues identified before scheduling continues.

Batch Scheduling

The tool then builds a proposed schedule across the selected work. It can take account of constraints around the jobs and operatives, including earliest and latest service dates, site access times, operative working hours, holidays, existing job commitments, geographical location and operative tags. TeamPoint uses those constraints to work out how jobs can be grouped, ordered and allocated to suitable operatives.

Rather than immediately applying those changes, TeamPoint presents the proposed schedule for review. The planner can see the jobs allocated across each operative’s day, together with the amount of work and travel involved, before deciding whether to apply it. Once the planner is happy with the result, the schedule can be confirmed and the assignments applied to the jobs. For a business managing a large planned-service programme, this can remove a significant amount of repetitive scheduling work while still taking account of the practical rules that determine when a job can be completed, where it is and which operatives are suitable for it.

TeamPoint schedule visualisation showing a proposed batch schedule across multiple operatives, with allocated jobs, timings, and work and travel time visible for review before the schedule is applied.

Schedule Preview

Schedule multiple connected jobs and visits separately within each Project

In TeamPoint, a Project brings together all of the individual jobs that make up a larger piece of work. Each job remains part of the same Project but can be planned and scheduled independently according to who needs to do it, when it needs to happen and how long it is expected to take.

A commercial roof refurbishment is a good example. The overall Project might include strip-out and roof deck repairs, insulation and membrane installation, followed later by final inspection and snagging. Those stages belong to the same piece of work, but they may need different operatives or teams on different days.

Project Jobs

Each Project job can be scheduled using the normal TeamPoint controls, including operative, date, time, duration and Scheduled or Dispatched status.

This means larger or more complex work can be broken into the individual visits needed to deliver it while keeping those visits connected to the same Project, customer and wider job record.

Plan first, dispatch when the schedule is ready.

TeamPoint separates Scheduled work from Dispatched work. When a job is first placed into the calendar, it can remain Scheduled while the planner builds and adjusts the day, week, month or beyond. That gives the office room to balance geography, workload and availability without every tentative change immediately being pushed out to the people carrying out the work.

Once the plan is ready, clicking Dispatch sends the confirmed work to the operative’s mobile device. Individual jobs can be dispatched one at a time, or all of the jobs on the loaded schedule can be dispatched together.

If something changes after dispatch, the schedule can still be updated. A job might need to move because another urgent call has come in, an appointment has changed or the original plan needs adjusting. The revised information is then updated on the operative’s mobile app. If they are temporarily out of signal, the app synchronises the change as soon as a connection becomes available again.

From there, the mobile app remains connected to the office schedule rather than operating as a separate system. Status changes made by operatives can update the schedule automatically, with stages including Scheduled, Dispatched, On Route, In Progress and Complete, allowing office staff to follow the progress of work through the day.

You can read more about working on site with the TeamPoint mobile app, including job information, forms, photos, signatures, further work and offline working in our article, 'Working on site with the TeamPoint mobile app.'

If further work is identified on site, operatives can also suggest or request recall or follow-on work from the mobile app so that it can pass back into the office process rather than being lost in a phone call or note.

TeamPoint makes it easier to adapt when the day changes.

In the real world, things do not always run to plan. A job may take longer than expected, a customer may move an appointment, or a burst pipe may suddenly bring a ceiling down at the embassy. Whatever the reason, the schedule needs to be able to change with the day rather than fall apart the moment something unexpected happens.

TeamPoint supports multiple office schedulers working in the same plan at the same time. If one person moves or reschedules a job, the change appears automatically in the other schedulers’ views without the need to refresh the page. In a larger operation, where different people may be planning separate teams or regions, this means everyone is working from the same current picture rather than from their own version of events.

For a wider look at how TeamPoint supports customer communication and the relationship around the work, read From First Enquiry to Ongoing Service: Managing Customer Relationships in TeamPoint.

Some of our customers take that visibility a step further and keep the live schedule displayed on a large screen in the office. As operatives travel to jobs, begin work and complete them, the jobs change status and colour on the calendar, so the wider team can see the day unfolding at a glance. There is something quite satisfying about watching the completed jobs build up across the screen, but it also gives everyone in the office an immediate visual picture of how the day is progressing.

There is also a Scheduling Log which records activity as it happens, including who made a change and what was altered. That creates a clear running record of how the schedule has evolved through the day, which is useful when several people are involved in planning and reallocating work.

Customer office with TeamPoint scheduling displayed on wall-mounted screens, giving the wider team a live view of jobs and daily progress.

Live Schedule display

The same flexibility extends beyond the office. Customer and internal notifications can be configured around the way the business works, including events such as jobs being booked, scheduled, completed, overdue or placed under review. Appointment reminders and change notifications can also be set up where required.

If a job has already been dispatched and the plan changes afterwards, the operative is not left working from old information. The revised schedule updates on the mobile app when the device is connected, or synchronises as soon as signal becomes available again if they are working offline. An additional SMS alert can also be configured where the business wants to make an important change harder to miss.

Use reports to learn from what actually happened.

Once the work has been planned and carried out, TeamPoint gives managers a way to look back at how that schedule actually performed. Rather than judging success by whether the diary looked full, they can see how work was delivered in practice — who attended, how long jobs took, whether work was completed on time and whether repeat visits were needed.

That information comes through a range of operational reports. For example, the Job Attendance report records who attended, when they started and finished, and the total hours spent on site, while the Job On Time / First Time Performance report shows how often work was completed on time and first time. Individual employee calendars can also be used to look more closely at a particular person’s historic and future workload where that level of detail is useful.

Over time, this gives managers a much better picture of how the operation is really performing. Patterns start to emerge: some teams may consistently complete more jobs, certain types of work may generate more return visits, or one region may regularly run differently from another. That is the point at which scheduling data becomes useful management information rather than just a record of what was put in the diary.

Good Scheduling decisions depend on having the wider job information to hand.

The strength of TeamPoint scheduling is not any one calendar view, map or report in isolation. It is the way those tools sit within the wider job management platform, with the information around the work kept connected.

That means the scheduler is not making decisions from a diary alone. They can take account of the job itself, the customer and site, who is available, who has the right skills, where people are working, how much is already in the day and what has happened before. When the plan changes, that same information continues to move with the job rather than becoming separated across different systems or conversations.

As the business grows, that becomes increasingly important. Scheduling stops being something that can live comfortably in one person’s head and becomes a shared operational picture that other people in the office can understand and work from too.

That is really what TeamPoint is designed to support: not just putting work into a calendar, but helping the business plan, adapt and keep control of work as it moves from one stage to the next.

Support Hub

Scheduling FAQs

Answers to some of the most common questions about how TeamPoint handles scheduling, recurring work, reactive jobs and changes to the plan.

Help Desk

Still have questions?

Can't find the answer you're looking for? Our friendly UK-based support team is a message away and ready to help.

Talk To Us

Yes. Planned maintenance, reactive work, recalls and other job types can be managed within the same operational environment, with tools including priority levels, calendar scheduling and map-based scheduling.

Yes. Service Contracts can use Auto Run to check live contracts each day and create required jobs for the next two months, based on the service schedule.

TeamPoint offers an optional AI-informed automated batch scheduling tool for businesses that need to organise hundreds or thousands of planned or recurring jobs.

The revised information is updated in the operative’s mobile app when connected, or synchronised when connectivity returns. Additional notifications can also be configured.

Operative tags and skill information can be used to narrow the people suitable for a job, alongside visibility of holidays, sickness, training, working hours and other availability information.

What are your scheduling priorities?

Most established service businesses already use some form of software to help schedule work. The more important question is whether it still fits the way the business operates now — and whether it supports the things that matter most to you.

That might be better visibility of workload, faster response to reactive jobs, less unnecessary travel, stronger control over recurring work, easier coordination between office and mobile teams, or simply fewer workarounds around the system.

TeamPoint is designed to adapt around different ways of working rather than force every customer into the same scheduling process. We work with customers to understand how they plan and allocate work, then configure the platform around their teams, job types, priorities and workflows. That support continues after go-live, with a UK-based team that develops the platform in response to the operational challenges customers bring to us.

If your current scheduling software technically works but still leaves your team compensating for it with spreadsheets, phone calls, workarounds or knowledge held in individual heads, it may be worth asking whether it is still the right fit.

What matters most in your scheduling process, and where does your current system make that harder than it should be?

See TeamPoint in action.

From Planning to Dispatch: Scheduling in TeamPoint

From Planning to Dispatch: Scheduling in TeamPoint

Plan work around the way the business actually operates.

Match jobs to operatives with the right skills and availability.

Visually plan workloads and avoid over allocation.

Plan work around geography and travel time.

Prioritise emergency reactive work without losing sight of the initial plan.

Recurring Service Contract jobs can be created automatically ready for scheduling.

Build large schedules automatically

Schedule multiple connected jobs and visits separately within each Project

Plan first, dispatch when the schedule is ready.

TeamPoint makes it easier to adapt when the day changes.

Use reports to learn from what actually happened.

Good Scheduling decisions depend on having the wider job information to hand.

Scheduling FAQs

Still have questions?

What are your scheduling priorities?

You may also like

From First Enquiry to Ongoing Service: Managing Customer Relationships in TeamPoint

Working on site with the TeamPoint mobile app

From Quote to Invoice: How TeamPoint Keeps the Commercial Process Connected.

What software does a UK retrofit contractor need to manage projects and be audit ready?