Trip events and roles
Define arrival, entry and exit as distinct events. Capture when an event occurred, when it was recorded and which role supplied it.
Two dispatch teams can agree when a truck left and still disagree about how long it waited. GreyBath builds portals that keep each trip event, its evidence and the reviewer’s decision together. Start with one completed trip and reconstruct where the timings differ.
See the two-clock trip example
01 / What we build
Define arrival, entry and exit as distinct events. Capture when an event occurred, when it was recorded and which role supplied it.
Give drivers or coordinators a way to submit an event and supporting reference. Let an authorised reviewer compare versions and save the accepted time with a reason.
Show intervals with their event names, review status and any missing evidence. Provide an approved trip export for the accounts handoff.
City context, honestly stated
Karaikal Port’s operator describes truck loading for road cargo movement. This is an invented trip for an independent haulier. Its events and review steps are examples for the haulier’s own portal. GreyBath delivers remotely.
In the example, a truck reaches the haulier’s holding yard at 11:20. The gate slip records entry at 11:42 and exit at 12:17. The interval inside the gate is 35 minutes, and the interval from holding-yard arrival to gate exit is 57 minutes. Label both intervals and show which event started each one.
The driver’s first entry says 11:38 for gate-in. The dispatch reviewer compares it with the 11:42 gate slip and records 11:42 as the accepted value, with a reason and reviewer name. Preserve the driver’s original entry. A trip without a gate slip remains open for review under the haulier’s agreed evidence rules.
If the customer disputes the 57-minute figure, show the separate 22-minute interval from holding-yard arrival to gate entry and the 35-minute gate interval. Pass the approved events and supporting records to accounts. Which intervals qualify for a charge depends on the business’s own approved terms and decision process.
Where it fits
A spreadsheet can be enough when one dispatcher verifies every trip. A portal is useful when the driver, dispatch office and accounts team each hold a different part of the evidence and corrections need to remain traceable.
Choose the minimum set of events worth recording and define who owns their timestamps.
See whether the timing is reported, backed by evidence or still awaiting review.
Add a missing event or a permitted slip reference without rewriting a previously accepted time.
Review the approved trip intervals and supporting evidence against the customer’s agreed terms.
How we work
Enter the three events and confirm the review screen shows two clearly named time spans.
Compare the 11:38 driver entry with the 11:42 gate slip, record which value was accepted and confirm both entries remain visible to authorised reviewers.
Remove the exit evidence in a second trial. Check that accounts can see the missing item and the owner before the trip is approved for export.
Use one invented trip or a redacted example. Start with manual events and references that the business has permission to hold. Confirm the evidence policy, reviewer permissions and what the portal should export before discussing integrations.
Discuss your projectDefine what holding-yard arrival, gate-in and gate-out mean for your team. Record occurrence and entry times separately so late entries are visible.
Choose what a reviewer can accept, how corrections are recorded and how long references or attachments need to be held.
Choose the trip identifier and accounts destination. Check whether any external data source is available and authorised before estimating an integration.
It depends on the events being compared. The example shows 35 minutes inside the gate and 57 minutes from holding-yard arrival to exit. A charge decision is a separate review.
Yes. Preserve when it happened, when the entry was submitted and whether it has supporting evidence. A late entry can be reviewed under the same rules.
The first trial can use manual timestamps and permitted references. Any GPS or external system connection is a separate feasibility and permission decision.
Show the reported value and accepted value with reviewer, reason and revision date. Make it clear which approved value produced the exported interval.
An invented or redacted trip with two competing times, a sample evidence reference and the roles that review and export the record.
An elapsed time needs two agreed events.