Rail works to fixed windows. The line goes back at 05:00 whether the work is finished or not. Everything depends on knowing where you actually are, not where the plan says you should be.
On most projects, a delay costs a day. On rail, it costs the possession — and the next available window might be a month away.
Background exists to catch the drift while the window is still open, not to explain it afterwards.
None of these come from one source. They come from reading across them.
Will we make handback?
What is actually stopping the next activity starting?
Where did the last three possessions lose time?
Is the isolation confirmed before anyone is on track?
Grounded in your project’s own record. Not general knowledge.
One window or a year of them — the operating model is the same. Only the scope changes.
The questions change. The operating model doesn’t.
Background helps teams understand where the possession actually is, while there is still time to change the outcome.
Every feed in those findings already exists on your sites. Walk one from the feeds that produced it to the person who acted on it.