edge.by truckaurbus.
Talk to the desk

Products

Who you are

The record

Research

Field note / Contract performance

An uptime promise needs a shared clock.

A service commitment becomes useful when everyone can establish when it started, what interrupted it and when the vehicle returned to work.

Buses and service infrastructure in a public transport depot
Operating context
01

Start with the promise

An availability commitment may look simple on the first page of an agreement. Its practical meaning lives in the definition of an eligible event, the exclusions, the evidence required and the point at which the clock begins.

For a fleet and its service partner, the useful first task is to write those definitions down together. A driver reporting a fault, a workshop accepting the vehicle and a technician starting work are different events. The contract may attach consequences to one of them.

The principle

An observation is not yet an agreed event.

02

Keep the records separate before reconciling them

An operating log can show that a vehicle missed a duty. A workshop record may show that it was mechanically serviceable. A charging record can describe an interruption at the depot. Each observation has a scope; none alone necessarily explains the whole event.

A sound event timeline retains the source and timestamp of every observation. Conflicts become questions for review. An absent location signal remains an absent signal until other evidence establishes what happened.

edge. Contract performanceIllustrative
Let the contract explain the accountTRN-1049 · detention and rate reconciliation
Gate in08:00
6 h free4 h chargeable
Gate out18:00
4 hours×₹3,000 / h=₹12,000
ChargeInvoicedSupported
Linehaul₹2,40,000₹2,40,000
Detention₹18,000₹12,000
Other agreed₹6,000₹6,000
Account for review₹2,58,000Difference₹6,000

Explore the working example

03

Make the monthly account reviewable

The proposed account should connect each adjustment to a clause, the events used in its calculation and the documents supporting those events. A reviewer should be able to reproduce the time window and the amount without trusting a summary.

Keep agreed facts, agreed calculations and disputed interpretations distinct. This lets a counterparty accept the parts it can establish while the remaining question is resolved. It also makes recurring evidence gaps easier to address in the next reporting cycle.

The review question

Clause, event window, proposed account.

04

Measure what gets accepted

An exception detected is the beginning of work. The useful outcome is a supported account, an accepted correction or a documented reason that no adjustment applies. Track those results alongside review effort and resolution time.

In a design partner engagement, Edge starts with one operating cycle and an agreed definition of success. That provides a practical basis for deciding which parts of the process are worth operating repeatedly.

This field note explains the proposed approach. Scope, evidence requirements and commercial terms are agreed for each engagement.

The next conversation

Discuss your next programme.

Tell us the decision, the institution and the evidence available. We’ll help define a focused first engagement.

Start a conversation

Talk to the desk.

Tell us who you are and the decision you are pricing. The first conversation costs nothing. A reply comes on working days.

Or write to [email protected].