An hour before doors, the main screen went dark and the venue’s own technicians were still two hours out. I did not wait for them, and I did not guess. The opening started on time.
One hour before the doors opened, the main LED screen went dark. It would not play a single file, and guests were already outside.
The first call was the obvious one: the venue manager, to get their in-house technicians. It was a holiday weekend. Their people were two hours out. The doors were opening in one.
The obvious call was the wrong call.
It was also the only one most people would have made.
I had spent two years at event-execution companies, and I knew something about how they are staffed: firms like that keep screen and electrical-control specialists on the payroll, because a screen going down an hour before doors is not a rare event — it is a Tuesday. So I called a third-party execution partner instead of waiting, and had a qualified technician on site diagnosing while the venue’s team was still driving.
The cause was not the screen. The storage system in the control room that fed it was full, so it could not read the video files at all. When the venue staff arrived we used their admin access to clear out unused content, and the loop played.
The opening started on time. Zero delay.
Then I did the part that actually mattered. I worked out how much runtime and storage the daily loop genuinely needed, had the team clean the backend down to it, and set the player to loop mode so it could not fail the same way twice. That setup became a standard pre-event check, and the problem never came back.
What I take from it is not the fix. It is the first sixty seconds: the obvious call would have been correct on any other day, and useless on that one. Knowing who else is staffed for your problem — before you need them — is most of what crisis management actually is.
I only answer from what is written on this site.
Type a few words — I will show you where it says so.