Coordinate event run-of-show cues, owners, vendor commitments and readiness checks, then manage event-day execution and closeout.

Cue connects a client event brief to timed show execution. Producers create cues with owners, record vendor commitments, and complete readiness checks. Required vendors must be Confirmed and checks Done before the event can go Live; closeout also requires every required cue Done. Reopening preserves the log, vendor confirmations and check completion while resetting cue states to Planned. The English pilot uses ToolJet Database and fictional data. Package export and clean-install validation remain pending.
Built for Event producers coordinating a client event, venue, show cues, vendors and readiness work.
Coordinate event run-of-show cues, owners, vendor commitments and readiness checks, then manage event-day execution and closeout.
Select an event and see its first four cues, owners and production readiness.
Record the client, venue, producer and date with a unique event reference.
Create and edit cue time, owner, required status and execution evidence. Advance the event lifecycle here.
Record provider, service, contact, arrival time, cost, requirement and confirmation note.
Assign readiness items and record evidence before going Live.
Create events and update client, venue, date and producer while the event is Planning or Live.
Use same-day venue-local HH:MM times. Mark cues Planned, Live, Done or Skipped during execution and record completion notes.
Track required or optional providers, arrival time and nonnegative commitment cost; confirmation requires a note. No payment is processed.
Go Live only with a rundown and all required checks/vendors ready. Close only when required cues are Done. Cancel and reopen while retaining the production log.
The pilot uses 1 table with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Events | 3 sample events | Planning, Live and Closed examples with 9 embedded cues, 4 vendor commitments and 6 readiness checks. |
No invitations, ticketing, payments or automatic vendor communication. Times use same-day local venue HH:MM; no timezone conversion or overnight scheduling. Optional cues, vendors and checks do not block progression. Reopening resets cue states to Planned while preserving confirmations/check completion. Desktop English pilot with a disclosed 1,000-event limit. Public deploy/download awaits package and clean-install validation.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance once the template is released.
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.
Event briefs, timed show cues, owners, vendor commitments, readiness checks and a Planning-to-Live-to-Closed workflow across five pages.
The event needs at least one cue. Required readiness checks must be Done and required vendor commitments Confirmed.
Required cues must be Done. Optional cues may remain unfinished. Required vendor and readiness conditions are checked again at closeout.
Cue states reset to Planned. The production log, vendor confirmations and completed readiness checks are preserved for review.
No. It records operational details and commitments without sending messages, processing payments or connecting to external calendars.
Yes. Use a prompt to adapt colors, branding, layout, fields and workflows. Requested extensions require implementation and testing.
Public deployment and download remain disabled until an actual import package and a clean installation are validated.