Skip to content
Solutions

Multi-event management: one crew register, one project per production

Tuesday. The spring festival's dugnad list is being built while a hall show loads in across town, and the person who ran the bar last weekend is being asked to drive on Thursday. Three productions, one organisation, one list of people who work for it. This page is about what one account shares between projects and what each project keeps to itself.

Who this is for

Organisations that run more than one production a year on the same crew and suppliers: a festival with a winter edition and a summer edition, a venue with a season of one-off shows, a promoter with several events in parallel, a municipality with several cultural events. The projects differ. The crew, the suppliers and the sites largely do not.

Shared once, at account level

The crew register

One record per person, whichever projects they work on. Profile, contact details, competence with expiry, allergies, clothing sizes and contract history stay with the person. Someone already active just takes the next shift, and someone suspended or removed comes back on the same record. A new contract is a manager's step, and the group's project coverage shows who has none for that project.

Groups

Teams, clubs, volunteer organisations and supplier crews, with a default worker type and an overtime policy. Groups belong to the account and work on every project; linking one to a project shows its contract coverage there. Each person is in one group at a time.

Shift roles

Bartender, runner, rigger, defined once and used on every project's schedule.

Suppliers

One register with Brønnøysund company data and documents that expire, so the same stage supplier is not registered three times.

Accreditation types

Defined on the account, issued per project.

Locations

The site structure in levels, with zones, gates and parking. A location is assigned to all projects or to selected ones, so the venue's house structure serves every show and a festival site serves only its own.

Per project

Shifts and hours

Shifts and sessions are tied to a project, so parallel events stay apart in one workspace.

Phases

Build, show days and take-down, or whatever the production calls them; passes, permits and the plan follow them.

Vehicle and accreditation records

Issued for one project, by phase or by date.

The production plan

One per project, with its departments, deliveries and suppliers on the tasks they deliver.

Incidents and risk assessments

Can be filed on the project and the location they concern.

Across projects

Overlaps checked across the whole account

Every assignment, signup, approval and import is checked for overlap across all projects on the account. A self-signup that would overlap is refused. A manager's assignment that would overlap is blocked. Rest below the account's minimum stops a self-signup; when a manager assigns directly, it gives a warning they can override.

One person, several projects

Crew pick from the open shifts their group can take, across all projects, and see one list of upcoming shifts.

One view or one project

The dashboard and the schedule statistics can show one project or all projects together. Payroll export covers all crew or the groups you choose; session exports exist per project and per group, as CSV and PDF.

A direct comparison between projects or seasons is not a report view today.

What you need

A Workforce plan for the crew side. Ops, as an optional paid add-on on the same account, for suppliers, deliveries, vehicles, accreditation and the production plan. Incidents is included in both.

See it on your own operation.

Tell us how your events run and we'll show the flow on your real crew size and calendar.