Operating Decisions

operating decisionsdecision

Routes, schedules, assignments and trips: what each record should control

When route planning, recurring rules, resource commitments and daily execution are stored as the same thing, transportation becomes difficult to control.

Review your route and schedule model Explore Codefy ERP

Decision summary

A route controls geography and movement logic.

A schedule controls recurring timing and service rules.

An assignment controls execution responsibility and commercial readiness.

A trip records dated execution without overwriting the recurring plan.

Operating chain

What must connect

01Route

02Schedule

03Assignment

04Trip

Warning signals

One giant trip table stores every rule and every execution event.

Teams edit every future trip manually after a resource or price change.

Historical supplier, driver, or vehicle context is overwritten.

Supplier pricing exists only on trips, not in the plan that generated them.

Planned versus actual history disappears after exceptions are handled.

Controls to define

Separate geography from recurring timing.

Use schedule assignments for route and schedule operation responsibility.

Use validity dates for supplier, driver, vehicle, and price changes.

Keep generated trips linked to the schedule context that created them.

Codefy connection

How Codefy ERP separates these records

Codefy ERP uses route schedules for recurring transport rules and schedule assignments for the driver, vehicle, supplier, working days, and validity context that generated trips rely on.

The transportation module treats schedule assignments as the canonical schedule-level assignment source.

Generated trips can preserve schedule, assignment, resource, GPS, attendance, and commercial context.

Supplier, fleet, and finance modules then read a clearer operating trail.

Employee and Student Transportation Supplier Management and Payables Fleet Management

Four concepts that solve different problems

Route, schedule, assignment, and trip should not be treated as synonyms. Each record answers a different operational question: where does movement happen, when does it repeat, who is responsible for execution, and what happened on a specific date.

Route

The route defines geography and movement logic: origin, destination, stops, direction, and service pattern. It should not carry every driver or supplier change that happens over time.

Schedule

The schedule defines recurring timing and service rules: working days, shift, departure time, direction, transport mode, and expected passenger demand. It explains when the route should operate.

Assignment

The assignment defines execution responsibility and commercial readiness: supplier or owned fleet, driver, vehicle, validity period, working days, supplier price, and vehicle requirement.

Trip

The trip is the dated execution created from the plan. It should preserve what actually happened, including replacements, completion, attendance, incidents, tracking signals, and financial results, without destroying the recurring plan.

Why effective dates matter

A supplier, vehicle, driver, or rate may change next month while historical trips must retain the previous context. Effective dates let operations change the future without rewriting the past.

Common modeling mistakes

Common mistakes include one giant trip table, editing every future trip manually, overwriting historical assignments, storing supplier pricing only on trips, and losing planned versus actual history.

Related pages for this decision

Operating Decisionsdecision

How to structure employee transportation from client contract to daily trip

Define the operating hierarchy before generating trips.

Continue with this guide

Operating Decisionsdecision

What should be validated before tomorrow's transportation trips are generated

Treat trip generation as a validation boundary, not a blind batch process.

Continue with this guide

Operating Decisionsdecision

Planned versus actual transportation: what management should really measure

Start with what was supposed to happen.

Continue with this guide

FAQ

Questions buyers usually ask

What is the most important split in transportation data modeling?

Separate recurring planning records from dated execution records. Routes, schedules, and assignments define the plan. Trips record what happened on a specific date.

Why do assignments need validity dates?

Validity dates let teams change resources or pricing for future service while keeping historical trips tied to the context that actually applied at the time.