Industries

The day itself: the run sheet, hour by hour

What ruins an event is almost never a service. It is the twenty minutes between two of them.

Published on 9 July 2026 — Algeria Agency

The article beside this one says you sell a date and that it expires at the stated hour. That is true, and it describes everything that happens before: the quote, the deposit, the calendar, the cancellation.

This article is about the date itself. It lasts between six and fourteen hours, it is made of things that follow one another, and the document that holds it is a run sheet.

Most run sheets in circulation are programmes: a list of what happens, on round hours. A programme is for guests. A run sheet is for the people working, and it is not the same document.

The difference fits in one sentence, which is this article’s thesis: what ruins an event is almost never a service, it is the minutes between two of them. The run sheet describes the joins.

What a run sheet is not

It is not the programme. The programme says "7.00 pm: reception, 8.30 pm: dinner, 10.00 pm: cake", it is accurate, it is useful to guests, and it lets nobody organise anything.

Nor is it the quote reread. The quote lists services bought; the run sheet places them in time, in an order that depends on the venue, and that order cannot be deduced from the list.

It is not a countdown plan either. A countdown plan organises the preceding weeks; the run sheet organises one day, and the two are frequently confused in the documents we are shown.

It is a working document for people standing up, in noise, with their hands full. That imposes constraints of form: one page, large type, a column of hours, a column of names, and nothing that has to be read twice.

The test is simple and brutal: give the sheet to somebody who took no part in preparing it and ask what happens at 6.40 pm. If they hesitate, the document is a programme.

Unequal segments, and what happens between them

An event day is not a regular grid. It is made of blocks of very different lengths: three hours of setup, forty minutes of reception, two hours of dinner, ten minutes of speeches, twenty minutes of cake.

Writing them at their real length rather than on round hours is the first act of this document. A dinner that takes an hour and forty minutes written as "8.30 – 10.00" has already produced twenty minutes of delay before anybody has made a mistake.

Between every pair of blocks there is a join, and that is where the subject is. A room turning from reception to dinner, a stage changing speaker, a photo corner being taken down: those moments exist, they take time, and they almost never appear on the document.

The consequence is arithmetic: a day where only the blocks were written is a day underestimated by the sum of its transitions. Six joins of ten minutes make an hour, and that hour is lost at the end, on the last segment — the one that matters most to the client.

Writing the joins is therefore the act that separates a run sheet from a programme. They appear in full, with a duration and a person responsible, exactly like the services.

The transitions are the real subject

A transition has three properties that explain why it is the weak point. It involves several people at once, it belongs clearly to nobody, and it is invisible to guests until the moment it fails.

It involves several people: the venue clears, the caterer lays up, the technician changes a source, somebody moves chairs. Those four actions get in each other’s way if nobody has decided their order.

It belongs to nobody, because every supplier has a brief that begins or ends there. The caterer thinks the venue is clearing; the venue thinks the caterer is laying up. It is the most reliable structure there is for producing ten minutes in which nothing happens.

It is invisible until it fails: guests do not see a successful transition and see perfectly well a half-laid room with people standing beside it. That is why transition faults are over-represented in what clients remember.

The rule that settles all three is short: every transition carries a name, a duration and a single person responsible. Not whoever owns what precedes it, not whoever owns what follows — one name, with authority over the join itself.

One name per segment, and only one

Every line on the sheet carries a name, and it is the name of whoever starts it, not whoever performs it. The distinction looks subtle and is decisive: ten people can perform, one decides that it begins.

That name is a person present, not a function and not a company. "The caterer" is not a name: there are four of them on site and none considers themselves the one you were speaking to.

The segment owner’s job is modest: look at the clock, check the entry condition is met, start it. They are not in charge of the segment and do not need to know how to do it.

One name coordinates the whole and it is yours, or a designated member of your team. That role has to be physically identifiable — suppliers must know who to go to without hunting, which means saying so at the briefing.

The corollary that costs most to respect: whoever coordinates holds no post. A coordinator who is also serving, or photographing, or greeting, is a coordinator absent at the three moments they will be looked for.

Suppliers work to their clock, not yours

Every supplier has their own logic of time, and it is not the event’s. The caterer thinks in cooking time, the florist in freshness, the technician in rigging time, the photographer in light.

The run sheet must therefore carry, for each of them, two hours and not one: the hour they must be present and the hour their service starts. Confusing the two is the most ordinary cause of a late start.

The arrival hour is calculated backwards from their own constraint, and it is asked of them. "How long do you need on site before you can start" is a question they can all answer precisely and that almost nobody puts.

You also have to write down what each of them needs on arrival: access, a power point, a table, water, somewhere to change. Those needs are known in advance and are discovered on site at most events, which costs fifteen minutes each.

Finally, the sheet goes to everybody, whole. A supplier who sees only their own line cannot anticipate; the same supplier seeing what happens before them adapts on their own, and it is the cheapest benefit in the entire document.

The point of no return for each service

Every element of an event has a moment after which it can no longer be changed or cancelled without loss, and those moments are not in the same place in the day.

The covers freeze several hours before the meal, sometimes the day before. An installed decoration does not change. A cake order cannot be modified past a point. A set piece once positioned does not move without dismantling.

Those points have to be written on the sheet, at their hour, with a note of what is no longer possible afterwards. They are the only lines in the document that describe not an action but a closure.

Their usefulness is twofold. They prevent the impossible request — a client learning at seven that ten more covers can still be added while the kitchen is running — and they give the coordinator a clear answer to a question asked in a hurry.

They are also what lets you say yes more often. A coordinator who knows the points of no return accepts without hesitation everything that arrives before them, which is most requests.

What is decided beforehand because it cannot be decided in the moment

Some decisions are impossible to take during an event, not for want of time but because the competent person is busy or emotional. They therefore have to be taken beforehand, written down, and applied without further consultation.

The commonest is weather for an outdoor event: at what hour do we decide to move inside, who decides, and on what criterion. Taken on the day, that decision is always taken too late, because nobody wants to be the one who gave up.

The second is delay: what do we do if an element runs an hour late. Push everything back, cut something, or shorten. All three are defensible; what is not defensible is discussing them at that moment, with a tense client.

The third is the end. What time the music stops, what time the staff leave, who clears. An event whose end is not written stretches, and the stretching is paid for by people nobody warned.

These decisions are taken at the last meeting before the event, in ten minutes, and each is noted in one line. It is the most profitable passage in the entire preparation.

The phone on the day

On the day, your phone is a workstation and has to be organised as one. Without that it becomes the bottleneck: one person holds all the information, and that person spends the day answering.

The rule that unblocks it is one channel per subject rather than one per person. A group conversation with suppliers, one with the team, and the client separately — three threads, and everybody knows where to write.

The second rule is harder to hold and worth more: the client is not in the suppliers’ thread. They have no business arbitrating a rigging problem, and giving them access to those exchanges hands them a day of anxiety they did not buy.

The third concerns who must not be called. On the sheet, beside each name, who calls them. A supplier called by four different people about the same question loses more time than the problem was costing.

Finally, plan for no signal: an underground venue, a function room in a basement, a rural area. The printed sheet is the answer, and it is the least glamorous and most frequent reason this document exists on paper.

Slack: where to put it, and why not at the end

Every run sheet must contain time that does nothing, and where you put it decides how well it works.

The reflex is to put it at the end, finishing earlier than necessary. That is the worst place: final slack absorbs delays once they have all accumulated — which is to say once it has already been spent.

Useful slack goes before the irreversible moments and before the visible ones. Twenty minutes before guests arrive is worth an hour at the end of the evening, because it protects the one impression nobody can recover.

A second piece of slack goes in the middle, usually after the meal, because that is the segment whose length is least predictable. A meal depends on numbers, on service and on atmosphere — three things no preparation fixes.

Slack is written as a line, with an hour and a duration, not as an empty space. A line reading "buffer, twenty minutes" is respected; a blank between two lines is filled by the first delay that comes along without anybody noticing.

The written fallback, and the one that does not exist

A written fallback is short: three lines, for the three things that can genuinely happen in your configuration. Writing more produces a document nobody reads on the day.

The three usual candidates are rain for an outdoor event, a power cut, and the absence of a key supplier. Each is handled in a sentence: who decides, at what hour, and what we do.

The power cut deserves particular mention in this country, and it is prepared physically rather than in writing: knowing where the board is, who has the key, and whether the venue has backup supply. Three questions asked at the site visit.

There are also risks for which there is no fallback, and they should be named rather than papered over. A venue flooded the day before, a death in the family, an administrative closure: the answer is not a plan, it is a conversation and a contract clause.

Distinguishing them explicitly is what makes the rest credible. A supplier who claims a solution for everything is not reassuring; a supplier who says "for these three, here is what we do; for that one there is nothing, and here is what the contract provides" is far more so.

What is noted during, and the figure nobody can take

One thing is noted during the event, and it goes on the sheet itself: the real start time of each segment, written beside the planned one.

It takes three seconds a line and it produces, by the end of the evening, the only genuinely useful document in this trade: a comparison of what was planned with what happened, on an event you still remember.

Reread the next day, that column says exactly where your sheet is wrong. The same gap recurs from one event to the next — almost always in the same place, almost always on a transition — and three events are enough to correct the document for good.

The figure we will not give is the standard duration of a transition, and it is not because it is a secret. It is measured nowhere because it cannot be: the only people in a position to observe a transition are the ones performing it, and while they are doing it they are timing nothing.

That is not fixed by hiring an observer, which would be absurd for an event. It is fixed by the column of real times, which is the only measurement this trade can produce — local, specific to your venue and your team, and available from your next evening onwards.

What we do, and what we refuse to do

What we do is a document and a meeting: we put your run sheet into the format of one page readable standing up, with the transitions named and the points of no return at their hour, and we hold the ten minutes of advance decisions with you.

We do not coordinate your event. That is a profession, it is done on site, and it requires knowing the venue, the team and the client — three things an outside supplier does not have on the day. We refuse that role even when it is asked for.

We will not sell planning software for a one-page document that has to work with no signal in a basement. The printed sheet is the right technology here, and saying so costs us a subscription.

We will promise no standard transition duration, for the reason written in the previous section. A figure from us would become the basis of your sheet while describing neither your venue nor your team, and it would produce a wrong sheet with the authority of a number.

Finally, the substance happens without us and starts at the next event: writing the transitions as lines, putting a name on each, and recording the real times as you go. Three seconds a line, and three events to have a document that is right.

Frequently asked questions

What is the difference between a programme and a run sheet?

The programme is for guests: what happens, on round hours. The run sheet is for the people working: segments at their real length, transitions written as lines, one name per line. The test: give it to somebody who took no part in preparing it and ask what happens at 6.40 pm. If they hesitate, it is a programme.

Why write the transitions down?

Because that is where days are lost. A transition involves several people at once, belongs clearly to nobody — the caterer thinks the venue is clearing, the venue thinks the caterer is laying up — and is invisible to guests until it fails. Six joins of ten minutes make an hour, taken from the end, from the segment that matters most.

What should be asked of each supplier?

Two hours rather than one: the arrival hour and the hour their service starts. And a question almost nobody puts: "how long do you need on site before you can start". Also write down what each needs on arrival — access, a power point, a table, water — because those needs are known in advance and discovered on site.

Where should slack go?

Not at the end. Final slack absorbs delays once they have all accumulated, which is once it has already been spent. Put it before the irreversible moments and before the visible ones: twenty minutes before guests arrive is worth an hour at the end of the evening. And write it as a line — a blank between two lines is filled by the first delay that comes along.

Should the client be in the suppliers’ group?

No. They have no business arbitrating a rigging problem, and giving them access hands them a day of anxiety they did not buy. Three separate threads: suppliers, your team, the client. And on the sheet, beside each name, who calls them — a supplier called four times about the same question loses more time than the problem was costing.

How long should a transition take?

We give no standard duration, and not because it is a secret: it is measured nowhere because it cannot be. The only people in a position to observe a transition are the ones performing it, and while they are doing it they are timing nothing. Record the real times on your own sheet: three events are enough to get a document that is right for your venue and your team.

Where we come in

The real start time of each segment, written beside the planned one, corrects your run sheet better than any preparation meeting.

We bring it down to a single sheet legible on your feet, in low light.
We name the transitions rather than only the segments, because that is where it slips.
We leave the document with you, in a format that prints anywhere.

A one-page document calls for no planning software: we will not sell you one to replace a sheet that works standing up.

See the Entertainment & Events page Start with the free audit

Let us talk about your project

A free audit, no commitment: we look at your online presence and tell you what is holding it back.

Request the free audit Write to us