How to Handle Event Delays in Nigeria Like a True Professional

Your event was supposed to begin at 4pm.

It is now 4:35pm, the keynote speaker is still on the way, the sound team needs another ten minutes and somebody backstage is asking whether the opening performance should still happen before everything else.

This is the point where a good event schedule stops being a document and becomes a decision-making tool.

Running behind schedule does not automatically mean the event has failed.

What matters is what the organising team does once the original timing is no longer realistic.

The worst response is often pretending the old schedule still exists. Activities remain untouched, everybody tries to move faster and the team gradually pushes the entire programme later without deciding what actually deserves to stay.

A better response is to acknowledge that the event now has a different amount of time available and rebuild the remaining programme around what matters most.

First, Find Out How Far Behind You Really Are

Do not react to a delay before understanding it.

There is a big difference between being ten minutes behind and discovering that an important guest will not arrive for another ninety minutes.

Ask what has actually changed.

Which activity was supposed to be happening now? What is preventing it from happening? How long is the delay realistically expected to last? Does the problem affect only one programme item, or does it block several things that depend on it?

Sometimes the delay is smaller than the panic around it.

A speaker needs another ten minutes and the programme already contains enough flexibility to absorb that difference.

At other times, the problem is structural.

If the headline performer is delayed by two hours, the programme may need to be redesigned rather than simply paused.

Get the facts first.

Do Not Keep Following a Schedule That No Longer Exists

Once the event is meaningfully behind, the original running order may need to change.

This is where organisers sometimes make the problem worse.

The programme says thirty minutes for a panel, so the panel still gets thirty minutes. The award presentation still gets twenty. Every speech stays untouched. Every performance remains.

The event eventually ends hours later because nobody was willing to make a decision.

A schedule is not sacred.

Its purpose is to help the event work.

When circumstances change, the schedule should change with them.

Identify the Moments the Audience Actually Came For

When time becomes limited, protect the core value of the event first.

At a concert, that may be the main performances. At a conference, attendees may have paid specifically to hear certain speakers or participate in particular sessions. At a wedding reception, some moments carry much more emotional importance than others.

Ask what cannot reasonably disappear without changing the event people were promised.

Those moments become priorities.

Everything else can then be reviewed around them.

This is much more useful than treating every item on the programme as equally important simply because somebody originally gave it a time slot.

Know What Can Be Shortened Without Destroying Its Purpose

Some programme items can survive being shorter.

A twenty-minute welcome address may still work in ten. A long transition can be tightened. An unnecessarily extended introduction can become more direct.

But shortening should be deliberate.

A sixty-minute workshop may not still deliver meaningful value if it is suddenly reduced to fifteen minutes. A performer who was booked for a defined set may need to agree before that set changes substantially.

Do not reduce everything equally.

Look at the purpose of each programme item and decide what minimum amount of time it needs to still make sense.

Some Things Should Be Removed Completely

Trying to preserve every activity can create an event where everything happens badly.

Sometimes one programme item should simply go.

Perhaps there were three speeches saying almost the same thing. Maybe an optional entertainment segment was added mainly to fill time that you no longer need to fill. A second break might no longer be necessary.

Removing something cleanly can be much better than rushing through it while everybody watches the clock.

The decision should protect the overall event rather than the ego of whoever originally requested that activity.

Do Not Cut the Things Guests Actually Need

There is another danger when organisers begin trying to recover time.

They sometimes remove breaks, food service or other guest needs because those appear easier to sacrifice than programme content.

Be careful.

If people have been sitting through a conference for several hours, eliminating the only meaningful break may create another problem. If meal service was included in the ticket experience, repeatedly delaying it because speeches ran long can make attendees resent the programme itself.

Recovering time should not mean ignoring basic comfort.

Give One Person Authority to Control the Revised Programme

An event running late becomes much harder when several people start making independent schedule decisions.

The MC wants to move one activity forward. A sponsor representative insists their presentation should remain at the original time. The backstage team wants to delay another segment. Somebody else tells the DJ to extend the music.

Now the event has several competing schedules.

One person needs operational authority over the running order.

That might be the event manager, stage manager, programme director or another clearly assigned member of the organising team.

Suggestions can come from everywhere.

The final schedule decision should not.

Update the Run Sheet Instead of Managing the Delay From Memory

If your event is using a run sheet, update it once the programme changes.

The document should reflect the event that is actually happening.

This does not require producing a beautifully formatted new PDF while guests are waiting.

The person controlling the programme needs a clear revised sequence and the relevant team members need to understand it.

If the keynote is now after the panel, the MC, technical team, photographer and anyone else affected should know.

If a performance has been removed, backstage should not continue preparing it as though nothing changed.

Our guide on creating and using an event run sheet explains how to build the document so that changes during the event do not turn it into something nobody follows.

Tell the MC What Changed Before They Walk Back On Stage

The MC can help an event recover, but only if they know what the new plan is.

Do not send the host back on stage with instructions such as “Just keep them busy for now.”

Tell them what they are bridging towards.

Do you need five minutes or thirty? Is the next speaker almost ready? Has the programme order changed? Is there information attendees should hear?

A good MC can make transitions feel natural when they have enough information.

An uninformed MC may accidentally announce something the team has just postponed or fill so much time that another programme segment is delayed further.

Entertainment Should Be a Bridge, Not a Distraction From Bad Communication

The original version of this article recommends games, dancing and music so that guests do not realise there is a delay.

That can work for very short gaps where there is genuinely nothing important to communicate.

It should not become the default response to every delay.

If a conference keynote has moved by an hour, attendees may need to know. If gates are opening late, people standing outside deserve useful information. If a headline performance has been rescheduled, pretending nothing happened may make the audience more frustrated.

Use entertainment to keep energy comfortable while the team solves the problem.

Do not use it to hide information guests reasonably need.

Sometimes the Most Professional Thing You Can Say Is That There Is a Delay

Organisers can become afraid of acknowledging anything has gone wrong.

But uncertainty often frustrates attendees more than the delay itself.

If people have been waiting forty minutes without explanation, they begin creating their own explanation.

Perhaps the performer is not coming. Maybe the organiser is unprepared. Maybe the event has been cancelled.

A short, accurate update can reduce that uncertainty.

You do not need to broadcast every backstage problem.

Guests do not need to know that two vendors are arguing or that somebody forgot an important cable.

Tell them what affects their experience.

For example, you can acknowledge that the programme is starting later than planned and give a realistic updated expectation where one is available.

Never Announce a New Time You Have Not Confirmed

False reassurance makes delays worse.

If you tell attendees that the programme will begin in ten minutes, you should have a reasonable basis for believing that.

Do not keep moving the estimate.

Ten more minutes.

Then another ten.

Then fifteen.

After several incorrect updates, people stop trusting the announcements completely.

If you do not yet have a reliable time, say that the team is resolving the issue and that another update will follow when the timing is confirmed.

Accuracy is more useful than optimism.

Attendees Outside the Venue May Need Different Communication

Some schedule changes affect people who have not arrived yet.

Perhaps severe weather has pushed the opening time. A venue access issue may mean check-in begins later than advertised. A morning session could be delayed significantly before most ticket holders have left home.

In those situations, communication inside the venue is not enough.

If attendees booked through Shows.ng, organisers can send an email message directly to the attendees connected to that event.

From the organiser dashboard, you can open the event's attendee list and use the Send Message to Attendees option to send a subject and message by email.

The Shows.ng attendee messaging guide explains the process.

This can be useful when the timing change is significant enough that people should know before travelling or when important arrival instructions have changed.

It is not a replacement for every other communication channel. For urgent event-day information, use the channels your audience is most likely to see in time.

Tell Staff Before Guests Start Asking Them Questions

An attendee usually asks the person closest to them.

That may be an usher, security officer, registration staff member or volunteer who had nothing to do with creating the schedule.

Those people still need an answer.

When timing changes, brief front-of-house staff quickly.

They do not need the entire backstage story.

They need a simple, accurate explanation of what guests should currently expect.

If the main programme will begin at 5pm instead of 4:30pm, staff should not be giving five different answers depending on which entrance somebody used.

Separate Internal Updates From Attendee Updates

The team needs more detail than the audience.

Internally, you may need to know that the artist's flight was delayed, soundcheck has moved and two performances are switching positions.

Attendees may only need to know that the headline performance will begin later than originally scheduled.

Keep those communication levels separate.

Too little internal information creates operational mistakes.

Too much unnecessary public detail can make an event feel more chaotic than it actually is.

Protect Sponsors and Partners Without Letting Them Control the Entire Recovery

If a sponsor has an important activation, stage appearance or representative scheduled, a major programme change may affect them.

Tell them.

This is particularly important if their agreed visibility depends on a particular moment.

But handling sponsors professionally does not mean every sponsor activity must remain untouched while everything else is squeezed around it.

If the event is seriously behind, have the necessary conversation.

A shorter sponsor presentation delivered while the audience is still engaged may create more value than preserving a lengthy segment that pushes the headline programme another forty minutes later.

VIP Guests Need Accurate Information, Not Constant Special Treatment

The old article recommends handling VIPs carefully, which is sensible when the delay affects their arrangements.

But do not create two completely different realities where one small group receives constant updates while the general audience is left confused.

If a delay affects everybody, everybody deserves appropriate information.

A VIP may need additional communication where transport, backstage access or a specific appointment is affected.

The principle is relevance, not status alone.

Do Not Punish the Next Speaker for the Previous Speaker's Overrun

One common source of schedule drift is programme items taking longer than agreed.

A speaker gets twenty minutes and uses forty.

The next speaker is then told they have eight minutes because the event needs to recover.

That may sometimes be necessary, but it should not become the automatic pattern throughout the programme.

Manage overruns earlier.

Give stage participants clear timing. Use visible time cues where appropriate. Brief the MC or stage manager on how to close sessions politely when time has expired.

If nobody is willing to stop the first three overruns, the final programme items will pay for all of them.

Build the Revised Programme Around Dependencies

Some activities cannot simply move anywhere.

A performer may need a soundcheck. A dinner service may depend on food being ready. A panel may require several speakers who have limited availability. A presentation might need equipment that another session is currently using.

When rebuilding the schedule, look at those dependencies.

You may discover that moving one activity forward creates three new problems.

The best replacement order is not necessarily the one that looks neatest on paper.

It is the one the team can actually execute.

Use Something That Is Already Ready When You Need to Fill a Short Gap

If you need ten minutes, choose something that can genuinely begin now.

Perhaps the DJ can play. The MC can handle a brief audience interaction. A planned short video might be moved forward. Refreshments may already be available.

Do not create a second delay while trying to hide the first one.

If the games team needs fifteen minutes to prepare a “quick activity”, it is not solving your immediate problem.

This is another reason to identify flexible programme elements before event day.

Do Not Add New Activities Just Because the Programme Is Temporarily Stuck

A delay can tempt the organising team to improvise excessively.

Somebody suggests a competition. Someone else invites an unplanned guest to speak. Another person decides this is the perfect moment for sponsor announcements that were never in the programme.

Those additions may fill time now while creating another timing problem later.

Use existing flexible material first.

The goal is recovering the schedule, not expanding it.

Food Service Can Sometimes Move, but Coordinate It Properly

At some events, meal or refreshment service can help absorb a timing change.

If lunch is ready earlier than expected and a speaker has been delayed, moving the break forward may be sensible.

But check the operational consequences.

The caterer needs to be ready. The venue may need tables prepared. Guests may not be expecting food yet. Another programme item may depend on the room staying seated.

A schedule recovery decision should solve more problems than it creates.

Weather Delays Require a Different Kind of Flexibility

Outdoor events can lose time because of rainfall, heat, wind or other conditions.

Do not treat weather only as a timing issue.

Safety comes first.

If conditions make a stage, electrical setup or audience area unsafe, the organiser may need to pause activity even when the schedule becomes worse.

Once conditions improve, reassess the remaining programme exactly as you would any other serious delay.

Do not simply restart from the point where you stopped and assume the original closing time no longer matters.

Venue Closing Times Can Make Some Delays Non-Negotiable

Sometimes you cannot simply let the event run later.

The venue may have a contractual closing time. Local operating restrictions may apply. Vendors may have agreed hours. Transport arrangements may depend on the advertised finish.

Know those constraints before deciding what can be recovered.

If the venue must close at 11pm, a one-hour delay means you may now have one hour less programme.

That reality should influence what gets shortened or removed.

Ignoring the closing time does not create more time. It creates another problem at the end of the night.

Some Delays Affect Ticket Value More Than Others

If an event begins twenty minutes late but delivers everything important, the impact may be limited.

If a major advertised performance disappears because the event ran out of time, the issue becomes much more significant.

Ask whether the recovery plan changes what attendees reasonably believed they had purchased.

If it does, the organiser may need a stronger response than simply apologising for lateness.

Exactly what is appropriate will depend on the event, the ticket terms, the scale of the change and applicable obligations.

The important point is recognising the difference between a schedule adjustment and a materially changed event.

Do Not Blame Vendors Publicly While the Event Is Still Happening

Perhaps the delay genuinely is a vendor's fault.

That still does not mean the MC should announce it to the room.

“Sorry everybody, the caterer is late again.”

That may satisfy the organiser's frustration for thirty seconds while making the entire event look less controlled.

Deal with accountability afterwards.

During the event, communicate what attendees need to know and focus the team on recovery.

There will be enough time later to establish what caused the problem and who was responsible.

Keep a Record of Major Schedule Changes

After a hectic event, people remember timing differently.

The speaker says they started only ten minutes late. The production team remembers thirty. Someone else thinks the problem began with registration.

Where practical, keep simple notes of significant changes.

When did doors actually open? When did the programme begin? Which major segment overran? What was removed or moved?

This gives the post-event review something better than memory.

Find the Root Cause After the Event, Not Just the Most Visible Delay

If the keynote began an hour late, the keynote may not have been the real cause.

Perhaps registration opened late because setup was incomplete. That delayed the opening. The first panel then overran, which pushed lunch later. The delayed lunch eventually affected the keynote.

The final visible problem was only the end of a longer chain.

Review the sequence.

Ask what first pushed the event behind and why the programme never recovered.

That is much more useful than adding a vague note to “start earlier next time”.

Do Not Blame Everything on Traffic or “African Time”

Traffic can affect events. Guests can arrive later than expected. Vendors and speakers can also face genuine delays.

But turning lateness into a cultural joke makes it easier to avoid examining preventable problems.

If a vendor needed to arrive at noon for setup and was scheduled to leave their location at 11:45am, that is not simply a traffic problem.

If the programme could not begin because the organiser had not completed the stage setup by the advertised opening time, that is not an audience-punctuality problem.

Plan according to the conditions you realistically expect.

That includes travel time, setup time, guest behaviour and the complexity of the programme.

Build Buffers Into the Parts of the Schedule Where They Actually Help

A buffer is useful when it absorbs normal variation.

It should not become an excuse to publish one time while privately planning to start an hour later.

Build breathing room between complex transitions, performer changes, technical setups and other moments that realistically take time.

You do not necessarily need fifteen empty minutes printed between every activity.

The run sheet can contain operational flexibility that guests never see.

A good schedule has enough structure to control the event and enough breathing room that one small delay does not destroy the entire day.

Rehearse the Transitions Most Likely to Go Wrong

Delays often appear between programme items rather than inside them.

The panel ends but nobody knows where the next speaker is. A performance finishes and the stage needs fifteen minutes of unexpected rearrangement. An awards segment begins but the trophies are still backstage.

Identify complicated transitions before event day.

Who moves what? Who confirms that the next person is ready? What equipment changes? How long does the transition realistically take?

The smoother those handovers become, the less schedule recovery you will need later.

Your Run Sheet and Delay Plan Should Work Together

The best time to think about schedule recovery is before the event starts.

When creating the run sheet, identify which programme items are fixed, which can move and which could be shortened if necessary.

Know the venue's hard closing time. Understand speaker availability. Decide who has authority to change the running order.

Then if something slips, the team is not inventing the recovery strategy from nothing.

The schedule was built with some understanding that real events can change.

The Goal Is Not to Pretend the Delay Never Happened

A professional event is not one where nothing ever goes wrong.

It is one where the team can protect the experience when something does.

Find out how serious the delay actually is. Stop treating the original schedule as untouchable. Protect the moments people came for, shorten or remove lower-priority material and update the people responsible for delivering the new programme.

Communicate with guests when the change genuinely affects them rather than trying to distract everybody indefinitely.

If a significant timing or arrival update needs to reach registered attendees outside the venue, Shows.ng's attendee messaging feature gives organisers a direct email route to the people attached to that event.

And once the event is over, compare what actually happened with the original run sheet so the next schedule is based on what this event taught you rather than what everybody hopes will happen next time.

When you are preparing that next event, you can create your event on Shows.ng and keep the attendee-facing side organised while your team builds a programme that has enough structure to stay useful even when timing changes.

When an event falls behind, the job is not to make every original activity happen somehow. The job is to protect the experience people came for with the time you still have.