Built for when it actually happens

Ten years of crew, contracts and event days.

HR Cluster began in 2015 as an internal tool, built by a production manager for use on real productions. The first problem was practical: crew registration, onboarding and the admin that followed were eating time in spreadsheets, paperwork, after-shift reconciliations and payroll preparation. The tool existed to make that faster, simpler and more accurate. Nothing more was planned.

What started as a lightweight system for registering crew and logging hours grew into a complete workforce platform for high-tempo operations. It grew one problem at a time: contracts before the first shift, shifts across several projects, attendance at the gate. Each piece was added because a production needed it, and kept because it held up.

Over the years, HR Cluster has been proven in live environments such as Oktoberfest Oslo, Sommerbris, and other festivals and projects across Norway. In settings where large crews need to be hired, scheduled, checked in, and paid efficiently, the platform continued to evolve through real operational use.

Today HR Cluster is a product, and it is still used in live event operations. That is where the next problem tends to show up first.

Built from real operations.

That is still how HR Cluster is developed. New modules and improvements usually begin as a concrete problem in a live operation, not as a line on a roadmap. We solve it where it occurs in the workflow, use it in real operations, and refine it against what comes back from the field. The platform has been shaped through real productions and input from more than 50 people working across different parts of event operations, from site crews and rigging to stage and production management.

It is also why the platform covers what it covers. Live event operations do not split neatly into workforce and production. The same people, projects and timelines run through both, so HR Cluster connects them. Crew, the production plan, suppliers, deliveries, vehicles, accreditation and incidents sit in the same platform because the problems that produced them crossed that line: a delivery needs a vehicle, the vehicle needs a driver with access, and an incident at the gate involves the crew, the supplier and the zone at the same time. None of it came from a decision to build an all-in-one system. It came from problems that kept crossing the line.

Production Plan is the clearest example. It became one workflow because planning, checklists, supplier details and crew information kept describing the same event, and keeping them in separate documents was the problem. The same principle applies across workforce operations: recruitment, scheduling, accreditation and timekeeping are different stages involving the same people and projects.

This is why the platform can evolve quickly without drifting apart: every new piece is built around the same people, projects and operational data as the rest. The goal has never been to have the most modules, or to replace the specialist systems an event already runs. It is a simpler operation, with fewer spreadsheets, fewer disconnected systems and less manual coordination.

Built in Norway. Tested in the field. Designed for modern workforce operations.