Skip to content

Previous-tacho pre-fill

Previous-tacho pre-fill is the small convenience that, when you open the Log Flight screen for a new flight, the Start meter value is already filled in with the End meter value of the most recent log on that asset. You only have to type the end number.

The value is a suggestion, not authoritative. You can edit it freely, and the edited value is what Syndik8 saves. Pre-fill applies only on create; editing an existing log shows the log’s own saved Start.

Pre-fill is the nudge; the look-back check is the safety net

Section titled “Pre-fill is the nudge; the look-back check is the safety net”

The pre-fill and the auto-finalise look-back continuity check defend the same fact — that the start meter on a new flight should equal the end meter on the previous flight — but at different points in the workflow:

  • Pre-fill is the front-line defence at data entry. It removes the typing step where most continuity errors are introduced. If you accept the pre-filled value as-is, you cannot accidentally invent a discrepancy.
  • The look-back check is the safety net at finalisation. Because pre-fill is editable (and skipped on edit-mode), it cannot guarantee continuity. The look-back check re-verifies at submit time and gates auto-finalisation when the values have drifted apart — see tacho-continuity conflict.

Together they give you “easy by default, but verified before money moves”.