I was in the fab shop fault finding on one of our saws when we heard an almighty crash.
I remember saying, half jokingly, "I hope that wasn't on our site."
Unfortunately, it was.
A huge tree had come down in the wind, gone straight over our boundary fence and completely flattened our neighbour's double shed.
At that moment, nobody cared about the tree.
The only thing that mattered was making sure nobody was inside the shed.
Thankfully, everyone was safe.
Once we knew that, we got to work.
We used the forklift and the telehandler to carefully lift the tree back over onto our side of the fence. Our neighbour asked if we could clear what was left of the shed and everything inside it, so that's exactly what we did.
We replaced the damaged fence.
The rest of the day was spent with chainsaws cutting the tree into manageable pieces. The smaller logs went home with the lads for their log burners, and the larger sections were loaded into a skip.
If you'd looked at the maintenance plan that morning, none of this was on it.
No job card.
No work order.
No planned maintenance.
Just a problem that needed solving.
That's one of the things I've always liked about engineering teams.
When something goes wrong, people don't stand around asking whose job it is.
They roll their sleeves up and get stuck in.
Looking back, I don't think our neighbour will remember the tree.
I hope she'll remember that a group of engineers stopped what they were doing to help when she needed it most.
Engineering isn't just about keeping machines running.
It's about taking ownership, solving problems, and doing the right thing—even when the problem has nothing to do with production.
Sometimes the most important job you'll do all day isn't the one on the maintenance plan.
Have you ever had a day where your biggest challenge had nothing to do with the job you thought you were going to do?