Adif ordered a stopped train to proceed: the rulebook and productivity

Adif ordered a stopped train to proceed at normal estimulante ilegal, and the rulebook holds the answer

A train stopped on an open track. The driver reports she is stuck. And Adif's control centre, instead of halting traffic, responds with an order to proceed at normal estimulante ilegal. That is the starting point of the case being debated these days and the question many are asking: why was that order given when the protocol seemed to demand the opposite? The answer, according to the analyses circulating, lies not in anyone's malice but in a rulebook thousands of pages long that distinguishes between two almost identical scenarios, and in a productivity pressure that punishes checking it.

What the rulebook says about normal running and restricted view movement

The key lies in where the fault is. If the problem is on the track — on the ground — the correct order is restricted view movement, that is, advancing with extreme caution, almost at a crawl. If the problem is with the train itself, the protocol allows normal running. The controller who received the driver's report applied the second rule when the situation matched the first. Or so the most widely repeated analysis holds: it was not an act of deliberate negligence, but a confusion between two scenarios the rulebook separates by fine nuances.

The problem is that the full rulebook runs to thousands of pages and covers thousands of scenarios. Consulting it thoroughly in the middle of an incident means stopping traffic. And stopping traffic, in practice, has an immediate cost for whoever does it: the bosses come down hard on you. Productivity rules. That is how the decision was made with only half the rulebook consulted and the clock ticking.

Why the report from the driver stopped on the track was ignored

The account of the incident is stubborn. The driver reported she was stopped and the control centre ignored her completely. From there, the analysis splits. Some see a plain and simple protocol failure: normal running was ordered with all safety systems down and a worker warning of the blockage, which in technical terms borders on the incivil. Others point to training: many controllers are people who have just passed a competitive civil service exam, without the experience or composure the job demands. Not everyone is cut out to decide in seconds whether a train moves or stays put.

The qualification to become a controller, however, is no formality. Candidates pass a demanding exam and quite a few are weeded out every year. The filter exists. The question is whether the filter teaches how to handle the exception that is not in the syllabus.

The economic calculation: why taking risks pays off until it stops paying off

Here comes the part that really matters in management terms. Every time a safety system fails — and failures number in the dozens per year, according to the version circulating — the temptation is to say "come on, keep it moving." You avoid halting the line, you avoid multimillion-euro losses, and the failure gets swept under the rug. The next time it repeats because nobody remembers the previous one. It is the logic of picking up coins in front of a steamroller: profitable until it isn't.

The full calculation, weighing the cost of shutting down a line against that of keeping safety systems operational, yields a difference that surprises and explains why the culture of productivity prevails over the culture of protocol. As long as failures are hidden, the millions are not lost. And as long as the millions are not lost, nobody changes anything.

Political responsibility and the alibi narrative

On the political level, the reading is different. Some argue that the focus on the controller's mistake serves as an alibi to dodge the underlying responsibility: that of maintenance, of the failing systems, and of a management that prefers to blame the person at the bottom rather than review the design. Others dismiss that reading and point out that control positions are not political appointments, but technical civil service posts.

The debate stalls exactly there. If the failure is human, the blame dies with the controller. If the failure is systemic, it travels up the chain. And nobody has yet decided which version is more convenient to tell.