Quick answer: An exhibitor certificate of insurance checklist should show who must provide a certificate, which event-specific requirements apply, the submission deadline, who reviews it, what remains incomplete and whether the show organiser has issued formal clearance. Track exhibitor documents separately from exhibitor-appointed contractor (EAC) documents. A status call can chase a missing file or identify a contact at the broker; it cannot determine that insurance is sufficient or authorise an uninsured contractor to enter the show floor.
A stand can be ready, freight can be booked and staff can be travelling while one document quietly threatens move-in. An exhibitor may have uploaded the wrong certificate. A booth builder might be listed under its trading name rather than the insured legal entity. Or a policy may cover public show days but not the earlier installation period. These are coordination problems until they reach the person empowered to review the insurance and apply the show’s rules.
Why exhibitors and appointed contractors need separate checks
An exhibiting company and its external booth builder are not automatically the same insured party. Show manuals often distinguish their responsibilities, forms and deadlines. Event-specific contractor documentation, insurance and access rules vary, and some shows require the exhibitor name and booth number to align across the contractor notification and the certificate. These are examples, not universal rules for every event.
The organiser should start from the current event’s exhibitor kit, contract, venue rules and insurance instructions. Do not copy insurance limits, additional-insured names or submission dates from another show’s PDF. The correct deadline may depend on when an external contractor starts work, not when the exhibition opens to visitors.
Build two linked records: the exhibitor record and a separate record for each appointed contractor. One exhibitor may have several EACs covering stand construction, lighting, graphics and dismantling. A single approved exhibitor certificate should never automatically mark every contractor as cleared.
Build the documentation register before inviting uploads
Use one event-level reference register maintained by operations or risk management. Store the event name, venue, move-in and move-out dates, authoritative manual version, authorised reviewer, escalation contact, and the show’s own acceptance criteria. Then create one submission item per legal entity.
For each item, capture the exhibitor and booth reference; contractor and scope, if applicable; legal insured name; broker contact; file-received timestamp; policy period as declared on the certificate; requested additional-insured wording; reviewer; and an evidence link in a permission-controlled repository. A board column reading “Uploaded” is not the same as “Accepted.”
Where the organiser uses an external COI verification service, record the external case reference and the status reported by that service. Avoid copying full insurance schedules and unnecessary personal details into a general-purpose project board. Keep the authoritative document under the access rules agreed with the organiser and its vendors.
Work backwards from move-in, not opening day
A useful workback plan has four checkpoints. The relative schedule below is an illustrative operational cadence, not a regulatory deadline or a substitute for the show’s exhibitor manual.
Six to eight weeks before move-in: announce the requirements
Send one clear instructions package containing the current rules, the required form, the submission route, the responsible contact and the date by which a reviewer must receive the documents. Ask exhibitors to identify every external stand contractor. Do not simply email “Please send your insurance”; that leaves exhibitors guessing which entity and event period matter.
Four weeks before move-in: reconcile the contractor roster
Compare the exhibitor portal, show-floor contractor roster and received COI records. If an EAC is named on the form but has no submission item, flag it. If the contractor has changed, retain the superseded record and start a new review. This is also the point to discover that a document was submitted to a general mailbox but never connected to the correct booth.
Two weeks before move-in: review exceptions with a named owner
Generate a queue of missing certificates, certificates awaiting review and specific deficiencies returned by the authorised reviewer. Communicate the stated deficiency, not your interpretation of coverage. Allow enough time for brokers to reissue documents. Escalate potentially blocked access in accordance with the organiser’s escalation rules.
Final move-in readiness: publish only authorised clearance
Produce a controlled access list using the definitive reviewer or accreditation team’s approved status. If a contractor arrives while its review is pending, staff should follow the event’s escalation and security process. “We are waiting for the broker” is not permission to enter.
Give every record a status that means one thing
A practical status sequence is Not requested → Requested → Received → Under review → Changes requested → Accepted or Rejected. Use a separate Access cleared field, because an accepted COI may be only one requirement among work permits, badges or safety inductions. Add a time-stamped event to the record every time a reviewer updates the status.
Do not use “Complete” for both document upload and approval. An operations manager needs to answer three distinct questions: Has the file arrived? Has the authorised reviewer accepted it? May the entity access the hall during its required dates? If the system collapses these questions, it creates false confidence precisely when deadlines are tight.
A refusal or incomplete review should preserve the exact source, deficiency code, responsible reviewer and next action. A status of “needs revised wording” is more actionable than “failed.” Keep a trail of replacement files; the most recent upload is not necessarily the approved version.
Example: a stand builder has the wrong cover dates
Consider a hypothetical exhibitor whose external stand builder is booked to assemble a booth on Monday. Its certificate begins on Wednesday, the first public show day. The coordinator records Received, attaches the secure evidence reference and routes it to the organiser’s insurance reviewer. The reviewer requests proof covering the required installation period.
The coordinator can contact the builder to ask whether its broker has issued a corrected certificate, then record the expected submission time. The coordinator should not amend insurance dates, assume cover exists or assure security that the builder is approved. After the reviewer updates the official clearance result, the event access roster is updated from that authorised result.
The difference may feel bureaucratic, but it protects exhibitors, organisers, the venue and the contractors from a misleading document-status dashboard.
Use a short AI follow-up only for administrative progress
For a high-volume event, manually chasing dozens of brokers and exhibitors creates email noise. A controlled outbound check-in can ask: “Has the requested revised certificate been submitted? If yes, which approved channel was used? If not, who owns the next step and when can our reviewer expect it?” The call must identify the organisation, respect calling and consent requirements, and never claim to be the insurer or an underwriter.
AI Workflow Design offers status-update agents and workflow integrations that can support approved status collection. Any event-specific COI workflow, document security controls or access-roster integration needs to be scoped and tested; a generic check-in agent is not an insurance verification system. Record unsuccessful contacts as unresolved rather than converting silence into approval.
Measure completion without gaming the deadline
Report the percentage of entities accepted by the required decision date, not just the upload rate. Also track missing EAC declarations, average review turnaround, resubmission loops and the number of move-in escalations. Segment by exhibitor and contractor. A high upload rate paired with numerous unreviewed records is a warning that the last-mile process has failed.
Use these measures to improve the next event’s instructions and lead times. If many certificates are returned for the same description-of-operations problem, revise the sample and submission instructions; do not pressure reviewers to accept incomplete evidence.
Final pre-show checkpoint
Before doors open to contractors, reconcile the authorised insurance status with the badge list, contractor roster and approved work windows. Keep an exception owner available on site. The checklist has done its job when the operations team knows exactly what is documented, what is awaiting a qualified decision and who can resolve it—without an automated tool quietly making the decision itself.
Next step
Want these follow-ups handled consistently? Explore Autoza AI for monday.com or talk to AI Workflow Design about scheduled, permissioned status follow-ups that leave approvals with the right people.
Frequently asked questions
Does every exhibitor need to submit a COI?
Requirements vary by show and role. Some organisers require exhibitor certificates; others primarily collect them for EACs. Use the current exhibitor manual and the organiser’s written instructions.
Is a contractor covered by the exhibitor’s insurance certificate?
Do not assume so. Appointed contractors may need their own documentation, and the organiser or its authorised insurance reviewer must determine whether the event’s conditions are met.
What information should an exhibitor COI tracker record?
At minimum: entity, booth and role, required event dates, file receipt, reviewer status, deficiency or next action, responsible owner and an authoritative clearance reference.
Can an AI agent approve an insurance certificate?
No. It can request a missing submission or report administrative status. Coverage assessment and event access clearance belong to the designated insurer, reviewer, organiser and security process.
What should happen if a certificate arrives after the deadline?
Mark it late, send it through the authorised review process and follow the show’s escalation rules. Arrival alone must not unlock contractor or exhibitor access.
Related reading
- Post-Event Equipment Returns: A Supplier Follow-Up Workflow
- Exhibitor Move-In Deadlines: A Pre-Show Follow-Up Checklist
- Venue Access and Load-In: Who Confirms Each Event Logistics Milestone?
- Event Accessibility Deliverables: Confirm Captions, Access Routes and Services
- Sponsor Artwork Deadlines: Follow Up on Event Branding Deliverables
- Event Load-In Scheduling: Prevent Loading Dock and Delivery Conflicts