Exhibitor manual version control for when the fire marshal changes a rule

The manual went out in March. In June the venue's fire marshal looks at your hall plan and decides that any covered ceiling over 100 square feet now needs a sprinkler drop, which was not the rule at your last edition and is not the rule printed on page 71. Your operations lead does the sensible thing and emails a corrected pdf to every exhibitor.

In September a company arrives on the floor with a booth built to the March rule, because the person who read the manual in March left in May and the person who replaced her downloaded the file from the portal in April. Exhibitor manual version control is the boring fix for this, and almost nobody has it. The manual gets stored as one document, and every rule inside it has a separate history that the document cannot express.

Pure Exhibits (2026) puts the typical exhibitor manual at between 50 and a few hundred pages. ExpoFP (2026), setting out an 18 month planning timeline, has the exhibitor kit going out four months before the show. Four months is long enough for a venue to change a rule, a contractor to change a rate and a city to change a permit requirement, and the document that landed in an exhibitor's inbox in March is the one they will build against in September.

What actually changes in a manual after release?

Go back through the last two editions of one show and the changes fall into a small number of kinds.

Rules imposed from outside. The fire marshal's ruling on covered ceilings. A new venue requirement on rigging points. A city permit that now needs 30 days rather than 14. These arrive without warning and the show cannot negotiate them.

Rules the show changes itself. A tightened height limit at the back of an island, a new rule about noise from demonstration areas, a change to what an exhibitor appointed contractor has to submit.

Numbers that move. Late order surcharges, drayage rates, labour rates for overtime. These are not rules at all, but they live in the same document and exhibitors treat a printed rate as a promise.

Corrections. A wrong phone number, a deadline printed as the 14th that was always the 4th, a form that references a section that got cut.

The four kinds behave differently and matter differently, and a single reissued pdf flattens them into one undifferentiated event. An exhibitor who is told the manual has been updated has no way to know whether their booth is now illegal or whether somebody fixed a typo.

Give every rule a number, a version and a scope

Version control belongs at the level of the individual rule.

Pull the manual apart into numbered rules once, by hand, and accept that this is a week of somebody's time. Each rule gets a stable identifier that is never reused, even if the rule is deleted. Then each rule carries: the text, the version it was introduced in, the version its text last changed in, the date it takes effect, the booth types it applies to, and where it came from.

That last field is the one operations teams skip and the one that pays for the whole exercise. A rule sourced from the fire code cannot be waived by the show. A rule sourced from the general contractor's work rules probably can, for a price. A rule the show wrote itself last year because one exhibitor was annoying can be waived by the show director in about nine seconds. When a coordinator gets a call at 4pm on a Friday asking whether a rule can be bent, the source field answers the question without anyone having to remember why the rule exists.

Scope is the second field that earns its place. Most rules in a manual apply to a subset of exhibitors. A rule about hanging signs applies to islands and peninsulas. A rule about exhibitor appointed contractors applies to the companies bringing one. A rule about carpet applies to everyone. Recording scope means a change to the hanging sign rule generates notices only for the exhibitors who can hang a sign.

Version the manual as a whole with a simple counter, and increment it whenever any rule's text changes. Release 1.0 in March, 1.1 in April, 1.2 in June. What matters is that a coordinator on the phone can ask which release the exhibitor is working from, and that the answer is a release number they can read off the front page.

How much does a diff actually shrink the notice?

Here is the arithmetic on a mid-sized show, with figures made up to be followed rather than measured.

The manual holds 180 numbered rules across 214 pages. The show has 412 exhibiting companies. Between release 1.0 in March and release 1.3 in July, 11 rules changed, which is 6.1 per cent of the manual. Four of the 11 apply to every exhibitor, including the covered ceiling ruling. Five apply only to island and peninsula booths, of which the show has 96. Two apply only to companies bringing their own contractor, of which it has 37.

Total notices generated is 4 times 412, plus 5 times 96, plus 2 times 37, which is 1,648 plus 480 plus 74, or 2,202. Spread across 412 exhibitors that averages 5.34 changed rules each. The heaviest case, an island booth with its own contractor, gets 11. A 10 by 10 inline with the general contractor gets 4, and can read all four in under a minute.

Now price the alternative. Reissuing the manual asks 412 companies to reread 214 pages. At a generous 40 seconds a page that is 143 minutes each, or about 980 hours across the show. The reason nobody rereads the manual is that rereading the manual is a week of work per exhibitor and the change was six per cent of it.

The point of the diff is that the second number never had to exist. You already know which 11 rules moved. The only thing standing between you and a four line email is that the manual was stored as a pdf instead of as rules.

The change notice exhibitors will read

Keep the notice to the changed rules, in the exhibitor's own terms, with the old text and the new text side by side.

Lead with the rules that can stop a booth going up. A change to a fire rule, a height limit or a rigging requirement goes at the top with the effective date and a plain statement of what the exhibitor has to do differently. A change to a surcharge percentage goes lower down. A corrected phone number goes at the bottom or in no notice at all.

Say where the rule came from. "The venue fire marshal has required this since 12 June" is a sentence exhibitors accept. "The manual has been updated" is a sentence they ignore, and it is the one most change notices lead with.

Send the notice by email and post it in the portal, and record which exhibitors opened it. The portal record is the one that survives a dispute at the service desk in September, and the completed-task view of portal adoption tells you whether the population you are notifying is one that uses the portal at all.

What version history buys you at the service desk

Three things, all of them at move in, which is when the manual stops being paperwork.

A coordinator can answer which release an exhibitor built against. If the company downloaded 1.0 on 14 March and the rule changed in 1.2 on 9 June, the show knows the exhibitor was not told in time and can decide to eat the cost. If they downloaded 1.3 in July and built to the old rule anyway, that is a different conversation.

The show can see which rules generate the most argument. Rank rules by how many exhibitor questions cite them, and the top of that list is your redraft list for next year. Tagging inbound exhibitor email to the task or rule it refers to is what makes that ranking possible.

And the rule table becomes the thing the portal renders. Deadlines, booth type rules and forms all read from one place, so a rule cannot be current in the portal and stale in the pdf, which is the failure mode most shows are living with right now.

Where this stops

Version control records what your manual said and when. It has nothing to say about whether the rule was right.

The fire marshal's ruling in the opening paragraph is the usual case: a person with authority makes a decision in a meeting, nobody writes it down in a form you can cite, and your rule record ends up holding your operations lead's interpretation of a verbal instruction. Six months later an exhibitor challenges it and the source field says "venue fire marshal, June", which is better than nothing and considerably worse than a written ruling. Ask for the ruling in writing every time, and record when you asked and did not get it.

The second limit is reach. Version control tells you a rule changed and who it affects. It cannot make an exhibitor read the notice, and the exhibitors who most need it are the first timers who downloaded the manual once and have not logged in since. That is a different problem, and completion rates by task type across the onboarding window is where it gets measured.

The third is effort. Cutting a 214 page manual into 180 rule records is genuinely a week, and the show that has just closed does not want to spend a week on documentation. It gets easier every edition afterwards, because from then on you are editing individual rule records, but the first pass is real work with no visible output on the day it is done.

Start with one section. Take the booth display rules out of your current manual, number them, add the scope and source fields, and diff them against last edition's. Whatever comes back on that list is the set of changes your exhibitors were never told about, and it takes an afternoon to find out how long it is. If you want the wider picture of how the onboarding workflow hangs together, that is where the deadline calendar and the compliance record join up.