Railway Time Tracking: Driving, Shifts and Traceability

Workday registration in a railway company cannot be reduced to installing a terminal at the door. A service may begin with a sign-on, continue with checks, driving, an operation-conditioned break, a handover outside the usual center, and end with closing tasks. In parallel, workshops and depots work with orders, positions, and shifts; stations combine customer service, operations, incidents, and location changes.

The record must distinguish working time from operational safety. Before choosing software, check the applicable railway requirements and demonstrable product functions. Do not assume Induly provides service planning, qualification management, work-order integration or legal alerts.

Executive Summary

Article 34.9 of the Workers' Statute requires recording the specific start and end time each day and keeping the records for four years.
For mobile workers in cross-border railway services there are additional sector rules: driving limits, breaks, and a daily record of working and rest hours kept for at least three years.
It is advisable to separate four dimensions: presence, effective work, driving, and activity or cost center. A single entry and exit button does not explain the operation.
The design must accommodate sign-on, handover, break, incident, center change, and sign-off, even with poor connectivity.
The audit must demonstrate integrity: identity, time stamp, correction history, validation responsible party, and legible export.

1. Why Railway Breaks the Simple Entry and Exit Model

In a stable office, entry and exit usually occur in the same building. In rail, the working day may start at a residence or depot, continue in the cab, pass through an intermediate station, and end at another location. A service delay can shift a break or handover. A station worker may cover a different position within the same shift. In depots, two people present for the same hours may charge their time to completely different work orders.

That is why the minimum data —start and end— satisfies a basic legal need, but is not enough to manage the operation. The system must be able to answer, without mixing concepts:

When did the workday begin and end?
What part was driving, preparation, accompaniment, intervention, or break?
Where did the sign-on and sign-off take place?
To which service, shift, order, or center was the activity charged?
Who corrected a record and why?

Attendance records, time study of an operation and statistical estimation of activity shares answer different questions. WorkSamp supports state-observation studies; these replace neither individual start/end records nor railway safety systems.

2. The Legal Basis: A General Obligation and a Specific Railway Layer

General Workday Record

Article 34.9 of the Workers' Statute requires guaranteeing a daily record that includes the specific start and end time of each person's working day. The company must keep it for four years and make it available to workers, their representatives, and the Labor and Social Security Inspectorate.

The rule does not impose a specific technology. Consequently, an organization may use a terminal, web, mobile, or an integrated system, provided the result is reliable, accessible, and adequate to its work organization. Collective bargaining or company agreements intervene in the organization and documentation of the record.

Mobile Workers in Cross-Border Services

Royal Decree 1561/1995, modified to incorporate the conditions of mobile workers performing cross-border interoperability services, adds specific rules. Among those affecting data design are:

maximum driving time of nine daytime hours or eight nighttime hours;
maximum of eighty driving hours in two weeks;
for a driver without a second driver, a 45-minute break when working time exceeds eight hours;
a break of at least 30 minutes if work exceeds six hours and does not exceed eight;
at least 30 minutes of the break between the third and sixth hour;
a record of daily working and rest hours, kept for at least three years, for the services included in that regulation.

These rules should not be applied indiscriminately to every person working near a train. The scope refers to mobile workers defined by the rule in cross-border interoperability services. For non-included personnel, the Statute, collective bargaining, and the provisions corresponding to their activity apply.

Directive 2005/47/EC is the European framework of the agreement on certain working conditions of these mobile workers. It is advisable to cite the applicable rule, not to configure a "universal railway limit" without verifying position, service, and agreement.

Operational Safety Is Not the Same as Time Tracking

Royal Decree 929/2020 develops operational safety and railway interoperability in the General Interest Railway Network. On the other hand, Order FOM/2872/2010 regulates enabling titles for safety-related personnel, including driver license and diploma.

A time control can show that a mark conflicts with a planned shift, but it should not declare by itself that a person is qualified or fit to operate. The correct integration is an alert and a review flow, not the automatic replacement of the safety management system.

3. Data Model: Four Clocks That Must Not Be Confused

The clearest architecture separates four layers:

Layer	Question	Examples	Main use
Workday	When was the employment relationship of the day in force?	start, end, break	Legal record
Operational state	What was being done within the workday?	preparation, driving, handover, intervention	Operations and analysis
Assignment	To which unit was it charged?	service, station, order, shift	Costs and planning
Evidence	How was the event originated or corrected?	terminal, web, offline mark, validation	Audit

This avoids a frequent mistake: treating the end of an activity as the end of the workday. A driver may stop driving and begin a handover task; an operator may close an order and remain present on another; a station agent may change function without clocking out.

The proposed design retains start/end records and, where necessary and lawful, connects operational events through references. This is a requirement to verify with the supplier, not an asserted Induly feature. A bogie-overhaul standard needs a specific method study; waiting proportions may be studied with WorkSamp.

4. Recommended Flow for Drivers and Mobile Personnel

A defensible event flow can contain:

Sign-on: identity, date, time, base, and mark channel.
Preparation: checks and documentation associated with the service.
Driving start: internal reference of service or shift.
Break: start, end, and type; without assuming that every train stop is rest.
Handover: location, time, and planned or incident-driven handover.
Other activity: considered work wait, accompaniment, handover, or training.
Driving end: distinct from end of workday when tasks remain.
Sign-off: closing of the daily record.

Coverage unavailability cannot erase the event. The application should create the mark locally with a time stamp, flag it as pending, and sync it afterwards. The audit must distinguish the event time from the sync time. An administrator should not be able to "normalize" both without leaving a trace.

It is also advisable to prevent simple inconsistencies: end before start, two open workdays, break without start, or driving that continues after sign-off. However, blocking a record due to a real incident can be worse than allowing it. The prudent pattern is record, flag the anomaly, and review.

Exception-review needs depend on event volume and risk. Measure review effort during the pilot rather than using unverified workforce figures as a sales argument.

5. Depots and Workshops: Presence, Order, and Standard Time

In depots, time tracking must coexist with the work order. An operator may be at the center for eight hours, but distributed among inspection, repair, movement, material wait, cleaning, and training. Reducing everything to "productive" or "unproductive" prevents acting on the cause.

A practical taxonomy is:

Planned WO: work associated with a planned order;
unscheduled corrective: failure intervention;
diagnosis: cause search and confirmation;
logistics: spare parts, tools, or movement;
coordinating wait: authorization, track, or equipment;
training and briefing;
break;
others, with mandatory comment.

In workshops, request a demonstration of attendance recording and any required operational references. Do not infer standard times or activity shares from presence alone.

Clocked hours should not be compared with a standard as if they were identical magnitudes. Presence hours include events that the standard time of an operation is not intended to cover. The useful comparison links each datum with its scope.

6. Stations: Distributed Positions and Role Changes

Station staff present another pattern: stable location, but variable roles and handovers. Traveler service, operations, assistance, opening, closing, and incident management can share a shift. The fixed terminal works if there is one per center and never requires queuing; the corporate web or mobile is useful for authorized location changes.

The record should contemplate:

assigned station or center;
planned position and actual position;
center change during the workday;
handover and person responsible for validating it;
incident preventing marking;
work outside planned hours;
correction requested by the worker.

There is no need to store a continuous GPS trajectory to prove an entry. It is more proportionate to save the selected center location or a punctual validation when there is an organizational basis for it. The system must configure permissions by role: the person sees their data; the manager validates exceptions in their scope; HR administers calendar and export; audit consults without altering.

Validate the proposed configuration in a pilot covering drivers, workshops and passenger service. A single template may omit exceptions or request unnecessary data.

7. Integrity, Corrections, and Audit Trail

A reliable mark is not necessarily immutable. People forget to clock in, a terminal fails, and shifts change. What is required is that the correction does not destroy the history.

Each modification should preserve:

original value;
corrected value;
requesting user;
validating user;
date and time of both acts;
coded reason and comment;
linked document or incident, if any;
exportable version.

Require corrections to retain date, reason, editor and previous value. Check daily/monthly reconciliation and readable exports. Overlap or rest alerts are requirements to verify and need human interpretation: the software is not claimed to include them or guarantee compliance.

Retention must respect the general four-year period of article 34.9. In the cited cross-border railway case, the sector rule requires at least three years; keeping four years allows covering the general period simultaneously, always subject to the organization's legal and data protection policy.

8. Simulated case: implementation across four railway centres

Simulated methodological case: operator with a driving base, a depot, and two stations. The following magnitudes describe the pilot design and do not attribute results to an identifiable company.

The previous system only stored entry and exit. The team detected three problems: breaks were reconstructed by email, off-base handovers were corrected without history, and depot hours could not be linked to orders.

The implementation was divided into four weeks:

mapping of events by group;
pilot with one shift from each center;
joint review of anomalies;
gradual rollout with brief training.

Three templates were configured: mobile, depot, and station. The driver recorded sign-on, break, handover, and sign-off; the depot added order or cause; the station allowed position changes. When there was no connectivity, the mark remained pending with its original time.

The acceptance criterion was not "zero corrections," because that would have incentivized hiding incidents. It was verified that every correction preserved the original, that no end of activity mistakenly closed the workday, and that those responsible could export a complete record. The pilot allowed refining the taxonomy before scaling, without claiming unmeasured savings or percentages.

9. Implementation Plan and Quality Checklist

Phase 1: Define Scope

Inventory groups, agreements, bases, stations, depots, devices, and existing systems. Identify who is a mobile worker in the regulatory sense and who is not. Review with labor relations which events form workday, work, driving, presence, or rest.

Phase 2: Configure the Data

Create calendars, roles, centers, correction reasons, and operational states. Integrate only necessary identifiers. The service or order ID may suffice; there is no need to copy all operational information to the time system.

Phase 3: Pilot Exceptions

Test delay, remote handover, lack of connectivity, broken terminal, night shift crossing midnight, station change, and subsequent correction. The normal case rarely reveals design flaws.

Phase 4: Audit

Compare calendar, marks, and exports. The organization can resort to the ASETEMYT directory to locate methods engineering profiles that help define processes, without attributing certification or inspection functions to the directory.

Checklist

Specific start and end recorded each day.
General retention configured for four years.
Driving separated from presence and from workday.
Breaks recorded as events, not inferred from stops.
Handovers and center changes contemplated.
Offline operation with event time and sync time.
Corrections with original, reason, requester, and validator.
Minimum permissions by role and scope.
Readable daily and monthly export.
Alerts reviewed by a person, not automatic sanctions.
Pilot conducted with mobile, depot, and station groups.
Legal and collective review before generalizing sector limits.

Conclusion: Record Better Without Confusing Systems

The railway challenge is not capturing more marks, but correctly representing a distributed workday. The data must separate start and end, driving, activity, break, handover, center, and evidence. This way it is possible to demonstrate labor compliance, analyze the operation, and correct incidents without erasing history.

Software selection requires testing the described workflows. Attendance records document working time; time study determines standards under a defined method; work sampling estimates state proportions. None independently certifies employment-law compliance or railway safety.

Discover Induly and propose a time control pilot adapted to your operation. The final configuration must be validated with labor representation, prevention, data protection, and the company's safety managers.

Verified Sources

Technical reference.