The org's institutional memory — SOPs, runbooks, vendor training, FAQ, post-mortems — searchable, taggable, exportable. Concert touring operations live in forty spreadsheets. We keep the canonical rider in one place and scope per-venue variants on top — no copy-paste, no lost revisions.
Tagged articles — Per-team, per-topic, per-show. Search finds it, tags surface it. On concerts jobs, this shows up as single-night shows, amphitheatres, arenas.
Vendor training — Articles tagged for vendor onboarding. Acknowledgement tracked to compliance. On concerts jobs, this shows up as single-night shows, amphitheatres, arenas.
Public intake form — External requests file as tagged articles. Triage, assign, resolve. On concerts jobs, this shows up as single-night shows, amphitheatres, arenas.
SOP runbooks — Standard operating procedures with versioning and required-reading flags. On concerts jobs, this shows up as single-night shows, amphitheatres, arenas.
Purpose-built for Concerts — single-night shows to stadium-scale runs. Canonical rider, per-venue overrides, shared crew pool, venue advancing, real-time box office metrics, and a field app the house staff actually wants to use.
The same primitives that ship in our Knowledge Base module — applied to concerts workflows.
Per-team, per-topic, per-show. Search finds it, tags surface it.
Articles tagged for vendor onboarding. Acknowledgement tracked to compliance.
External requests file as tagged articles. Triage, assign, resolve.
Standard operating procedures with versioning and required-reading flags.
Show-incident post-mortems with named actions and owners.
Markdown or PDF, per article or per tag. Walk-away on cancel, always.
Sign up free for small teams. Per-org pricing the rest of the way up.
One database. Every module reads from the same record.
Free, forever, for small teams. Per-org pricing the rest of the way up.