Prioritise requests based on feasibility and impact on the event. Communicate realistic timelines and delegate tasks efficiently to address changes without disrupting the event’s flow.

We’re seeing so many new people coming to online events that would not have been able to participate in our in-person events. I am amazed at how effective the 1:30-3:00 pm timeslot is for people! Before, you would have never hosted an event at that time on a weekday, but I do them all the time now, and they are very successful. Because people are already at their computer, it’s easy to tune in at that time. And for people like stay-at-home parents; they can tune in when their child is taking a nap. This opens events to many people who would have otherwise felt excluded or who could not have joined in-person.

Communication amongst all parties is key .. Assessment of requests Not knowing what the event is , full questions to the parties involved . Sending clear emails with lists and plan of action beforehand might allow for gig time changes .

Inhale Exhale Repeat All we have in now And in the now we have IT ALL Sat chits ANNDA Practice, practice, and all is coming

Well, prioritization is key here. If the problem will make the product look lets say "not as good as planned" but we can make it on time, then we go for it. Live events wait for no one and shit happens. With that said communication with everyone involved can make the difference going from "meh" to Ok didn't go as planned but looks good anyways.

Always have a back up and then a back up after that no stress all you have to do is be prepared completely know about the bosses and what their requirements are and how they might react in other words. Just find out more about them. Put your job description.