An ABA field schedule travel matrix estimates whether home and community visits fit when service time, route time, transitions, documentation, breaks, staff starting points, traffic conditions, parking, and other paid work are included. It uses time bands and route evidence instead of straight-line distance alone. Wage-hour treatment, payer reimbursement, mileage or expense policy, and clinical scheduling remain separate decisions.

Build rows for real travel legs

Record origin type, destination, departure window, route band, parking or entry time, equipment load, expected travel, high-percentile travel, transition tasks, service window, and source date. Keep home-to-first-site, site-to-site, break travel, last-site-to-home, special assignment, and overnight travel as distinct leg types.

Use a matrix with defined assumptions

A practical row includes staff home base or starting category, origin site, destination site, day and time band, ordinary route estimate, high-traffic estimate, parking or access time, walking, equipment handling, required handoff, documentation, and source date. Avoid storing more precise home information than the approved purpose requires.

Version the matrix when traffic patterns, site access, construction, territories, or service windows change. The matrix is a planning input. Actual payable time and expense reimbursement follow the governing rules and the employee's real work.

Separate payroll from reimbursement

DOL Fact Sheet 22 says travel from job site to job site during the workday is work time under the FLSA, while ordinary commuting generally is outside work time. Actual facts, classification, agreements, and state or local law can change treatment. Payer reimbursement and mileage or expense policy answer different questions.

Calculate a complete field-day denominator

Start with paid capacity for the workday, then subtract assigned services, compensable travel and transitions, meetings, training, documentation, breaks under applicable rules, and fixed duties. Reserve a realistic contingency for traffic and urgent work. Do not divide available hours only by session length.

For planning, total day demand equals service minutes plus each associated travel and transition segment plus other scheduled duties. Compare that demand with the reviewed paid-time model. If the route crosses overtime, meal, rest, or expense thresholds, route the actual facts to the workforce owner before release.

Reserve the full transition

Include parking, security, walking, equipment setup, required calls, record access, handoff, approved documentation, and the next departure. A 20-minute drive can require a 35-minute transition. Record which tasks may occur during paid time and which require a separate location or privacy control.

Use time bands and sensitivity cases

Test ordinary, high-traffic, severe-weather, school-dismissal, and event conditions where relevant. Schedule against a planning percentile selected from observed data rather than the fastest route. For a tight transition, calculate how a 10- or 20-minute delay affects arrival, service duration, family notice, later visits, and overtime.

A route that succeeds only under the ordinary estimate has little operating margin. The practice can change the visit time, territory, staff start point, documentation plan, or client sequence instead of treating repeated lateness as an individual performance issue.

Use service and clinical gates

A route that fits on a map may still fail the client's service window, staff qualification, supervision, access, safety, or clinical needs. The BACB Ethics Code addresses competence, resources, supervision, risk, and documentation for covered professionals. Operations should route case-specific fit to the qualified clinician.

Protect client and staff information

Give schedulers and routing tools only the location and service details needed for planning. Restrict home addresses, safety instructions, health information, and free-text notes by role. Use approved devices and maps, and define what may be cached, printed, or shared with a substitute.

When a travel vendor or system processes protected information, confirm the applicable privacy, security, and contract route. A convenient consumer map does not automatically become an approved clinical scheduling system.

A fictional route calculation

Maya has an 8-hour paid field day. Two visits use 2.5 hours each. The matrix reserves 55 minutes for the first transition, 45 for the second, 30 for documentation, and 30 for a meal period under the practice's reviewed rules. Total planned time is 7 hours 40 minutes, leaving 20 minutes of contingency. A third visit cannot fit.

Stress-test Maya's schedule

The two visits use 300 minutes. Transitions use 100 minutes, documentation 30, and the meal period 30, for 460 minutes. An eight-hour day provides 480 minutes, leaving the stated 20-minute margin. A 25-minute traffic overrun would exceed planned capacity by five minutes and affect the second visit or later work.

This arithmetic check is why the matrix should show every component. The practice can adjust visit timing, route, documentation block, or staffing before a narrow margin becomes routine lateness or overtime. Any meal-period treatment must follow the reviewed rule for the actual jurisdiction and facts.

Compare plan and actuals

Track planned and actual travel by band, late arrivals tied to routes, paid travel share, overtime exposure, canceled service, mileage or expense exceptions, and transitions missing required tasks. Refresh a route after a new site, schedule, traffic pattern, parking rule, construction project, service window, or staff starting arrangement.

Maintain the matrix from real observations

Sample planned and actual departure, arrival, parking, setup, and handoff times without using surveillance beyond the approved purpose. Review medians and higher-percentile values by route band. Separate staff-controlled delays from system, traffic, site, or family factors.

Retire stale route rows and keep their effective dates for historical review. Owners should see which territories regularly consume more paid travel or create service loss, then decide whether to redraw territories, shift start times, or change capacity promises.

A route-change example

A school visit ends at 2:30 p.m., and a home visit begins at 3:15. The ordinary map estimate is 22 minutes, but dismissal traffic raises the reviewed planning estimate to 34 minutes. Parking, walking, equipment transfer, and the required handoff add 12 minutes. The real transition is therefore 46 minutes before any unexpected delay, so the visits do not fit as scheduled.

The owner can move the second start, change the assignment, adjust the territory, or revise another operational component after the applicable checks. Shortening service solely to protect the calendar would require its own clinical and payer review. Record the rejected route and reason so a later scheduler does not restore the same fragile pairing.

Owner travel-matrix questions

Ask which route bands rely on generic estimates, which transitions repeatedly consume contingency, and whether the matrix includes every paid or required task. Compare plan with actuals by time band without turning location data into unnecessary surveillance. Also check whether a route change affects family notice, access support, overtime, expense reimbursement, or later visits. The planning model should make these dependencies visible while qualified workforce and legal owners decide the governing treatment.

Use a named owner and effective date for each material route assumption. A newer observation should update future planning without rewriting what the earlier schedule relied on.

Related resources

Sources