Custom Solutions·Business Solutions & Strategy· 2 min read

Triplet Planning (Truck-Trailer-Driver) Without Rewriting History

In real operations, truck-trailer-driver combinations change frequently, sometimes 2-4 times in one shift. If your system cannot represent those changes over time, it rewrites history and creates errors in reporting, performance splits, and compliance control.

Jakub Bílý
Jakub Bílý

Head of Business Development

Triplet Planning (Truck-Trailer-Driver) Without Rewriting History

In real operations, truck-trailer-driver combinations change frequently, sometimes 2-4 times in one shift. If your system cannot represent those changes over time, it rewrites history and creates errors in reporting, performance splits, and compliance control.

Article series: Dispatch → Cash Flow  

Definitions

Definition: Reservation lifecycle
A set of states and transitions that define what “done” means over time and when an item becomes an exception. A practical minimal set:
Draft → Confirmed → Planned → In-Execution → Completed → Invoice-ready → Settled
Each transition has entry conditions (mandatory data / document / approval). If conditions are not met by the deadline, the item moves to Overdue/Exception .

Why this matters

When assignment is overwritten in place, you lose basic traceability:

  • who executed a specific segment
  • with which equipment
  • under which constraints

This impacts financial calculations and auditability.

Correct design approach

Use a time-aware assignment model:

  1. assignment is an event with valid_from and valid_to
  2. every change creates a new record, not overwrite
  3. ride execution references the assignment state valid at that time

This keeps history consistent even with multiple same-day changes, including swaps after only 1-2 hours.

Implementation notes

  • define which changes are audit-critical
  • keep planning speed high, not only data purity
  • ensure reports can reconstruct state for any date/time

Where custom development helps

This usually goes beyond standard setup. Custom implementation often covers:

  • temporal data model design
  • migration of legacy historical records
  • integration with payroll, performance, and compliance rules

Operational takeaway

If assignment changes rewrite the past, the system will not stay trustworthy. Time-based event modeling is foundational.

Recommended next reads

CTA

Seeing traceability issues after assignment changes? Book a model workshop with us.

Jakub Bílý

Jakub Bílý

Head of Business Development

Let's Drive Results Together!

Fill out the form, and we'll respond within 8 business hours.
We are happy to answer all your questions!
We'll analyze your project and discuss the details.

Get in Touch