Case studiesAV and live events

HYSS: crew scheduling, booking conflicts and payments

HYSS gives AV and live-events companies a connected workflow for staffing, scheduling and paying crew. Zain Raza led the build for Ego Eimi, developing the platform architecture and backend around the rules of each assignment.

Business
HYSS
Sector
AV and live events
Scope
Crew scheduling and payment workflows
Contributor
Zain Raza
Editorial illustration: black AV flight cases, a coiled cable and an orange crew pass
AI-generated editorial illustration of the project’s domain.

A crew booking carries more information than a calendar entry.

Availability arrived through messages and spreadsheets. A manager could make a booking without seeing another assignment, and a changed event date could invalidate a plan that had looked settled. Revised call sheets then had to reach the people working at the venue.

The same person might work as an employee on one job, a freelancer on another and an agency hire on a third. Rates, overtime and payment authority needed to follow the actual assignment rather than a fixed label on the worker profile.

Keep worker type, availability and payment authority on the assignment.

Zain placed the worker-source type on each assignment. That context determined rate handling, overtime, cost allocation and payment routing. Shared jobs retained separate employer invoice and payment authority.

The conflict engine checked availability before writing a booking and showed the impact of a proposed change before it committed. Recurring schedules expanded into individual occurrences. Shadow profiles allowed planning with unregistered crew while formal assignment required registration.

What the workflow includes

  • Check booking overlaps before saving an assignment.
  • Show the affected bookings and constraints before an edit commits.
  • Carry employee, freelancer or agency context with the assignment.
  • Separate payment authority and employer invoices on shared jobs.

Project details

The HYSS system architecture diagram showing the booking model, conflict engine and payment routing

Project materials showing the workflows and interfaces described in this case.

Product walkthrough

Crew scheduling and payment workflows. The delivery section explains the workflow demonstrated here.

One assignment model connects scheduling to payment.

The delivered platform connected employer and freelancer workflows across web, iOS and Android. An assignment could carry its worker context from availability and scheduling through rates and payment. Tests around pay and access boundaries supported the implementation of those rules.

What this means for the technology owner.

The business dependency is the assignment model across scheduling and payment. A new feature needs to respect the same rules as an existing booking. A technology owner should keep those rules, external integrations and test cases in the operating record so the system can evolve without depending on one developer’s memory.

Tech Team: ongoing technology responsibility →

Web appiOSAndroidGoogle CalendarQuickBooksStripe

Project contribution: Zain Raza. The scope described above identifies the work behind this case.

HYSS — project link

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Related case studies

Editorial illustration: an automotive key and orange dispatch tag on a dark road-shaped base
Vehicle buying and dispatch

Vehicle Lead & Dispatch

Messaging rescue and workflow extension

Read the case →
Editorial illustration: a three-rail task-card rack with one orange card
Work management software

TaskOPad

Application performance and scaling

Read the case →
All case studies46 projects

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.

Start a conversation More case studies