Scheduling Teams and Equipment

Schedule a field team directly from DayBack calendar. See technician, lead, and vehicle availability at a glance, with drive times calculated automatically.

If you run field operations (maintenance crews, construction teams, or mobile health care technicians), you know the morning dispatch routine. Someone has to figure out who’s available, which vehicle to send, whether the job requires a lead technician, and what time everyone needs to leave to arrive on schedule. That usually means checking several screens, cross-referencing a spreadsheet, and making a few phone calls.

We recently built a workflow in DayBack that consolidates all of that into a single screen. When a dispatcher clicks on a job, they can schedule the entire field team (technicians, lead, vehicle, departure plan, and equipment) without leaving the calendar.

Seeing Availability at a Glance

The first thing dispatchers need to know is who’s actually available. This workflow begins by narrowing down to just those technicians with a skill and location match for the job. Then, each technician and vehicle is shown with a simple status indicator: available, partially available, or unavailable. These statuses are pulled from Salesforce in real time, reflecting PTO, existing assignments, and equipment reservations.

Dispatchers don’t have to open a separate screen to check. They can see the full roster, pick their team, and move on. A capacity bar in the topbar tracks total tech hours at a glance, so you know immediately if the day is under- or over-committed.

If the job requires a lead technician (say, for a Class 3 difficulty rating), the modal calls that out with a badge in the header and highlights which team members hold the right certification.

• Blue highlight marks the currently selected team members.
• Partial means partially available. They have a conflicting assignment but could still be shifted.
• Unavailable means they’re blocked: PTO, a prior commitment, or an equipment hold.
• Star identifies certified lead technicians.

In this example, we show each crew member’s status, but this workflow can also be prefiltered to focus only on the resources who are available and who meet all job requirements.

This is similar to the availability patterns described in our post on coordinating crews and assignments, but here the logic is focused on a single job rather than an overview of the week.

Traffic-Aware Departure Planning

Once the team is selected, the next question is: when do they need to leave? That depends on where the job is, what traffic looks like, and how long the work itself will take.

This workflow integrates with the Google Maps Platform to calculate real-time, traffic-aware drive times from your staging location to the job site. The dispatcher sets the on-site start time and the number of working hours, and DayBack works backward to determine when the crew should depart.

It also calculates the return trip, so you get a complete picture of the day:

• Depart — when the crew leaves the shop or yard
• Arrive — estimated arrival based on current traffic conditions
• Back — return drive time (traffic patterns often differ by direction and time of day)
• Return — when the crew is expected back

The drive time and distance come from the Google Maps Directions API, using departure-time-aware routing. That means a 25-mile job site might show a 53-minute drive during morning rush and a 24-minute return in the early afternoon. Dispatchers see both, so they can set realistic expectations with the client and avoid under-scheduling the day.

Adjusting the start time or hours on site recalculates everything instantly. If the dispatcher shifts the start from 8:30 AM to 9:00 AM, the departure, arrival, and return times all update to reflect the new plan.

Certifications and Job Requirements

Not every technician is qualified for every job. Some tasks require specific certifications, licenses, or experience levels. In this workflow, job difficulty or classification data from Salesforce drives a requirement check: if the job is rated Class 3 or above, a “Class 3 — Lead Assigned” badge appears in the modal header, confirming that a qualified lead is on the team. If no lead has been selected yet, the badge color updates to reflect that gap.

The certification status is pulled from the technician’s Salesforce record, so it stays current as people earn new credentials or as certifications expire. If a dispatcher tries to dispatch a team without a required lead, the workflow warns them before the crew rolls out.

This kind of rule lives in your Salesforce data, not hard-coded in the calendar. Your admin can adjust the thresholds, add new certification types, or change which job classifications require a lead, all without modifying the DayBack action code.

Equipment Allocation

Field work usually requires more than people and a truck. Crews need tools, safety gear, materials, or specialized equipment. This workflow includes an equipment checkout step where the dispatcher selects the required items from an inventory list maintained in Salesforce.

Each item shows current availability, so dispatchers know immediately if something is already checked out to another crew. When the team is dispatched, the selected equipment is reserved against the job, preventing double-allocation later in the day.

After the job, equipment can be checked back in through a follow-up action, closing the loop on asset tracking without requiring a separate system.

One Screen, One Decision

The point of this workflow is to collapse a series of decisions (who, which lead, what vehicle, what equipment, when to leave) into a single, well-organized screen. The dispatcher doesn’t need to open Google Maps in a separate tab, check a vehicle spreadsheet, or call a supervisor to verify certifications. Everything is right there, updated in real time, and connected to the data already living in Salesforce.

When they click “Dispatch Team,” the calendar events are created, equipment is reserved, and the crew’s schedule is updated. The entire interaction takes less than a minute.

Adapting This to Your Operations

The example here is built around trail maintenance crews, but the pattern applies anywhere you’re scheduling a team and sending them to a location:

• Mobile healthcare — dispatch clinical teams with the right credentials and supplies to patient locations.
• Utility and telecom — dispatch repair crews with the right certifications and equipment to job sites across a service territory.
• Construction — scheduling daily crews for multi-trade projects, accounting for travel time between sites.
• Environmental and survey teams — coordinate field scientists, sampling equipment, and vehicles for remote locations.
• Property maintenance — route technicians to service calls with traffic-aware scheduling and tool requirements.

The specifics change, but the core challenge is the same: get the right people, with the right gear, to the right place, at the right time. And know when they’ll be back.

How It’s Built

Everything here is built on top of the extensibility layer that’s available to every DayBack customer. The workflow is implemented as a DayBack custom action that runs inside the calendar and interacts with your Salesforce data through DayBack’s action framework. The team roster and equipment inventory come from your standard or custom Salesforce objects, and all the business rules (certification requirements, difficulty thresholds, equipment availability) are configured in your org.

Want to Build Something Like This?

If your team spends time each morning juggling crew assignments, checking availability across systems, or estimating drive times by hand, this kind of workflow can make a real difference. We build these as part of our implementation packages, tailored to your specific operations, data model, and scheduling rules.

Reach out to our team and tell us about your crew scheduling challenge. We’ll walk through how DayBack can help and what an implementation would look like for your organization.