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. That includes a ground run or ferry flight logged during maintenance, since those move the meter too. 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 both defend the same fact (that the start meter on a new flight should equal the end meter on the previous flight), but they do so 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 mismatch. Change it to something that does not follow on and a line under the Start says where the last flight ended.
- The look-back check is the safety net before money moves. Because pre-fill is editable (and skipped on edit-mode), it cannot guarantee continuity. The look-back check runs on every leg as soon as a flight is logged, and the pilot and the admins get a Flight logs don’t follow on alert when the values have drifted apart (a mismatch with an earlier booking waits ten quiet minutes first, in case more legs are still uploading). It runs again when the booking is closed or finalised, where it gates the pilot’s close and auto-finalisation. See tacho-continuity conflict.
Together they give you “easy by default, but verified before money moves”.