In Flooptimize, staff scheduling builds on the planning of your jobs, events, or assignments. That might be a festival, a catering job, or a match day. An event you create is the start of the operation you build on — and that has clear advantages over loose, standalone scheduling tools.
Everything that follows — days, sales points, shifts, the portal, hours — hangs off that one source: the event or job you schedule, brief, process hours for, and later pay out against.
Fields
Event days
What is an event (also called a job or an assignment)?
As above, an event is the instance that forms the basis of your schedule. It is the assignment your operation revolves around: a festival weekend, a catering job at a client site, a match day, a conference.
In the backoffice this is usually called an event. Depending on your industry, other terms such as “job” or “assignment” may sound more natural.
Event, event day, and sales points: what are these?
Layers that build on each other:
- Event / job — the whole assignment (for example “Lowlands”, “Jansen wedding”, “Ajax–Feyenoord”).
- Event day — one date within that event. An event can span multiple dates.
- Sales point — a place on the event where you schedule staff. You might also call it a zone or location. Examples: Bar A, a specific food truck, zone X.
- Shift — one planned deployment of one worker. A shift can be linked to different contexts.
Later in the product series we go deeper into the event overview and the event day. For now: without a clear event you do not know where shifts belong; without an event day you do not know when; without a shift you do not know who does what.
Examples for businesses in different industries
Food truck / event catering
- Festival weekend with two trucks on different days.
- Pop-up catering job at a company: one or two days, one or more sales points.
Staffing / flex for events
- Assignment for a client at an event venue: the job is the client assignment, not “week 32 in Excel”.
- Multiple zones or bars at one festival, under one event.
Sports / venue hospitality
- Match day or conference day as the event, with zones (gate, hospitality, bar) as places where shifts land.
What do you set at event level — and what later?
On the event you usually capture what applies to the whole assignment: name, period, overall location or context, and which days (event days) belong to it. Often you already attach sales points or zones here (more in the article on concepts and sales points — coming next).
On the day or at the place you fill in further: exact times, headcount per sales point, generating or adjusting shifts, briefing details that belong to that day or place.
You do not need to enter every detail perfectly in one go — you can always add and change information. For generating shifts, though, it matters that event days, their times, and sales points are entered correctly.
How does this fit the rest of Flooptimize?
- Here: event / job as the starting point
- Alongside: shift rules and generation, shift templates, functions and roles
- Next: the chain from job or event through to payout; later also concepts & sales points and event/day overviews
Want to see how this fits your operation? Book a demo.
Want to see this in your operations?
Book a short demo. We will check whether Flooptimize fits your events and crew.