Document control in four rules
- Use the current show edition and official portal as the binding baseline.
- Separate general guidelines, show-specific deviations and project-specific requests.
- Link each submitted file to an owner, revision, submission record and response.
- Do not describe document preparation as an approval guarantee.
1. Build the official source hierarchy
Begin with the exhibitor admission, current organizer portal and the venue information linked for that show. Record the exact event edition, venue, hall, stand number and access account. General technical guidelines explain the baseline, while show-specific chapters, order portals and direct project requests can add or change requirements.
Messe Düsseldorf provides a useful public example: its 2026 Technical Guidelines are published centrally, but the venue states that exceptions or alterations may apply to individual trade fairs and guest events. This is why a generic checklist cannot replace the current event record.
Sources for this section: [1]
2. Classify the documents before producing them
A document register should distinguish project baseline, design drawings, technical descriptions, specialist evidence, venue service orders and submission correspondence. Not every booth requires every document. The register therefore includes a requirement source and status rather than assuming that a long list is universally mandatory.
Typical working files may include a floor plan, elevations, dimensions, material notes, structural or fire-safety evidence where requested, installation requirements and forms for special structures or technical services. The current organizer or venue information determines the actual set and accepted format.
- Requirement and exact official source
- File owner and reviewer
- Revision and approval status
- Submission channel and timestamp
- Official response or open question
Sources for this section: [2]
3. Control drawings and revisions
Every drawing should carry a project identifier, title, revision, date and responsible owner. When a drawing changes, the register records what changed and whether the change affects a previously submitted file. Sending a revised attachment without withdrawing or replacing the earlier version creates avoidable ambiguity.
The design view, execution drawing and venue submission may serve different purposes. A presentation rendering communicates intent; a technical submission needs the information requested by the relevant authority. The team should never treat a visual concept as proof that all technical requirements have been reviewed.
4. Separate preparation, submission and decision authority
A local project team can collect inputs, prepare files, translate questions and coordinate submission. The exhibitor may need to provide account access, declarations, corporate information or formal authorization. The organizer, venue or appointed reviewer decides whether a submission is required, complete or accepted.
Messe Düsseldorf's English order-form page illustrates this separation: the exhibitor receives access to the Online Order System and can authorize another party to order assigned services. Access and authorization are operational prerequisites; they do not transfer the venue's decision authority to the contractor.
Sources for this section: [2]
5. Close the loop before production and travel
Before production, compare the current design and execution files with the latest submitted revision, official response and outstanding conditions. Before shipping or travel, repeat the check for access, traffic, service orders and show-specific notices. A submission receipt alone is not the same as approval.
Keep the final record with the approved or accepted version, correspondence, service confirmations and unresolved items. This supports handover and future review without turning an old event pack into the baseline for the next edition.
Booth document register: minimum control fields
| Document group | Owner | Evidence to retain | Decision source |
|---|---|---|---|
| Event baseline | Exhibitor | Admission, stand plan, current manual | Organizer |
| Design drawings | Project team | Revision and written sign-off | Exhibitor / reviewer |
| Technical evidence | Qualified contributor | Requested file and response | Venue / appointed body |
| Venue services | Authorized account owner | Order confirmation | Venue / service partner |
| Submission status | Named coordinator | Timestamp, receipt, decision | Official submission channel |
Questions about German booth approval documents
Do all exhibition booths in Germany require approval drawings?
No universal rule applies to every show and stand. Requirements depend on the current organizer, venue, event edition and booth design. Check the official event portal before deciding which drawings or evidence are required.
Can a booth contractor guarantee approval?
No. A contractor can prepare and coordinate documents, but the decision belongs to the organizer, venue, authority or appointed reviewer. Any guarantee that ignores project-specific rules should be treated cautiously.
Is a submission receipt the same as approval?
No. A receipt only confirms that a file or form was submitted. Retain the official response, status and any conditions, and connect them to the exact drawing revision that was reviewed.
Can we reuse last year's document pack?
Use it only as a reference for questions. Current guidelines, event-specific deviations, portals, forms and stand details may differ. Build the new register from current official sources.
Scope and legal limitation
This guide is a document-control method, not organizer guidance or legal, structural, fire-safety or engineering advice. Requirements and decisions must be confirmed in the current official event sources. The cited Messe Düsseldorf pages are examples, not a universal German rulebook.
Source review against current public AUMA and Messe Düsseldorf information; event-specific confirmation remains mandatory.
Last reviewed: 3 September 2026Official reference sources
Turn the event pack into a controlled register
Send the event, stand plan and current organizer documents. We will identify missing inputs, document owners, official dependencies and the next review point.
Request a document check →