Spreadsheet column referenceCopy link
This page lists every column Routing24 can read from a spreadsheet, sheet by sheet, with the header spellings it accepts, the format each cell expects, and example values.
Download template (on the Home page, or under More on any list page) gives you a workbook with these headers and example rows, and Import from Excel or CSV walks through the upload and review.
A workbook has up to four data sheets:
- Orders: one row per stop, with time windows, loads, service times, and tags.
- Depots: the places where routes start, end, and reload.
- Vehicles: capacities, shifts, costs, and break rules.
- Addresses: standalone Address Book entries.
Two sections come first: the matching rules that apply to every sheet, and the time and duration formats used throughout.
How columns are matchedCopy link
Routing24 recognizes a column by its header text, not by its position.
The rules:
- Any order works. Only the header row matters.
- One canonical name, plus aliases. In the tables below, the name on the left is the canonical one, used by templates and exports. Every spelling listed under Aliases imports the same way.
- Unrecognized columns are ignored. Extra columns (your own notes, bookkeeping, formulas) are skipped.
- Only ids and addresses are required. An order needs an Id and an Address, a depot the same, an Address Book row an Address, and a vehicle only an Id. Every other column is optional, and an empty cell means "no limit" or "use the default".
How to read the tablesCopy link
Each table row documents one column:
- The left cell shows the canonical header, with its accepted aliases underneath.
- The first line on the right gives the format, whether the column is required, and, where it applies, Import only or Export only. Everything else round-trips both ways.
- A PRO or STARTER pill marks a column that belongs to a paid tier. Import and export work on any tier; the tier matters when you optimize. See Plans, billing, and free limits.
- Below that: what the column means, its rules, and one or two example values.
The tables below are generated from the same column definitions Routing24 uses to read and write workbooks. The Documentation sheet inside every export repeats them next to your data.
They are shown here in kilometers and the 24-hour clock. Your own workbook
follows your location and browser: in the United States that means miles and
12-hour times (Cost, mi, 3:30pm), while in most of Europe it means
kilometers and 24-hour times (Cost, km, 15:30). Both spellings import
either way, and you can override the choice in Settings.
Time and duration formatsCopy link
Times and durations appear on every sheet: order windows, vehicle shifts, depot opening hours, service times. Two rules cover all of them:
- Times (windows, shifts, opening hours):
HH:MMin the 24-hour clock, like08:00or15:30. If your Settings use the 12-hour clock,8amand3:30pmwork too. - Durations (service time, max duration): minutes as a plain number
(
45is 45 minutes), orH:MM(1:30is an hour and a half).
On import, a time cell may hold plain text in any of these shapes:
| You type | Read as |
|---|---|
08:00, 8:00 | 08:00 |
8 | 08:00 (bare hour) |
8:00:30 | 08:00:30 (seconds allowed) |
8am, 8 AM, 3:30pm | 08:00, 15:30 |
12am / 12pm | midnight / noon |
Anything else (0830, 8.30, 8h30) is not recognized, and the cell is
treated as empty. Duration columns follow the same rules, plus the
plain-number-means-minutes shortcut.
Columns marked Format: Time * are written by exports as a real
Excel time value,
not as text. Excel stores a time as a fraction of a day: 12:00 is the number
0.5, 08:00 is 0.333…, and the cell's number format is what displays it
as 08:00. That is why a time cell may look different after you change the
column format, or show as a decimal if you clear the formatting. Real time
values sort correctly and work in formulas such as =B2-A2 for a window's
length.
On import, the plain-text shapes in the table above are also accepted.
Distance units follow your Settings: Cost, km reads Cost, mi on an
imperial profile, and both spellings import on either.
Day offsets: times on a later dayCopy link
A time column says what time, never which day. For multi-day plans, each
time column has a paired ... day column that carries the day, counted from
the start of the plan: empty (or 0) is the first day, 1 the next day, 2
the one after.
A stop open from 6pm until 2am the following morning:
| Open from | Open from day | Open to | Open to day |
|---|---|---|---|
18:00 | (empty) | 02:00 | 1 |
Without the 1, the window says 18:00 to 02:00 on the same day, which ends
before it begins, and the order becomes unservable.
The Excel export writes it the same way: a cell holding 1 displays as
+1 days.
The pairing works everywhere a time appears: vehicle shifts
(Shift end day), depot opening hours, the depot release time
(Ready from day), and each extra service window. Multi-day planning is free,
so none of the ... day columns carry a tier badge.
Address columns (Orders, Depots, and Addresses sheets)Copy link
Every sheet that holds a place uses the same five columns to say where it is. Give an address, coordinates, or both; an address without coordinates is geolocated during import.
| Column | Meaning |
|---|---|
| AddressAliasesAdress | Format: Text·Required Street address in free format. Address will be geolocated automatically during Excel import if coordinates are not provided. If address is not known, a unique string and geographical coordinates should be used instead. Example: |
| AreaAliasesCity | Format: Text·Optional Address country, state, city, or area name in free format. Can be specified in addition to address to increase address geolocation quality. Example: |
| LatAliasesLatitude | Format: Number·Optional Address latitude. When used, must be defined together with "Lng". If omitted, the address will be geolocated automatically during Excel import. Example: |
| LngAliasesLonLongitude | Format: Number·Optional Address longitude. When used, must be defined together with "Lat". If omitted, the address will be geolocated automatically during Excel import. Example: |
| LocationAliasesCoordinatesLat/Lng | Format: Text·Optional·Import only Address geo coordinates as "Latitude, Longitude" string. This column can be defined in import file instead of two separate columns "Lat" and "Lng". This format is useful to copy-paste coordinates from Google Maps or another online map. Example: |
Orders sheetCopy link
One row per stop. Beyond the id and address, the columns cover loads and transfers, time windows, service time, priority, and the tags that steer which vehicle may serve the stop.
| Column | Meaning |
|---|---|
| IdAliasesCode | Format: Text·Required A unique order identifier. Any unique string in free format. Example: |
| Order typeAliasesTransfer typeOrder kind | Format: Text·OptionalPRO What this order is: "depot" (a regular order served from the depot, the default), or one end of a site-to-site transfer: "pickup" or "delivery". A "depot" order is served from the depot: the load in "Delivery" is loaded at the depot and delivered to the site, and the load in "Pickup" is picked up at the site and brought back to the depot (reverse logistics). Leave the column blank (or "depot") for this regular kind of order. A "pickup" or "delivery" order is one end of a load moved between two sites: the load is picked up at the "pickup" order and delivered to the "delivery" order by the same vehicle on the same route, pickup first. Give both rows the same "Transfer id" to link them into one pair. Example: |
| Transfer idAliasesTransfer IDTransfer | Format: Text·OptionalPRO The shared id that links the pickup row and the delivery row of one site-to-site transfer. Set the same id on both rows. Rows sharing a transfer id form one transfer: one with "Order type" = "pickup" and one with "Order type" = "delivery". The load is then picked up at the pickup site and delivered to the delivery site on the same route; the "Pickup" amount must equal the linked "Delivery" amount. Several rows with the same role are alternative locations for that end (the solver serves exactly one per role). Leave blank for a regular "depot" order: it is served from the depot and has no linked partner. Example: |
| Pickup | Format: Number·Optional Load to be picked up from this stop. Defined using the same units as vehicle capacity, (weight, volume, items, seats). If not defined, no load is picked up at this stop. For a regular ("depot") order the load is brought back to the depot; for a "pickup" transfer order (see "Order type") it is carried to the linked delivery order. The load to be picked up must fit into one of the available vehicles; the vehicle's capacity must be greater than or equal to the load size. Example: |
| DeliveryAliasesQuantity | Format: Number·Optional Load to be delivered to this stop. Defined using the same units as vehicle capacity, (weight, volume, items, seats). If not defined, no load is delivered to this stop. For a regular ("depot") order the load is loaded at the depot; for a "delivery" transfer order (see "Order type") it arrives from the linked pickup order. The load to be delivered must fit into one of the available vehicles; the vehicle's capacity must be greater than or equal to the load size. Example: |
| Priority | Format: Number·Optional Relative importance of serving this order (1 to 1000). Every order is optional. When the fleet cannot serve all of them, higher-priority orders are kept and lower-priority ones are dropped first. Defaults to 1 when not set. Use a large value (e.g. 1000) for "serve this unless physically impossible". Example: |
| Open fromAliasesOpen at | Format: Time *·Optional Site time window start. Earliest time when the job can be started at this site. If not defined, the job can be started at any time. Add "Open from 2".."Open from 4" (+ matching "Open to N") columns for alternative delivery windows. Example: |
| Open from day | Format: Number·Optional Relative day of the site time window start. If not defined, time window starts on the same day. For value of "1", time window starts on the +1 day (next day), etc. Example: |
| Open toAliasesOpen until | Format: Time *·Optional Site time window end. Latest time when the job can be started at this site. If not defined, the job can be started at any time after time window start. Example: |
| Open to day | Format: Number·Optional Relative day of the site time window end. If not defined, time window ends on the same day. For value of "1", time window ends on the +1 day (next day), etc. Example: |
| Open from 2 .. Open from 4AliasesOpen at 2Open at 3Open at 4 | Format: Time *·Optional Start of an additional delivery window. An order with several windows is delivered within exactly ONE of them. Up to 4 windows per order: "Open from 2".."Open from 4" with the matching "Open to N". Example of two windows: "Open from" = 08:00, "Open to" = 10:00, "Open from 2" = 16:00, "Open to 2" = 18:00 — the order is delivered 08:00–10:00 OR 16:00–18:00. Example: |
| Open from 2 day .. Open from 4 day | Format: Number·Optional Relative day of an additional delivery window start. If not defined, the window starts on the same day. Example: |
| Open to 2 .. Open to 4AliasesOpen until 2Open until 3Open until 4 | Format: Time *·Optional End of an additional delivery window. See "Open from 2". Example: |
| Open to 2 day .. Open to 4 day | Format: Number·Optional Relative day of an additional delivery window end. If not defined, the window ends on the same day. Example: |
| Job timeAliasesService time | Format: Number·Optional Duration of the job or service at the stop, minutes. If not defined, the vehicle will depart from the stop immediately after arrival. Example: |
| Ready fromAliasesRelease atReady at | Format: Time *·Optional Depot release time for the site load. Time when the load is ready to be picked up at the depot. If not defined, load is available for pick up at depot from the opening time. Example: |
| Ready from dayAliasesRelease at dayReady at day | Format: Number·Optional Relative day of the depot release time. If not defined, release time is on the same day. For value of "1", release time will be on +1 day (next day), etc. Example: |
| Max time in vehicleAliasesShelf lifeMax ride time | Format: Number·OptionalPRO Max time in vehicle (shelf life), minutes. On a plain order, service must start within this many minutes of the order's "Ready from" time. The clock is pinned there: without a "Ready from" time it runs from the start of the planning horizon (00:00 on day 0), which is stricter, so set "Ready from" whenever you use this column. It covers the "Delivery" load only. Import ignores the cell with a warning and brings the order in unconstrained when the order also carries a "Pickup" load, or when its opening hours all open later than "Ready from" plus this value; the same combination authored in the order editor stops the optimization with an error. On a linked (pickup & delivery) order, this instead bounds the ride time from pickup to delivery (the planner delays loading where that shortens the ride, so only unavoidable waiting counts; a reload does not reset the clock) -- set the same value on every end of the transfer; ends that disagree are warned about and the whole transfer is skipped at optimization. Driver breaks combine with a bounded linked order: break placement avoids the pickup-to-delivery span where it can, and a break placed inside it counts as ride time, charged against "Max ride overtime"; beyond that allowance the bound is hard and the transfer is unassigned with the "Max time in vehicle" reason. Leave blank for unlimited. Example: |
| Max ride overtimeAliasesRide overtime allowance | Format: Number·OptionalPRO Max ride overtime (linked orders only), minutes. Linked (pickup & delivery) orders only: ride time in minutes past "Max time in vehicle" that is still allowed, priced by the vehicle's "Cost, ride overtime hour" (Vehicles sheet). Beyond this allowance the bound is hard. The value does not apply to a plain order: import reports an error and skips that row, and the solver leaves such an order unassigned. An allowance with no "Max time in vehicle" to extend is ignored with a warning on import, and stops the optimization with an error when it reaches the solver. Set the same value on every end of the transfer; ends that disagree are flagged on import and the whole transfer is skipped at optimization. Leave blank for no allowance (the bound is hard). Example: |
| Required tagsAliasesTags required | Format: Text·OptionalPRO Tags a vehicle must carry to serve this order. A comma-separated list of tags. A vehicle may serve this order only if it carries every one of these tags (see the vehicle "Tags" column). Example: |
| Forbidden tagsAliasesTags forbidden | Format: Text·OptionalPRO Tags a vehicle must NOT carry to serve this order. A comma-separated list of tags. A vehicle carrying any of these tags may not serve this order. Example: |
| GroupAliasesAlternative group | Format: Text·OptionalPRO Alternative order group name. Orders sharing a group name are alternatives: the solver serves at most one of them (whichever fits best) and leaves the rest as "not chosen" rather than unassigned. Leave blank for a standalone order. Example: |
| No breakAliasesNo breaks | Format: Text·Optional Driver breaks: "Yes" forbids scheduling a driver break while waiting at this stop. Blank allows breaks (the default). Example: |
| Sequence groupAliasesSequence | Format: Text·OptionalPRO Sequence group name: these orders run together, in order. Orders sharing a sequence group are served all-or-none, by ONE vehicle, in non-decreasing "Sequence rank" order (other stops may come between them). 2 to 16 orders per group; a member cannot also be a transfer end or an alternative-location candidate, and has one service window. Goods move along the run using the members' own "Pickup" and "Delivery" amounts: a pickup at one stop feeds the deliveries of later-ranked stops, so a run picking up 5 and then dropping 3 and 2 leaves the depot empty and peaks at 5 on board. Runs may span reloads; cargo picked up on the run rides through them. Leave blank for an unconstrained order. Example: |
| Sequence rankAliasesSequence order | Format: Number·OptionalPRO Position within the sequence group (lower runs first). A non-negative whole number; orders with equal ranks may run in any order relative to each other. Ignored without a "Sequence group". Example: |
| Load classAliasesProduct class | Format: Text·OptionalPRO Product class for vehicle-level segregation. Which classes may not share a route is set per vehicle in the Vehicles sheet's "Do not mix" column: a vehicle never serves two classes of one of its groups on one route (reload trips included). A class listed in no vehicle group costs nothing. Both ends of a transfer must carry the same class. Leave blank for a classless order (never conflicts). Example: |
| Unplanned | Format: Text·Optional·Export only Why this order was left unplanned (solution export only). Present only on an exported solution; blank when the order was served. Not read on import. Example: |
Plus the address columns above. For what these fields do to a route, see Time windows, service time, priority, and load, Pickup & delivery transfers, Alternative pickup & delivery locations, and Order sequences.
Depots sheetCopy link
One row per depot: its id and address, opening hours, and the handling time a visit there takes.
| Column | Meaning |
|---|---|
| IdAliasesCode | Format: Text·Required A unique identifier for the depot. Example: |
| Handling timeAliasesService time | Format: Number·Optional Handling time spent at the depot on each visit (load/unload). Enter minutes (e.g. 15) or an HH:MM duration. If not defined, no handling time. Example: |
| Open fromAliasesOpen at | Format: Time *·Optional Depot opening time. Earliest time a vehicle may depart from / arrive at it. If not defined, the depot is open at any time. Example: |
| Open from day | Format: Number·Optional Relative day of the depot opening time. For value of "1", opening is on the +1 day (next day), etc. Example: |
| Open toAliasesOpen until | Format: Time *·Optional Depot closing time. Latest time a vehicle may depart from / arrive at it. If not defined, the depot is open at any time. Example: |
| Open to day | Format: Number·Optional Relative day of the depot closing time. For value of "1", closing is on the +1 day (next day), etc. Example: |
| No breakAliasesNo breaks | Format: Text·Optional Driver breaks: "Yes" forbids scheduling a driver break while waiting at this depot (including reload stops). Blank allows breaks (the default). Example: |
Plus the address columns above.
Vehicles sheetCopy link
One row per vehicle type: capacity and count, start and end depots, shift times, costs, and the paid-tier columns for tags, route limits, and driver breaks.
| Column | Meaning |
|---|---|
| IdAliasesCode | Format: Text·Required A unique identifier for the vehicle type. Example: |
| Capacity | Format: Number·Optional Vehicle capacity. Total load a vehicle can carry, in user-defined units (e.g., weight, volume, items, seats). If not defined, the vehicle will have unlimited capacity. Note that the vehicle capacity must be greater or equal to the orders load. Example: |
| CountAliasesAvailable | Format: Number·Optional Total number of vehicles of this type available for planning. If not defined, only one vehicle of this type will be available. Example: |
| Start depotAliasesStart depot id | Format: Text·Optional Identifier of the depot where the vehicle starts its route. The value must match the ID of a depot defined in "Depots". If not defined, vehicle starts its route from the first order. Example: |
| Reload depotsAliasesReload at | Format: Text·OptionalPRO Depots this vehicle may reload at mid-route (comma-separated depot ids). Setting this (or "Max reloads") enables multi-trip: the vehicle can return to one of these depots to unload/reload and keep serving orders. If left empty while "Max reloads" is set, the vehicle reloads at its own start depot. Example: |
| End depotAliasesEnd depot id | Format: Text·Optional Identifier of the depot where the vehicle ends its route. The value must match the ID of a depot defined in "Depots". If not defined, vehicle ends its route at the last order. Example: |
| Cost, fixedAliasesFixed cost | Format: Number·Optional Vehicle fixed cost. Added to the total cost of the route once, when vehicle of this type is selected for a route. Example: |
| Cost, kmAliasesCost, miDistance cost | Format: Number·Optional Vehicle distance cost per km. Added to the total cost of the route for each kilometer a vehicle of this type travels. An empty cell means 0. When no vehicle in the plan has a distance or time cost, the optimizer minimizes plain travel distance instead. Example: |
| Cost, hourAliasesTime cost | Format: Number·Optional Vehicle time cost per hour. Added to the total cost of the route for each hour a vehicle of this type spends on the route. An empty cell means 0. Note that the vehicle's time on route includes not only travel time but also any job and waiting time. Example: |
| Cost, stopAliasesStop cost | Format: Number·Optional Vehicle cost per stop. Added to the total cost of the route for each stop the vehicle makes, excluding depot and reload visits. A pickup and its linked delivery count as two stops. Example: |
| Cost, overtime hourAliasesOvertime cost | Format: Number·OptionalPRO Vehicle overtime cost per hour, in addition to the time cost per hour. Charged on top of the regular time cost for each hour of overtime (time worked beyond the max duration, up to the max overtime). If overtime is allowed but this is left empty, it defaults to the time cost per hour, or to 1 per hour when that is 0 or empty, so overtime is never free. An explicit 0 makes overtime free. Example: |
| Cost, ride overtime hourAliasesRide overtime cost | Format: Number·OptionalPRO Cost per hour of a linked (pickup & delivery) order's ride time inside its ride overtime allowance. Charged for ride time past a linked order's "Max time in vehicle", up to its "Max ride overtime" allowance (see the Orders sheet). Beyond the allowance the bound is hard. A driver break taken between the pickup and the delivery counts as ride time and is charged the same way. Left empty or 0, that allowance is free. Example: |
| Load cost, kmAliasesLoad cost, miLoad distance cost | Format: Number·OptionalPRO Cost per unit of load carried per km (or mile), charged on every leg for the load on board. Each leg charges the load leaving its origin times the leg length, so heavier cargo is steered onto shorter paths and dropped early. Models load-dependent fuel or refrigeration burn. Counts as pricing the fleet, like the distance and hour rates. Left empty or 0, carriage is free. Example: |
| Shift startAliasesStart at | Format: Time *·Optional Vehicle shift time window start. Earliest time when the vehicle can start its shift. If not defined, the shift can start at any time. Example: |
| Shift start dayAliasesStart day | Format: Number·Optional Relative day of the shift time window start. If not defined, time window starts on the same day. For value of "1", time window starts on the +1 day (next day), etc. Example: |
| Shift endAliasesEnd at | Format: Time *·Optional Vehicle shift time window end. Latest time when the vehicle can end its shift. If not defined, the shift can be ended at any time. Example: |
| Shift end dayAliasesEnd day | Format: Number·Optional Relative day of the shift time window end. If not defined, time window ends on the same day. For value of "1", time window ends on the +1 day (next day), etc. Example: |
| Latest startAliasesStart by | Format: Time *·Optional Latest time the vehicle can start its shift (leave the depot). The vehicle can still work until the shift end. Distinct from the shift end: it caps only when the vehicle may start, not when it must finish. Must be between the shift start and shift end. If not defined, there is no latest-start limit (equivalent to the shift end). Example: |
| Latest start day | Format: Number·Optional Relative day of the latest shift start. If not defined, the latest start is on the same day. For value of "1", the latest start is on the +1 day (next day), etc. Example: |
| Max durationAliasesMax shift duration | Format: Number·OptionalPRO Maximum duration of a vehicle shift. Total time a vehicle of this type may spend on a route (travel + service + wait). If not defined, the shift duration is unlimited. Enter minutes (e.g. 480) or an HH:MM duration (e.g. 8:00). Example: |
| Max overtime | Format: Number·OptionalPRO Maximum overtime allowed on top of the max duration, at additional cost. Extra working time a vehicle may spend beyond the max duration, billed at the overtime cost per hour. If not defined or 0, no overtime is allowed. Enter minutes (e.g. 30) or an HH:MM duration (e.g. 0:30). Example: |
| TagsAliasesCapabilities | Format: Text·OptionalPRO Capabilities this vehicle carries (comma-separated). Free-form tags matched against order "Required tags" / "Forbidden tags". A vehicle may serve an order only if it carries every required tag and none of the forbidden tags. Example: |
| Do not mixAliasesSegregated classesIncompatible classes | Format: Text·OptionalPRO Product classes this vehicle must never carry together: ";" separates groups, "," separates classes within a group. Each group lists order "Load class" values that must never share one route of this vehicle (reload trips included). Groups are independent: "frozen, dry; fish, dairy" forbids frozen with dry and fish with dairy, but allows frozen with fish. A group needs at least two distinct classes; smaller groups are ignored with a warning. A class no order carries has no effect. Leave blank to allow any mix on this vehicle. Example: |
| Max reloadsAliasesReloads | Format: Number·Optional Maximum number of mid-route reloads (multi-trip). Multi-trip is on by default. The vehicle may return to a depot to reload and continue (a value of N allows N reloads, i.e. up to N + 1 trips). Leave empty for unlimited reloads (the solver self-limits). Set to 0 for a single trip (no reloads). Example: |
| Max distance, kmAliasesMax distance, mi | Format: Number·OptionalPRO Maximum route distance, in kilometers. Maximum distance a vehicle of this type may travel on a route. If not defined, unlimited. Example: |
| Force allowAliasesForce allow orders | Format: Text·OptionalPRO Order ids this vehicle may serve regardless of tags (comma-separated). Overrides tag compatibility for these orders only. "Force deny" wins over "Force allow". Example: |
| Force denyAliasesForce deny orders | Format: Text·OptionalPRO Order ids this vehicle may NOT serve regardless of tags (comma-separated). Overrides tag compatibility for these orders only. Wins over "Force allow". Example: |
| Break ruleAliasesBreaks | Format: Text·OptionalPRO Driver-break rule: "EU" (45 min before exceeding 4.5 h driving, splittable 15+30), "US" (30 min interruption after 8 h driving; stops of 30 min or more count), or "Custom" (define the rule with the "Break ..." columns). "EU" and "US" expand to the legal constants and ignore the detail columns. "Custom" reads them: "Break max driving, h", "Break duration", "Break split" and "Break service counts". Leave blank for no driving-triggered breaks (fixed breaks may still be set). At most one driving rule per vehicle. Example: |
| Break max driving, hAliasesBreak after driving | Format: Number·OptionalPRO Custom break rule: a break is required before the driver exceeds this much accumulated driving (hours, decimals allowed). Read only when "Break rule" is "Custom". Example: |
| Break durationAliasesBreak minutes | Format: Number·OptionalPRO Custom break rule: length of the required break. Read only when "Break rule" is "Custom". Enter minutes (e.g. 45) or an HH:MM duration (e.g. 0:45). Example: |
| Break split | Format: Text·OptionalPRO Custom break rule: optional split into two ordered parts, as "first+second" minutes (e.g. "15+30"). Only completing the second part resets the driving clock. Read only when "Break rule" is "Custom". Leave blank for an unsplittable break. Example: |
| Break service countsAliasesService counts as break | Format: Text·OptionalPRO Custom break rule: whether time at stops (service) counts toward the required break, US-style. "Yes" or blank. Read only when "Break rule" is "Custom". Example: |
| Fixed break from, Fixed break 2 from | Format: Time *·OptionalPRO Fixed break (e.g. lunch): earliest clock time the break may start. The break must START within the from-to window. Set "from", "to" and the duration together. Example: |
| Fixed break to, Fixed break 2 to | Format: Time *·OptionalPRO Fixed break: latest clock time the break may start. Set "from", "to" and the duration together. Example: |
| Fixed break duration, Fixed break 2 duration | Format: Number·OptionalPRO Fixed break: pause length. Enter minutes or an HH:MM duration. Set "from", "to" and the duration together. Example: |
| Driving limit, hAliasesPeriod driving limit | Format: Number·OptionalPRO Driving-hours budget per period (e.g. 56 per week under EU rules). The route is capped at the REMAINING hours: this limit minus "Hours driven". Example: |
| Hours drivenAliasesHours already driven | Format: Number·OptionalPRO Hours this driver has already driven in the current period (tracked outside routing24, e.g. from the tachograph). Never copied between vehicles; per-driver state. Example: |
The rules behind these columns live in Shifts, working hours, and route limits, Vehicle costs, Tags, Multiple depots, open routes, and reloads, and Driver breaks.
Addresses sheetCopy link
The Addresses sheet holds standalone Address Book entries and uses exactly the five address columns listed at the top: Address (required), Area, Lat, Lng, Location.
Next stepCopy link
Download a template from any list page's More menu: it ships with these headers, example rows, and a Documentation sheet that repeats this reference next to your data. Then see Import from Excel or CSV for the review flow.