Core Thesis
Trade show logistics is not just shipment tracking. It is a deadline-bound, venue-specific execution problem with many hidden dependencies.
01 Summary
One Shared Execution Plan
ShowOps Portal is a multi-party web application for coordinating trade show booth logistics from pre-show planning through inbound freight, booth installation, show operation, dismantle, outbound freight, and post-show closeout.
Service Value
Robert's company can use the portal as a free value-added service that improves customer confidence and reduces manual status chasing.
SaaS Path
Paid tiers can add multi-event portfolio management, advanced AI risk detection, white labeling, integrations, API access, and analytics.
02 Research
Domain Realities the Product Must Respect
Operational Constraints
- Material handling/drayage often covers unloading freight, booth delivery, empty storage, return of empties, and reload after the show.
- Advance warehouse and direct-to-show windows drive cost, timing, risk, and exception handling.
- Large venues may require target move-in dates, freight planning questionnaires, marshaling yard check-in, and driver-specific instructions.
- Outbound release often depends on correct MHA/BOL paperwork, labels, carrier check-in, and avoiding forced freight.
Collaboration Constraints
- EAC rules and COI requirements create compliance gates that affect install access.
- Some services may be exclusive to official contractors, including material handling, electrical, rigging, or lead retrieval depending on show rules.
- Exhibitors often include marketing owners who are not logistics experts, so the app must translate operational complexity into plain next actions.
- Existing exhibitor portals and freight visibility tools show market demand for dashboards, deadlines, document context, milestone visibility, alerts, and AI risk signals.
03 Positioning
Between Project Management, TMS, and Exhibitor Portal
Not Generic PM
It understands show manuals, freight milestones, move-in and move-out rules, material handling, EAC/COI deadlines, booth readiness, and outbound release paperwork.
Not Just Freight Visibility
It tracks whether the booth can actually open on time, not only whether a truck is moving.
Not Just Service Ordering
It is operated by the logistics provider and focuses on execution, collaboration, risk, and closeout across parties.
Recommended Positioning Statement
"A trade show logistics command center that gives exhibitors and their partners one shared execution plan from first shipment to final outbound release."
04 Users
The Participant Network
Logistics Coordinator
Owns service delivery, exceptions, customer status, and control tower operations.
Exhibitor Marketing Owner
Needs a simple readiness plan, deadline alerts, and plain-English guidance.
Exhibitor Ops or Procurement
Handles shipment details, vendors, insurance, approvals, and internal coordination.
Exhibit House or Booth Builder
Needs shipment instructions, crate inventory, pickup windows, and arrival proof.
Carrier Dispatcher or Broker
Coordinates appointments, check-ins, ETAs, driver updates, and exception notes.
Driver or Owner-Operator
Needs mobile access for instructions, ETA, photo proof, and document upload.
I&D Lead or EAC
Needs install dependencies, freight arrival, COI/EAC status, and punch list flow.
Venue, GSC, or Service Desk
May receive limited event-specific visibility into freight and paperwork status.
Executive Observer
Needs high-level readiness, risk, and closeout reporting without operational noise.
05 Lifecycle
From Event Setup to Closeout
Create Event
Capture venue, dates, move-in/out windows, warehouse rules, manuals, and contacts.
Onboard Booth
Invite exhibitors, vendors, carriers, and onsite contacts with role-specific tasks.
Plan Freight
Associate inbound shipments, crate details, pickup plans, labels, and target windows.
Manage Readiness
Use checklist, Kanban, Gantt, documents, Q&A, alerts, and threaded decisions.
Execute Install
Track booth delivery, empties, labor blockers, photo proof, punch list, and show-ready.
Move Out
Confirm outbound carrier, labels, MHA/BOL, service desk submission, and pickup.
Close Out
Collect POD, exceptions, cost/risk history, lessons learned, and post-show report.
06 MVP
Prove Coordination Value First
MVP Must Include
- Multi-tenant events, exhibitors, booths, users, and roles.
- Event setup with dates, windows, contacts, documents, and show rules.
- Booth workspace with readiness checklist.
- Task/deadline engine with dependencies, Kanban, and basic Gantt.
- Inbound/outbound shipments with milestones, documents, contacts, and ETA fields.
- Document checklist for labels, BOL/MHA, COI, EAC, packing list, and invoices.
- Contextual threaded discussions and email reply-to-thread.
- Rules-based exceptions, subscriptions, reminders, and escalations.
- Control tower, exhibitor dashboard, AI Q&A, and audit log.
MVP Can Defer
- Broad carrier API coverage and EDI automation.
- Advanced predictive AI risk scoring.
- Full critical path graph visualization if basic dependency views are enough.
- White-label self-service administration.
- Full billing, metering, and SaaS plan management.
- QR/barcode asset scanning and offline mobile mode.
07 Requirements
Functional Requirements
P0 MVP
P1 V1
P2 Later
Account, Access, Event, and Booth Management
| ID | Priority | Requirement | Review Note |
|---|---|---|---|
| ACC-01 | P0 | Support tenants for Robert's company, customer organizations, vendors, and optional white-label customers. | Users may belong to multiple organizations and events with different roles. |
| ACC-02 | P0 | Provide role-based permissions for coordinators, exhibitors, vendors, carriers, drivers, onsite leads, observers, and admins. | Every object must be scoped by event, booth, shipment, organization, and role. |
| ACC-03 | P0 | Support magic links or limited-access links for drivers and one-time participants. | External participants can update assigned work without full account setup. |
| EVT-01 | P0 | Create events with venue, time zone, show dates, move-in/out windows, target dates, warehouse windows, and service contacts. | Event setup becomes the source of deadlines, alerts, and rules. |
| EVT-02 | P0 | Upload show manuals, deadline PDFs, labels, EAC forms, and service instructions. | Uploaded files are searchable and permissioned. |
| EVT-03 | P1 | Extract candidate dates, addresses, contacts, shipment windows, and rules from documents for human review. | Approved extracted data can generate event tasks and risk rules. |
| BOO-01 | P0 | Create booth records with exhibitor, booth number, hall, size, target dates, and primary contacts. | Each booth gets a workspace with tasks, timeline, docs, messages, risks, and shipments. |
| BOO-03 | P1 | Track booth asset inventory, crates, cases, pallets, graphics, demo products, and equipment. | Assets can later be linked to package-level shipment tracking. |
Tasks, Deadlines, Shipments, and Documents
| ID | Priority | Requirement | Review Note |
|---|---|---|---|
| TSK-01 | P0 | Generate event-specific task checklists from show rules and templates. | Tasks include owner, due date, dependency, status, reminder cadence, and evidence. |
| TSK-03 | P0 | Provide list, Kanban, calendar, and basic Gantt views. | Views should show move-in/out windows, shipment milestones, and blocking dependencies. |
| TSK-04 | P1 | Provide dependency graph and critical path analysis. | System identifies items that can delay show-ready status or outbound release. |
| SHP-01 | P0 | Create inbound and outbound shipments with carrier, broker, driver, origin, destination, service level, tracking, pieces, weight, and target windows. | Shipment detail page includes timeline, documents, messages, ETA, and risk state. |
| SHP-03 | P0 | Track configurable shipment milestones from planned pickup through POD. | Must handle advance warehouse, direct-to-show, marshaling yard, booth delivery, outbound release, and delivery. |
| SHP-04 | P0 | Allow manual updates, email updates, driver mobile updates, and later API/EDI updates. | Each update records source, time, user/system, and confidence. |
| DOC-01 | P0 | Store documents by event, booth, shipment, task, and organization. | Files are searchable, permissioned, versioned, and attachable to discussions. |
| DOC-03 | P0 | Track required documents and structured MHA/BOL completion fields. | System flags missing destination, carrier, contact, piece count, weight, signature, and related fields. |
Collaboration, Alerts, Dashboards, Mobile, and Integrations
| ID | Priority | Requirement | Review Note |
|---|---|---|---|
| COL-01 | P0 | Provide threaded discussions tied to events, booths, shipments, tasks, documents, and exceptions. | Threads support mentions, attachments, due dates, decisions, and internal notes. |
| COL-02 | P0 | Support email reply-to-thread. | External users can stay in email while preserving context in the portal. |
| NOT-01 | P0 | Users can subscribe to event, booth, shipment, task, document, risk, or role-based alerts. | Notification controls must avoid alert fatigue through severity and digest options. |
| ANA-01 | P0 | Provide event control tower dashboard. | Coordinator sees all booths, readiness, shipment status, risks, deadlines, and unresolved messages. |
| ANA-02 | P0 | Provide customer booth dashboard. | Exhibitor sees simple status, next actions, key dates, shipments, docs, and support threads. |
| MOB-01 | P0 | Mobile-responsive views for drivers, onsite leads, and booth staff. | Core workflows must work on common phone screen sizes. |
| INT-01 | P0 | CSV import/export for events, booths, contacts, tasks, and shipments. | Supports real-world bootstrapping from spreadsheets. |
| ADM-01 | P1 | Tenant branding, terminology, templates, roles, and notification defaults. | Required for a professional SaaS add-on and future white-label offer. |
08 AI and Risk
Operational Assistance with Human Control
AI Q&A
- Answer questions over show manuals, event rules, booth data, shipments, tasks, documents, and threads.
- Support prompts like "What must I do this week?", "Where is shipment 102?", and "What risks could prevent booth 471 from opening?"
- Generate customer-ready status summaries for coordinator review.
- Recommend next best action for risks with rationale and source references.
Guardrails
- Never expose data outside the user's permissions.
- Cite event documents or structured records for operational answers.
- Label uncertain inferences clearly.
- Require human approval for customer-visible messages, carrier instructions, compliance conclusions, and service substitutions.
- Audit accepted, rejected, and edited AI recommendations.
Default Exception Library
Freight Timing
ETA outside warehouse window, direct-to-show target, move-in window, or outbound carrier cutoff.
Missing Inputs
Carrier, driver, tracking, pickup appointment, package counts, weights, labels, or contact details missing near cutoff.
Compliance Gates
Missing EAC authorization, missing COI, expired coverage, or service restrictions that block install work.
Install Dependencies
Booth install blocked by freight, electrical, flooring, rigging, labor, empty labels, or unresolved approvals.
Outbound Release
Destination, carrier, MHA/BOL, labels, service desk submission, or driver check-in incomplete before move-out cutoff.
Communication Risk
Critical mention unanswered, ambiguous commitment in a thread, conflicting dates, or missing decision owner.
09 Data and Permissions
Core System Model
Core Entities
Tenant, Organization, User, RoleAssignment, Event, Venue, ShowRule, Booth, Stakeholder, Shipment, ShipmentLeg, Package, Milestone, Task, Dependency, Document, DiscussionThread, Message, Risk/Exception, NotificationSubscription, KnowledgeSource, AuditEvent, and IntegrationConnection.
Sensitive Data Controls
- Internal Robert's company notes are hidden from customers and vendors.
- Pricing, contracts, and invoices require separate permissions if added later.
- AI answers use only sources the requesting user is allowed to access.
- Export permissions must be explicit and auditable.
Default Role Access
| Role | Typical Access |
|---|---|
| System Admin | All tenants and platform configuration. |
| Tenant Admin | Tenant users, templates, events, branding, and reports. |
| Logistics Coordinator | Assigned events, booths, shipments, documents, messages, risks, and internal notes. |
| Exhibitor Admin | Own organization, booth, invited vendors, shipments, documents, and messages. |
| Exhibit House or EAC | Assigned booth tasks, install documents, freight data needed for work, and relevant messages. |
| Carrier or Broker | Assigned shipments, movement details, documents needed for transportation, and shipment threads. |
| Driver | Assigned shipment mobile workflow only. |
| Observer | Read-only dashboard and reports for assigned events or booths. |
10 Roadmap
Recommended Delivery Plan
Phase 0
Discovery and prototype
Interview users, collect real show manuals and workflows, map templates, prototype key screens, and select a pilot show.
Phase 1
MVP pilot
Build the core portal and run 1 to 3 shows with 10 to 30 exhibitor booths under concierge operations.
Phase 2
Operational scale
Add templates, bulk operations, email ingestion, document extraction, mobile improvements, reporting, and key integrations.
Phase 3
SaaS add-on
Add white labeling, SSO, API/webhooks, billing, QR assets, advanced AI risk, and portfolio analytics.
11 Commercial Model
Free Value-Add with Paid Expansion
Free Value-Added Tier
- Included when Robert's company manages logistics.
- Booth workspace, shipments, deadlines, documents, threaded collaboration, and basic alerts.
- Limited AI Q&A and status summaries.
- Limited seats per customer event.
- Improves customer experience, reduces check calls, and creates switching costs.
Paid SaaS Add-On
- Multi-event portfolio management.
- Advanced AI risk detection and summaries.
- Carrier/TMS/API integrations.
- White-label portal, SSO, audit exports, and enterprise controls.
- Advanced analytics and post-show benchmarking.
12 Success Metrics
How to Know It Works
1
Higher logistics customer close rate when portal is included in proposals.
2
Fewer "where is my shipment?" emails and status calls per show.
3
Improved on-time advance warehouse and direct-to-show arrival rates.
4
Higher percentage of booths show-ready by target time.
Operational Metrics
- Shipments with complete data before pickup.
- Missing EAC, COI, MHA, and BOL issues by show.
- Exception detection lead time and resolution time.
- Outbound shipments released without missing paperwork.
- Carrier no-show incidents caught before forced-freight cutoff.
Engagement and AI Metrics
- Invited stakeholders activated.
- Task completion rate before deadline.
- Threads resolved without coordinator intervention.
- AI answer citation rate and human correction rate.
- False positive and false negative risk rates.
13 Risks
Product and Delivery Risks
| Risk | Impact | Mitigation |
|---|---|---|
| Carrier and show APIs are unreliable or unavailable. | Visibility gaps. | Design MVP around manual updates, email ingestion, mobile links, and CSV import first. |
| Show rules vary by venue, contractor, and year. | Bad assumptions create operational mistakes. | Use templates with event-level human review and source citations. |
| External users resist accounts. | Lower adoption. | Use email reply-to-thread, magic links, and minimal role-specific screens. |
| AI gives overconfident advice. | Trust and liability risk. | Require citations, label uncertainty, filter by permissions, and require human approval for action. |
| Exception fatigue. | Users ignore alerts. | Use severity, ownership, deadlines, digest mode, and tunable rules. |
| SaaS scope expands into TMS, e-commerce, or labor dispatch. | Delivery risk and product dilution. | Keep initial scope centered on booth execution and logistics collaboration. |
14 Open Questions
Decisions for Robert and the Team
Market Focus
Which segment anchors the MVP: Robert's current logistics customers, small exhibitors, enterprise exhibitors, exhibit houses, or agencies?
Operating Model
Will the portal be used only when Robert's company controls logistics, or also when customers use other carriers?
Data and Systems
Which TMS, CRM, task tool, or customer portal should integrate first?
Workflow Scope
Should international customs and commercial invoice workflows be included in the first release?
AI Boundaries
What level of AI guidance is acceptable in high-value shipment and compliance contexts?
Pricing
Which pricing dimension best supports business development without turning a free value-add into a support burden?
15 Sources
Research Links
- GES: Material Handling Made Easy
- GES: What is a Material Handling Agreement?
- ENTELEC: EAC Rules and Regulations
- IMTS 2026: Carrier Information
- IAEE: CEM Event Operations Workbook
- GoShow Nexus Exhibitor Portal
- ExpoPlan trade show project management
- Find Your Freight real-time freight visibility
- FreightPOP inbound and outbound tracking
- Portcast supply chain visibility and AI risk detection