How To Avoid Scheduling Disasters At Your Nigerian Event (Pro Tips For Smooth Planning)

Your headline artist says they can only arrive after 8pm. One guest speaker has a flight that lands that afternoon. Another speaker needs to leave early for another engagement. The comedian wants thirty minutes on stage, the panel discussion is already running long and somebody has promised the chairman that his speech can happen whenever he arrives.

This is how an event programme that looked perfectly reasonable on paper begins to fall apart.

Scheduling performers and guest speakers is not simply about giving everyone a time slot. You are dealing with people who may have travel arrangements, other commitments, technical requirements, entourages, rehearsals and their own understanding of when they are expected to appear.

The organiser's job is to turn all of those moving pieces into one programme that still makes sense to the audience.

That requires more than telling everybody to come early. You need to know which parts of the schedule are fixed, which ones can move and who has the authority to make changes once the event is already happening.

Ask for Their Real Availability, Not Just Whether They Are Available

There is a big difference between asking someone, "Are you available on Saturday?" and asking what their availability actually looks like on Saturday.

A performer may say yes because they are available for part of the evening while still having another engagement earlier that day. A guest speaker may be free for your conference but need to leave by 2pm. Someone flying into Lagos may technically be available that day while still depending on a flight arriving on schedule and enough time to travel from the airport to your venue.

Get those restrictions early.

Ask what time they can realistically arrive, whether they have another engagement before or after yours and how long they are expected to remain at your event. If travel is involved, understand the itinerary rather than assuming the person will somehow appear backstage at the exact time written on your programme.

This information gives you something much more useful than a simple yes.

You can then build the programme around genuine constraints rather than discovering them through an apologetic phone call on event day.

Arrival Time and Stage Time Should Never Be the Same Thing

If a speaker is scheduled to address the audience at 4pm, telling them to arrive at 4pm is inviting trouble.

People need time to enter the venue, find the appropriate person, get settled and understand what is happening before they step on stage. Performers may need significantly more preparation depending on the production involved.

A musician could need a sound check or conversation with the band and technical crew. A keynote speaker may need to test their presentation. A panel guest may need to meet the moderator and understand how the session will run.

Decide on a call time separately from the performance or speaking time.

The amount of preparation required will depend on the person and type of event, so there is no universal buffer that works for everybody. A comedian arriving for a short set has different requirements from a live band bringing instruments and a technical rider.

The important thing is that your programme does not depend on someone walking through the gate and immediately stepping onto the stage.

Build the Running Order Around What Cannot Easily Move

Not every part of an event schedule has the same flexibility.

A speaker joining virtually from another country at a specific time may be difficult to move. A performer who must leave for another engagement may have a narrow window. A meal service already coordinated with catering may become expensive or inconvenient to delay significantly.

Those are the pieces you should identify first.

Once you know the genuinely fixed moments, you can arrange more flexible parts of the programme around them.

This is much safer than creating the programme because one sequence looks attractive and then trying to force everybody into it afterwards.

It also helps when a change becomes necessary. If the programme manager already knows which sections can move, decisions can be made quickly without accidentally creating another conflict somewhere later in the day.

Do Not Pack the Programme So Tightly That One Delay Destroys Everything

A programme can look beautifully efficient in a spreadsheet and become exhausting in real life.

Speaker A finishes at 3:20pm. Speaker B begins at exactly 3:20pm. A performance ends at 4:00pm and the panel begins at 4:00pm.

There is no time for the MC to make a transition, no time to change microphones, no time for people to move on or off stage and absolutely no room for someone exceeding their allotted time.

Events need transitions.

The audience may barely notice some of them, but the production team certainly does. A microphone may need to change hands. Chairs might need to be repositioned. A laptop needs to connect. A performer has to leave the stage while somebody else enters.

Give those moments somewhere to exist.

This does not mean inserting a long empty gap between every programme item. It means being realistic about how long one activity actually takes to become the next.

A schedule with some breathing room is easier to recover than one where every minute has already been spent before the event begins.

Know How Long People Actually Need on Stage

Another common source of conflict is vague duration.

A speaker thinks they have thirty minutes. The organiser believes the session is twenty minutes. The MC was told to expect fifteen.

Everyone discovers the difference while the person is already holding the microphone.

Agree on stage duration beforehand and make sure the person understands whether that time includes introductions, questions or audience interaction.

This is particularly important for panels. Four panellists speaking for ten minutes each does not automatically create a forty-minute session once the moderator's introduction, follow-up questions and transitions are included.

Performances need the same clarity. A musical act may describe their booking as a thirty-minute performance, but production may also require setup or changeover time that affects the programme even though the audience is not watching the artist perform during that period.

Your run time should reflect what happens to the event clock, not only how long the person is actively speaking or performing.

Put the Important Details in Writing

A scheduling conversation can begin on a phone call, but important arrangements should not live only inside someone's memory.

Confirm the event date, venue, agreed arrival time, expected stage time and duration in writing. If there are rehearsals, sound checks or other preparation requirements, include them too.

For paid performers and professional speakers, these details should also align with whatever booking agreement or contract exists.

The point is not to create unnecessary paperwork. It is to reduce situations where the organiser remembers one arrangement and the performer remembers another.

As the event gets closer, send an updated confirmation rather than assuming everybody still remembers a conversation from three months earlier.

People's calendars change. Flights change. New engagements appear. Catching a conflict several days before the event gives you far more options than discovering it when the person's phone suddenly goes unanswered backstage.

Give Each Important Guest One Person to Talk To

A performer should not need to call the event planner, then the MC, then the production manager, then somebody's assistant just to understand where they are supposed to go.

For important speakers or performers, assign a clear liaison.

That person can confirm arrival, meet them where necessary, communicate changes and let the programme team know when they are actually ready.

This becomes especially useful at larger events where the person arriving may not know anyone on the organising team personally.

The liaison should also know enough about the programme to answer practical questions without becoming another middleman who has to call the organiser every thirty seconds.

If the guest is delayed, the liaison communicates that quickly. If the stage is running behind, they can explain the updated expectation to the guest rather than leaving them backstage wondering whether they have been forgotten.

Good coordination often feels like hospitality because the guest is never left trying to work out what is happening.

The MC Should Not Be the Last Person to Hear About a Change

Your MC can rescue an awkward transition, but only when they know there is something to rescue.

If a guest speaker is running twenty minutes late, the MC should not discover that after announcing their name.

Programme changes need to reach the people responsible for the audience experience before they become visible on stage.

The MC may be able to extend another segment slightly, move a planned interaction forward or introduce something else that was already part of the programme. The DJ or production team may also need to know if a performance order changes.

This is why key people should be working from the same run sheet rather than separate versions of what they think the programme looks like.

If you have not built one yet, the Shows.ng guide on how to create an event run sheet explains how to organise timing, activities and responsibilities into one usable event-day document.

Do Not Promise the Same Prime Slot to Everybody

Scheduling becomes especially difficult when several people have been told privately that they will appear at the “best time.”

A sponsor expects their representative to speak shortly before the headline act. A politician's aide says they cannot wait long. One performer was promised the closing slot. Another believes they are the main attraction.

Those conversations eventually meet each other on event day.

Be careful about making scheduling promises before the full programme is understood.

If a particular stage position is part of an agreement, record it. Otherwise, explain that the final running order will be confirmed closer to the event.

This protects you from building an impossible programme around commitments made casually during separate conversations.

It also gives the programme manager room to design the event for the audience rather than arranging everything according to whoever applied the most pressure.

Think About Energy, Not Only Availability

A technically conflict-free schedule can still be a poor programme.

You could put six speeches next to one another because every speaker is available at that time, but the audience may be exhausted by the fourth one.

Programme design should consider how the room will feel.

A performance can create a useful change of pace after a long discussion. A short presentation may work better before a major keynote than after it. At a concert, the order of performers affects how energy builds throughout the evening.

This becomes a balancing act because availability still matters. You may not always get your ideal creative sequence.

The goal is to find the best programme possible inside the practical constraints rather than treating the schedule like a diary where anybody free at 6pm automatically belongs in the 6pm slot.

Travel Deserves More Respect Than “They Said They Are On Their Way”

Someone being on their way is not the same as someone being nearby.

Traffic, flight delays and travel between cities can affect Nigerian events, but the solution is not to shrug and assume every programme will therefore start late.

Understand where important people are coming from.

If a keynote speaker is flying in on the morning of your conference, recognise the dependency you have created. If the headline performer is coming directly from another event across Lagos, the schedule needs to reflect that reality rather than pretending both engagements exist in separate universes.

Where the person is critical enough, arriving in the city earlier may be worth discussing during booking.

When that is not possible, know which part of the programme can move if travel causes a genuine delay.

The strongest schedule is not one that assumes nobody will ever be late. It is one that can absorb a reasonable disruption without collapsing.

Decide in Advance What Happens When Someone Is Late

This decision is much harder to make when hundreds of people are already sitting in front of you.

If a speaker misses their slot, do you move them later? Shorten their session? Remove it entirely? If a performer arrives after another act has already taken their position, does the original running order return or does the new order remain?

There is no universal answer.

A keynote speaker may be important enough to move. A short welcome speech may not be. A headline artist's delay could justify a larger programme adjustment, while allowing every late guest to choose a new slot can eventually destroy the schedule for everybody who arrived on time.

Agree internally on who makes those decisions.

For a smaller event, that may simply be the organiser. At a larger production, the programme or stage manager may need authority to adjust within agreed limits without searching the venue for approval every time something shifts.

Once a decision is made, communicate it quickly to the people affected.

Shows.ng also has a separate guide on what to do when an event runs off schedule, which is useful when the problem has moved beyond one delayed speaker and is beginning to affect the rest of the programme.

A Backup Does Not Always Need to Be Another Performer

Organisers sometimes hear “have a backup” and imagine paying another major artist to sit backstage just in case somebody fails to appear.

That is rarely realistic.

Your backup can simply be programme flexibility.

The MC may have an audience interaction that can move forward. A DJ set can run slightly longer. A networking segment or break may be brought forward when appropriate. Another speaker who is already present may be willing to swap positions.

The important thing is that these options are thought about beforehand.

Filling time should also suit the event. A corporate conference experiencing a speaker delay does not necessarily need an unexpected dance competition. A wedding and a professional summit require very different ways of keeping guests engaged.

A good backup feels like part of the programme rather than evidence that everybody backstage is panicking.

Protect the People Who Arrived on Time

One person arriving late should not automatically punish everyone else.

If speakers were told to arrive by noon and one important guest appears at 3pm, be cautious about allowing the entire programme to stop and rebuild itself around them.

Constantly moving people who followed the schedule can create resentment backstage and confusion for the crew.

There will be exceptions. Some guests genuinely have enough importance to justify a change, and unexpected circumstances happen.

But lateness should not automatically create priority.

The more consistently your event respects agreed timings, the easier it becomes to work with professional performers, speakers and vendors who also have schedules to protect.

The Final Programme Should Have One Owner

Several people may contribute to an event schedule, but somebody needs to control the final version.

Otherwise the decorator has one programme, the MC has another, a sponsor was emailed an older version and the stage manager received a WhatsApp message changing two sessions that nobody else saw.

Once the event is close, establish which schedule is current and who can approve changes to it.

Your run sheet should reflect that version.

If something changes on event day, key team members need to receive the update rather than quietly editing their own copies and assuming everybody else somehow knows.

Version control sounds like a small administrative detail until two performers are both standing backstage because each was told they are next.

A Good Schedule Feels Natural to the Audience

Guests should not need to understand how difficult the programme was to coordinate.

They do not know that one speaker had a flight to catch, the band requested an earlier sound check or the comedian came directly from another engagement.

They simply experience whether the event flows.

That is what good scheduling creates.

Confirm genuine availability before assigning slots. Separate arrival time from stage time. Understand technical and travel requirements, leave room for transitions and make sure the important people backstage are working from the same programme.

Then decide what can move before something actually forces you to move it.

If someone is late, the organiser should be choosing from options already understood rather than inventing a completely new event while the audience waits.

When the wider event plan is ready, you can create your event on Shows.ng and keep the public-facing event details clear while your programme team manages the timing behind the scenes.

A strong event schedule is not one where nobody is ever late. It is one where one person's delay does not become everybody else's problem.