Running event production
The hall is confirmed, catering is still a quote, and the DJ said yes out loud. On the day, the run of show sits with the producer, and the on-site crew works from a group chat.
Who it is for
For a producer with several events at once and different vendors on each. A poor fit for a one-off private party with no vendors and no on-site crew.
Problems this page addresses
A vendor with no status
Three vendors for the same role. One is confirmed, one is backup, one never answered. On the sheet they all look "in progress".
The run of show is not with the crew
The producer knows when the ceremony starts. The crew on site hears it ten minutes prior, because the file was not updated after the family changed the time.
A double-booked date
Two events on the same night share a vendor or a crew member. The clash shows up when someone is already on the way.
What you get
An event card with vendors
Each role has a status: asked, quoted, confirmed, backup. Two vendors cannot both be confirmed for the same role without a note.
A run of show for the crew
The evening timeline, in Hebrew, available to whoever is on site. A family change updates that version, not a second file.
A date clash check
Before a vendor or a crew member is locked, you see whether they are already placed on another event that day.
Common questions
Does the run of show have to be in Hebrew?
Yes. The crew, the family, and the vendors read Hebrew on the night. An English file, or a foreign system’s labels, does not get read on site.
What if part of the crew is temporary staff?
The placement for the night sits on the event. Hiring, availability, and the agreement sit on the staffing page. Here you only see who is placed on this event.
Can an event stay open before every vendor is locked?
Yes. An event can be open with some roles still quoted. What matters is that you do not go on site with a role that has no owner.
Related pages
A CRM shaped around how you already work
An off-the-shelf CRM asks the team to adopt someone else’s stages and fields. We build the record around the approvals, statuses, and fields that already decide who the customer is and what happens next.
A mobile app on the same core as the web
The office works comfortably on a large screen, and the field stays on screenshots and group chats. We build the phone actions on the same server and the same permissions, not as an app with a database of its own.
Placement management for a staffing company
The client asks for people on a site, the candidate was approved by phone, and the hours arrive at week’s end on a sheet that does not match who actually showed up. The same person appears once as a candidate and again as a placement.