Outcome. A stand enquiry becomes a held package with an expiry date, then a contract that gets chased three times on a schedule nobody has to remember, and the moment it is signed the production tasks appear: booth number, passes, artwork, invoice.
Workflow map
Enrollment, branches and actions at a glance
events-002
flowchart TD
A[Deal created in Sponsorship, stage Enquiry] --> B[Notify owner, task send prospectus]
B --> C{Prospectus sent within 3 days?}
C -->|no| D[Task and manager notice]
C -->|yes| E{Package held within 10 days?}
D --> E
E -->|no| F[Requalify task, end]
E -->|yes| G[Set hold expiry, copy passes, notify inbox]
G --> H{Contract sent within 7 days?}
H -->|no| I[Task for owner]
H -->|yes| J[Reminder 1 at 3 days]
I --> J
J --> K[Reminder 2 at 4 days, names the expiry]
K --> L[Reminder 3 at 5 days, manager notified]
L --> M{Signed before hold expiry?}
M -->|no| N[Hold expired, release the slot, end]
M -->|yes| O[Copy tier to company, artwork received = No, notify production]
O --> P[Four tasks: booth, logistics, invoice, passes]
P --> Q[14 days before artwork deadline]
Q --> R{Artwork received?}
R -->|no| S[Specification email and task]
R -->|yes| T[End]
S --> U[3 days before artwork deadline]
U --> V{Still not received?}
V -->|no| W[Escalate to production manager]
V -->|yes| T
When to use it, when not to
- UseUse it when you sell sponsorship or floor space against a deadline, which means every edition with a printed floor plan and an artwork cut off.
- UseUse it when more than one person sells, since the hold count is what stops two of them promising the same headline package in the same afternoon.
- SkipDo not use it for ticket sales. Individual tickets belong in the ticketing platform, and one deal per attendee turns the pipeline into a mailing list.
- SkipDo not use it if your sponsorship pipeline shares stages with new business. The stage filters here are specific, and a mixed pipeline will enrol client work into a stand chase.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.13 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.13 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.7 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.4 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
